Country dossier
Worldwide badge coverage for United States, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.
Seeded artifacts
Official announcement and archive-photo documented pre-electronic name tag
A DEF CON 1 pre-electronic name-tag and paper-badge artifact documented by the official 1993 announcement, the official DEF CON I archive page, and the official DEF CON media-server badge photo.
Official-photo documented pre-electronic chest credential
A DEF CON 2 physical access/identity credential documented by InfoconDB event metadata, the official DEF CON II archive page, and official DEF CON media-server event photos from the Sahara Hotel and Casino.
Official-photo documented pre-electronic waist credential
A DEF CON 3 physical access/identity credential documented by InfoconDB event metadata, the official DEF CON III archive page, and official DEF CON media-server event photos from the Tropicana Resort & Casino.
Official-photo documented pre-electronic chest credential
A DEF CON 4 physical access/identity credential documented by InfoconDB event metadata, the official DEF CON IV archive page, and official DEF CON media-server event photos from the Monte Carlo Resort and Casino.
Official-photo documented pre-electronic hanging credential
A DEF CON 5 physical access/identity credential documented by InfoconDB event metadata, the official DEF CON 5 archive page, and official DEF CON media-server event photos from the Aladdin Hotel & Casino.
Official-photo documented pre-electronic conference credential
A DEF CON 6 physical access/identity credential documented by InfoconDB event metadata, the official DEF CON 6 event page, and official DEF CON media-server photos from the Plaza Hotel & Casino.
Official-photo documented pre-electronic lanyard credential
A DEF CON 8 physical lanyard credential documented by InfoconDB event metadata, the official DEF CON 8 event page, and official DEF CON media-server event photos from Alexis Park.
Official-photo documented pre-electronic lanyard badge
A DEF CON 9 physical lanyard badge documented by InfoconDB event metadata and official DEF CON media-server event photos from the Alexis Park conference.
Pre-electronic physical badge with corner-hole lore
A DEF CON 10 physical badge artifact documented by InfoconDB event metadata, the official program's note about the badge form factor, and official DEF CON media-server badge images.
Official archive photographed pre-electronic identity badge
A DEF CON 11 human badge documented by InfoconDB event metadata, the official program PDF, and official DEF CON media-server photos explicitly filed as DEF CON 11 badge images.
Unofficial forum identity badge
A community DEF CON 12 forum badge documented by the official forum thread as a printable avatar/nickname template, intended as an extra badge for forum members rather than the official attendee credential.
Public-domain photographed pre-electronic identity badge
A DEF CON 13 human badge documented by a public-domain Wikimedia Commons original photo and an official pre-conference DEF CON forum note that the 2005 badges were ready before registration.
First official DEF CON electronic badge
A Joe Grand-designed skull-shaped PCB badge for DEF CON 14, built around active electronics, open hackable circuitry, two blue LEDs, one button, seven soldermask role variants, and an official badge-hacking contest.
95-LED scrolling-text badge with capacitive controls
A Joe Grand / Grand Idea Studio electronic badge for DEF CON 15, built around a Freescale MC9S08QG8, a 5-by-19 matrix of 95 LEDs, capacitive touch controls, customizable vertically scrolling text, persistence-of-vision behavior, and another official badge-hacking contest.
SD-card infrared file-transfer and TV-B-Gone badge
A DEF CON 16 electronic badge built as a hackable Freescale-based platform with SD-card storage, infrared file transfer, TV-B-Gone behavior, role-color variants, one-button state control, and published source, schematics, and development resources.
Sound-reactive RGB badge with MC56F8006 DSP
A Joe Grand / Grand Idea Studio electronic badge for DEF CON 17, built around a Freescale MC56F8006 16-bit digital signal controller, an amplified MEMS microphone, an RGB LED, wired multi-badge communication, and a static serial bootloader.
Electronic party-invitation badge with published docs and firmware
Ninja Networks' 2009 DEF CON party invitation was an electronic badge built for DEF CON 17, documented by a primary DEF CON forum post plus a technical archive with Creative Commons Attribution schematic/Gerber docs, public-domain badge code, and a BOM.
Lithographed aluminum e-paper-style badge
A DEF CON 18 electronic badge built as polished hackable jewelry: lithographed aluminum, a low-power 128x32 Kent Displays cholesteric display, USB connectivity, role variants, and published badge-making materials.
Titanium non-electronic puzzle badge
A Ryan Clarke / 1o57 DEF CON 19 badge that intentionally stepped away from electronics and used a waterjet-cut commercially pure titanium physical artifact as the event credential, puzzle surface, role marker, and social-interaction prompt.
2.4 GHz RF spectrum-analyzer badge
The ToorCon 13 badge was an open-source 2.4 GHz RF spectrum-analyzer badge from Great Scott Gadgets, with 13 LEDs representing the 13 Wi-Fi channels and public Project Ubertooth hardware and firmware archives under the `tc13badge` code name.
Propeller multicore IR puzzle and development badge
A Ryan Clarke-designed DEF CON 20 electronic badge manufactured by Parallax around the Propeller P8X32A multicore processor, infrared badge-to-badge communication, eight LEDs, USB programming, many physical variants, and a crypto/social badge challenge.
HackRVA MSP430 badge with Nokia LCD and source archive
The RVAsec 2012 badge is documented by HackRVA's public `rvasec-badge-2012` repository, which preserves Eagle board and schematic files, Gerbers, graphics, component datasheets, and release firmware for a badge built around an MSP430-class controller and Nokia 5110 / PCD8544 LCD behavior.
USB-controlled sub-1 GHz RF badge
The ToorCon 14 badge was an open-source sub-1 GHz wireless-transceiver badge from Great Scott Gadgets, controlled over USB from a computer and shipped with atlas's RfCat firmware plus CC Bootloader.
Non-electronic PCB playing-card puzzle badge
A Ryan Clarke-designed DEF CON 21 badge series built as poker-card printed circuit boards: non-powered identity artifacts whose copper, soldermask, silkscreen, inner-layer metal, role variants, and encoded face-card relationships formed a cryptographic and physical badge challenge.
HackRVA electronic badge with LEDs, IR, audio, and USB
The RVAsec 2013 badge was a HackRVA-built electronic conference badge documented by official RVAsec and HackRVA sources, with LEDs, infrared badge-to-badge play, a piezo speaker, USB support, and badge-game behavior tied to conference interaction.
HeatSync Labs solderable PCB badge
The CactusCon 2014 PCB badge is preserved through Eric / Robot Ambassador's first-hand writeup, which describes 300 event badges designed by Erik Wilson, given away at the HeatSync Labs booth, and assembled by attendees with LEDs, resistors, batteries, and acrylic hardware.
Propeller 1 infrared puzzle and contest badge
A Parallax-built official DEF CON badge for DEF CON 22, based on the Propeller 1, infrared transmit/receive hardware, touch-pad buttons, LEDs, full USB programming, exposed I/O, and thirteen attendee-role styles.
Issued physical badge for the tenth HOPE
The HOPE X Badge was the physical badge issued at the tenth Hackers On Planet Earth conference in New York City, preserved here through a real CC0 Wikimedia Commons attendee/uploader photograph of the event badge.
PIC32 badge with LCD, IR, capacitive sliders, and public firmware
The RVAs3c 2014 badge was a redesigned HackRVA electronic badge whose official preview and public firmware source document a PIC32-based platform with LCD, infrared, capacitive sliders, LEDs, speaker, micro USB, and game/application code.
Arduino-clone badge with FTDI header, blinky expansion board, and hidden challenges
The SAINTCON 2014 badge was an Arduino-compatible conference badge designed for attendee soldering and badge hacking, with FTDI programming, LED blinky behavior, a companion blinky expansion board, and hidden Hacker Challenge secrets documented in first-hand and Hackaday coverage.
ESP8266 Badger hacking board
The BSidesPDX 2015 Badger badge is a conservative source-backed badge-hacking board record tied to the official Electronic Taxidermy: Badger Hacking workshop and the public PDX Badgers 2015 PCB and firmware repositories.
Playable vinyl-record noir puzzle badge
A Ryan Clarke / 1o57-designed DEF CON 23 badge issued as an actual playable 7-inch vinyl record, with role-colored editions, printed mystery alphabets, inner-groove markings, lanyard ciphers, record audio, and a noir-themed badge challenge.
PSoC4 blinky badge and VoCore OpenWRT network badge
LayerOne 2015's badge effort produced two electronic badge designs documented by the official Hardware Hacking Village archive and CharlieX's Hackaday.io project: a battery-powered PSoC4, ESP8266, and WS2812B blinky badge plus a VoCore/RT5350F OpenWRT network badge with Wi-Fi and dual Ethernet intent.
Hand-built HackRVA PCB badge with IR, LCD, audio, and USB
The RV4sec 2015 badge is documented by HackRVA's official build post as a hand-built electronic badge with custom PCB assembly, surface-mount components, IR, audio, micro USB, LCD, and an optional reset-header development path.
Cisco CMX-linked attendee badge with LCD, buttons, schedule, and challenge score
The SAINTCON 2015 badge was a purpose-built Wi-Fi enabled attendee show badge described by Cisco as a conference-scale experiment: roughly 550 participants carried LCD-and-button badges that used Wi-Fi location data for zone awareness, schedule lookup, and live Hacker Challenge score display.
Unofficial DEF CON 24 STM32 and RFM69 badgelife badge
The AND!XOR DC24 Bender Badge was an unofficial DEF CON 24 badgelife badge with a Bender-shaped PCB, STM32F103 controller, OLED screen, RGB LEDs, RFM69W 433 MHz radio, USB serial terminal behavior, games, GPIO breakouts, and a public post-event hardware/software archive.
ATTiny85 capacitive LED PCB badge
The BSidesPDX 2016 badge is a source-backed Portland Security BSides PCB badge record tied to Calagator's event listing, official BSidesPDX 2016 schedule and speaker pages, and the public PDX Badgers ATTiny85 Eagle board, schematic, BOM, and Arduino firmware archive.
555-timer light-reactive soldering badge kit
CarolinaCon 12 included an easy-to-assemble electronic kit badge in the price of admission, with a 555 timer, LED, photoresistor, resistors, capacitor, AAA battery holder, wire, protoboard space, and Hardware Hacking Village support.
Electronic skull badge with Konami and serial puzzle paths
A Ryan Clarke / 1o57 DEF CON 24 electronic skull badge with a mini processor, buttons, LED eyes, printed codes, hidden-trace/silkscreen text, serial strings, lanyard data, conference-media files, and a badge challenge that used the Konami Code as an early visible hook.
PIC18 LED-matrix badge with IR and accelerometer
The 2016 Hackaday Superconference badge, also documented as the Supercon II badge, was a Voja Antonic-designed open hardware badge with a red 8x16 LED matrix, PIC18LF25K50/PIC18F25K50-class MCU, integral LIS3 accelerometer, infrared communication, USB bootloader, five tactile controls, and expansion pads.
PSoC4 and ESP8266 badge with 20 WS2812B LEDs
LayerOne 2016's electronic conference badge returned to the PSoC4, ESP8266, and WS2812B platform as a single LED badge with Wi-Fi working before the event, a mini prototyping area, exposed rails and I/O, and public build logs from CharlieX.
Hand-built badge with USB reflashing and CTF challenge hooks
The RVA5sec 2016 badge is documented by HackRVA's official interview as a hand-built custom-firmware electronic badge with reused/improved hardware, standard USB reflashing, low-frequency serial-transmission experimentation, and CTF challenge hooks.
D1 Mini ESP8266 badge kit with MAX7219 LED display and Hackers Challenge registration
The SAINTCON 2016 badge was an electronic kit badge built around a D1 Mini ESP8266 development board, MAX7219 LED driver, and two 4-digit LED modules, with public assembly, flashing, and Hackers Challenge registration documentation.
Unofficial DEF CON 25 nRF52 BLE badge with BOTNET game
The AND!XOR DC25 Badge was an unofficial DEF CON 25 badgelife board built around a Rigado BMD-300 / Nordic nRF52 module, color TFT, WS2812B LEDs, sensors, microSD, BLE smartphone integration, TCLish scripting, BYOB bling, CHIP8/SCHIP games, and a badge-to-badge BOTNET game.
Nordic BLE badge and Ox-Vox add-on target
The BSidesPDX 2017 badge is a source-backed Portland Security BSides badge archive tied to the official schedule's badge context, Rob Rehrig's Ox-Vox add-on talk, and the public PDX Badgers Eagle board, schematic, and BOM repository for a BMD-300/OLED/CR2032 design.
Soldered WemOS scanner badge
The CactusCon 2017 badge is preserved through a first-hand attendee writeup that describes paying for the badge package, soldering and troubleshooting the board at the Phoenix-area event, and using it as a tiny Wi-Fi and Bluetooth scanner.
TYMKRS cubic mesh-network puzzle badge
The CypherCon 2.0 Cube was a three-dimensional electronic badge by TYMKRS, assembled from cube-edge PCBs with LEDs, microprocessors, buses, USB, battery charging, mesh-network behavior, text-adventure firmware, and a badge-to-badge programming premise.
nRF52832 BLE OLED wagon-game badge
The DC503 Wagon Party badge is a source-backed party badge documented by the no-visible-license `pdxbadgers/wagonparty` repository, whose README calls the target a badge and whose firmware advertises a `503WAGON` BLE device with OLED game modes.
Rubber identity badge in a badgelife breakout year
A DEF CON 25 official admission badge recorded in DEF CON feedback as a rubber or plastic identity badge, not an electronic puzzle board, paired historically with an unusually large wave of unofficial DEF CON 25 hardware badges and badge-maker coordination.
Special lifetime-access electronic award badge
The DerbyCon 7.0 Legacy Black Badge was a special electronic black-badge award artifact made for DerbyCon 2017, using an Atmel XMEGA core, a large LED-heavy PCB, laser-cut acrylic, custom STL work, and first-hand published build notes.
PIC32 camera badge with OLED and MicroSD
The 2017 Hackaday Superconference badge was an official Mike Harrison camera badge with a PIC32MX170F256D, OV9650 camera module, 128x128 color OLED, MicroSD storage, accelerometer, buttons, bootloader, white LED illuminator, prototyping area, and expansion header.
STM32F4 badge for CAN bus and vehicle-hacking experiments
LayerOne 2017's electronic badge was a CAN-bus-focused STM32F4 conference badge with a TFT display, storage, USB device and host behavior, external CAN headers, audio output, rechargeable battery planning, PC-side CAN tooling, and J2534-adjacent software work.
First Recon Village spy-silhouette badge
Recon Village's first Badge Life entry was The Original, a DEF CON 25 electronic badge with the village's spy-silhouette design, die-cut shape, hardwear.io lanyard, and foundation-of-tradition framing.
HackRVA badge artifact with badge-intro and CTF-room context
The RVAsec 2017 badge record is intentionally conservative: official RVAsec sources place HackRVA badge distribution in the 2017 layout and sponsor trail, and InfoconDB preserves a Badge Intro item, but this pass did not recover final component, firmware, schematic, or complete attendee-guide evidence.
Raspberry Pi Zero W badge with TFT, SNES-style buttons, MiniBadges, and Hacker Challenge registration
The SAINTCON 2017 badge was an electronic conference badge built around a Raspberry Pi Zero W and a custom SAINTCON board with a 2.8-inch TFT display, SNES-style buttons, battery power, MiniBadge expansion, Hacker Challenge registration, and a post-conference RetroPie conversion path.
ATmega32u4 tesserHack maze badge
The THOTCON 0x8 badge was a Chicago electronic conference badge built around an ATmega32u4, four RGB NeoPixel LEDs, three potentiometers, micro USB, two CR2032 coin-cell holders, and tesserHack stock firmware for an 8x8x8 maze game.
Unofficial DEF CON 26 ESP32-WROVER Wild West of IoT badge
The AND!XOR DC26 Badge was an unofficial DEF CON 26 badgelife board themed as the Wild West of IoT, built around an ESP32-WROVER module with WiFi/Bluetooth, a color LCD, microSD, IS31FL3736-driven RGB lighting, CP2102N USB serial, LULZCODE scripting, the B.E.N.D.E.R. console challenge, and badge-to-badge networking ambitions.
Attendee kit badge by Jonathan Singer
The BSides Orlando 2018 badge is preserved as a simple discrete marquee badge given to attendees as a kit, documented by Jonathan Singer's Hackaday.io project record and anchored to the official Security B-Sides Orlando 2018 event site.
Tampa Bay BSides badge/lanyard artifact with electronic assembly context
BSides Tampa 2018 is represented here by a visible event badge/lanyard artifact in a CC BY-SA documentary photo, paired with an attendee report that says more than 750 attendees participated in Electronic Badge Assembly among the event activities.
ATTiny861 LED and SAO badge archive
The BSidesPDX 2018 badge is a source-backed Portland Security BSides badge archive tied to the official BSidesPDX 101 badge panel and the public PDX Badgers KiCad, BOM, LED mapping, and ATTiny861 firmware archive.
Ticketed paid-badge registration artifact
CactusCon 2018 is seeded as a conservative paid-badge record because contemporaneous Arizona LoCo Team meeting notes say the September 28-29 Mesa Convention Center event required tickets, offered free admission, and let attendees pay to get a badge.
Bluetooth LE wrist party badge
The DC503 DEF CON 26 VIP Banglet is a source-backed wrist-worn party badge documented by the Apache-2.0 `pdxbadgers/2018-banglet` repository and by BSidesPDX 2018's public Making of the Banglet talk listing.
Tymkrs electronic text-adventure badge
A Tymkrs / Toymakers official DEF CON 26 electronic badge with a PIC32MM0256GPM controller, reverse-mounted LEDs, capacitive controls, four-AA battery stack, USB serial interface, badge-to-badge connector, add-on header, and a retro text-adventure badge challenge.
BASIC and CP/M handheld computer badge
The 2018 Hackaday Superconference badge was a battery-powered handheld retrocomputer with a 320x240 color display, mini QWERTY keyboard, speaker, flash storage, expansion header, BASIC interpreter, and Z80 CP/M emulator.
ESP32-WROOM-32 audio badge with Alexa experiment path
LayerOne 2018's electronic badge was an ESP32-WROOM-32-based audio and network badge documented by the official HHV archive, Hackaday's event report, the linked CharlieX ESP32_Alexa repository, and mmca's public hardware notes.
Spy and skull Recon Village badge variants
Recon Village's DEF CON 26 badge entry, The Dual Design, used two official visual variants: a classic spy silhouette and a detailed skull design in a black-and-white aesthetic.
HackRVA electronic badge with games, puzzles, and two-channel audio
HackRVA's 2018 recap and badge wiki document more than 300 RVAsec electronic hardware badges with badge games, puzzles, two-channel audio behavior, challenge content, and badge-hacking competition context.
ESP32 MicroPython badge with 8x32 LED matrix and twelve minibadge spots
The SAINTCON 2018 ESP32 Badge was an electronic conference badge built around a LOLIN D32 / ESP32 module running MicroPython, an 8x32 LED matrix, three buttons, a rechargeable battery, Wi-Fi configuration behavior, Hacker Challenge score display, and twelve minibadge spots.
Battery-powered WiFi signal-strength badge
The ShmooCon XIV badge is preserved here as a battery-powered WiFi signal-strength meter from the 2018 Washington, DC conference, with corroborating public notes for an ESP8266 core, serially addressable LEDs, and an injection-molded rocket enclosure.
MSP430 electronic jar-of-fireflies camp badge
ToorCamp 2018's badge is preserved as a Great Scott Gadgets and OSH Park sponsored electronic jar of fireflies: a soldering-station badge kit built around an MSP430G2211, six green through-hole LEDs, CR2032 power, and open design/firmware files.
SMD Challenge and 8-bit art badge
The ToorCon San Diego 20 badge is preserved here as a 400-kit official-badge request that folded MakersBox's SMD Challenge into a larger 8-bit-art conference badge with hidden codes, eight SMD LEDs, and an ATtiny84.
Unofficial DEF CON 27 nRF52840 hardware-hacking badge
The AND!XOR DC27 Badge was an unofficial DEF CON 27 badgelife board built around a Rigado BMD-340 / Nordic nRF52840 core with an IS31FL3741 LED matrix, light pipes, glow-in-the-dark capacitive touch, USB-C, FT2232H hardware-hacking bridge, SWD/Tag-Connect programming paths, SAO 1.69bis support, BOTNET mesh behavior, and B.E.N.D.E.R. v2.0 challenges.
Capacity-managed admission badge for BSidesLV
BSides Las Vegas 2019 is represented here by its official participant/admission badge system: badges were required for entry, walk-in badges were no longer available, and attendees secured badges through room-block, donor, sponsor, volunteer, speaker, student, local, or related conference paths.
ESP8266 Badge Pirates badge with Wi-Fi beacon game
The BSidesKC 2019 conference badge was a Badge Pirates ESP8266 badge with Wi-Fi behavior, reverse-mount LEDs, participant/speaker/organizer/volunteer/sponsor/pirate variants, a related Jr Hacker badge, and a rights-cleared repository photo served locally as optimized WebP.
ATtiny85 LED badge archive
The BSidesPDX 2019 Multnomah badge is a source-backed Portland Security BSides badge archive tied to the official schedule's badges-and-contests context and the public PDX Badgers KiCad, BOM, and firmware repository.
Reprogrammable ATTINY85 badge with dual SAO ports
The BSidesROC 2019 badge is preserved through the official event archive and badge page, which describe a fully working reprogrammable electronic badge, about 200 assembled units, PCB fallback for attendees without the assembled option, and a best-hacked-badge contest.
Printed or electronic ticket-type conference badge
CactusCon 8 is seeded as a conservative ticket-type badge record because official registration pages for the December 2019 Mesa event say CactusCon attendees received either a printed badge or an electronic badge depending on ticket type.
SMART Response XE RF party pager
The 5ohBEE is a source-backed 2019 503 Party pager and game artifact documented by the Apache-2.0 `pdxbadgers/5ohBEE-2019` repository as a SMART Response XE-based pager project.
Crystal NFMI badge-game platform
A Grand Idea Studio DEF CON 27 badge built around NXP hardware with a KL27 ARM Cortex-M0+ controller, NFMI communication, quartz or crystal face details, role-specific badge identity, public firmware and schematics, and a conference-wide interaction game.
ECP5 RISC-V badge in a Game Boy form factor
The 2019 Hackaday Superconference badge put a Lattice ECP5 FPGA, RISC-V soft-core SoC, color LCD, eight buttons, cartridge slot, HDMI, SAO headers, PMOD footprint, and mass-storage app workflow into a Game Boy-like handheld.
ATtiny85 and APA102 blinky CTF badge
Kernelcon's 2019 K-shaped badge was an electronic badge controlled by an ATtiny85, powered by three CR2032 cells, and fitted with five APA102 addressable RGB LEDs plus a button-driven mode system and CTF clues.
ATtiny2313 Blade Runner badge with ESP32CAM add-on path
LayerOne 2019's electronic badge used a Blade Runner / Voight-Kampff theme around a small ATtiny2313 LED-and-button badge, with Hackaday documenting optional add-on boards including an ESP32CAM eye/face-recognition module for the badge's test-of-humanity behavior.
Membrane-keyboard ARG badge
The Queercon 16 Q Badge was an electronic DEF CON-adjacent social badge with a custom membrane keyboard, 2.9-inch e-paper display, RGB lighting, Bluetooth-capable TI CC2640R2 controller, Holtek LED driver, AA battery power, RJ12 6P6C badge-to-badge connector, and ARG mechanics across Q, C, and Handler badge roles.
Steampunk Recon LED-eye badge
Recon Village's DEF CON 27 badge entry, The Skull Badge, was a steampunk-recon skull-shaped PCB design with mechanical artwork, LED eye illumination, and a CREW staff variant.
Arduino-compatible badge with games, base-station laser tag, and C interpreter
HackRVA's RVAsec 8 badge post documents the 2019 conference badge as a custom Arduino-compatible layout with games, Badge Monsters, Maze, base-station Laser Tag, a scoreboard plan, and a public Dustin Firebaugh C-interpreter repository.
STM32 and iCE40 Enigma-machine badge with linked-ring challenge
The SAINTCON 2019 Enigma Badge was a two-board electronic conference badge shaped as a segment of an Enigma rotor, combining a curved RGB LED matrix, lampboard LEDs, 26 buttons, plugboard wiring, minibadge-holder support, and badge-to-badge connectors for a cooperative ring challenge.
DePaul IRL ESP32 badge with capacitive pads, LEDs, speaker, and microphone
The THOTCON 0xA / Infinity badge was a Chicago electronic conference badge produced with DePaul's Idea Realization Lab for the May 3-4, 2019 event. DePaul Newsline reported a six-month, 1,700-unit custom circuit-board badge build; the public Poplicola repository documents a SparkFun ESP32 Thing Dev base, five capacitive touch pads, six LEDs, speaker output, microphone input, stock-firmware restore commands, and Arduino examples.
ATtiny841 soldering badge with colored and RGB LEDs
The WOPR Summit 0x00 badge was an attendee-assembled electronic badge for the inaugural Atlantic City conference. Hackaday documents a WarGames/WOPR-inspired board with a dozen colored LEDs, eight RGB LEDs, through-hole LEDs and resistors, battery holders, and an ATtiny841 controller, while Russell Handorf's build guide preserves the soldering and staff-flashing workflow.
Unofficial DEF CON 28 STM32F412 badge with BlackBerry keyboard CTF
The AND!XOR DC28 Badge was an unofficial DEF CON 28 Safe Mode badgelife board shipped through pandemic-era proxy drops, with an STM32F412RET6 MCU, 0.96 inch OLED, ST7735 128x160 TFT, APA-102C LEDs, BlackBerry Q10 keyboard, USB-C, Keystone 1020 battery holder, MyBASIC hardware scripting, and an embedded BENDERPISS CTF text adventure.
Talking LED presenter wearable
A source-backed BSidesPDX 2020 presenter wearable artifact documented by the public PDX Badgers `2020-mask` repository, built as a voice-reactive LED face-mask project for the all-digital conference year rather than a conventional attendee badge.
Cassette-tape puzzle badge
A LosT / 1o57-designed DEF CON 28 Safe Mode support badge built as an audio cassette in a jewel case, with puzzle material spread across the A/B tape audio, lanyard characters, printed liner notes, media-server contents, and DEF CON forum solving space.
Community KiCad/OSH Park badge template for the virtual event
Thomas Flummer's 2020 Remoticon badge was an unofficial CC BY-SA 4.0 KiCad PCB template released for the virtual Hackaday Remoticon, combining decorative Remoticon artwork, prototyping area, a MakersBox SMD challenge circuit, Feather-mounting pads, Gerbers, and an OSH Park shared-project path.
ATmega328P dual-PCB image-reel badge
The Kernelcon 2020 Hack-Master badge was a dual-PCB electronic badge with an ATmega328P-AU, three-AAA power, nine APA102 RGB LEDs, a backlit custom image reel, serial-port game plans, EEPROM mode storage, and ICSP pogo-pin programming.
Pandemic-era HackRVA firmware archive with LCD, IR, audio, USB, and apps
The RVAsec 2020 badge is seeded from HackRVA's public firmware repository. The source tree documents a real badge software target with LCD display code, buttons, IR packet handling, menus, badge apps, audio/image asset playback, LED control, USB bootloader tooling, and a small C-like interpreter.
Virtual-edition shipped badge package with MiniBadge and Hackers Challenge context
SAINTCON 2020 is represented here by its virtual-edition shipped badge package. The official archive identifies 2020 as a virtual SAINTCON year, InfoconDB supplies the October 27-30 dates, and first-hand DC540 coverage documents a physical badge package with the badge itself, an included MiniBadge, a coupon for a custom MiniBadge, and Hackers Challenge CTF badge context.
Arduino Nano breadboard badge for the virtual Badge Village
The Diana Initiative 2020 off-the-shelf virtual badge was a self-built Arduino Nano and breadboard-badge workshop artifact for the online conference. Sched documents the August 22, 2020 `Basic Arduino coding using virtual Badge` Village Workshop, while TechGirlMN's archive preserves the Tinkercad virtual badge, hardware BOM, wiring notes, and Arduino Create firmware examples.
Merch-bundle electronic badge kit for the online con
CarolinaCon Online 2021 offered a merch bundle with a CarolinaCon Online T-shirt, sticker, and a kit containing all parts needed to make that year's badge; after orders closed, the organizers began bulk-ordering shirts and badge supplies for shipment.
RP2040 New Normal macro-pad badge
An MK Factor official DEF CON 29 electronic badge built around Raspberry Pi's RP2040, a 1.8-inch LCD, six-button D-pad surface, SAO connectors, USB-C, speaker, coin-cell plus USB power behavior, UF2 firmware updates, HID macro-pad mode, and a New Normal challenge path.
KiCad badge canvas with MicroMod carrier variant
Thomas Flummer's Remoticon.2 badge project published a KiCad badge canvas for the 2021 virtual Remoticon, giving builders a Remoticon.2-shaped PCB with open prototyping space plus uploaded KiCad, artwork, Gerber, and MicroMod carrier-board files.
Hack Live customizable hotkey badge
Kernelcon 2021's Hacker HotKey was a customizable hotkey stream-deck badge configured for Hack Live voting, challenge sabotage, hint, and website-launch behavior, with public Arduino Leonardo firmware examples.
Source-limited Badge Intro artifact in the continuing HackRVA electronic-badge lineage
The RVAsec 2021 badge record is intentionally narrow: InfoconDB preserves a Badge Intro session at the November 4-5, 2021 Omni Richmond event, and HackRVA's current badge page describes an annual electronic badge lineage with schedules, games, surprises, sponsorship, and limited badge availability.
Official and unofficial MiniBadges documented by the archived 2021 SAINTCON page
SAINTCON 2021 is represented here by its archived MiniBadge collection page, which documents in-person registration/status MiniBadges, community and challenge MiniBadges, soldering and puzzle badges, sponsor or booth-distributed badges, and a separate unofficial badge section.
ESP32 retro-controller badge with LEDs, buzzer, accelerometer, and Wi-Fi
The THOTCON 0xB badge was a rescheduled-2021 Chicago electronic conference badge in a retro controller / circus-ticket form factor. Rob Rehrig's first-hand writeup documents an ESP32 main controller, reverse-mount RGB and single-color LEDs driven by an IS32FL3731 LED driver, capacitive touch buttons, piezo buzzer, accelerometer, 2.4 GHz Wi-Fi node behavior, IRC remote connectivity, and serial interface.
Arduino-programmable rubber-ducky badge
The BSidesSF 2022 Hardware Village badge is a source-backed pre-assembled badge distributed in limited quantities to village participants for Arduino-programmable rubber-ducky experiments.
Pre-order merch-bundle Conference PCB Badge
CarolinaCon Online 2's official pages advertised a merch bundle containing a CarolinaCon T-shirt, shot glass, sticker, and Conference PCB Badge, with pre-orders closing on the last day of the April 29-May 1, 2022 online conference.
MK Factor musical keyboard badge
An MK Factor official DEF CON 30 musical badge with Raspberry Pi Pico/RP2040-class hardware, a playable keyboard, display, speaker, audio input/output behavior, boot-mode and mass-storage update paths, and a music-and-pop-culture badge challenge spread across nine badge variants.
Front-panel 4-bit computer badge with 272 LEDs
The 2022 Hackaday Supercon 6 badge, also documented as Voja4, was a front-panel-style 4-bit computer badge designed by Voja Antonic and implemented on a PIC24FJ256GA704 with 272 LEDs, direct button programming, serial save/load, internal flash storage, SAO serial expansion, and a public assembler/emulator/tooling archive.
ESP8266 watch-badge firmware archive
Kernelcon's 2022 Watch Badge is preserved through its public firmware repository, which documents the kernelcon_watch_v4 firmware, generic ESP8266 core targeting, Arduino IDE build path, hard-coded Wi-Fi configuration, and deauther-software lineage.
Circular global-surveillance badge
Recon Village's DEF CON 30 badge entry, The Radar Badge, was a circular radar-themed badge with a world-map overlay, teal and emerald styling, compass markings, and coordinate markings.
Pico-era firmware with LCD, IR, D-pad, rotary encoder, and simulator
HackRVA's public RVAsec 2022 repository documents badge firmware for hardware and simulator targets, with RP2040/Pico SDK build flow, LCD display, three-color LED, D-pad, IR transmit/receive, rotary encoder, UF2 flashing, CLI startup path, and app/game framework.
Official, sponsor, community, and personal MiniBadge assembly-guide set
The SAINTCON 2022 MiniBadge Assembly Guide preserves a broad MiniBadge ecosystem: official community and status badges, sponsor badges, personal/trading badges, acquisition notes, rarity/difficulty labels, and assembly instructions for through-hole, SMD, RFID, motorized, and programmed badge variants.
OlyMEGA light-sensing LED spider badge
ToorCamp 2022's badge is documented by an official badge-talk session and assembly PDF as an OlyMEGA-built soldering badge: four LEDs forming spider eyes, a photocell, potentiometer, MOSFET, slide switch, resistors, and a battery holder whose circuit lights the eyes in darkness.
Documented conference-badge-to-Wi-Fi-analyzer soldering activity
A public BSides Greenville 2023 event listing says the Circuit Board Medics Soldering Village would help participants solder and transform a conference badge. A contemporaneous BSidesGVL announcement says the conference badges could become Wi-Fi analyzers and identifies Circuit Board Medics as the team that designed the badges. A public attendee report after the event says that its author made a Wi-Fi analyzer at BSidesGVL. Together, these sources establish a real event-linked badge-conversion activity without identifying the original board or the resulting analyzer's components.
Badge Pirates ESP32-S2 home-automation badge
The CactusCon 11 badge was an ESP32-S2 WROOM electronic conference badge by Badge Pirates and the CactusCon team, built around the event's Nightmare House theme, IoT interaction, LEDs, buttons, optional OLED support, GPIO expansion, and USB serial access.
Mar Williams physical badge with SAO chamber
A Mar Williams / spuxo official DEF CON 31 physical badge produced for a deliberately non-electronic year, with the public pre-con badge news centered on a customization-friendly SAO slot and media-server add-on design assets.
RP2040 analog vectorscope and waveform badge
An analog-inspired Hackaday Supercon badge that combined a fake-phosphor vectorscope display, programmable waveform generator, AK4619 ADC/DAC path, Raspberry Pi Pico/RP2040 control, MicroPython, joystick and buttons, and a through-hole prototyping area.
Analog TA7642 AM radio badge
Kernelcon's 2023 1337 kHz badge was an old-school analog AM radio badge based on the TA7642 radio IC, a 1.5 V design, small transistor amplifier, headphone output, RF gain knob, and hacker-playground prototyping area.
PIC16F1455 USB keyboard badge with addressable LEDs
LayerOne 2023's electronic badge was a PIC16F1455 USB HID and keyboard badge with WS2812B/SK6812-style addressable LEDs, DFU update workflow, writable flash-backed macro behavior, and a badge-competition path around a partial RubberDucky 2.0 script interpreter.
Classic spy badge with speaker variant
Recon Village's DEF CON 31 badge entry, The Spy Silhouette, returned to the fedora silhouette with die-cut shape, LED illumination, a speaker-badge variant, and custom Recon Village lanyard.
HackRVA electronic badge with UF2 flashing, audio output, IR, and games
The RVAsec 2023 badge is backed by official RVAsec package language for limited HackRVA electronic badges and HackRVA's public firmware repository. The repository documents LCD display, three-color LED, D-pad, IR Tx/Rx, rotary encoder, audio output, micro-USB UF2 flashing, SDL simulator support, and a broad app/game tree.
Community, event, contest, and personal MiniBadges documented by the 2023 data export
SAINTCON 2023 is represented here by its public MiniBadge ecosystem: the official 2023 FAQ documents MiniBadge popularity and attendee trading, while the community MiniBadge Wiki export preserves year-specific personal, event, community, and contest badge records.
DEF CON 31 youth-challenge ATtiny1614 LED badge
The Flux Decoder was a Social Engineering Community Youth Challenge badge for DEF CON 31, preserved through a public repository with KiCad board files, schematic material, and Arduino-style firmware for an ATtiny1614-powered flux-capacitor LED badge.
Contra-themed laser-tag badge with custom clear-PC housing
The THOTCON 0xC badge was a Chicago electronic conference badge built around a Contra-inspired, conference-wide laser-tag game and a custom injection-molded clear polycarbonate housing. Rob Rehrig's first-hand writeup documents the badge theme, enclosure work, IR receiver/emitter layout, TIR lens work, Xometry manufacturing path, and roughly 2,000-badge production scale.
First AvengerCon electronic scavenger-hunt badge
The AvengerCon VIII 8-8-8 badge was the conference's first electronic badge, documented by U.S. Army public-affairs coverage as a scavenger-hunt badge where attendees collected codes to light LEDs or hacked the badge to bypass the contest.
ESP32-C3 BLE rock-paper-scissors conference badge
Somerset Recon's post-event source archive says 400 badges were distributed at BSides San Diego 2024. It documents a custom ESP32-C3 conference board with a Bluetooth LE rock-paper-scissors game, high-level Wargames-themed UART and SAO CTF context, and KiCad, Gerber, BOM, and Arduino-style source material. The README also distinguishes the conference units' earlier firmware from later archived source behavior.
CircuitPython IR trading badge
The BSidesPDX 2024 badge is a source-backed OpenTaxus badge customized for Portland's Security BSides event, documented by the official Badge Talk page and the PDX Badgers public repository with RP2040-class hardware, OLED display, five-way d-pad, infrared trading, NeoPixels, AA or USB-C power, CircuitPython, and event-game code.
Specially designed HCV badge CTF artifact
The BSidesSF 2024 Hardware Challenge Village badge is a source-backed village badge used for electronics tinkering and a competitive badge CTF contest at City View at Metreon, with attendee-report evidence for a screen, joystick, battery or USB-C power, and badge-to-badge clue exchange.
Project NeoRogue ESP32-S3 badge archive
The CactusCon 12 badge is preserved through Badge Pirates' public CactusCon-12 repository, which includes KiCad CAD files, Gerbers, BOM exports, QA code, art assets, reference documents, and ProjectNeoRogue front/back raster outputs for the 2024 CactusCon badge.
RP2040 CAN-bus badge with CHV SAO ecosystem
Car Hacking Village's DEF CON 32 badge ecosystem centered on a main RP2040 badge with CAN-network surfaces, four CHV SAO connectors, public board and firmware repositories, public CTF challenge notes, and IOActive's separately documented key-fob badge / SAO build.
Independent three-board LED badge with a later DEF CON 33 vendor-list trail
redactd's Tindie listing introduces Dante's Inferno as an electronic badge just in time for DefCon 32, inspired by the Dante's Inferno Room. It describes three connected circuit boards, special two-color solder mask on the top two boards, sixty LEDs, an included CR123A battery, a populated SAO v1.69bis port, custom-printed box, laser-cut foam insert, and lanyard. The same maker's public repository documents a USB/UF2 firmware-update procedure and a July 2024 v1.1 release for pre-sale 1.0/1.01 units. A Hacker Couture DEFCON 33 product list later repeats the $100 product and core three-board, sixty-LED, CR123A, and SAO claims. Together, these sources establish one source-backed independent 2024 DEF CON 32 artifact with a later 2025 vendor-list recurrence, not an official DEF CON credential, a second DC33 badge, confirmed distribution at either event, a complete electrical design, a licensed source-code archive, or reusable-image rights.
RP2350 handheld-game badge
An official DEF CON 32 electronic badge built around Raspberry Pi RP2350 silicon, a handheld-game-style interface, LEDs, firmware archives, and a DEF CON 32 badge game whose GB Studio project files were published after the event.
Unofficial ESP8266 proximity-animation badge
BadgeBuddy was an unofficial GrrCON 2024 electronic badge built for roughly thirty friends, using an ESP8266 WiFi module, an 8x8 LED matrix, battery power, proximity scanning for other BadgeBuddy SSIDs, and a public code/wiring archive.
Six-port Pico W SAO hub
The Supercon 8 official badge used a Raspberry Pi Pico W and six SAO ports as an I2C playground, bundling touchwheel, LED petal matrix, blank protoboard, and CH32V003 I2C proto-petal add-ons with MicroPython examples.
Unofficial ESP32-C3 handheld-style DEF CON 32 badge
The Hackbat Badge is an unofficial DEF CON 32 badgelife board documented by the Hackbat project page and GPL-3.0 GitHub repository, with ESP32-C3 Wi-Fi/BLE, OLED display, WS2812 LEDs, six buttons, AA-cell case support, and production files.
ESP32-C3 badge with Badge Clinic and MicroPython workflow
The HOPE XV Electronic Badge was issued to in-person attendees as an ESP32-C3 badge with purple attendee boards, black pro boards, case variants, 16 WS2812-class RGB LEDs, buttons, IR blast behavior, vibration feedback, open hardware files, and MicroPython hacking notes.
Hayes SmartModem-inspired Wi-Fi modem badge
The JawnCon 0x1 modem badge was a wearable miniature Hayes SmartModem homage for the October 2024 Philadelphia-area hacker con. JawnCon's official write-up says it used RetroWiFiModem to simulate the AT command set and drive the LEDs, with a PCB carrying an ESP radio, level shifter, and vintage red LED front; Hackaday covered it as an ESP8266-powered Wi-Fi modem badge for early-Internet services.
Analog 555 and 4017 LAN cable tester
Kernelcon's 2024 [a]nalyze [i]nternet badge was an analog LAN cable-tester badge built without a microcontroller, using a 555 timer, 4017 decade counter, RJ45 path, diode network, head LEDs, and a detachable remote.
ATTiny4313 POV fidget-spinner badge
The LayerOne 2024 POV Spinner Badge was an electronic fidget-spinner conference badge that displayed words and patterns through a 12-LED persistence-of-vision strip while spinning.
Multi-layer tactical recon badge
Recon Village's DEF CON 32 badge entry, The Recon Soldier, was a tactical-recon multi-layer PCB badge with red and blue LED eyes, 3D assembled design, and military helmet artwork.
Retrospectively documented independent ESP32-S3 electronic badge
Retia, LLC's public repository is currently named `DefconBadge2026`, but its immutable first source-release commit calls the project `DEF CON badge (2024)` and its README is titled `DEF CON Badge (2024) — ESP32-S3`. That source snapshot includes KiCad and fabrication material named `2024_def_con_badge_v1`, a badge photograph, and high-level hardware documentation. The official DEF CON archive identifies the 2024 event as DEF CON 32, so the record is attached to that existing edition as a retrospectively documented independent artifact; neither Retia nor DEF CON source reviewed here calls it an official Human badge, an attendee entitlement, or a confirmed event handoff.
HackRVA firmware and emulator badge with IR, audio, games, and badge-hacking context
The RVAsec 2024 badge record combines official RVAsec package/layout evidence for limited HackRVA electronic badges and badge-hacking context with HackRVA's public firmware and emulator repository. The source tree documents LCD, three-color LED, D-pad, IR, rotary encoder, audio output, SDL simulator, and expanded games/apps.
Official and submitted MiniBadges documented by the 2024 trading build-guide trail
SAINTCON's 2024 MiniBadge Trading page documents an official trading area and a public build-guide link covering submitted MiniBadges that attendees designed and brought to the conference, including official MiniBadges.
Camp identity, Shadybucks payment, and Euphoria CTF artifact
ToorCamp 2024's source-backed badge artifact is modeled here as the Shadybucks wristband / Shady Tag flow: each attendee received a wristband at registration, activated Shadybucks at Shadytel, registered a Shady Tag handle, and used the badge or wristband trail as an entry point into the Euphoria CTF.
Linux ADS-B badge with Winglet OS 2.0
Aerospace Village's DEF CON 33 badge record documents the DC32 ADS-B badge hardware returning for DC33 with new software, Winglet OS 2.0 release artifacts, DC33 SAO support, and an ADS-B accessory ecosystem.
SpiderOak workshop ESP32-S3 messaging board
Aerospace Village's DEF CON 33 workshop schedule documented a SpiderOak Aranya hands-on workshop where up to 20 attendees received free ESP32 badge-board hardware, flashed a distributed wireless messaging application, and kept the board afterward.
Four-challenge serial CTF badge
The AvengerCon IX electronic badge carried a built-in four-challenge CTF, coin-cell blink behavior, BAT CON battery jumper, micro-USB connection, CP2102 USB-to-UART serial path, and post-event unlock codes published by the official badge page.
Afro-pick commemorative village badge
Blacks In Cybersecurity's official BIC Pick page documents a DEF CON 33 village badge designed as a red, green, and gold Afro pick celebrating the five-year anniversary of the BIC Village.
Compute Module 5 medical-AI badge
Biohacking Village's DEF CON 33 Distiller BHV badge was a CM5-based medical-AI badge built with SolaSec and PamirAI, combining local voice/chat interaction, e-ink UI, physical buttons, colored LEDs, battery power, and public BHV software branches.
ESP32-WROVER MicroPython conference e-badge
BSides Fort Wayne 2025 had an electronic conference badge documented by a first-hand badge-team writeup and a public organization repository, with ESP32-WROVER hardware, dual SPI display headers, seven WS2812B LEDs, accelerometer, buzzer, LiPo charging, MicroPython firmware, and badge CTF challenge apps.
Maker-documented ESP32-S3 electronic conference badge
BSides Knoxville's 2025 official guide says Fox Pick made the event badges. In a public post-event talk, a Fox Pick representative describes the resulting electronic badge as ESP32-S3 based, with Bluetooth Low Energy and 2.4 GHz Wi-Fi, an SSD1309 display, capacitive touch controls, USB-C, a CH340 USB-UART bridge, battery voltage monitoring and charging/protection circuitry, a NeoPixel status light, and exposed I/O pads. The talk says source code was made available through a QR-linked GitHub page, but this pass did not recover a direct repository URL.
Maker-published one-off ESP32 badge-challenge device
A source-bounded independent BSides Peoria 2025 challenge-badge dossier. Technet8394's event-period public HackTheBadge README calls the work "My ESP32 code for the BSides Peoria Badge Challenge 2025." Its later source release documents an ESP32, a 240×320 ILI9341 TFT panel, two batteries, and wiring. BSides Peoria's official 2025 announcement establishes the October 25 Bradley University event, and its 2026 organizer retrospective says the prior edition drew nearly 350 people and had electronic badges. No reviewed organizer source links this specific maker project to a main attendee badge, official issuance, or completed handoff, so the catalogue keeps it as an independent event-associated challenge device.
Badge Pirates ESP32-S3 touchscreen conference badge with a later firmware path
The BSidesKC 2025 badge was a Badge Pirates fully electronic conference badge documented through public production and fulfillment updates: 250 fully assembled ESP32 touchscreen badges from PCBWay with 3.2 inch touch screens, Wi-Fi, SD card slots, customs delays, tariff impact, and post-event pickup or shipping handling. A current maker-hosted flasher identifies its target as ESP32-S3, while a 2026 Badge Pirates announcement says the delayed 2025 hardware, not a new board, received a Lunar Lander contest continuation for BSidesKC's Ad Astra programme.
Pacific Hackers and Hackerwares HCV badge
The BSidesSF 2025 Hardware Challenge Village badge is a source-backed badge designed specifically for the village's electronic tinkering, programming, and competitive CTF challenge.
custom ESP32-S3 / LoRa Meshtastic badge
The BSidesSLC 2025 E-Badge is a source-backed custom electronic badge that BSidesSLC describes with an ESP32-S3-WROOM, LoRa, 25 addressable LEDs, TFT display, Micro-USB or three-AA power, mini-badge slots, and custom Meshtastic firmware.
Four-button, four-LED challenge badge
Bug Bounty Village's BBV Badge 2025 was a DEF CON 33 village challenge badge with four buttons, four corresponding LEDs, and a reward path for attendees who lit all four LEDs.
Badge Pirates CC13 ESP32-S3 badge archive
The CactusCon 13 badge is preserved through Badge Pirates' public CactusCon13 repository, which publishes KiCad CAD files, Gerber output, outer-board variants, 3D-print assets, ESP32-S3 reference material, and a MIT-licensed source archive for the 2025 CactusCon badge.
Layered-lens physical badge
An official DEF CON 33 non-electronic physical badge by Mar Williams, built around layered art, 3D image interactions, lenses, clue spotting around the con, and an Arts & Entertainment booth badge challenge.
Independent ESP32-S3 party badge with a scheduled DC33 BadgeLife drop
BigTaro's Tindie listing calls FightDystopia 2025 an electronic party badge, prices it at $150, and displays an out-of-stock state that says it has been sold out since August 11, 2025. The maker says it detects a user-defined list of BLE MAC addresses to give a heads-up about what is around the user; includes a CTF with Windows Vista-era throwbacks, hardware and software puzzles, unlockable bling and GIFs, two custom PCBs sandwiching a screen for a retro-TV aesthetic, an ESP32-S3-based fully-programmable claim, twelve RGB LEDs, a custom lanyard, and stickers. The DEF CON 33 Creator Events List independently schedules a Friday BadgeLife Community drop naming FightDystopia alongside Submarine and FrogStar. This establishes a source-backed independent 2025 electronic artifact and scheduled event association, not an official DEF CON credential, universal or completed handout, BLE detection mechanism, security or privacy assurance, firmware source release, party-benefit accounting, or reusable-image rights.
Unofficial electronic badge with a documented DEF CON 33 BadgeLife drop schedule
BigTaro's FrogStar 2025 project page calls FrogStar an unofficial DEFCON badge, and the DEF CON 33 Creator Events List schedules a BadgeLife Community Table 1 drop that explicitly names the FrogStar Badge alongside two other BigTaro artifacts. The maker page identifies a Raspberry Pi RP2350, 1.28 inch GC9A01 240 by 240 round LCD, two SAO V1.69bis ports, addressable WS2812B RGB LEDs, an infrared receiver, six buttons, frog-themed CTF and game framing, and a Firmware v1.0 UF2 download with a copy-to-flash instruction. A Tindie listing separately calls it an electronic badge and says it was a Defcon pickup preorder; a later Uberflux listing shows an $80 / seven-sold / 23-remaining snapshot, a DEF CON 34 drop label, and $11 USPS Flat Rate shipping. These sources establish a real independent electronic artifact and a scheduled 2025 event association, not a confirmed completed handout, official DEF CON issuance, admission, exact production count, completed later fulfillment, firmware source release, or reusable-image rights.
Independent ESP32-S3 Wi-Fi monitoring and foxhunt badge sold for DEF CON 33
HackMy*'s maker storefront labels GigaGeiger a Wi-Fi badge for DEF CON 33 and shows a USD 120 price with a sold-out-since-August 6, 2025 state. The same listing describes a retro Geiger-counter-inspired device with a single rotary dial for 2.4 GHz channel monitoring, MAC-address foxhunting, and browser-based firmware flashing; it says the product shipped with a lanyard and batteries. Its linked public Penzz-HM repository publishes an MIT-licensed Arduino/C++ implementation for an ESP32-S3-WROOM, GC9A01 display, rotary input, Wi-Fi scanning, promiscuous-mode packet counting, RSSI tracking, and a local web updater, plus firmware binaries, Gerbers, and enclosure STL files. A separately published GigaGeiger PCB project on PCBWay is dated June 25, 2025, names Matt Wagner, provides Gerbers, and is marked CC BY-SA. These sources establish a real independent 2025 BadgeLife artifact and a public design trail, not official DEF CON issuance, admission, a completed event handoff, a complete electrical specification, universal radio/OTA safety, or a rights-cleared hero image.
Independent IR game/TV-control badge and Sheriff SAO combo listed for DEF CON 33
BigTaro's Tindie page calls Gunslinger-B-Gone an electronic badge with laser tag, a TV-B-Gone, a CTF, and an included Sheriff SAO; the page shows $100 and says it has been sold out since September 13, 2025. A separate Hacker Couture DEFCON 33 Product List independently lists a Gunslinger-B-Gone Badge by BigTaro at $140 and describes laser-tag play with the Sheriff SAO, making friends' badges light up, pointing an IR blast at a TV to power it down, CTF challenges, bling modes, Drinking Roulette, and a fully-programmable claim. BigTaro's Sheriff guide identifies the Sheriff companion as an RP2040-chip board, documents a CR2032 or LIR2032 battery holder with magnet and sticky pad, an independent battery switch, a standalone/wearable configuration, and an optional soldered SAO connection to the Gunslinger with the notch side up. These sources establish a real independent electronic-badge combo and a 2025 DEF CON vendor-list association, not a BadgeLife drop, official DEF CON issue, admission credential, complete IR or electrical specification, confirmed vendor handoff, firmware source release, or reusable-image rights.
ESP32-S3 LoRa mesh communicator badge
The 2025 Hackaday Supercon Communicator Badge is a handheld mesh-chat badge with ESP32-S3, 8 MB PSRAM, 16 MB flash, a wide LCD, custom Solder Party keyboard, SX1262 LoRa radio, SMA antenna path, LiPo charging, SAO v2 connector, LVGL MicroPython firmware, public hardware files, and user-app examples.
RP2350A ICS security badge tool
The ICS Village Badge for DEF CON 33 was a FREE-WILi and Intrepid Control Systems sponsored hands-on industrial-control-security badge tool with RP2350A control, ESP32-C6 Wi-Fi, sensors, GUI support, USB API, WASM scripting, and Build-A-Badge customization software.
Raspberry Pi Pico racing badge
Kernelcon's 2025 Race Condition badge was a Raspberry Pi Pico electronic badge with a TM1637-driven seven-segment display, three-AAA power, seven addressable RGB LEDs, buzzer, track-racing modes, reaction test, synthesizer, achievements, and CTF flag unlocks.
Electronic Cats OLED and nRF24L01 village badge
Electronic Cats' public La Villa Hacker 2025 Badge repository documents a village badge with OLED display, nRF24L01 radio, two-AAA power, Shitty Addon connector, KiCad hardware files, firmware sources, and a released VillaHacker.hex binary.
RP2040 and iCE40 glitching badge for hardware hacking
LayerOne 2025's GLiTCh BadgE was a conference electronic badge and hardware-hacking platform centered on an RP2040, iCE40 FPGA, voltage glitching, crowbar control, SWD, AVRISP, analog monitoring, multiple USB modes, and CLI-driven experiments.
Limited LoRa mesh badge for DEF CON 33 pickup
Lonely Hackers Club's Meshtastic Badge 2025 was a limited 50-unit community badge offered for DEF CON 33 pickup, built around a Heltec Wireless Tracker V1.1 LoRa radio board, preconfigured LHC channel behavior, and attendee pairing workflows.
Pico 2 maritime bus and voltage-glitching badge
The Differential Destroyer was Maritime Hacking Village's official DEF CON 33 badge, published as an OSHWA-certified open hardware platform for maritime bus work, scripting, signal interaction, and experimental voltage glitching.
Independent ATtiny1616 analog-input puzzle badge with a scheduled DC33 drop and current DC34 continuity
Hak4Kidz Lab's Tindie listing calls Masonic33 a cryptic, interactive badge for puzzle lovers, hackers, and DEF CON attendees. It says two 10 kΩ potentiometers control an ATtiny1616-based board with eleven independently controlled LEDs; players tune analog inputs to unlock a hidden LED sequence and solve four puzzles. The listing also names a UPDI-compatible one-wire programming interface, 4.5 V AAA-battery input with batteries included, a 4.25-inch black-solder-mask/white-silkscreen PCB, custom VHS-style box, patches, lanyard, and stickers. A recovered public DEF CON 33 schedule records a 10:30-10:59 PDT BadgeLife Community Masonic33 Badge drop credited to Heal-Hak4Kidz, while the Hacker Couture DEFCON 33 product list separately shows the Masonic33 Badge at $125. Badge.Life's live DC34 Village Schedule additionally lists Masonic33 Badge — heal at 10:30 AM on Friday August 7 and 11:00 AM on Saturday August 8, 2026, without naming a changed board or revision. These sources establish a real independent 2025 puzzle badge with planned 2026 continuity, not official DEF CON issuance, admission, a confirmed completed drop, a separate DC34 artifact, a complete circuit/firmware archive, a connection to any fraternal organization, or reusable-image rights.
Unofficial badgelife robot-fighting badge set
NilbinSec's Hack 'Em Crack 'Em Robots was a DEF CON 33 badgelife release announced in the DEF CON #Badge Life forum, sold as a limited full-size badge set through RENXCHANGE, and listed in the DC33 community schedule as a badge drop.
Voodoo Heart electronic badge and Learn to Solder artifact
NolaCon 2025's Patches badge continued the conference's Learn to Solder badge tradition, with the official badge page presenting Patches as a customizable Voodoo Heart-series character whose limbs, LEDs, and personal flair could make each build unique.
Work-in-progress MicroPython game-badge archive
A source-conservative OzSec 2025 badge record: the organizer-linked repository calls itself the code and supporting-document archive for the CRASHANDBURN badge, while retaining work-in-progress hardware alternatives and MicroPython game source.
Large physical ATM attack-surface simulation artifact
A preserved DEF CON 33 programme describes Payment Village's Vulnerable ATM Badge as the conference's largest badge that year: a physical form factor attendees could carry with two hands, built to simulate ATM attack surfaces. Payment Village's own DEF CON 33 page confirms the village/event context, while its 2026 schedule still lists an Introduction to the Vulnerable ATM Badge. The recovered sources establish the named physical educational artifact, not its electronics, a reusable current build, or a 2026 reissue.
Battery-less ZBD shelf-label badge with per-attendee firmware images
PhreakNIC 26's official electronic badge reused dead-battery ZBD 55c-RB electronic shelf labels as 3D-printed pager-styled badges with static 240x96 one-bit displays, QR-code-backed attendee customization, and on-site reflashing.
DEF CON 33 RF badgelife badge with dual CC1101 radios
Rabbit-Labs and The Pirates' Plunder Badge was an independent DEF CON 33 collaboration badge that debuted at the Rabbit-Labs vendor booth, with public firmware options, an ESP32-S3-N16R8, two CC1101 433 MHz radios, an OLED, joystick controls, SDIO storage, and 32 WS2812B / NeoPixel LEDs.
Cyber Vigilance owl badge
Recon Village's DEF CON 33 badge entry, The Cyber Owl, was a cyberpunk owl electronic badge with intricate mechanical detail, metallic blue-gray finish, and glowing pink LED eyes.
First electronic badge in summit history
Red Team Summit's official history identifies the March 11-12, 2025 Redmond event as the first Red Team Summit with an electronic badge. The same historical record gives 194 attendees, 61 organizations, and 108 CFP submissions, but does not describe the badge's physical form, technology, maker, or recipient scope.
Official limited Custom Hack.RVA Electronic badge package record
The RVAsec 2025 badge is seeded from the official RVAsec 14 registration page, which listed a guaranteed hotel package with a custom RVAsec challenge coin and a Custom Hack.RVA Electronic badge while supplies lasted. No public 2025 hardware repository, firmware tree, schematic, BOM, or final badge photo provenance was recovered in this pass.
Independent 25-slot Simple Add-On host badge; later DEF CON 34 roster continuity
Coruscant Ventures' official SAO Many SAOs Badge page identifies the object as a DEFCON 33 product, presents it as a 25-design Simple Add-On display platform, and says its outer LEDs require the separate SmartAO SAO. The maker's public technical README says the badge has two pre-installed 18650 batteries, USB and barrel-connector power/charging paths, up to 25 SAO slots, and an approximately 300 mA at 3.3 V total SAO budget when using charged batteries. A July 2026 public DEF CON 34 Badgelife response marks SaO MANY SAOs as Update to Existing, gives an $80 price and Venmo acquisition note, and repeats 25 SAO slots plus a 360 by 360 mm size. The current roster does not identify a changed board or new revision, so this is one independently documented DEF CON 33 host badge with a later availability/continuity record, not a duplicate DEF CON 34 artifact, official credential, completed sale, confirmed delivery, or rights-cleared image.
RP2040 galvanic-vestibular badgelife badge
The Tipsy Badge was an independent DEF CON 33 electronic badge by seeess, sold at the Hacker Warehouse vendor booth, with public CC BY-NC 4.0 repository documentation, firmware, a badge photo, 2xAAA power, RP2040 control, TFT display, buttons, LEDs, SAO port, custom photo storage, and galvanic vestibular stimulation modes.
Independent electronic badge and Pirate Flag SAO bundle with a scheduled DC33 BadgeLife drop
BigTaro's Tindie listing calls this the Submarine Badge & Pirate SAO and describes a $150 Defcon-pickup preorder. It frames the electronic artifact as an interactive underwater world with CTF package deliveries in DEF-SEA, pirate battles, underwater cults, Atlantis, hardware/software puzzles, and soldering challenges. The source says it has a super-bright round display, more than six buttons, one SAO port, exposed extra GPIO, a fully-programmable claim, an exclusive Pirate Flag SAO bundle, stickers, and an interaction with Gunslinger-B-Gone. BigTaro's own Submarine page supplies a live dashboard-like maker surface, and the DEF CON 33 Creator Events List independently schedules a Friday BadgeLife Community Table 1 drop naming Submarine alongside FrogStar and FightDystopia. These sources establish a real independent electronic-badge bundle and a scheduled 2025 event activity, not an official DEF CON credential, confirmed attendance or handout outcome, production count, electrical design, firmware source release, or reusable-image rights.
ESP32 touch-wheel badge with TFT, audio, LEDs, and games
The THOTCON 0xD badge was a Fourfold-built electronic conference badge for the May 30-31, 2025 Chicago event, documented as a 2,000-unit ESP32 touch-wheel badge with ST7789 TFT display, buzzer, six LEDs, LiPo power, add-on header, games, visual effects, and challenge hooks.
Maker-stated DEF CON 33 multicolor-LED Simple Add-On; 2026 leftover pickup only
coryallegory's live Uberflux listing calls this the Vibe Coder Dog SAO, says Science Dog is now Coder Dog, and says the artifact was created for DEFCON 33. The same current listing says a few leftover units are available as a 2026 pre-order for pickup at DEF CON 34 or BSidesLV in Las Vegas. Its August 4, 2026 snapshot lists $15, five sold, and zero remaining, with a free Saturday August 8 BadgeLife Village pickup label. The maker says the unit is fully assembled, has a standard 2 by 3 SAO header, and uses cycling multicolor LEDs to light its keyboard with AI magic. This is source-backed evidence for an independent DEF CON 33-associated LED Simple Add-On, not proof of the original 2025 distribution, a specific controller or actual AI behavior, final 2026 pickup, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Antisyphon-sponsored ESP32-S3 badge CTF
The Wild West Hackin' Fest Deadwood 2025 e-badge was the conference's electronic badge and badge CTF artifact. The official WWHF e-badge page identifies Antisyphon Training as the badge sponsor, Meta CTF as the scoreboard/challenge partner, multiple challenges solvable from badge behavior or firmware, and Ray Feltch, David Fletcher, and Rick Wisser as badge-team contacts.
Pre-event 16-red-LED Simple Add-On with a maker-stated fundraiser context
caelyb's live Uberflux listing describes the #NOICE Simple Add-On as designed for DEF CON 34. Its August 4, 2026 marketplace snapshot lists $20, eight sold, and 92 remaining, with BadgeLife Village, LineCon, and Queercon Mixer drop labels plus post-DEF-CON CONUS shipping. The listing names sixteen side-emitting XL-1606SURC red LEDs, a tactile effect button, persistent last-effect memory, and a stated 2.7–3.7 V input range. It says the board has several fast and slow flashing, heartbeat, and breathing/fade effects, includes a lobster-clasp lanyard, and frames the project around the maker's stated concerns about U.S. immigration enforcement. The maker also says a portion of proceeds goes to the Immigrant Defenders Law Center. This is a source-backed pre-event independent lighting SAO record, not verification of the listing's policy statements or donation outcome, final manufacture, electrical safety, host compatibility, delivery, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Independent brass Coin M0 text-adventure and CircuitPython eChallengeCoin planned for DEF CON 34
AoSC's 2026 eChallengeCoin page describes a planned limited run of 40 brass electronic coins, framed as gifts for participants in its Choose Your Own Charity initiative rather than items for sale. It describes a Sara and the Missing Artifacts terminal text adventure, three groups of NeoPixels, a small speaker, one large touch pad for CircuitPython, no battery, 46-gram brass construction, and a Micro-USB serial connection; its form says a $100-or-greater youth-STEM-charity donation may receive a 2026 coin by U.S. mail or DEF CON pickup. The same page links the official CircuitPython Bradán Lane STUDIO Coin M0 profile as the build specifically for the eChallengeCoin. That profile identifies an ATSAMD21G1A, 4 MB flash, three RGB-NeoPixel groups, three capacitive touch pads, a speaker, and native USB-C. The linked primary sources therefore document a real planned independent DEF CON 34 electronic artifact while also disagreeing about USB connector type and touch-pad count; this record preserves the conflict rather than resolving it. They do not establish final manufactured-unit parity, confirmed donations or delivery, charity/tax treatment, official DEF CON issuance or admission, game-source licensing, or reusable-image rights.
Officially announced pre-event volunteer identity artifact
Adversary Village's official DEF CON 34 volunteer notice lists Adversary Village badges among the benefits for selected volunteers and explicitly says those badges do not give access to the con. The organizer's main event page confirms the August 7-9 Las Vegas Convention Center programme. This source-backed record models a planned volunteer identity artifact only; it does not identify a physical form, electronics, access-control mechanism, issued quantity, or handoff.
Planned winnable CTF badge with an NFC game claim
The public DEF CON 34 BadgeLife roster contains a new listing submitted as Lockheed Martin - Aeronautics Cyber Range (ACR) for a badge titled SR-71. The named team says the badge is only winnable through a CTF it plans to host at its Aerospace Village booth and on its Discord, and describes a TCG-type card-collection game using NFC peer-to-peer and reader modes. That is concrete first-hand pre-event artifact evidence, while Aerospace Village's official page independently establishes the DEF CON 34 context; neither source publishes the badge's physical construction, NFC-hardware placement, or final distribution.
Independent RP2040-Zero firmware project; physical build and event handoff unverified
MadmanTimmy3241's public repository describes itself as DEF CON 34 'Agency' SAO badge firmware for a Waveshare RP2040-Zero, and its commit-pinned source header calls the sketch DEF CON 34 "Agency" badge - V2. The public Arduino/C++ tree contains current display, scrolling, button, switch, buzzer, and infrared source paths, while dated first-person commit messages report staged local hardware smoke, display, input, and buzzer testing. The source header simultaneously says handshake, infrared, and logging logic is not wired up yet. This is sufficient to retain a distinct, independent pre-event event-labelled firmware-project record, not proof of a completed board, an event badge run, a compatible SAO, a delivered unit, DEF CON authorization, admission use, or a reusable image.
Current $60 ATtiny1616 BadgeLife wand; DC34 handoff and final-unit parity unverified
Brooke's Bytes' live Uberflux listing identifies Agency Wand as an independently offered DEF CON 34 iteration of a wand-shaped badge first made for HackSpaceCon 2025. The current listing shows a $60 price, 19 remaining, 11 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village drop listed for August 7 at 4 PM. It names an ATtiny1616, five reverse-mounted addressable LEDs, ambient/setup LEDs, two buttons, a CR2032, and exposed UART pins, while explicitly saying specifications and functionality may vary as fabrication and development continue. TrueControl's public documentation describes this as the second Wand iteration and publishes more DC34 hardware/firmware context, including a clearly labelled REV1 hardware-issue section. The sources support a distinct pre-event electronic badge record, not completed manufacture or handoff, DEF CON issuance or admission function, final stock/payment status, a universally safe device, final firmware parity, or reusable marketplace/repository images.
Pre-event independent BENDER contest badge with activation pending
AND!XOR's source-backed DC34 5N4CK3Y project is an independent DEF CON BadgeLife contest badge with limited philanthropy units and a stated free-badge distribution route through challenges, contests, events, and other convention activity. Its official product page says BENDER hacking challenges and same-day activation instructions are scheduled for the event, but does not yet disclose the board or firmware implementation. It is a pre-event independent record, not the official DEF CON 34 Human badge.
Alex Glow's MIT-licensed hardware-experimentation event PCB badge
Alex Glow's public repository describes this as an official PCB-badge commission for Avnet's FAE Institute 2026, and its linked Hackster project calls it a cyber-gem and platform for hardware experimentation. The commit-pinned source archive contains KiCad 9 board files, Gerber outputs, custom footprint libraries, and front/back repository rasters. Public vendor updates identify the July Phoenix FAE Institute's hands-on technical-training context. Together these sources establish a real event-specific hardware design, but not participant-wide issuance, a final manufactured configuration, a source-to-unit mapping, or a delivery ledger.
Current $10 three-flashing-red-LED SAO; handoff and host compatibility unverified
Brooke's Bytes' live Uberflux listing calls Badge Crown SAO a Crown Shitty Add-On for a conference badge. The current page shows a $10 price, 10 remaining, 20 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village drop listed for August 7 at 4 PM. It describes a fully assembled SAO with one SAO connector, three flashing red LEDs, and three resistors; its own listing says no soldering, programming, or separate battery is required and tells users only to connect it to a compatible badge. Badge.Life separately schedules Brookes Bytes Badge and SAOs in the same Friday 4 PM village slot. These sources establish a distinct pre-event electronic add-on record, not a documented pinout, voltage/current budget, universal host fit, completed sale or handoff, DEF CON issuance or credential role, or image reuse.
Published pre-event RP2354 BadgeLife village badge; allocation and handoff unverified
Badge.Life's public archive documents Badgey Bodgerton as the Badgelife Village Badge for DC34 / 2026. Its published guide names an RP2354 microcontroller with integrated flash, eight addressable RGB NeoPixel LEDs, three user buttons, one user-installed 3 mm challenge LED and polarized buzzer, USB-C power, USB CDC serial CLI, UF2 firmware flashing, a single-cell 18650 battery with charging and protection circuitry, two Simple Add-On v2 headers, and an infrared receiver. It also documents a supplied bodge-wire challenge and supplied LED/resistor/buzzer challenge parts. This establishes a distinct, technically documented pre-event BadgeLife village electronic badge, not proof that DEF CON designed, issued, or will distribute it; that it is a Human admission credential; that every participant receives one; that a final badge run, pickup, or delivery occurred; or that any displayed image is cleared for reuse.
Independent ATtiny814 24-NeoPixel minibadge holder offered for DEF CON 34
Cabinet of Distinctm1nd's live Beelzebub Minibadge Holder listing is a $45 offer that displayed sold out in this August 4, 2026 source pass and says DEF CON pickup is only for August 6-8 pickup attendees. The maker describes 24 NeoPixel LEDs, an ATtiny 814, USB-or-battery power, custom or pre-programmed themes, and an assembled board whose minibadge headers and optional battery holder still require soldering; it also says shown minibadges are not included. The public `distinctm1nd/beelzebub_minibadge_holder` repository corroborates a holder for five minibadges, a 24-LED source layout, button-selected theme code, and KiCad/BOM material. Its hardware archive includes a filename with `saintcon_2025`, so it is a useful implementation and lineage source, not proof of a completed SAINTCON distribution, an unchanged final 2026 build, final fulfillment, official DEF CON issuance, a complete source-license grant, or reusable-image rights.
Completed DEF CON ticket-verification conference identity artifact; handoff details remain unverified
Black Hat's official 2026 DEF CON-registration and attendee-resource pages say that a registrant who bought a DEF CON ticket through an eligible Black Hat pass receives a DEF CON symbol printed on their Black Hat badge. The person presents that marked badge during the August 6 pickup workflow, where staff hole-punch it as proof of pickup, but the sources do not identify the badge's material, artwork, barcode/QR/RFID/NFC/electronic form, broader access behavior, or completed handoff.
Current $80 RP2354 breadboard-prototyping badge; fulfillment unverified
Tw0nkus's live Uberflux listing calls Breadbadge a badge by day and a breadboard-prototyping tool by night. It identifies an RP2354A main MCU, INA3221 I2C voltage/current/power monitor, ST7789 SPI display, six WS2812 RGB LEDs, navigation joystick/back button, UART/UPDI/I2C/5 V/3.3 V/debug breakouts, and a Defcon34 drop. The same current listing displayed $80, five remaining, and four sold. Badge.Life's current DC34 Village schedule independently lists Bread Badge by Tw0nkus in its Friday 1:30 PM badge-drop slot. This is enough evidence for a distinct, independently offered pre-event electronic badge associated with DEF CON 34, not proof that DEF CON issued it, that it is an admission credential, that inventory/payment/fulfillment figures are final, that a drop or handoff occurred, or that marketplace images are cleared for reuse.
Iowa CH585 RISC-V NFC badge with village-collection CTF
An official BSides Des Moines 2026 badge documented by the iot-pwn bsidesdsm26 repository as a WCH CH585 RISC-V board with an integrated ISO 14443A NFC reader, four SK6812 RGBW LEDs, a main control button, audio, and a three-layer CTF with two static flags, an eight-tag village-collection challenge, and a hash-based unlock, for the June 13, 2026 edition in Ankeny, Iowa.
Optional organizer e-badge ticket add-on paired with a distinct 2026 source archive
BSides Fort Wayne's organizer ticket page offered a $30 optional e-badge add-on for the June 6, 2026 conference. The public BSidesFW2026Badge repository has distinct June 2026 activity, including a dedicated STLs/2026 enclosure set and default badge data changed to 2026, together with MicroPython source and inherited V4 technical documentation. The evidence links a real optional e-badge offer to a 2026 source archive without claiming a confirmed sale, physical receipt, firmware deployment, or exact final hardware configuration.
Current capacity-managed conference admission badge
BSides Las Vegas's official 2026 registration and ticketing sources call this a Participant Badge required for general conference access. The official registration page documents on-site pickup and separate queues for different badge types, while the ticketing page says a participant badge is required separately for Training Ground classes. It is recorded as a current identity/access artifact, not an electronic badge.
Interactive hackable lighthouse attendee badge with a pulsing beacon
BSides Maine's official Bluesky account called its 2026 badge electronic, described it as a puzzle, and revealed the main attendee badge as a hackable lighthouse with a pulsing beacon. The official agenda says attendees collected conference badges and materials at registration, and its closing description refers to whether anyone solved the badge. This completed-event record therefore documents a real electronic attendee badge and its stated puzzle role without supplying unannounced technical details.
Attendee badge-package non-electronic challenge coin
Official BSides Nashville 2026 event information says each attendee badge included a BSides Nashville 2026 challenge coin. The organizer's public feed later re-shared an attendee note about receiving coins. This record models the source-backed coin as a physical, non-electronic badge-package companion artifact; it does not use an Electronic Badge Sponsor line as proof that a 2026 electronic board existed.
Custom PCB badge with pre-sale allocation; electronics undocumented
BSides NOLA's 2026 event listing advertised a custom PCB badge from Fox Pick and a pre-sale package with a guaranteed PCB badge. A post-event attendee account describes leaving with a Rougarou circuit-board badge, confirming a physical board artifact while leaving the badge's components, behavior, and final allocation unresolved.
Organizer-published four-LED KiCad badge design for the upcoming September conference
BSides Orlando's official GitHub organization published 2026-badge, a public KiCad 10 schematic and PCB project, as the conference's current 2026 badge-design trail. The schematic identifies four 3 mm blink-labeled LEDs, a Keystone 3002 1x2032 cell-holder footprint, an MST22D18G2 125 power-switch component, and a 2x3 2.54 mm socket. The official event site sets the conference for September 26 at Full Sail Live in Winter Park, Florida. This supports a planned organizer-published discrete LED badge design, not a released or allocated physical badge, attendee credential, finished BOM, final board revision, firmware, or image license.
Planned Illinois Security BSides badge with sponsor-logo surface
A conservative planned Illinois Security BSides conference-badge record from organizer sponsorship material. The BSides Peoria 2026 call for sponsors says organizers are locking in badge runs, and the official 2026 prospectus includes a Logo on Badge sponsorship benefit. The official home places the October 24 event at Bradley University, but these pre-event sources do not establish a final credential form, electronics, ticket inclusion, allocation, or delivery.
Admission badge with a web-puzzle companion; electronics undocumented
BSides Roanoke 2026's organizer-operated General Admission listing explicitly included a badge. A separate ShenLabs website declares itself a work of fiction created for the BSides Roanoke 2026 badge challenge. Together they support an admission-badge and web-puzzle record, but do not identify a physical link, electronics, or an embedded challenge mechanism.
ESP32 portable CTF badge
BSides San Diego 2026 handed attendees a Cyberpunk Bunny electronic badge: an ESP32-powered portable CTF with cryptography challenges, wireless hacking, hidden secrets, an accelerometer-driven oracle, BLE co-op behavior, and an ultimate hidden flag path.
Patron-benefit conference identity artifact; handoff unverified
BSides Seattle's official 2026 ticket page lists a Special badge at the event among the additional benefits of being a 2026 patron. The organizer's conference page places the event at Building 92 in Redmond on February 27-28, but the source does not identify the artifact's material, artwork, barcode/QR/RFID/NFC/electronic form, exact patron-tier allocation, or actual pickup/delivery.
Official Tampa badge/lanyard challenge and Uber Badge award trail
BSides Tampa 2026 is represented here by official attendee-badge and badge-challenge sources: the current FAQ says every participant gets a badge and lanyard, the badge-challenge page tells attendees that their badge is part of the puzzle, and the Uber Badge page records the lifetime-admission award path for badge-challenge winners.
Source-conservative afterparty admission identity artifact
BSidesKC's current 2026 activities page says attendees had to present a BSidesKC badge for afterparty entry. Together with the official event page, that establishes a 2026 badge-linked admission artifact; it does not identify a material, design, QR/barcode, RFID/NFC, electronics, or whether it was the separately documented 2025 Badge Pirates hardware.
Pre-event BTV fundraiser for a DC32-origin ESP32 camera badge
Blue Team Village at DEF CON's Eventbrite offer schedules the BTV Camera Badge as a DEF CON 34 fundraiser for August 7-9, 2026 at the Las Vegas Convention Center West Hall, with in-person village pickup only. It offers an assembled badge and lanyard for $120 or an intermediate-to-advanced soldering kit for $60. The listing says the badge does not take photos; instead, in an appropriate mode, its camera-lens display shows when deauthentication packets are being sent or Flipper Zeros are nearby, and says its brain is an ESP32 board capable of custom software. BTV's public MIT `btv_dc32_badge` archive explicitly describes the artifact as a DEF CON 32 indie badge and preserves its Arduino source, KiCad project, Gerbers, CAD/fabrication files, parts list, and assembly guide. This is a current source-backed fundraiser for a documented DC32-origin design, not evidence of a newly engineered DEF CON 34 hardware revision, completed pickup, final 2026 firmware, radio-detection performance, electrical safety, conference admission, or reusable-image rights.
Speaker-colored electronic admission badge; allocation evidence is limited
Cackalackycon 2026's organizer-provided Call for Papers promises every selected speaker a speaker-colored electronic badge and free admission. It separately gives the speaker one paper-badge guest admission, noting that a guest who wants an electronic badge must purchase a ticket. The organizer-linked ticket page also markets a 2026 electronic badge, and post-event organizer and badge-team reports corroborate that badges were made and handed out. This record therefore captures a source-backed speaker electronic-badge allocation, not a universal attendee or technical claim.
Student-admission paper identity artifact; explicitly not electronic
Cackalackycon 2026's official event and Cackalackycon 101 pages say students with a valid student ID can attend for free with a paper badge, no electronic badge, and no preregistration. This record models that explicitly disclosed student identity artifact only; related speaker electronic-badge evidence is kept in a separate, scoped record rather than becoming a student hardware claim.
Badge Pirates ESP32-S3 hardware archive
The CactusCon 14 badge is preserved through Badge Pirates' public CC14 repository, which publishes KiCad design files, schematic PDF, interactive BOM, Gerbers, STEP exports, 3D-printable enclosure parts, and art assets for the 2026 CactusCon conference badge.
RP2040 CAN/CAN FD vehicle-network CTF badge, with post-event fulfillment unverified
Car Hacking Village publicly announced its DEF CON 34 CTF badge. Official Village posts identify an RP2040, DB9 CAN 2.0/CAN FD support, interactive power management, and a 12 V 1.5 A power supply; the public `chv_badgetools` repository identifies itself as host-side CAN utilities for the DEF CON 34 badge. The scheduled August 6-9 Las Vegas event window has elapsed, but reviewed post-date sources still do not prove final badge manufacture, allocation, handoff, CTF operation, or a released final firmware.
Completed ESP32-S3 CircuitPython conference badge with public source
Carolina Code Conference's organizer documented Circuit Board Badge pickup for its August 14-15 event, and its named badge partner published a source archive for an ESP32-S3 CircuitPython board. The archive identifies five WS2812 LEDs, three buttons, a 1.77-inch ST7735S display, Micro-USB, and CR123A or USB power. It supports a released badge software and hardware reference, not a recipient ledger, an independently audited final production configuration, or a rights-cleared physical-badge image.
Pre-event ESP32-S3 LoRa mesh BadgeLife communicator
WyrdWyrks' live Uberflux listing identifies the $150 Celestial Wayfinder Badge as a DEF CON 34 pre-sale. At this August 3, 2026 source pass, the listing shows 5 sold and 95 remaining, with four pickup labels: DC34 Reddit Meetup Wednesday, DC34 Reddit Meetup Thursday, and DEF CON 34 BadgeLife 1 and 2. The maker describes an ESP32-S3, custom four-layer PCB, 128×128 OLED, SX1276 LoRa, GPS, magnetometer/IMU, five Cherry MX-compatible switches, a rotary encoder, 61 WS2812B LEDs, a buzzer, 3D-printed parts, a Li-ion battery, USB-C updating/charging, a LoRa mesh, Wi-Fi geolocation fallback, and a PWA. The public MIT-licensed firmware repository documents v1/v2/v3 platform variants, a 915 MHz SX127x-class LoRa mesh, GPS/status PingMessage data, PlatformIO build paths, RPC, and remote USB/BLE/web configuration; v4.0.0 publishes v3 and v2 binaries. A separate Fusion360/STL CAD repository and web-companion repository are public but have no detected license. This is a source-backed pre-event independent BadgeLife record, not proof of final fulfillment, a final production BOM, radio/regulatory performance, safety certification, universal update compatibility, official DEF CON admission status, or reusable-image rights.
Sold-out independent ESP32-S3 wrist badge with a second-run interest list
Bryce's official Clip-Boy shop explicitly presents Clip-Boy as an unofficial DEF CON 34 electronic badge: a wrist-mounted ESP32-S3 artifact with maker-described Wi-Fi/Bluetooth analysis tools, deauthentication detection, customizable LEDs, a theremin, collectibles, and a 3D-printed enclosure. Its live public inventory endpoint currently shows the complete first run at zero availability: 86 $120 Standard, 25 $130 Pro, and five $140 RAD badges, while the storefront says all 152 first-run units shipped and is only gauging interest for a possible second run. The seller states units ship in a passive listen-only mode and that a user may load an optional research build with additional capabilities for authorized testing. This is a current source-backed independent badge record, not a claim of official DEF CON affiliation, DEF CON admission, final hardware/BOM, delivered-unit receipt, a universally available research build, safe/legal use in every jurisdiction, or reusable-image rights.
Independent planned ESP32-S3 battle-game badge project for DEF CON 34
Cyber Professionals Enthusiast Club's public `DC34-Mech-Badge` repository calls the work the DC 34 MechBattle Badge, describes it as the second iteration of menu and game logic for a CPEC DC34 badge offering, and says it is not final; its GitHub description explicitly calls it a DEFCON 34 Mech Badge by CPEC. A second CPEC repository publishes an in-progress PlatformIO/Arduino game codebase targeted at an Adafruit Feather ESP32-S3 no-PSRAM board, with source-level display, Bluetooth Low Energy, QR, and sound surfaces. A third CPEC repository says it contains design files for SAO plug-in modules for the CPEC DC 34 badge; its commit-pinned source tree includes native KiCad project, PCB, and schematic paths with fist, gatling, laser, missile, panel, and sword filenames, an Arduino source file, and BOM/placement artifacts. The linked game-mechanics document is also a draft. These primary sources establish a real independent planned badge and companion-add-on design trail, not final physical hardware, manufactured units, electrical compatibility, availability, event authorization, DEF CON organizer affiliation, admission, deployed radio behavior, or reusable-image rights.
Pre-event ESP32 ritual-game BadgeLife badge
Pfarrside Creations' badge-only listing describes the Cult of Cthulhu Indie DEF CON 34 Badge as an ESP32-powered interactive BadgeLife project that turns a DEF CON setting into a Cthulhu summoning ritual. The seller's page names ESP32, USB-C, rechargeable Li-Po power, ten LEDs, a screen, one-button input, badge types, a 13-chapter Ritual, six side-quest challenges, badge-to-badge Séance behavior, and unlockable games. It also states a second-week-of-July US-only shipping schedule with no DEF CON pickup. This is a maker-published independent badge listing, not verified final delivery or an official DEF CON admission credential.
Small-batch pre-event RP2040 youth-coding giveaway badge for DEF CON 34
A late-July public r/Defcon post by u/ProfessionalPea2218 says its author has been designing and hand-soldering a small batch of badge PCBs to help launch Cyb3rBytes404, a self-described San Diego nonprofit for free hands-on youth coding and electronics projects. The author says the badges are not for sale and are intended for random giveaway throughout ‘the con.’ Separately, the public Cyb3rBytes404 GitHub repository calls itself the official repository for the cyber coding camp and documents a custom RP2040 cyber-cat badge, MicroPython starter material and challenges, an MPU-6050 motion module, and thirty WS2812 RGB LEDs. Its visible commit history places the reviewed README update on July 28, 2026. The shared project name supports a source-backed pre-event DEF CON 34 association, but it does not establish that the Reddit author controls the GitHub namespace, that every physical PCB matches the repository snapshot, final hardware, the run size, a completed giveaway, or a DEF CON-issued credential.
Official lanyard-and-plastic attendee identity artifact
CypherCon 9's official 2026 registration listing describes its Analog / Plastic Entry Pass as a lanyard and physical plastic entry pass supplied with a digital program. The official FAQ separately distinguishes analog tickets that redeem a plastic badge from the general electronic and limited premium badge forms, so this record remains an explicitly non-electronic identity artifact rather than an inferred PCB badge.
Official interactive PCB ticket-tier artifact; final build remains unarchived
CypherCon 9's official 2026 registration listing describes its Digital / Circuit Badge ticket tier as an interactive circuit-board PCB badge. The official FAQ distinguishes that general digital/PCB/electronic tier from limited Extreme/Ultimate and Analog ticket forms, while a public organizer-account timeline mirror records the April event opening and wrap. Those sources establish a real completed-event ticket artifact, not a component-level board specification or an individual fulfillment record.
Official premium electronic and upgraded-PCB ticket-tier artifact
CypherCon 9's official 2026 registration page separately advertised an Extreme Badge ticket tier with unique collectible electronic-badge wording and an exclusive upgraded-PCB feature. The official FAQ calls the limited VIP form an Extreme/Ultimate badge, but the recovered sources do not say whether it was a distinct physical board, an upgrade of the Digital / Circuit Badge, multiple artifacts, or a final fulfilled configuration.
Open-source pre-event 125-unit Meshtastic Simple Add-On for DEF CON 34
Darknet-NG's own current badge page identifies the Darknet-NG SMAO as its Level 3 build: a full Meshtastic node in an SAO form factor. The maker's live Uberflux product payload describes a $55 125-unit presale and currently reports 125 sold with zero remaining, no shipping options, and DEF CON 34 contest-booth pickup only; that is a time-specific availability snapshot, not proof of completed manufacture, collection, or delivery. A matching maker-owned, commit-pinned `dcbokonon/darknet-smao` release now publishes the v1.4 KiCad project, fabrication outputs, BOM/placement data, firmware build material, and RF-tuning source, alongside an MIT-licensed official upstream board render. This is a source-backed independent pre-event mesh-radio add-on record, not independent RF/compliance validation, a DEF CON organizer-issued product, conference credential, admission right, or completed fulfillment record.
Independent blue/yellow LED Day of the Dead Turkey v1 soldering kit offered for DEF CON 34
Cabinet of Distinctm1nd's live Day of the Dead Turkey v1 product page listed a currently available $12 kit in this August 4, 2026 source pass. It calls the artifact either an oversize minibadge or a standalone badge that can be pinned to a lanyard; in standalone form it uses a CR2032 battery and has blue-or-yellow LED colors. The maker says it requires soldering and that all components are 1206 or larger, then limits DEF CON pickup to buyers planning collection on August 6-8, 2026. The public DEF CON 34 Badgelife response separately lists Day of the Dead Turkey v1, v2 as a new $12 badge and calls it a standalone small badge or a Saintcon minibadge. These sources establish a real planned independent light-up kit and current event association—not the exact distinction between v1 and v2, final circuitry or components, completed fulfillment, SAINTCON distribution, official DEF CON issuance or admission, firmware/source/license terms, or a rights-cleared image.
Independent blue/yellow LED Day of the Dead Turkey v2 soldering kit offered for DEF CON 34
Cabinet of Distinctm1nd's live Day of the Dead Turkey v2 product page listed a currently available $12 kit in this August 4, 2026 source pass. It calls the artifact either an oversize minibadge or a standalone badge that can be pinned to a lanyard; in standalone form it uses a CR2032 battery and has blue-or-yellow LED colors. The maker says it requires soldering and that all components are 1206 or larger, then limits DEF CON pickup to buyers planning collection on August 6-8, 2026. The public DEF CON 34 Badgelife response separately lists Day of the Dead Turkey v1, v2 as a new $12 badge and calls it a standalone small badge or a Saintcon minibadge. These sources establish a real planned independent light-up kit and current event association—not the exact distinction between v1 and v2, final circuitry or components, completed fulfillment, SAINTCON distribution, official DEF CON issuance or admission, firmware/source/license terms, or a rights-cleared image.
Public KiCad/Arduino DEF CON 34 project; production and distribution unverified
eggsactly's public `DC-34-Countdown-To-Singularity` repository explicitly calls itself KiCad 6 design files for a DEF CON badge that lets users display an estimate for when the AI singularity will occur. Its README names eight seven-segment displays, a real-time clock, front buttons for changing the estimate, a KiCad board tree, an Arduino firmware tree, and a BOM that includes an ATmega328P-PU, PCF8523T, seven 2×3 SAO connectors, three buttons, 9 V input/battery parts, and display/power components. This is a real, independently documented pre-event source project, not proof of an assembled run, a specific final unit, DEF CON authorization, allocation, sale, delivery, credential function, or a rights-cleared image.
Documented independent pre-event ESP32 RFID-kit badge; distribution unverified
The public `slash128v6/DC34_Cnet_Badge` repository documents a DC34-named electronic kit titled “DC34 CompuNet Badge - Malware Scan Tool 3000.” Its README has a banner reading “Join CompuNet & Critical Start at Defcon!” and lists a PCB, ESP32 Dev Module, round LCD, RFID reader, microSD reader/card, RGB LED, six-pin female SAO header, four-AAA battery holder, 3D-printed stand and slides, RFID sticker tags, plus a separate RGB-LED SAO. The public project tree includes hardware, software, SD-card assets, and a root MIT license. It is therefore a real, independently documented pre-event DEF CON 34-associated kit record, not evidence that DEF CON, CompuNet, or Critical Start authorized, made, issued, sold, or distributed it.
Pre-event RP2040 mechanical macropad BadgeLife project
DCZia's MK9 is a public-source 3×3 mechanical macropad intended as a neck-wearable DEF CON 34 BadgeLife project. Project documentation specifies nine MX switches, RGB per-key and edge lighting, an accelerometer, two 6-pin SAO connectors, USB-C or three-AAA power, CircuitPython firmware, and QMK-compatible hardware. A public August 2 announcement says the project plans BadgeLife pickup, but this remains a pre-event independent badge rather than an official DEF CON admission credential.
Completed electronic Human badge with Baochip, QR interaction, and post-event token conversion
DEF CON's official news confirms DEF CON 34 wrapped on August 10, 2026. Its official badge-help page now documents the issued electronic Human badge's post-conference conversion to a hardware security token, current firmware-update path, public source-code links, and the in-conference encrypted-QR light-pattern exchange. The official July 31 reveal names Bunnie Huang as creator and Baochip as the inspectable silicon platform, while the public core-module KiCad archive and `dc34-vault` source provide a specific hardware and software trail. This establishes a completed official badge record without treating later public source as a production ledger or a reusable-image grant.
Independent LED/2×3-header SAO source project; physical build and host compatibility unverified
The public narengogi/defcon-34-shitty-add-on repository describes itself only as an SAO for DEF CON 34. Its single commit contains a native KiCad project, board, schematic, Gerber outputs, an archive, and vector artwork; the board source includes DC 34 and narengogi silkscreen text, a 2×3 generic connector, and LED/resistor-labelled source entries. That is enough to preserve an independent, source-only pre-event add-on project whose formal product name is not published. It is not evidence of a fabricated board, a specific SAO version or pinout, working electronics, a compatible host, a DEF CON or BadgeLife relationship, a sale or giveaway, attendee delivery, a credential function, or a reusable image.
Maker-published physical silent-disco badge; organizer role and handoff unverified
LastZactionHero's public repository is titled DEF CON Silent Disco Badge and documents a wearable electronic badge that plays local DJ mixes, drives a music-linked light show, and syncs badge-to-badge over infrared. Its August 4 maintainer update says the boards were fabricated, assembled, and playing music, and that every badge's QR silkscreen points to the repository. The public archive contains KiCad design and fabrication material, firmware, and a MIT license, sufficient to record a distinct maker-published physical DEF CON 34-associated artifact. No reviewed DEF CON, venue, silent-disco organizer, sales, or handoff source establishes official issuance, a run size, recipient allocation, or completed event distribution.
Sold-out RP2040, LoRa, NFC, and LED community-event badge preorder
DEFCON Furs' official 2026 site and Hack Your Lives donation-store listing identify a distinct 2026 #badgelife badge for the DEF CON 34 period. The currently sold-out listing describes an assembled badge plus a blank PCB, an RP2040, LoRa radio, NFC, 48 RGB LEDs, MicroPython, touch points, and an SAO 1.69bis interface. It says paid orders will be assembled and shipped by September 30, while blanks were offered for in-person DEF CON pickup. Those are organizer-published preorder and planned-fulfillment statements, not proof that every order shipped, that each unit has the described final configuration, or that a specific recipient collected one.
Independent CH32V003 touch-and-audio SAO announced for DEF CON 34
BigFuckingBadge's live DEF CON 34 page presents a $20 OffensiveSAO around touching Lintile's face to play a "Don't Fuck It Up" cheer track. The public DEF CON 34 Badgelife response identifies that item as the DFIU SAO from BigFuckingBadge / Hexum064 and links public CH32V003 hardware and firmware repositories. The firmware's PlatformIO target is `genericCH32V003F4U6`; its `main.c` initializes touch ADC support, reads a touch input on PD2, starts sampled audio when the threshold is crossed, and configures a PWM audio path plus D/F/I/U and display LED outputs. The public hardware tree contains a KiCad PCB/schematic, BOM/position files, and Gerbers. Together these sources establish a real planned independent electronic SAO associated with DEF CON 34—not an official DEF CON issue, admission credential, confirmed handoff, final production revision, safety-tested product, open-source license grant, or rights-cleared image.
Pre-event independently organized EFF-affiliated BadgeLife fundraiser
Eventbrite lists EFF "Electric Fist" BadgeLife (DEF CON 34) under H4r0ld & V3rbaal's House Of Hacker Horrors. The listing says its BadgeLife proceeds support Electronic Frontier Foundation's mission to defend digital privacy and online freedom; its FAQ says the project is officially affiliated with EFF but independently organized by H4r0ld and V3rbaal. It calls Electric Fist the pair's third EFF BadgeLife design, offers reruns of two prior designs at checkout, and announces online orders with Demo Labs pickup from 10 AM to noon on Friday and Saturday. This is a source-backed pre-event BadgeLife fundraising offering, not a delivery report, hardware specification, official DEF CON admission credential, or an EFF-designed or EFF-sold product claim.
Sold-out pre-event Lepi Labs SAOv3-proposal lighting Simple Add-On for DEF CON 34
Lepi Labs' own Uberflux listing identifies the Firefly Jar as a DEF CON 34-drop Simple Add-On. Its August 4, 2026 marketplace state is out of stock, with 25 sold, zero remaining, and a $25 listed price. The maker describes seven orange reverse-mounted LEDs, an ATtiny824 controller, UPDI reprogramming, vendor commands, and compatibility with Rare Circuit's proposed SAOv3 I2C-based interface. It says the SAO can expose vendor/product IDs, port and command metadata, generic LED controls, and its own lighting modes; the listing also explicitly says it does not support SAOv3 ARP or hot-plugging features. Lepi Labs' first-hand DC34 announcement corroborates planned Friday and Saturday BadgeLife Village drops. This is a source-backed pre-event independent lighting SAO, not proof of final host interoperability, full SAOv3 implementation, firmware release, delivery, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Pre-event FirstBuild / GE Appliances 100-free-badge washer/dryer motion giveaway project
FirstBuild's official DefCon34-Badge repository describes an Arduino-compatible FirstBuild / GE Appliances washer/dryer badge for DEF CON 34. Its README names a current production target of an STM32G031F8P6 with an MXC6655XA three-axis accelerometer and eight SK6805 side-emitting RGB LEDs, driving an infinity-mirror water effect that follows gravity. The repository publishes firmware, a schematic PDF, an MIT license for software and associated documentation, and a distribution guide that says the project is intended to be distributed as firmware installed on physical badges. A first-person r/Defcon post reviewed on 2026-08-05 says its public-account author is returning with the GE Appliances booth in IoT Village, has another 100 free badges to give away, and plans an unspecified number per day; it calls the item a cartoon UltraFast Washer/Dryer Combo with a motion-responsive infinity mirror. In a comment, the author says the artwork, PCB design, and software were done in-house at FirstBuild. That account statement does not independently establish the author's employment, formal FirstBuild or GE Appliances authority, official booth authorization, final stock, or completed handoff. GitHub still shows no release or tag, and the record remains a separate event-associated pre-event project, not the official DEF CON attendee credential or an image-reuse grant.
Pre-event FloridaMan Party access-and-challenge artifact
FloridaMan Party's official 2026 storefront offers a FloridaMan 2026 Badge for $90, currently marks it out of stock, and tells prospective attendees that it is no longer shipping and to come to DEF CON. The same official storefront calls FloridaMan 2026 the biggest Florida-themed party at DEF CON, says entry is badge-only for venue access, and says each badge unlocks a live hacking challenge with stages and a scoreboard. The official party page schedules the event for Thursday, August 6, 2026, 9:00 PM–1:00 AM PT in Las Vegas, with the location provided upon purchase. This is a source-backed pre-event party-access and challenge artifact, not evidence of an electronic badge, DEF CON's official Human badge, conference registration, completed shipment or handoff, final venue admission rules, released challenge software, or a rights-cleared badge image.
Completed independent three-radio ESP32-S3 RF-awareness badge
The public Friend or Foe project archive documents a three-board ESP32-S3 badge shown at DEF CON 34 Packet Hacking Village. Its hardware documentation records a 45-badge DEF CON run and the project root describes a wearable, passive RF-awareness platform with an uplink/display controller and dedicated BLE and Wi-Fi scanner boards. Packet Hacking Village's official DEF CON 34 programme independently establishes the completed village setting and the Friend or Foe presentation. These sources establish a completed independent electronic project, not an official DEF CON Human badge, conference-wide handout, admission credential, or recipient ledger.
Pre-event ESP32-C3 bat-shaped LED party-fundraiser badge
Gothcon's official badge store describes a custom bat-shaped PCB LED badge for the free Gothcon dance party at DEF CON 34. The $80 fundraiser package names 44 independently controlled RGB LEDs, a 2,000 mAh Li-Po battery, USB-C recharging with overcharge protection, a removable laser-etched acrylic shield, a custom lanyard, and an ESP32-C3 with 4 MB flash. The public `claviger/gothcon-firmware` repository adds MicroPython firmware, KiCad schematic/PCB/Gerber material, GPIO mapping, pattern/palette controls, and ESP-NOW badge-to-badge contagion. The store explicitly says its SAO connectors are mirrored and not functional with a standard SAO. Pre-orders are closed and the store says badges will be sold at DEF CON; this remains a pre-event party-fundraiser record, not proof of final sales, delivery, party outcome, or official DEF CON credential status.
Planned volunteer staff identity credential for Grand Rapids conference
A conservative planned GrrCON 2026 volunteer identity-artifact record from the organizer's official volunteer terms. The terms say selected volunteers will be given a GrrCON staff badge and say dismissal revokes that badge. The official home places the September 24-25 conference at DeVos Place in Grand Rapids, but neither source establishes the badge's material, electronic form, technical function, completed issuance, or use by general attendees.
Pre-event independent two-object ESP32-S3 interaction badge project for DEF CON 34
Two contemporaneous project posts authored by the public Reddit account u/zer0patient and signed H4irl1n3 M0gg3r5 describe an independent planned DEF CON 34 Zombie Badge project. The later source explicitly describes two objects using ESP32-S3, IR, NFC, BLE, a buzzer, and a source-described transmission/counter relationship; it also announces a firmware-based, multi-stage CTF and an unreleased backend. It further describes crew-operated live transmission zones, fixed Cure Stations, hidden 3D-printed medkit props, and a separate brain-in-a-jar SAO. The earlier post calls the work the team's first year making badge or badges, says a second variant is part of the experience, and announces intended drop-based distribution. These are source-backed pre-event maker statements about a real planned artifact system, not proof of final manufactured variants, component selection, wireless behavior, game implementation, inventory, drops, event authorization, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Current $10 no-MCU CR2032 flashing-LED soldering kit; handoff and assembly outcome unverified
Brooke's Bytes' live Uberflux listing calls Hacker Boba a beginner-friendly Hacker Boba PCB Badge Kit. The current page shows a $10 price, 17 remaining, 33 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village drop listed for August 7 at 4 PM. It lists a Hacker Boba PCB badge, keychain, power switch, CR2032 holder and included CR2032, three flashing RGB LEDs, and three resistors; it says the DIY kit arrives unsoldered, needs basic soldering supplies, has no microcontroller or firmware, and includes a QR code that opens a Google Maps Boba Shop search. Badge.Life separately schedules Brookes Bytes Badge and SAOs in the same Friday 4 PM slot. This supports a distinct pre-event electronic kit record, not a completed sale or assembly, DEF CON issuance or admission role, electrical-safety validation, a hardware-design release, or reusable listing images.
Maker-announced independent Hacker Pager revision for DEF CON 34; handoff outcome unverified
A first-hand Exploitee.rs announcement says the team is bringing a new Hacker Pager revision to DEF CON 34, with planned online availability and BadgeLife Village pickup. Its official project site documents an ESP32-S3, Semtech SX1262 LoRa radio, monochrome LCD, microSD, USB-C, rechargeable LiPo power, buttons, speaker, vibration motor, LEDs, and open design sources; its current update page labels firmware 2.7.26.pager as DEF CON 34. Public electronics and case repositories publish KiCad/BOM and mechanical source material under CERN-OHL-S-2.0. This is sufficient evidence for a distinct, independently sold pre-event BadgeLife artifact associated with DEF CON 34, not evidence of DEF CON issuance, authorization, admission, a completed sale, pickup, delivery, final production configuration, or rights-cleared image.
nRF52840/SX1262 electronic conference badge with a public post-event GPL firmware archive
Hackers Teaching Hackers' official materials establish the June 3-5, 2026 Columbus-area practitioner conference with villages and a CTF. Zack Nagaich's public Eagle 5 repository labels itself the 2026 HTH conference-badge firmware and documents an nRF52840 plus SX1262 electronic badge with LEDs, USB roles, RNode/Reticulum-oriented firmware, on-badge CLI, and CTF source context. An attendee account independently says their light-up badge was part of the conference CTF, while the organizer has not directly published this 2026 repository or a distribution record.
Ticket-listed badge offering; specifications undisclosed
HackNWA's official 2026 conference page and organizer-linked Eventbrite registration establish the completed April 17 Bentonville event and its CTF / ASMb1337 hardware-hacking context. The current registration page marks sales ended. A contemporaneous ticket-listing capture records a separate USD 109 VIP Assembled Badge category alongside USD 55 General Admission. Together these sources support a real time-specific badge offering, but do not establish whether the item was an electronic device, a PCB kit, a conventional physical credential, or another kind of assembled artifact, nor whether it was produced, collected, or delivered.
Pre-event 555-timer analog Simple Add-On for DEF CON 34
HogFillet's live Uberflux listing calls this the HackThePlanet SAO for DEF CON 34. Its August 4, 2026 marketplace snapshot lists $24 and a seller state of 19 sold from a listed total of 23. A public DEF CON 34 maker self-submission by FakeBobby / HogFillet calls the same linked product HTP Graffiti and gives the same $24 price; the catalogue treats that exact product-URL match as a source-backed alternate listing name, not a second board. The maker describes a 555 timer clocking a ten-bit ripple counter whose outputs drive eight LEDs through the board's graffiti art, with an onboard trimmer controlling the flash rate. It explicitly says the board has no firmware and no I2C handshake, and says a separate button can be connected to the odd or even GPIO line of the DEF CON badge's SAO header. The listing announces Friday and Saturday Badge Life Booth pickup slots, with mailing or refund offered if a stated drop is missed. This is source-backed evidence for a pre-event independent analog SAO, not proof of final delivery, exact components or circuit values, host behavior, electrical safety, optical safety, conference authorization, admission, or reusable-image rights.
Youth-attendee conference identity artifact; handoff unverified
Hak4Kidz's official 2026 flyer says youth attendees receive a fun badge, with lunch, snacks, a T-shirt, and prizes, for its June 6 Chicago event. The official home calls the event Time Travel: Capture the Flag, but the sources do not identify the item's material, artwork, barcode/QR/RFID/NFC/electronic form, linkage to the CTF, allocation, or actual pickup/delivery.
Independent ESP32-S3 BLE and Wi-Fi scanner badge offered for DEF CON 34
DC801's live Helgatchi product page identifies a $120 portable, rechargeable BLE-beacon and Wi-Fi-access-point scanner/hunter with configurable alerts. It names a XIAO ESP32-S3, 8 MB flash, a 400 mAh 3.7 V LiPo, 1.69-inch 240 by 280 Waveshare LCD, six RGB LEDs, vibration motor, and external SMA-RP 2.4 GHz antenna path. Pips801's public repository contains separate hardware and firmware/UI trees, while the public DEF CON 34 Badgelife response identifies DC801 + 801 Labs' Helgatchi as a new badge associated with the August event. The listing remains an independent seller artifact with planned July pickup/shipping terms—not official DEF CON issuance, a Human badge, admission, confirmed recipient delivery, a fully audited detection device, an open-source license, or a rights-cleared image.
Official completed-event digital admission-ticket identity artifact; no 2026 badge publicly identified
HOPE On Planet Earth's official 2600 store listing sold a $250 HOPE 26 In-Person Pass and said digital admission tickets would be generated asynchronously and emailed before the event; it also says they are non-refundable but transferable. The official HOPE home now says the August 14-16 New Yorker Hotel conference is history, but the reviewed event, wiki, schedule, and ticket pages do not identify a 2026 physical or electronic conference badge. This record therefore models the known digital admission-ticket identity artifact only, not a recurrence of the 2024 HOPE XV electronic badge, an issued event badge, a final attendee credential implementation, or a rights-cleared image.
Maker-published planned SSTV badge project for HRV/DEF CON 34; physical unit unverified
The public `livitup/hrv-sstv-badge` repository describes itself as building an SSTV #badgelife badge for HRV at DEFCON 34. Its commit-pinned source contains a project README, native KiCad board files, and a status document dated March 22, 2026 that still records design and prototype milestones rather than a shipped unit. Ham Radio Village's own page independently confirms its DEF CON 34 event in Las Vegas on August 6-9, 2026, but does not identify or endorse this project. The sources therefore support a publicly documented planned independent electronic-badge project associated with HRV/DEF CON 34, not an HRV- or DEF CON-issued artifact, ticket benefit, access credential, completed unit, allocation, delivery, or rights-cleared image.
Pre-event RP2350B multi-protocol OT and automotive research badge
The ICS Village DEF CON 34 Badge is an official FREE-WILi page-documented, on-site / Vendor Village, while-supplies-last hardware badge for DEF CON 34. Its technical page specifies an RP2350B-A4 platform with RS485/Modbus RTU, CAN/CAN FD, 10BASE-T1S and 10BASE-T1L, a DB15 connector, OLED, encoder and RGB UI, storage, USB serial, FreeWili Porpoise Purpose Firmware, OneWili API support, and a stated 3.7 V / 1000 mA internal battery. As of this pre-event source pass, it is not a delivered-run or official DEF CON admission credential.
Minew MTB11 ambient-light-harvesting BLE conference tag
IEEE RFID 2026's official conference page advertised a complimentary twentieth-anniversary Bluetooth Low Energy badge, with 100 badges available. Its dedicated badge page identifies the active artifact as a custom-printed Minew MTB11 ambient-light-harvesting BLE tag. The source says that, when sufficiently charged from ambient light, it transmits a unique 48-bit identifier, battery voltage, and temperature in Bluetooth Low Energy advertisement packets. The technical-programme chairs' welcome confirms the June 16-18 Santa Fe conference occurred, but the sources do not establish individual receipt or final device state.
Custom-printed passive UHF/QR conference tag
IEEE RFID 2026's dedicated badge page identifies a second conference artifact: a custom-printed passive RAIN RFID/UHF tag that can also be optically associated with its conference identifier through a QR code. The page says each tag uses a unique 96-bit, sequential conference/demo identifier rather than a GS1-compliant retail EPC, and that the identifier contains no personal attendee information. The technical-programme chairs' welcome confirms the June 16-18 Santa Fe event, while the published sources do not establish recipient assignment, completed handoff, physical tag construction, or detailed QR behavior.
Bare-PCB attendee badge and five advanced prototypes
IEEE Rising Stars' official post-event Badge Project page says every 2026 attendee received a bare PCB with no components, while only about five manually assembled advanced badges were prototyped. A separate pre-event SEAL-Embedded source snapshot documents a Raspberry Pi Pico W BLE networking-badge development track, but neither source identifies it as one of those five units. The record therefore keeps the all-attendee bare-PCB and limited-prototype claims separate and does not treat a public development branch as a universal working badge.
Maker-documented ATtiny1604 soldering-challenge Simple Add-On
NerdFlare's public repository describes a 2026 iFixit Shitty Add On (SAO), while its repository description labels the project an iFixit DEFCON 2026 SAO. The commit-pinned README documents a physical PCB art badge with multiple LED animations, an interactive surface-mount soldering challenge, user-programmable firmware, an ATtiny1604-SS target, PlatformIO/Arduino code, and KiCad design files. A dated July 18 source commit says "Version 0.1 - FINAL: art, code, and PCB. 1000 made for DEFCON34." Those are direct project-publisher statements sufficient to retain a distinct pre-event DEF CON 34 artifact, but not proof of organizer issuance, iFixit corporate publication, event authorization, attendee allocation, actual handoff, admission function, a final unit-by-unit configuration, or reusable-image rights.
Independent PFC161 two-LED message SAO update announced for DEF CON 34
BigFuckingBadge's public DEF CON 34 Badgelife response calls IFLFU SAO an update to an existing SAO, lists it at $20, and says it illuminates the words "I FUCKING LOVE FUCKING YOU" with the two "FUCKING" illuminations randomized. The same maker's live DEF CON 34 page has an unlabeled $20 OffensiveSAO card about a simple rectangle that sends a message at random; the roster supplies the direct IFLFU name/repository mapping. Hexum064's public `iflfu-v2-pfc161` C source includes PFC161 headers and drives two active-low LED outputs, each with an LFSR-based timing state, while the public hardware repository carries KiCad front/back boards and schematics, BOM/position files, Gerbers, and SAO-spacer models. These sources establish a real planned independent electronic SAO update associated with DEF CON 34—not official conference issuance, admission, a fully recovered earlier lineage, completed fulfillment, final production parity, safe/electrically characterized hardware, a source-license grant, or a rights-cleared image.
Completed independent RP2040 CRT-TV Simple Add-On
INSPECTRON 34 is an independent retro-CRT television-shaped Simple Add-On documented by its maker's post-conference public repository. The project records an RP2040, 16 MB flash, 1.14-inch ST7789V display, CircuitPython, USB-drive GIF loading, a DC34 right-port SAO design, and a completed DEF CON 34 run of about 20 sold boards. The post-conference handoff identifies V5 as the current released firmware. It is not an official DEF CON Human badge or admission credential.
ESP32 weather and crank-powered quest badge
Kernelcon's 2026 Off Grid badge is an ESP32 weather-prediction and quest badge with BME280 temperature, humidity, and pressure sensing, twenty addressable RGB LEDs, AAA and hand-crank power modes, BLE/proximity scanning, and MicroPython firmware.
Independent ATtiny814 five-NeoPixel minibadge holder offered for DEF CON 34
Cabinet of Distinctm1nd's live Krampus Minibadge Holder listing is a $45 offer that displayed sold out in this August 4, 2026 source pass and limits DEF CON pickup to August 6-8 pickup attendees. The maker describes five NeoPixel LEDs, an ATtiny 814, microcontroller development-pin access, USB-or-battery power, and custom or pre-programmed themes; it says minibadge headers and the optional battery holder require soldering and shown minibadges are not included. The public `distinctm1nd/krampus_minibadge_holder` repository corroborates an ATtiny814 holder described as holding six minibadges, a five-LED firmware layout, button-selected theme code, and KiCad/BOM material. Its hardware archive includes a `saintcon_2025` filename, so the tree is an implementation and lineage source—not proof of completed SAINTCON distribution, final 2026 production parity, fulfillment, official DEF CON issuance, a complete source-license grant, or reusable-image rights.
Pre-event RP2350 infrared game badge with conditional LoRa score sync
Laser* Tag Badge DS is an independent BadgeLife project planned for DEF CON 34. Its maker page describes an RP2350-based infrared tag game with a 915 MHz LoRa score-sync option and QR fallback, while a public late-July update says the boards have arrived and final assembly and flashing are in progress. The record is pre-event and independent; it is not an official DEF CON admission badge.
Assembled electronic keyboard badge with blinkies and UV-resin art
LayerOne 2026's electronic attendee and speaker badge was a three-button keyboard with blinkies and a self-printed UV-resin artwork layer. The official Hardware Hacking Village material says attendees assembled the electronic badge in the village, and the official wrap-up confirms the completed event badge and its hand-repair response.
Pre-event yellow-LED art Simple Add-On for DEF CON 34
delphi's live Uberflux listing calls Luna a simple PCB add-on for DEF CON 34. Its August 4, 2026 marketplace snapshot lists $10, six sold, and 44 remaining, with on-site-only DEF CON 34 pickup and tentative Friday/Saturday BadgeLife Village times. The product says each approximately 57 by 50 mm unit is fully assembled and tested, has a standard 2 by 3 SAO header, and lights a yellow LED in Luna's forehead when connected to the DC34 badge; it explicitly says no adapter is needed. The source supports a real planned light-up art SAO and an independent event-acquisition claim, but not its exact LED part, circuitry, power/current behavior, broad host compatibility, final inventory, completed pickup, DEF CON organizer status, conference admission, or reusable-image rights.
Pre-event RP2350B interactive Simple Add-On planned for DEF CON 34
ParallelLogic's Uberflux listing, public MalO_SAO source/design repository, and first-hand Hackaday.io project diary document a planned DEF CON 34 Simple Add-On based on the SCP-1471-A MalO setting. The marketplace's August 4, 2026 snapshot lists $50, 43 sold, and 57 remaining. The repository says the units are intended for online sale and DEF CON 34 handout in August 2026, identifies an RP2350B, 16 MB external flash, 1.5-inch 128 by 128 grayscale OLED, standard six-pin SAO header, USB-C, capacitive touch, potentiometer, buzzer, microphone, hall sensor, IMU, ambient-light sensor, IR transmit/receive, NFC/RFID, and LED banks. Its project diary confirms the work is ongoing and documents early prototype testing. The repository declares the work CC BY-SA 3.0. This is a source-backed pre-event independent badge record, not proof that a final revision has shipped, that all promoted functions are complete, that every radio/sensor interaction is safe or private, that a named third-party lore asset grants image rights, that the project is DEF CON-issued, or that it grants admission.
Pre-event red-eye art Simple Add-On with no described AI software
coryallegory's live Uberflux listing calls this METROPOLIS AI SAO and says it is inspired by Maria, the art-deco automaton from Fritz Lang's 1927 Metropolis. Its August 4, 2026 marketplace snapshot lists $20, 20 sold, and ten remaining, with a free Saturday BadgeLife Village pickup label and a pre-order statement for DEF CON 34 or BSidesLV pickup. The maker says each fully assembled unit uses a standard 2 by 3 SAO header and has a red eye that glows when powered through that header. The listing supplies no description of a model, application, controller, firmware, or other artificial-intelligence capability. This is a source-backed pre-event independent LED art SAO record, not evidence of AI software, final manufacture, completed pickup, universal electrical compatibility, use rights in the film inspiration, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Planned $20 independent Simple Add-On with a maker-stated surface-mount update
Rex's public DEF CON 34 Badgelife response labels MF Doom SAO v2 as an update to an existing SAO, marks it Coming soon, and gives a $20 price. The source-named Reddit account u/Truth-Miserable independently posted MF Doom SAO v2, said a limited original run existed the previous year, and said its parts will be surface mounted this time. Later maker comments describe direct-message preorders and planned local handoff near the Las Vegas Convention Center. These public maker statements establish a real planned independent 2026 v2 artifact, not an official DEF CON issue, admission credential, completed manufacture or delivery, a documented electrical implementation, firmware/source release, a rights-cleared image, or affiliation with MF DOOM or a rights holder.
Pre-event independent ESP32-C3 touchscreen badge project for DEF CON 34
Aask42's public MidWestCoastBadge repository identifies an independent MidWestCoast Badge project, labels its firmware as DEF CON 34 badge firmware, and frames it around a MidWestCoast Party / IoT-hacking context. Its commit-pinned firmware README names an ESP32-C3 driving a 240×320 ST7789 IPS panel plus a capacitive touch controller at I2C address 0x15, with swipe-and-tap controls and no buttons. A project MVP note identifies the Arduino/C++ tree as the current implementation. DEF CON's own registration page independently establishes the August 6-9, 2026 Las Vegas conference context. These sources support a real pre-event independent electronic-badge project associated by its publisher with DEF CON 34, not proof of final physical units, party or event authorization, DEF CON issuance or endorsement, allocation, price, delivery, attendance, admission, deployed firmware, or reusable-image rights.
Sold-out independent three-SAO monorail badge for DEF CON 34
Zach's Hacks' live Shopify listing calls the Monorail Con Badge sold out and says preorder customers will receive pickup details by email, while noting there may be a few extras to trade in person. Its current public product payload marks all three purchase options unavailable: a $65 badge-and-SAOs option, a $150 bundle option that adds Dani.pink's separately made Laser* Tag Badge DS, and an $80 voluntary extra-payment option. The listing describes a small monorail on a track, a clip for a paper ticket not included, three SAOs, a speaker/mini-SD sound surface, blinky lights, and a regulated 3.3 V supply from two AAA batteries. The maker explicitly says final versions may vary and that it has no affiliation with the Las Vegas Monorail. This is a source-backed independent pre-event badge record, not evidence of final manufactured specification, fulfilled pickup/trade, included transit fare, common hardware/firmware ownership with the bundled Laser* Tag badge, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Founder-announced 3D-printed/NFC badge for Pirate Pieces of Eight
NaClCON's official registration included a NaClCON Badge and access to the Pirate Pieces of Eight CTF, while the official schedule listed a CTF and Badge Intro. A public pre-event announcement by founder Luke McOmie (Pyr0) describes a 3D-printed/NFC conference badge for the Pieces of Eight CTF and Pirate Scavenger Hunt. The event later occurred, but no reviewed post-event source directly establishes final badge fabrication, attendee handoff, or the announced NFC implementation, so this is retained as a source-backed pre-event artifact announcement rather than a shipped-hardware claim.
Independent ATtiny1614 DEF CON 34 badge-challenge fuzzer SAO
NilbinSec's public DC34 Main Badge Fuzzer SAO repository documents a standalone SAO designed to exercise interfaces on the official DEF CON 34 Human badge using information published before the conference. Its README describes three initial modes: GPIO1/GPIO2 stimulation on the left SAO port, an open-drain CPU wake assertion on GPIO4 of the right port, and an I²C-address listening sweep. The repository provides a KiCad schematic, BOM CSV, PCB archive, C firmware, and compiled hex/ELF files. The README explicitly warns that Mode 1 may harm the main badge and says a convention reflash might follow. This is source-backed pre-event independent challenge hardware, not proof of a finished run, sale, giveaway, pickup, compatibility with a final main-badge revision, authorization to probe another badge, official DEF CON issuance or admission, a reusable-image grant, or an explicit software/hardware licence.
Independent planned free PAC-MAN Ghost SAO giveaway for DEF CON 34
NilbinSec's public DEF CON 34 Badgelife response names a new PAC MAN Ghost SAO, calls it free, says 1,000 will be given away, and promises social-media and village drops plus a Day-1 GitHub post. A first-party NilbinSec Bluesky reply in its Spectre Sniffer launch thread separately says a purchase includes a PAC-MAN Ghost SAO and helps fund more than 1,500 free SAOs for Vegas. The live Spectre Sniffer listing says it includes one Pac-Man Ghost SAO in one of four colors. Those sources establish a real planned companion SAO and current event association, but they do not establish whether the 1,000 giveaway, purchase-included, and four-color statements describe the same physical revision/variant; an electronic design, connector specification, final artwork, actual drop, GitHub release, official DEF CON issuance/admission, reusable-image permission, or third-party intellectual-property authorization.
Independent planned 500-unit Power Glove SAO re-release for DEF CON 34
NilbinSec's public DEF CON 34 Badgelife response identifies a Power Glove Re-release SAO as a free giveaway: 500 units, with drop announcements on social media and at the Badgelife Village, and a stated plan to post it to NilbinSec GitHub on DEF CON Day 1. The maker's existing DC32 Power Glove SAO repository preserves a historical fabrication/assembly trail—Gerbers plus a bill of materials with two 470-ohm resistors, three flashing RGB LEDs, one cloudy red LED, and a 2×3 shrouded SAO header. It does not publish a 2026-specific repository, firmware, change log, or production record. This is a source-backed planned independent re-release, not proof that the 500 units were made, dropped, received, electrically identical to the DC32 design, officially issued by DEF CON, usable for admission, licensed for reuse, or represented by a rights-cleared image.
Planned open-hardware CH32V003 light-up Simple Add-On for DEF CON 34
The maker-owned public `keeloi79/not-a-crosswalk-sao` repository explicitly calls Not Just a Crosswalk a Simple Add-On (SAO) project for DEF CON 34. Its README documents a CH32V003 F4P6 RISC-V controller, eighteen side-emitting addressable LEDs, persistent palette/effect settings, two controls, 3.3 V host-badge power stepped to 5 V or a USB-C 5 V input path, and claimed SAO V1.69bis/V2.0 compatibility. The source tree includes documentation, schematics, firmware, build instructions, and a three-part license declaration: CERN-OHL-S v2 hardware, GPLv3 firmware, and CC BY-SA 4.0 documentation/creative works. This is a source-backed planned independent DEF CON 34 add-on, not evidence of a final manufactured run, price, sales channel, quantity, pickup, recipient, host-badge test matrix, electrical-safety validation, official DEF CON affiliation, admission right, or rights-cleared badge image.
Pre-event ATMEGA328 multi-layer BadgeLife soldering kit
NYC Badge is an independent, pre-event BadgeLife soldering kit offered through Uberflux's Def Con 34 Badge Pickup. The storefront lists a $60 Original option and, at this August 3 source pass, shows the 20-kit listing as OUT with zero remaining and 20 sold. Its published kit list names a layered PCB build, pre-soldered lights, a pre-flashed ATMEGA328, crystal, passive parts, switches, an AAA holder, and included SAO material. This records a real upcoming small-run hardware listing, not final pickup, completed attendee delivery, or an official DEF CON admission credential.
Open ESP32-S3 Chicago builder-festival hardware badge
Onion DAO's official 2026 Chicago festival page says every accepted attendee gets a hardware badge at registration, with most components already on the board and a final soldering step. The same official site links to OnionDAO's public oniondao-badge repository, which documents a hacker-conference-style ESP32-S3 design, optional RF/audio modules, a display socket, secure element, expansion ports, and source trees for hardware and software. The public record supports a real organizer-published artifact and design, while exact recipient allocation, completed assembly, and final attendee population remain unverified.
SauceBot / Arduino Sopracciglio electronic badge with a post-event KiCad archive
Open Sauce 2026's SauceBot badge is documented by Caleb Marting's post-event public archive as an Arduino MKR Zero-compatible electronic badge with native KiCad sources, firmware, a microphone, button, red LEDs, battery holder, and optional Simple Add-On headers. The archive says at least two attendees hacked badges Saturday night and brought four new games on Sunday; an independent attendee firmware archive also describes receiving an eyebrow module and replacing the original Bop It-style firmware. Together the sources establish a real festival artifact and hands-on hacking trail, not a universal attendee allocation or organizer-owned source release.
Independent planned sensor-described Original Series Tricorder badge sale at DEF CON 34
MakeItHackin's public DEF CON 34 Badgelife response lists a new Original Series Tricorder badge, says it will be available on-site at DEF CON through Hacker Warehouse for approximately $125, and describes it as celebrating 60 years of Star Trek with various sensors. The source field for the current badge is still marked TBD. The same maker's public Tricorder SAO repository, tutorial, and live $30 Tindie listing document a differently named 2025 Tricorder SAO with separate badge-powered and rechargeable-battery forms. Those historical sources establish a related public maker lineage, but they do not map their electronics, LEDs, battery/USB-C details, form factor, price, or distribution to the current $125 Original Series Tricorder badge. This is a source-backed planned independent sensor-described event artifact, not proof of a completed sale, disclosed sensor suite, electronic design, final hardware/firmware, historical-SAO parity, official DEF CON issuance or admission, reusable-image permission, or Star Trek rights-holder authorization.
Independent CH32V003 bare-metal UART crypto-puzzle badge offered toward DEF CON 34
K Badges' maker-controlled Tindie listing identifies Ouroboros as a $29.99 bare-metal RISC-V-assembly electronic badge on a CH32V003, with a custom UART cryptographic puzzle, a 12-LED Charlieplexed matrix, a circular single-layer PCB with exposed traces, and a hand-soldered two-AA configuration. Its August 4, 2026 storefront snapshot is out of stock; the seller says a new order is coming and hopes to bring some to DEF CON, rather than confirming units, arrival, pickup, or delivery. In a first-person r/Defcon announcement, the maker says they created the project and links the Tindie page and a GitHub technical explainer, while separately offering to arrange a DEF CON pickup by email for Tindie buyers. The product also makes 115200-baud puzzle, cryptographic-framework, low-power, and performance statements, but neither the product nor the maker-linked generic AVR framework establishes a released matching CH32V003 firmware or hardware package. This is a source-backed independent pre-event maker offering, not an official DEF CON badge, registration credential, confirmed fulfillment, verified cryptographic implementation, hardware-safety record, or reusable-image source.
Source-published 15-pixel touch SAO firmware project; physical artifact and handoff unverified
Punk Security's public repository calls its Arduino sketch "the firmware for the OWASP DefCon 34 SAO." Its final public source snapshot provides an actual `main.ino` rather than an event-labelled name alone: it defines 15 addressable RGB pixel positions, three PTC capacitive-touch nodes, and a README that says the SAO header exposes UPDI for reprogramming. This clears the catalogue threshold for a named, source-published pre-event electronic add-on project. It does not establish a final PCB, microcontroller, power path, exact SAO specification, fabricated unit, approved OWASP or DEF CON relationship, price, allocation, pickup, delivered handoff, credential function, or reusable image rights.
Officially announced pre-event volunteer access credential
Payment Village's official DEF CON 34 volunteer notice says volunteers will receive access to the conference through a village badge, alongside a village T-shirt and learning opportunities. The village's official event page confirms the August 6-9 Las Vegas programme. This source-backed record models the stated pre-event volunteer identity/access artifact only; it does not identify a physical form, electronics, access-control mechanism, issued quantity, or a connection to the separate 2025 Vulnerable ATM Badge.
Pre-event planned electronic shelf-label follow-up
A conservative pre-event record for Tyler Crumpton's public plan to bring an even cooler MK.II electronic shelf-label badge to PhreakNIC 27, currently scheduled for November 6-7, 2026.
Pre-event CH32V303 Portal puzzle badge from a public DC34 source tree
BigFuckingBadge's live DEF CON 34 page calls this year's Portal Badge a 14×14-inch Companion-Cube-shaped, touch-activated badge, marks presale open with limited quantities, and advertises $120 before DEF CON 34 or $150 through hackerwarehouse during the con. A public GitLab hierarchy at `hexum-public-share/bfb/dc34/public/badge/portal-badge` contains separate software, hardware, and sound projects for the same Portal-themed badge. The source names a `ch32fun-portal-badge` firmware project and a `ch32v303-48lqfp-portal-badge` board project; its current software configuration targets a CH32V303CBT6 with PlatformIO and ch32v003fun. The committed firmware defines 85 LED pixels, fourteen active-low inputs, SD-card-backed audio with DAC playback, flash-persisted unlock state, a serial Portal Gun SAO/badge-to-badge protocol, and diode-solder-on detection. Its design document describes standby, Nyan, and a four-level Portal puzzle game built around spheres, portals, fire, and unlockable features. Public commits show software “final code checks” and hardware acrylic SVG work on August 2, 2026. This is a source-backed pre-event independent record, not proof of a completed sale, physical run, event allocation, pickup, official DEF CON credential, final binary, safety validation, third-party-IP permission, or reusable-image rights.
Independent PFC161 touch-and-four-LED companion SAO announced for DEF CON 34
BigFuckingBadge's public DEF CON 34 Badgelife response lists a new $20 PORTAL gun SAO and says touching its end changes animated colors and interacts with the PORTAL Badge. The maker's live DEF CON 34 page independently describes a $20 Portal-gun companion with blue, orange/red, and off modes plus interaction with that year's Portal Badge. Hexum064's public `portal-gun-sao-dc33-code` source targets PFC161, defines a four-pixel LED buffer, blue/orange color states, a capacitive-touch threshold, and a touch-triggered state update; the public hardware tree holds KiCad, BOM/position, Gerber, and acrylic files. The source repositories retain `dc33` in their names, so they are an implementation/reuse trail rather than proof of a newly designed or unchanged 2026 production revision. Together the sources establish a real planned independent electronic SAO associated with DEF CON 34—not official DEF CON issuance, admission, confirmed fulfillment, a finalized host-compatibility claim, final hardware/firmware parity, third-party-IP permission, a source-license grant, or a rights-cleared image.
Sold-out independent Puzzled Hackers LED meetup badge for DEF CON 34
Puzzled Hackers' own CTF checkout page calls this a limited-edition LED badge for DEF CON 34 and, in the August 4, 2026 source pass, lists $20 including tax, in-person pickup at the Linq 3535 / Circle Bar on Wednesday August 5 and Thursday August 6 from 7–10 PM PT, no shipping, and exhausted online allocations. A contemporaneous Puzzled Hackers Team announcement says the top 50 CTF participants received free-badge redemption on their accounts, remaining sales were capped to break even, further badges would move to random giveaways after the cap, and collection requires a meetup or arranged DEF CON handoff using an offline QR claim code. It also explicitly says the meetup is free and that an actual DEF CON badge is not required for the first Wednesday gathering. The sources support a real, independently distributed LED badge and a community CTF/meetup context, but not its physical construction, components, firmware, final quantity, free-claim count beyond the stated top 50, delivery, event authorization, DEF CON organizer affiliation, admission, or reusable-image rights.
Post-event STM32U073 badge with MIT firmware, AI control, and CTF surface
A post-event official RHC firmware release documents the AI-Connected DEF CON 34 badge as an STM32U073 device with a 1.54-inch 200×200 e-paper display, two WS2812 eyes, arm LED, buzzer, vibration motor, NEC infrared, CH340 USB serial, four buttons, on-badge CTF challenges, and AI Interactive Mode. The MIT-licensed source and binary were published August 18-20 after the scheduled August 6-9 Las Vegas programme. This establishes a released badge platform, not a recipient count, individual pickup, or a complete production ledger.
Pre-event ATtiny1616 cedar interactive Simple Add-On for DEF CON 34
MakeItHackin's live Uberflux listing describes Root Access as a home-milled Tennessee-cedar add-on built for the DEF CON 34 badge and says it also works with a standard six-pin SAO header. Its August 4, 2026 marketplace snapshot lists $50 and a seller state of 15 sold from a listed total of 100, with BSides Las Vegas and Linq Circle Bar drop labels. The maker's public RootAccess guide independently identifies an ATtiny1616, ten addressable RGB pixels, eleven discrete LEDs, fifty built-in animations, a physical button, I2C address 0x50, and non-volatile USERROW state. It documents standalone operation and host-controlled lighting over I2C, plus separate GPIO 1 and GPIO 2 circuits that can be used as LED outputs or button inputs. This is a source-backed pre-event independent SAO record, not proof of final manufacture, actual drop handoff, every listed compatibility claim, safe electrical integration, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Planned $80 Red Team Village badge with an on-site sale statement
Red Team Village's own public DEF CON 34 Badgelife response lists a new badge named RTV D20, says it will be available on site at DEF CON through the village, and gives an $80 price. The Village's official events page places Red Team Village at the Las Vegas Convention Center on August 6-9, 2026. These primary event and self-submission sources are sufficient to seed a planned village-associated artifact, but they do not identify whether the badge is electronic or non-electronic, its physical design, any components, functions, firmware, game, CTF role, quantity, final sale outcome, registration relationship, or reusable-image rights.
HackRVA firmware and simulator badge archive
RVAsec 2026 is now source-backed beyond the earlier package listing: the public HackRVA `badge2026` repository preserves Badge 2026 firmware, simulator/build instructions, UF2 flashing workflow, app source, image assets, and June 10, 2026 release binaries after the June 9-10 conference.
Pre-event main badge with 2.54 mm MiniBadge sockets
SAINTCON 2026 is represented by a conservative planned electronic-badge record: official pages state that the 2026 conference badge will have MiniBadge sockets on the standard 2.54 mm grid, while the sponsor prospectus distinguishes Electronic Badge and Non-Electronic sponsor-ticket types. The October event has not happened yet, so this record does not present the artifact as shipped.
limited first-180 ticket PCB badge
SECCON 2026 is represented by an official pre-event ticket source that says eligible passes include a PCB badge with CTFs and features, limited to the first 180 registrants.
Official interactive PCB ticket-tier badge; post-event delivery remains unverified
An official SecretCon 2026 Digital / Circuit Badge ticket-tier artifact advertised as an interactive circuit-board PCB badge for the June 4-5 St. Paul, Minnesota conference. The registration listing says the tier included a printed physical program and admission to talks, hands-on hubs, exhibitors, contests, and the official party; it separately describes a higher Extreme Badge tier with collectible electronic and upgraded-PCB wording, without establishing whether the physical boards were different.
Pre-event sold-out RP2040 dual-SAO BadgeLife restock
Uberflux lists Shitty Kitty V2 under the `lipo` maker handle and Uberfoo Heavy Industries, with DEF CON 34 as its only listed drop. At this August 3 source pass, the $75 listing is marked OUT with zero remaining and 15 sold, and says new stock is available for DEF CON 34 pickup. Its maker-published description names dual 0.96-inch color IPS screens, an RP2040 platform, two fully connected 1.69bis SAO ports, USB-C, LiPo power/charging components, five user buttons, a boot button, and SkittyOS features. It also announces new firmware with graphics and puzzles, but provides no release link. This is a documented pre-event restock listing, not proof of final pickup, a completed firmware release, a reproduced engineering archive, or an official DEF CON admission credential.
Publicly announced 100-unit ESP32-S3 badge offering planned for DEF CON 34
A contemporaneous public r/Defcon post calls this a Sneakreaper limited-edition DEF CON badge and says only 100 would be available at a Sneakreaper Industries booth; the post author later replies with Hall W4 and $150. The same post names an ESP32-S3-MINI-1-N8, Wi-Fi, Bluetooth, 13.56 MHz NFC, and programmable LEDs. Crucially, it says that most listed capabilities will not be ready out of the box: only LED colour/brightness changes, a hidden software CTF or scavenger hunt, and NFC read/write are marked as available on DEF CON day 1. The official DEF CON forum fixes the related conference at the Las Vegas Convention Center on August 6-9, 2026. These sources support a real independently announced pre-event hardware offering with a bounded day-one feature claim, not verified seller identity or Sneakreaper Industries relationship, official booth authorization, completed manufacture, final inventory, sale, handoff, electrical design, firmware release, future functionality, lawful-use assurance, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Pre-event sold-out XIAO ESP32S3 EMF BadgeLife release
NilbinSec's live Uberflux listing identifies the Spectre Sniffer Badge as a limited DEF CON 34 release. At this August 3, 2026 source pass, the $80 listing shows 80 sold and no units remaining. Its maker-published description names a XIAO ESP32S3, a live EMF detector with a real-time spike graph, a randomized-word Spirit Box whose output rate follows the stated EMF signal, a SAO v1.69bis connector with I2C, one included Pac-Man Ghost SAO in one of four colors, a protected 18650 battery and lanyard, and one- and two-player arcade games. The seller says release is pickup only at the BadgeLife Village and announced LVCC locations, with missed drops donated at closing ceremonies. This is a source-backed pre-event independent BadgeLife record, not proof of final handoff, finished firmware, component-level engineering, instrument accuracy, electrical safety, official DEF CON admission status, or reusable-image rights.
Independent planned Hak4Kidz Lab Phaser v2.2 SAO sale at DEF CON 34
Hak4Kidz Lab's public DEF CON 34 Badgelife response lists Star Trek SAO Phaser v2.2 as a new SAO, links a maker video with that exact title, says it can be purchased from Hacker Warehouse at DEF CON, and gives an approximately $35 price. The maker's live Tindie product page also identifies Star Trek SAO Phaser v2.2 as a Hak4Kidz Lab electronic badge wearable and a fun blinky add-on. That page says it can attach to a Badgelife-supported SAO 1.69bis connector, describes side-view and shine-down LEDs illuminating the PCB, barrel, and top tracer, and calls the SAO connector a DIY soldering part. It also says the named v2.2 listing was made for DC31 and is a follow-up to a 2019 v1; its coin-cell pin-wear path was still in works. These sources establish a real planned independent current-event sale and a historical same-name product lineage—not completed DEF CON sales, confirmed Hacker Warehouse stock, a final 2026 production/revision mapping, a supplied coin-cell wearable configuration, a complete circuit/firmware archive, official DEF CON issuance or admission, reusable-image permission, or Star Trek rights-holder authorization.
Pre-event independent BLE number-station puzzle badge for DEF CON 34
Station 562 is a source-conservative independent DEF CON 34 badge record from its public maker announcement. The project owner describes a proximity-controlled badge with a BLE number-station puzzle, red-versus-blue proximity game, autonomous social/dance mode, expressive BLE MIDI instrument, tamper-evident mode, Setup menu, and optional hardware CTF. In follow-up comments, the maker reports about 55 units made so far, signed firmware with a distinct key pair per badge, a constrained giveaway/sale plan, and RGB blank boards that omit the OLED, LiPo, and ESP32 module. No public repository, schematic, firmware release, final availability ledger, or reusable-image permission was recovered.
Organizer-revealed pre-event badge and lanyard
Telecom Village's official organizer account has introduced an all-new Telecom Village badge and lanyard for DEF CON 34. The same account previously said its badge package had been received and badges secured, while the official village site identifies PCBWay as Badge Sponsor. Those primary sources establish a real pre-event village artifact and accompanying lanyard, but do not establish its construction, electronics, final recipient scope, credential role, or completed handoff.
MIT-licensed ESP32-S3 badge with Doom, MicroPython, and IR boop
An official Temporal Replay 2026 developer-conference badge documented by the MIT-licensed temporal-community/badge.temporal.io repository as an ESP32-S3 app platform with an OLED and LED matrix, a Doom port, MicroPython, and infrared boop badge-to-badge networking, for the May 5-7, 2026 event in San Francisco.
Pre-event RP2350 temperature-measuring Simple Add-On for DEF CON 34's BCCC
The live maker listing for The Beer SAO, the public `aerospace-venoms/BCCC_Temperature_SAO` source tree, and BCCC's own DEF CON 34 page document an independent temperature-measuring Simple Add-On associated with the Beer Chilling Contraption Contest. The marketplace's August 4, 2026 payload shows a $45, 150-unit presale with 28 sold and 122 remaining, two BadgeLife Village pickup slots, and no shipping. It describes a roughly 100 mm beer-cup SAO with a waterproof temperature probe, triple seven-segment display, RP2350 with 2 MB flash, USB-C, and a supplied 180-degree adapter for the upside-down DC34 host ports. The source tree identifies an RP2350A, W25Q16 flash, DS18B20 temperature sensor, RGB-independent brightness control, Pico-SDK firmware, KiCad design files, a versioned UF2, and batch programming/soak-test tooling; it says BCCC winners receive copies while stock lasts. This is a source-backed pre-event independent badge record, not proof of final manufacture, pickup, contest results, host compatibility, temperature accuracy, safety, final firmware, DEF CON organizer endorsement, conference admission, or reusable-image rights.
Public player-guide electronic challenge badge; allocation unverified
BigDawgDave's public GitHub repository describes itself as the public repository for a DEF CON 34 RM-Cyber challenge badge called The Shattered Shard. Its Player Guide tells participants to use an assigned badge with a charged battery, a local Wi-Fi/browser interaction, a data-capable USB cable, a serial terminal, and one labelled-jumper task. It is enough evidence to preserve a separately named, independently documented pre-event electronic challenge badge, but it does not prove the RM-Cyber relationship, organizer authorization, hardware provenance, sale or giveaway, run size, allocation, physical handoff, completed on-site use, admission function, or a rights-cleared image.
Sold-out pre-event Lepi Labs UPDI-programmer moth Simple Add-On for DEF CON 34
Lepi Labs' own Uberflux listing identifies UPDeeDeeI as a DEF CON 34-drop moth Simple Add-On. Its August 4, 2026 marketplace state is out of stock, with seven sold, zero remaining, and a $35 listed price. The maker says a CH340E USB-to-serial converter supports UPDI programming of compatible ATtiny devices, names an onboard ATtiny814 with two RGB LED eyes, and describes USB-C plus a flexible FPC tongue used as a functional USB cable. It also claims configurable 3.3 V or 5 V UPDI voltage, SAO or included CR2032 power, and v1.1 pre-event corrections including an FPC power fuse. Lepi Labs' first-hand DC34 announcement corroborates planned Friday and Saturday BadgeLife Village drops. This is a source-backed pre-event independent programming-tool SAO, not proof of final board revision, safe programming configuration, USB/FPC durability, compatible target coverage, delivery, host compatibility, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Sold-out pre-event Lepi Labs novelty VOC-indicator Simple Add-On for DEF CON 34
Lepi Labs' own Uberflux listing identifies the Volatile Organic Canary as a DEF CON 34-drop Simple Add-On. Its August 4, 2026 marketplace state is out of stock, with 11 sold, zero remaining, and a $45 listed price. The product describes an SGP40 VOC sensor plus SHT4x temperature/humidity sensor, a two-character fourteen-segment display, RGB LED, ATtiny1616-S controller, UPDI reprogramming, SAO or included CR2032 power, and a lanyard clip. Its maker explicitly says the device is novelty-only and must not be relied on for accurate air-quality measurements; it also records a ten-minute VOC-index warmup and a v1.0 board-order/remediation plan. Lepi Labs' first-hand DC34 announcement corroborates planned Friday and Saturday BadgeLife Village drops. This is a source-backed pre-event independent sensor SAO, not proof of final manufactured hardware, sold orders, safe or accurate air-quality measurement, delivery, host compatibility, DEF CON organizer affiliation, conference admission, or reusable-image rights.
Pre-event ESP32-C3 commemorative badge for Whose Slide's tenth DEF CON year
Whose Slide Is It Anyway?'s maker storefront offers a $75 10 Year Anniversary Badge and says it is limited to 100 units. The listing describes an ESP32-C3, 24 RGB LEDs, three pre-programmed sound effects with corresponding light shows, and a silkscreen replication of its Whose Slide gong artwork. Its public Shopify product payload currently marks the only variant unavailable; that is an availability snapshot, not evidence that all 100 were made, sold, shipped, or collected. The maker says buyers may arrange DEF CON pickup this year or shipment by early August. The current public DC34 contest listing describes 2026 as the contest's tenth year, and the public DC34 BadgeLife index separately lists this artifact. This is a source-backed independent pre-event commemorative badge record, not proof of final production, final firmware/board revision, completed charity distribution, official DEF CON affiliation, conference admission, or reusable-image rights.
Pre-event RP2350 CTF-adventure BadgeLife badge for DEF CON 34
BigTaro's own Wordweaving Badge project page and live Uberflux listing describe an independent DEF CON 34 top-down adventure / CTF badge. The current maker payload shows a $120 100-unit presale with 41 sold, DC34 pickup, and post-con shipping; it also says the badge would be $140 at the maker-described Hacker Warehouse booth during the conference. The maker describes an RP2350 with 4 MB flash, 16 RGB addressable LEDs, a 128×128 grayscale display, rechargeable LiPo via USB-C, and a fully addressable SAO port. It publishes game, CTF, multiplayer, word-building, and optional-component claims, but says hardware documentation and a stub firmware will only be provided after the conference. The project page says 30-plus CTF puzzles while the live listing says 35-plus, so the record preserves a broad maker-described challenge surface rather than resolving the discrepancy. This is a source-backed pre-event independent badge, not proof of final hardware/firmware, shipment or pickup, game availability, CTF completion, venue authorization, DEF CON affiliation, conference admission, or reusable-image rights.
Post-event Pimoroni Blinky 2350 developer-conference badge; organizer allocation unverified
A public post-event app archive by Mainak Sarkar identifies a Pimoroni Blinky 2350 badge as handed out at Workday DevCon 2026 and says it ran the badgeware MicroPython operating system and app launcher. Workday's official pages establish the completed June 1-4 Las Vegas developer conference, but do not directly document badge issuance, recipient allocation, custom hardware, event firmware, or image rights. This is therefore a source-backed event badge record with intentionally limited organizer attribution.
Events
The July 9-11, 1993 first DEF CON edition represented here by official announcement and media-archive evidence of pre-electronic name-tag and paper-badge artifacts.
The July 22-24, 1994 DEF CON edition represented here by official-photo evidence of pre-electronic printed chest credentials.
The August 4-6, 1995 DEF CON edition represented here by official-photo evidence of pre-electronic colored waist credentials.
The July 26-28, 1996 DEF CON edition represented here by official-photo evidence of a pre-electronic chest identity credential.
The July 11-13, 1997 DEF CON edition represented here by official-photo evidence of a pre-electronic hanging identity credential.
The July 31-August 2, 1998 DEF CON edition represented here by official-photo evidence of pre-electronic lanyard and waist credentials.
The July 28-30, 2000 DEF CON edition represented here by official-photo evidence of a pre-electronic lanyard identity badge.
The July 13-15, 2001 DEF CON edition represented here by official-photo evidence of a pre-electronic lanyard identity badge.
The August 2-4, 2002 DEF CON tenth-anniversary edition represented here by an official-program and media-archive pre-electronic physical badge artifact.
The August 1-3, 2003 DEF CON edition represented here by an official-media-archive photographed pre-electronic human badge.
The July 30-August 1, 2004 DEF CON edition represented here by a source-backed unofficial forum-badge identity artifact; the main official badge remains source-limited in this pass.
The July 29-31, 2005 DEF CON edition represented here by a public-domain photographed human badge from the final pre-electronic-badge era.
The 2006 DEF CON edition whose Joe Grand-designed PCB badge introduced active electronics, open circuitry, colored attendee-role variants, and a badge-hacking contest to DEF CON.
The 2007 DEF CON edition whose Joe Grand / Grand Idea Studio badge used an MC9S08QG8, a 95-LED matrix, capacitive sensors, optional accelerometer and RF footprints, customizable scrolling text, and another badge-hacking contest.
The 2008 DEF CON edition whose Joe Grand badge combined SD-card file transfer, infrared exchange, TV-B-Gone behavior, role-color variants, and a hackable Freescale reference platform.
The July 30-August 2, 2009 DEF CON edition whose Joe Grand / Grand Idea Studio badge used a Freescale MC56F8006 digital signal controller, MEMS microphone, RGB LED, wired badge-to-badge interface, bootloader, role-shape puzzle pieces, and a 32-entry badge-hacking contest.
The 2009 Ninja Networks DEF CON party edition whose electronic invitation badge was built in a 500-unit hand-assembly sprint and later published with schematic, Gerber, BOM, and public-domain firmware archives.
The 2010 DEF CON edition whose lithographed-aluminum badge used a low-power Kent Displays cholesteric display, USB, role variants, and a polished hackable-jewelry form factor.
The August 4-7, 2011 DEF CON edition whose Ryan Clarke / 1o57 badge deliberately moved away from electronics into a commercially pure titanium physical puzzle, interaction, and conference-participation artifact.
The October 7-9, 2011 ToorCon San Diego 13 edition whose public conference metadata and Great Scott Gadgets badge page document an RF spectrum-analyzer badge tied to Project Ubertooth.
The 2012 DEF CON edition whose Ryan Clarke-designed Parallax Propeller badge mixed IR badge-to-badge communication, many physical badge styles, firmware releases, VGA/PS2 expansion, and a crypto/social badge challenge.
The June 15-16, 2012 RVAsec edition whose HackRVA repository preserves the RVAsec Badge 2012 hardware, Gerbers, documentation, graphics, and release firmware source.
The October 19-21, 2012 ToorCon San Diego 14 edition whose public conference metadata and Great Scott Gadgets badge page document a USB-controlled sub-1 GHz RfCat badge.
The 2013 DEF CON edition whose Ryan Clarke-designed playing-card PCB badges intentionally blurred non-electronic identity art, circuit-board construction, continuity testing, role variants, and a cryptographic badge challenge.
The May 31-June 1, 2013 RVAsec edition whose official registration update and later badge-team interview document electronic HackRVA badges with LEDs, infrared interaction, audio, USB, and badge-game behavior.
The April 2014 Arizona hacker/security conference edition whose public attendee-maker writeup preserves a 300-piece PCB badge giveaway with HeatSync Labs soldering-booth context.
The 2014 DEF CON edition whose Parallax-built Propeller 1 badge used infrared, touch pads, LEDs, full I/O access, role variants, C code releases, and badge-contest mechanics.
The tenth Hackers On Planet Earth conference, held July 18-20, 2014 in New York City, represented by a CC0-documented physical admission badge issued at the event.
The 2014 RVAsec edition whose official preview and firmware-release post document a redesigned HackRVA electronic badge with public firmware, bootloader goals, games, LCD, IR, capacitive sliders, LEDs, speaker, micro USB, and PIC32 hardware.
The October 20-23, 2014 SAINTCON edition in Ogden, Utah, whose first-hand attendee/project-owner write-up, SparkFun repost, and Hackaday coverage document an Arduino-compatible conference badge designed for soldering, hacking, and hidden Hacker Challenge secrets.
The October 16, 2015 Portland Security BSides edition whose official schedule lists the Electronic Taxidermy: Badger Hacking workshop with Michael Leibowitz and whose PDX Badgers repositories preserve the public Badger PCB and firmware archive.
The 2015 DEF CON edition whose official Ryan Clarke / 1o57 badge went fully analog as a playable 7-inch vinyl record with lanyard ciphers, groove clues, role colors, audio clues, and a noir badge challenge.
The May 23-24, 2015 LayerOne edition whose official Hardware Hacking Village archive and CharlieX Hackaday.io project document two electronic badges: a PSoC4/ESP8266/WS2812B blinky badge and a VoCore/OpenWRT RT5350F network badge.
The June 4-5, 2015 RVAsec edition whose official badge-build post documents HackRVA's hand-built PCB badge process, surface-mount assembly, IR/audio/USB/LCD components, and reset-header development option.
The October 27-30, 2015 SAINTCON edition in Ogden, Utah, whose official archive records the Weber State University venue and whose Cisco partner write-up documents purpose-built Wi-Fi enabled attendee show badges with LCD screen, buttons, schedule, live Hacker Challenge score, and CMX zone awareness.
The October 14-15, 2016 Portland Security BSides edition at Oregon Convention Center, corroborated by Calagator event metadata for PCB badge giveaway language while official BSidesPDX pages preserve the schedule, speakers, workshops, contests, and hardware-security context. PDX Badgers preserves the public ATTiny85 Eagle board/schematic/BOM/firmware archive.
The March 4-6, 2016 Raleigh CarolinaCon edition whose official site and badge PDF document an admission-included electronic kit badge assembled in the Hardware Hacking Village.
The 2016 DEF CON edition whose Ryan Clarke / 1o57 electronic skull badge used buttons, LED eyes, a mini processor, printed codes, serial strings, lanyard data, conference-media files, and Konami-code red herrings in the badge challenge.
The second Hackaday Superconference edition whose Voja Antonic-designed Supercon II badge evolved the Belgrade LED-matrix badge into a Pasadena electronic badge with accelerometer, infrared, USB mass-storage bootloader, expansion pads, firmware framework, and badge-hacking contests.
The May 28-29, 2016 LayerOne edition whose official Hardware Hacking Village archive and CharlieX Hackaday.io project document a PSoC4, ESP8266, and WS2812B electronic conference badge.
The 2016 RVAsec edition whose official HackRVA interview documents the fifth-conference badge line, hand-built custom firmware badges, reused/improved hardware, USB reflashing, CTF challenges, and more than 350 initially quality-checked boards.
The October 11-14, 2016 SAINTCON edition in Provo, Utah, whose official archive and public badge documentation record a D1 Mini ESP8266 electronic badge kit with MAX7219 LED driver, two 4-digit LED modules, Lua/NodeMCU flashing, and Hackers Challenge registration.
The October 20-21, 2017 Portland Security BSides edition at Oregon Convention Center whose official schedule included BSidesPDX 101 badge context and Rob Rehrig's Ox-Vox talk about an add-on for that year's unreleased BSides PDX badge, while PDX Badgers preserves the public BMD-300 Eagle board/schematic/BOM archive.
The September 29-30, 2017 Arizona hacker and security conference edition whose public attendee writeup preserves a soldered Wi-Fi/Bluetooth scanner badge built around a WemOS board.
The March 30-31, 2017 Milwaukee CypherCon edition whose official history records 525 attendees, the Game of Life / Hacker Glider theme, the TYMKRS Cube badge, and the badge-creator panel.
The 2017 DC503 Wagon Party badge archive whose public PDX Badgers repository preserves reprogramming notes, nRF52832 Arduino setup, SSD1306 OLED firmware, BLE banner control, and game-mode source code.
The 2017 DEF CON edition whose official badge was documented by attendee feedback as a rubber or plastic identity artifact without a badge challenge, while the wider event became a milestone year for unofficial badgelife hardware.
The September 22-24, 2017 DerbyCon Legacy edition whose public conference metadata and first-hand maker writeup document a special electronic Legacy Black Badge award artifact.
The Pasadena Hackaday Superconference edition whose Mike Harrison-designed official badge was a digital camera platform with PIC32, OV9650 camera, OLED screen, MicroSD storage, accelerometer, bootloader, and expansion hardware.
The May 26-28, 2017 LayerOne edition whose official Hardware Hacking Village archive and badge-team project page document a CAN-bus-focused STM32F4 electronic conference badge.
The 2017 Recon Village badge-lineage start documented by the official Badge Life archive as The Original spy-silhouette electronic badge with a hardwear.io lanyard.
The 2017 RVAsec edition whose official layout, sponsor, and InfoconDB trail document HackRVA badge distribution, badge-intro content, CTF-room context, and source-depth limits for the public badge record.
The October 10-13, 2017 SAINTCON edition in Provo, Utah, whose official archive and badge page documented a Raspberry Pi Zero W electronic badge, a custom TFT/button board, MiniBadges, and Hacker Challenge integration.
The May 4-5, 2017 Chicago THOTCON edition whose official schedule documents badge pickup at check-in and whose public badge-hacking record preserves the 0x8 electronic tesserHack badge.
The Central Florida Security BSides edition whose official site anchors the 2018 event and whose project-owner Hackaday.io record documents a simple discrete marquee badge kit given to attendees.
The 2018 Tampa Bay Security BSides edition whose public attendee report records more than 750 attendees and electronic badge assembly activity, while a CC BY-SA documentary photo preserves a visible BSides Tampa 2018 badge/lanyard artifact.
The October 26-27, 2018 Portland Security BSides edition at Oregon Convention Center whose official schedule included BSidesPDX 101 covering CTF, contests, events, badges, and more, while PDX Badgers preserves a public ATTiny861 KiCad/BOM/firmware badge archive.
The September 28-29, 2018 Arizona hacker and security conference edition whose contemporaneous local meeting notes document a ticketed event with a paid badge option but no recovered badge hardware archive.
The 2018 DC503 DEF CON 26 party-badge edition whose public PDX Badgers repository preserves the VIP Banglet wrist badge hardware, firmware sketches, 3D-print files, Apache-2.0 license, and credited Portland badge-team authors.
The 2018 DEF CON edition whose Tymkrs / Toymakers official electronic badge used a PIC32MM, LEDs, capacitive controls, USB serial text adventure, badge-to-badge connector, add-on header, and firmware-update trail.
The Pasadena Hackaday Superconference edition whose official badge reused the Hackaday Belgrade retrocomputer badge lineage with BASIC, CP/M, a color display, keyboard, speaker, flash storage, AA power, and expansion hardware.
The May 25-27, 2018 LayerOne Pasadena edition whose official Hardware Hacking Village archive, Hackaday event report, CharlieX repository, and mmca hardware notes document an ESP32-WROOM-32 audio/network conference badge.
The 2018 Recon Village badge edition documented by the official Badge Life archive as The Dual Design, with spy-silhouette and skull variants.
The June 7-8, 2018 RVAsec edition whose HackRVA recap, public badge wiki, official layout, and CTF page document more than 300 electronic hardware badges with games, puzzles, two-channel audio, and badge-hacking challenge context.
The September 25-28, 2018 SAINTCON edition in Provo, Utah, whose official archive and badge page documented an attendee electronic badge designed by compukidmike with expanded minibadge support and I2C interactivity.
The January 19-21, 2018 ShmooCon XIV edition at the Washington Hilton, whose public conference record and attendee write-up preserve a battery-powered WiFi signal-strength meter badge with last-minute reflashing and parts-shipping caveats.
The June 20-24, 2018 ToorCamp outdoor hacker camp at Doe Bay Resort & Spa, whose Great Scott Gadgets badge archive preserves an MSP430-based electronic jar-of-fireflies badge with open hardware, firmware, BOM, assembly photos, and a BSD-licensed repository photo.
The September 10-16, 2018 ToorCon San Diego 20 edition whose public conference metadata and Hackaday.io badge-builder log preserve a 400-kit official-badge request with SMD Challenge hardware, 8-bit art, and hidden codes.
The 2019 503 Party badge/pager archive whose public PDX Badgers repository preserves the 5ohBEE SMART Response XE pager setup, RF firmware sketches, HugQuest game behavior, repository license, and source credits.
The August 6-7, 2019 BSides Las Vegas edition whose official archive and registration pages document a capacity-managed admission badge model with no walk-in badges.
The April 26-27, 2019 Kansas City Security BSides edition at Plexpod Westport, whose Badge Pirates source trail documents the ESP8266 conference badge, kids badge, Wi-Fi exploration game, and badge variants.
The October 25-26, 2019 Portland Security BSides edition at Oregon Convention Center whose official schedule included BSidesPDX 101 covering CTF, contests, events, badges, and more, while PDX Badgers preserves a public Multnomah KiCad/BOM/firmware badge archive.
The March 23, 2019 Rochester Security B-Sides edition at the RIT Inn whose official archive and badge page document a reprogrammable ATTINY85 electronic badge, PCB fallback, SAO ports, and best-hacked-badge contest.
The December 6-7, 2019 Arizona hacker and security conference edition whose official registration sources distinguish printed-badge and electronic-badge ticket types without exposing hardware, firmware, or image reuse rights.
The 2019 DEF CON edition whose Grand Idea Studio crystal badge used NXP silicon, KL27 ARM firmware, NFMI communication, badge-type roles, and a conference-wide interaction game.
The fifth Hackaday Superconference, where the official badge became a Game Boy-shaped ECP5 FPGA platform running a RISC-V soft core with cartridges, HDMI, SAO, PMOD, and open toolchain workflows.
The April 5-6, 2019 inaugural Kernelcon in Omaha, where public badge sources document a limited electronic K-shaped badge with ATtiny85, APA102 LEDs, and CTF behavior.
The May 24-26, 2019 LayerOne Pasadena edition whose official Hardware Hacking Village archive, Hackaday report, and CharlieX repository document a Blade Runner / Voight-Kampff electronic conference badge and add-on kits.
The DEF CON 27-adjacent Queercon edition whose Q and C badge system used distinct electronic attendee artifacts, custom keyboard hardware, badge-to-badge token exchange, handler missions, and a shared ARG progress station.
The 2019 Recon Village badge edition documented by the official Badge Life archive as The Skull Badge, a steampunk-recon skull with an LED eye and staff CREW variant.
The May 22-23, 2019 RVAsec edition whose HackRVA post and GitHub interpreter repository document the eighth RVAsec electronic badge, its Arduino-compatible custom layout, games, base-station laser-tag behavior, and badge C interpreter.
The October 22-25, 2019 SAINTCON edition in Provo, Utah, whose official archive and organizer letter documented the Enigma theme, badge distribution, minibadges, Hardware Hacking Community support, and event badge challenge.
The May 3-4, 2019 Chicago THOTCON edition whose DePaul Newsline coverage, InfoconDB schedule, badge-hacking workshop record, and public Poplicola repository preserve the 0xA / Infinity electronic badge.
The inaugural 2019 Atlantic City WOPR Summit edition whose public Hackaday coverage and first-hand Russell Handorf build guide preserve the 0x00 soldering badge, badge-hacking area, and hardware-design workshop context.
The October 23-24, 2020 all-digital Portland Security BSides edition whose official pages preserve the online schedule, speaker list, and virtual venue context, while PDX Badgers preserves a talking LED mask repository described as a BSides 2020 presenter artifact.
The 2020 remote Safe Mode edition whose official support badge was a LosT / 1o57 cassette-tape puzzle artifact spanning the tape, lanyard, printed liner notes, audio contents, and forum/media-server collaboration.
The November 6-8, 2020 virtual Remoticon edition whose official Hackaday.io start page documents a distributed hardware-creation event and whose discussion thread explicitly pushed badge work into unofficial community builds.
The March 25-28, 2020 Kernelcon virtual edition whose Hack-Master badge was documented through public repository, talk, and ZonkSec writeup sources after the conference moved online.
The pandemic-era RVAsec 2020 badge archive whose HackRVA firmware repository documents LCD, buttons, IR, LED, audio, USB bootloader tooling, app framework, and interpreter behavior while distribution and final event context remain caveated.
The October 27-30, 2020 virtual SAINTCON edition whose official archive identifies 2020 as virtual, InfoconDB records the dates, and first-hand DC540 coverage documents a shipped badge package with a badge, included MiniBadge, custom-MiniBadge coupon, and Hackers Challenge CTF badge context.
The August 21-22, 2020 online Diana Initiative edition whose Sched archive documents a virtual conference and a `Basic Arduino coding using virtual Badge` Village Workshop by @TechGirlMN, while TechGirlMN's Maker Village archive preserves the off-the-shelf Arduino badge build materials.
The April 23-25, 2021 online CarolinaCon edition whose official site documents a merch bundle with an all-parts badge kit and later bulk ordering of badge supplies.
The 2021 hybrid DEF CON edition whose official MK Factor electronic badge used a Raspberry Pi RP2040, LCD, D-pad, macro-pad HID behavior, USB-C, SAO connectors, speaker, firmware updates, and a New Normal badge challenge.
The 2021 Remoticon.2 virtual edition represented here by Thomas Flummer's Hackaday.io DIY KiCad badge template and Hackaday coverage rather than a centrally issued attendee badge.
The April 30, 2021 Hack Live virtual Kernelcon event, whose public pages and repository document the customizable Hacker HotKey stream-deck badge.
The November 4-5, 2021 RVAsec edition whose InfoconDB schedule preserves Badge Intro context and whose current HackRVA badge page supports the ongoing electronic-badge lineage while year-specific hardware files remain unrecovered.
The October 18-22, 2021 SAINTCON edition in Provo, Utah, whose official archive, MiniBadges page, venue page, and Sched listing document an in-person MiniBadge collection with status, community, challenge, sponsor/booth, soldering, puzzle, and unofficial trading records.
The October 8-9, 2021 rescheduled Chicago THOTCON edition whose official archive, workshop listing, Fourfold portfolio, and Rob Rehrig project writeup preserve the 0xB electronic badge.
The June 4-5, 2022 San Francisco Security BSides edition whose official Sched archive documents a Hardware Village where limited participants received pre-assembled Arduino-programmable HID badges for harmless rubber-ducky experiments.
The April 29-May 1, 2022 CarolinaCon Online 2 edition whose official pages document a merch bundle with an electronic Conference PCB Badge.
The 2022 Hacker Homecoming edition whose MK Factor official musical badge used Raspberry Pi Pico/RP2040-class hardware, a playable keyboard, display, speaker, audio I/O, firmware extraction paths, and a multi-part community badge challenge.
The November 4-6, 2022 return-to-Pasadena Hackaday Supercon 6 edition whose official badge was Voja Antonic's Voja4 front-panel 4-bit computer running on a PIC24FJ256GA704 with 272 LEDs, button programming, serial save/load, manuals, assembler, emulator, firmware, and SAO/IO expansion.
The March 30-April 2, 2022 Omaha Kernelcon edition whose public badge repository preserves the ESP8266 watch-badge firmware and flashing workflow.
The 2022 Recon Village badge edition documented by the official Badge Life archive as The Radar Badge, a circular radar and world-map themed badge.
The RVAsec 2022 edition whose public HackRVA firmware repository documents an RP2040/Pico-oriented badge software stack, LCD, three-color LED, D-pad, IR, rotary encoder, UF2 flashing, simulator, CLI, and badge app framework.
The October 25-28, 2022 SAINTCON edition in Provo, Utah, whose official archive and MiniBadges-of-2022 assembly guide document official, sponsor, and personal MiniBadge categories, acquisition paths, assembly instructions, and community-booth badge activity.
The July 13-17, 2022 ToorCamp outdoor hacker camp at Doe Bay Resort & Spa, whose official schedule and assembly PDF document a Rich Gonzales / OlyMEGA badge with light-sensing LED spider-eyes and attendee assembly guidance.
The October 28, 2023 Greenville Security BSides conference. Its public event listing and a contemporaneous conference announcement document Circuit Board Medics-led soldering that transformed conference badges into Wi-Fi analyzers; an attendee later reported making one. The reviewed sources do not identify the underlying badge board, completed distribution, firmware, or a rights-cleared artifact image.
The January 27-28, 2023 Arizona hacker and security conference edition whose official event page anchors the Mesa event and whose Badge Pirates writeup documents the ESP32-S2 CactusCon 11 badge.
The 2023 DEF CON edition whose Mar Williams / spuxo official physical badge returned the mainline to a non-electronic format while exposing an SAO customization chamber and public add-on design assets.
The Pasadena Hackaday Supercon edition whose Vectorscope badge combined RP2040/MicroPython control, a round display, analog ADC/DAC signal paths, prototyping area, and a public badge-hacking ceremony.
The April 12-15, 2023 Omaha Kernelcon edition whose official badge site documents the analog 1337 kHz AM radio badge and hardware-hacking playground.
The May 27-28, 2023 LayerOne return-to-in-person edition whose official conference post, Hardware Hacking Village page, and public repository document the PIC16F1455 USB HID electronic badge.
The 2023 Recon Village badge edition documented by the official Badge Life archive as The Spy Silhouette with speaker-badge and lanyard context.
The RVAsec 2023 edition whose official hotel-package wording and HackRVA repository document limited electronic badges, Raspberry Pi Pico-style flashing, LCD, three-color LED, D-pad, IR, rotary encoder, audio output, SDL simulator, and app/game firmware.
The October 24-27, 2023 SAINTCON edition in Provo, Utah, whose official FAQ and community data trail document MiniBadge culture, attendee trading, and a year-specific community MiniBadge data export.
The Social Engineering Community Youth Challenge edition at DEF CON 31, documented by DEF CON forum and schedule sources as a youth-focused puzzle event in the Social Engineering Community Village and paired here with the public Flux Decoder badge repository.
The May 19-20, 2023 Chicago THOTCON edition whose official schedule documents badge pickup and badge-required party entry, while Rob Rehrig's first-hand maker writeup and Fourfold's portfolio preserve the 0xC electronic badge.
The February 28-29, 2024 AvengerCon edition in Augusta whose U.S. Army public-affairs article documents the first AvengerCon electronic badge, the 8-8-8 badge, as a scavenger-hunt and badge-hacking artifact.
The 2024 Southern California Security BSides edition whose official event archive and post-event Somerset Recon source release document an ESP32-C3 BLE conference badge; the source release says 400 badges were distributed and preserves hardware and firmware material.
The October 25-26, 2024 Portland Security BSides edition whose official schedule and speaker page document The Badge Talk, where Joe FitzPatrick presented the customized BSidesPDX badge design, gameplay, and hacking context.
The May 4-5, 2024 San Francisco Security BSides edition whose official Sched archive documents a Hardware Challenge Village using a specially designed HCV badge for electronics tinkering and badge CTF contest play.
The February 16-17, 2024 Arizona hacker and security conference edition whose InfoconDB event record anchors the Mesa Convention Center context and whose Badge Pirates repository preserves the CactusCon 12 badge archive.
The DEF CON 32 Car Hacking Village edition whose official badge sale page, public CHV repositories, CTF archive, SAO specification, and IOActive key-fob badge build series document a CAN-bus badge ecosystem.
The 2024 DEF CON edition whose official electronic badge used Raspberry Pi RP2350 silicon, a handheld-game form factor, firmware/game archives, GB Studio source material, and a public badge patch trail.
The 2024 GrrCON edition in Grand Rapids whose public first-hand BadgeBuddy writeup and GitHub archive document an unofficial ESP8266 friend-distribution badge and companion backpack scoreboard.
The Supercon 8 edition whose official badge centered on six SAO ports, Raspberry Pi Pico W, MicroPython, I2C experimentation, CH32V003 proto-petals, and a functional SAO contest.
The 15th Hackers On Planet Earth conference, held July 12-14, 2024, where an ESP32-C3 electronic badge, Badge Clinic, open hardware repository, firmware paths, and MicroPython hacking notes were documented through official HOPE sources.
The October 11-12, 2024 JawnCon 0x1 edition at Arcadia University's Commons Building, whose official event page and badge write-up document a modem-themed electronic badge for the Philadelphia-area hacker con.
The April 2-5, 2024 Omaha Kernelcon edition, with the main conference on April 4-5 and an official analog [a]nalyze [i]nternet cable-tester badge.
The May 25-26, 2024 LayerOne Pasadena edition whose official conference post, Hardware Hacking Village page, and public repository documented the POV Spinner electronic conference badge.
The 2024 Recon Village badge edition documented by the official Badge Life archive as The Recon Soldier, a multi-layer tactical reconnaissance design with red and blue LED eyes.
The RVAsec 2024 edition whose official package page, layout, and HackRVA repository document limited HackRVA electronic badges, badge hacking context, LCD, three-color LED, D-pad, IR, rotary encoder, audio output, simulator, and game/app firmware.
The October 22-25, 2024 SAINTCON edition in Provo, Utah, whose official site and MiniBadge trading page documented submitted and official MiniBadges, a public build-guide link, trading-booth hours, and MiniBadge standards.
The June 26-30, 2024 ToorCamp outdoor hacker camp at Doe Bay Resort & Spa, whose official wiki documents per-attendee Shadybucks wristbands, Shadytel activation, Shady Tag registration, and the Euphoria CTF badge challenge path.
The DEF CON 33 Aerospace Village edition where the DC32 ADS-B Linux badge hardware returned with new Winglet OS 2.0 software, DC33 SAO support, ADS-B badge accessories, and a SpiderOak Aranya ESP32-S3 workshop badge board.
The 2025 AvengerCon IX edition in Augusta whose official archive and badge page document a conference electronic badge with a built-in four-challenge CTF, CP2102 serial access, coin-cell power, and booth/village unlock-code flow.
The DEF CON 33 Biohacking Village edition whose public badge page, user guide, and post-event reporting document a Distiller BHV Compute Module 5 badge with local medical-assistant AI, e-ink UI, microphone, buttons, LEDs, and open software branches.
The DEF CON 33 Blacks In Cybersecurity Village edition whose official BIC Pick badge page documented a five-year-anniversary Afro-pick commemorative badge, village wearer roles, and on-site DEF CON 33 purchases and trades.
The June 7, 2025 Indiana Security BSides edition whose first-hand badge-team writeup documents an attendee badge, badge talk, and CTF challenge path while the public organization repository preserves the badge hardware and firmware archive.
The May 9, 2025 East Tennessee security conference in Knoxville. Its official guide says Fox Pick made the year's badges; a public Fox Pick maker talk later documents the ESP32-S3 electronic artifact, while no public recipient allocation, direct source-repository URL, or rights-cleared badge image has been recovered.
The completed October 25, 2025 Illinois Security BSides conference at Bradley University. The organizer's contemporaneous ticket announcement fixes the date and venue, while its 2026 retrospective says the prior event drew nearly 350 people and had electronic badges. Technet8394's public HackTheBadge archive calls itself code for the BSides Peoria Badge Challenge 2025, but the organizer does not directly link that source or establish a main-badge, attendee-allocation, or delivery relationship.
The April 25-26, 2025 Kansas City Security BSides edition listed by BSides Global, whose Badge Pirates source trail documents a fully electronic ESP32 touchscreen badge order, customs delay, and pickup or shipping fulfillment plan.
The April 26-27, 2025 San Francisco Security BSides edition whose official Sched archive documents a Hardware Challenge Village hosting a competitive CTF on a badge designed specifically for the village.
The April 10-11, 2025 Salt Lake City Security BSides edition whose current official site documents a 2025 E-Badge built on a LilyGO T-Deck S3 with keyboard, trackball, LEDs, ESP32-S3, LoRa, Meshtastic readiness, and later 2026 pickup for remaining stock.
The DEF CON 33 Bug Bounty Village edition whose official BBV Badge 2025 page documented a four-button, four-LED badge challenge tied to Zoom, Intigriti, HackerOne, and CTF.ae challenge inputs.
The February 14-15, 2025 Arizona hacker and security conference edition whose InfoconDB event record anchors the Mesa Convention Center context and whose Badge Pirates repository preserves the CactusCon 13 badge archive.
The 2025 DEF CON edition whose official Mar Williams art badge returned to a non-electronic physical format with layered 3D/lens interactions and an Arts & Entertainment badge challenge.
The October 31-November 2, 2025 Pasadena Supercon edition whose official Communicator Badge used ESP32-S3, LoRa mesh chat, a custom keyboard, LVGL MicroPython firmware, and public hardware/firmware repositories.
The DEF CON 33 ICS Village edition whose FREE-WILi and Intrepid Control Systems sponsored badge tool documented RP2350A, ESP32-C6, sensors, GUI support, USB API, WASM scripting, and Build-A-Badge customization software.
The April 3-4, 2025 Omaha Kernelcon edition whose official badge site documents the Race Condition Raspberry Pi Pico racing badge and bonus-track activity.
The August 8-10, 2025 Spanish-language hacker-village edition whose official site provides event context and whose Electronic Cats repository documents the La Villa Hacker 2025 badge.
The May 24-25, 2025 LayerOne Pasadena edition whose official event and Hardware Hacking Village pages documented electronic-badge ticketing, HHV badge support, and the GLiTCh BadgE hardware-hacking platform.
The DEF CON 33 Lonely Hackers Club release window for the limited LHC Meshtastic Badge 2025, with DEF CON pickup, LoRa mesh hardware, preconfigured firmware, and LHC channel context.
The DEF CON 33 Maritime Hacking Village edition whose official Differential Destroyer badge was OSHWA-certified and published as a Pico 2, maritime-bus, scripting, and voltage-glitching hardware platform.
The May 16-18, 2025 New Orleans hacker conference whose official badge page documented the Patches electronic badge as a Voodoo Heart badge-series continuation and Learn to Solder artifact.
The OzSec 2025 Wichita information-security conference represented by the organizer's CRASHANDBURN badge-design archive. The current event archive identifies the venue and badge USB-data-cable context but contains conflicting date text, while the public repository remains explicitly work in progress and does not prove final production or distribution.
The completed August 7-10, 2025 Payment Village at DEF CON 33. A preserved programme copy describes its Vulnerable ATM Badge as a large physical simulator of ATM attack surfaces that could be carried with two hands, while the organizer's own DEF CON 33 page confirms the event lineage. No public technical, allocation, image-rights, or final-handoff record was recovered.
The November 14-15, 2025 PhreakNIC edition in Murfreesboro, Tennessee, whose official schedule included Tyler Crumpton's electronic shelf-label talk and whose post-event project writeup documents the official PN26 electronic badge.
The DEF CON 33 vendor-booth debut context for the Rabbit-Labs and The Pirates' Plunder collaboration badge, an ESP32-S3 and dual-CC1101 RF badgelife board with public firmware options and pinout notes.
The 2025 Recon Village badge edition documented by the official Badge Life archive as The Cyber Owl, a cyberpunk owl design with glowing pink LED eyes.
The completed March 11-12, 2025 Red Team Summit in Redmond. Its official history records 194 attendees, 61 organizations, 108 CFP submissions, and calls this the first Red Team Summit with an electronic badge; no public technical, creator, recipient-allocation, delivery, or image-rights record was found.
The June 3-4, 2025 RVAsec 14 edition whose official registration page listed a limited Custom Hack.RVA Electronic badge in the guaranteed hotel package while detailed hardware and firmware sources remain unrecovered.
The DEF CON 33 sales and release context for seeess's Tipsy electronic badge, a community badge sold at the Hacker Warehouse vendor booth with public repository documentation and firmware.
The May 30-31, 2025 Chicago THOTCON edition whose official site, contests page, Hackaday.io project, and public example repository document an ESP32 touch-wheel electronic badge and badge-hacking contest.
The October 8-10, 2025 Wild West Hackin' Fest Deadwood conference at Deadwood Mountain Grand, whose official e-badge page documents the Antisyphon-sponsored electronic badge and MetaCTF badge challenge.
The planned August 7-9, 2026 Adversary Village return at DEF CON 34, described by its organizer as the village's sixth year at DEF CON. Its official volunteer notice names Adversary Village badges as a volunteer benefit and explicitly says they do not give access to the con. The public sources do not identify the badge's form, technology, allocation, handoff, or credential behavior.
The planned August 6-9, 2026 Aerospace Village edition at DEF CON 34, independently established by the village's official event page. Its current badge record is limited to a public BadgeLife self-submission for the Lockheed Martin Aeronautics Cyber Range (ACR) team's winnable SR-71 CTF badge; that self-submission does not establish that Aerospace Village designed, issued, endorsed, or distributed the artifact.
The July 12-17, 2026 Avnet FAE Institute professional embedded-engineering event in Phoenix. Public vendor updates describe hands-on technical training and a July 14 Avnet FAE Institute Showcase; Alex Glow's public pre-event source archive identifies a commissioned PCB badge for the event, without establishing participant-wide allocation, final production, or a rights-cleared local image.
The August 1-6, 2026 Black Hat USA cybersecurity conference at Mandalay Bay in Las Vegas. Official DEF CON-registration and attendee-resource pages say eligible pre-purchasers receive a DEF CON symbol printed on their Black Hat badge; it is presented and hole-punched during the scheduled August 6 DEF CON pickup workflow, without a published material, technology, or completed-handoff specification.
The June 13, 2026 Des Moines Security BSides edition whose iot-pwn bsidesdsm26 repository documents a CH585 RISC-V badge with an ISO 14443A NFC reader, SK6812 LEDs, and an eight-tag village-collection CTF with two static flags.
The June 6, 2026 Indiana Security BSides edition whose organizer ticket listing offered a $30 optional e-badge add-on. Its public 2026 source repository contains distinct June commits, but recovered sources do not establish final hardware, individual purchase, physical receipt, or attendee-wide delivery.
The August 3-5, 2026 BSides Las Vegas edition whose current official home, registration, ticketing, volunteer, and CFP pages document a capacity-managed participant/admission badge system, on-site pickup, badge-type queues, and a separate speaker/mentor special-badge path.
The completed May 30, 2026 inaugural BSides Maine hacker conference at Hannaford Hall. Its official account and agenda document registration badge pickup, an interactive hackable lighthouse attendee badge with a pulsing beacon, and a badge-puzzle activity, while technical specifications, final variant allocation, and reusable image rights remain unpublished.
The completed May 15, 2026 BSides Nashville information-security conference at Marathon Music Works and The Foundry. Official event information says every attendee badge included the conference's 2026 challenge coin; the organizer's post-event feed corroborates the event and attendee coin reports without supplying a detailed coin specification or separate electronic-badge documentation.
The completed May 12, 2026 BSides NOLA edition whose BSides Global event listing advertised a custom PCB badge from Fox Pick and a guaranteed pre-sale PCB badge, while a post-event attendee account confirms a physical Rougarou circuit-board badge. No technical implementation or final distribution count is public.
The upcoming September 26, 2026 Central Florida Security BSides conference whose official GitHub organization published a public 2026-badge KiCad design snapshot. The archive supports a planned discrete LED badge design, not final manufacture, attendee allocation, or delivery.
The planned October 24, 2026 Illinois Security BSides conference at Bradley University. Official organizer sponsorship material says 2026 badge runs are being locked in and its prospectus lists logo-on-badge placement, establishing a planned conference badge but not its final form, electronics, recipient eligibility, allocation, or delivery.
The completed June 5, 2026 BSides Roanoke at Virginia Western Community College, whose organizer-operated ticket listing included a General Admission badge and whose dedicated ShenLabs page explicitly identifies itself as the event's 2026 badge challenge, without describing the badge's construction or electronics.
The April 4, 2026 America's Finest BSides edition whose official site and badge-challenge page document a Cyberpunk Bunny ESP32 electronic badge with portable CTF, accelerometer, cryptography, BLE co-op, and hidden flag behavior.
The February 27-28, 2026 BSides Seattle information-security conference at Building 92 in Redmond. The organizer's 2026 ticket page lists a Special badge at the event as a patron benefit, but no reviewed source identifies its form, technology, tier-specific allocation, or actual pickup/delivery.
The May 16, 2026 BSides Tampa edition whose current official pages document USF Marshall Student Center event context, badge-and-lanyard admission materials, an on-site badge challenge, and Uber Badge award-path context.
The April 25, 2026 BSidesKC edition at Kansas City Kansas Community College whose current official site and activities page establish an afterparty requirement to present a BSidesKC badge, without identifying the 2026 admission artifact's form or mapping it to the separately documented 2025 Badge Pirates hardware.
The May 15-17, 2026 Cackalackycon edition in Durham whose official event and first-timer guidance specify that students with valid student ID receive a paper badge, not an electronic badge, without preregistration. An organizer-provided CFP separately promises selected speakers a speaker-colored electronic badge and says guests who want an electronic badge must purchase a ticket; no technical, physical, or wider allocation detail is public.
The February 6-7, 2026 Arizona hacker and security conference edition whose official site anchors the Mesa event and whose Badge Pirates repository publishes the CactusCon 14 badge hardware design and build archive.
The August 6-9, 2026 Car Hacking Village programme at DEF CON 34, whose official event page remains available after the scheduled Las Vegas Convention Center dates. Official announcements and the public `chv_badgetools` repository document an RP2040/CAN-FD CTF badge, USB host tooling, and an on-site-only CTF. The reviewed post-date sources do not confirm final badge manufacture, allocation, handoff, CTF operation, or a released final firmware.
The completed August 14-15, 2026 Greenville polyglot and cybersecurity conference. Its organizer's event-week update documents check-in and Circuit Board Badge pickup, while the named badge partner's public source archive documents the ESP32-S3/CircuitPython platform. The public sources do not provide a recipient ledger or a rights-cleared physical-badge image.
The April 1-2, 2026 Milwaukee CypherCon edition whose official registration and FAQ distinguish Digital / Circuit, Extreme, and Analog / Plastic badge-related ticket forms, while a public organizer-account timeline mirror records the opening and wrap of CypherCon 9.
The independent 2026 DCZia MK9 BadgeLife release for DEF CON 34. Its public source repository calls it a neck-wearable mechanical macropad badge for DEF CON and preserves the KiCad and CircuitPython material; a public August 2 announcement describes Friday and Saturday BadgeLife pickup. The event remains pre-event at this catalogue update and is not an official DEF CON admission-badge programme.
The completed August 6-9, 2026 DEF CON edition whose official news confirms the wrap-up. Its official Bunnie Huang / Baochip Human badge record now includes a post-conference support page, source links, firmware-update path, and bounded security-token conversion documentation.
The Gothcon gothic dance party at DEF CON 34 on Saturday, August 8, 2026. Its official badge store identifies the associated $80 bat-shaped electronic badge as a fundraiser for the free party, says the badge is not required to attend, and announces DEF CON availability after pre-orders close. The party and badge remain separate from the official DEF CON Human-badge programme.
The planned September 24-25, 2026 GrrCON conference at DeVos Place in Grand Rapids. Its official volunteer terms say selected volunteers will be given a GrrCON staff badge and say dismissal revokes that badge, establishing a planned volunteer identity credential but not its physical form, electronic features, technical function, individual selection outcome, or delivery.
The June 3-5, 2026 Spaceballs-themed Hackers Teaching Hackers practitioner conference, whose official materials document the Columbus-area hacker, village, and CTF event. A public post-event Eagle 5 firmware archive and attendee account establish an electronic badge trail, while final board, allocation, and organizer-owned 2026 repository evidence remain unrecovered.
The completed April 17, 2026 HackNWA cybersecurity conference in Bentonville. Official event material advertises a CTF and ASMb1337 hardware-hacking activity. Its organizer-linked Eventbrite registration page now marks sales ended; a contemporaneous ticket-listing capture records a USD 109 VIP Assembled Badge category alongside USD 55 General Admission. The source trail establishes a ticket-listed badge offering, not its materials, electronics, contents, production, collection, delivery, or allocation.
The June 6, 2026 Hak4Kidz youth ethical-hacking conference at the Irish American Heritage Center in Chicago. The official event page frames it as Time Travel: Capture the Flag, while the 2026 flyer says youth attendees receive a fun badge; neither source identifies its form, technology, CTF integration, completed allocation, or individual handoff.
The completed seventeenth Hackers On Planet Earth conference, held August 14-16, 2026 at the New Yorker Hotel in Manhattan. Official sources document a digital In-Person Pass admission ticket but do not identify a physical or electronic conference badge.
The announced August 6-9, 2026 ICS Village presence at DEF CON 34. The official village schedule establishes the Las Vegas Convention Center setting, while the official FREE-WILi badge page documents an on-site / Vendor Village, while-supplies-last DC34 hardware badge for OT, ICS, and automotive research. The event had not yet occurred at this catalogue update.
The completed June 16-18, 2026 twentieth IEEE International Conference on RFID in Santa Fe. Official conference sources document two custom-printed twentieth-anniversary conference artifacts: a Minew ambient-light-harvesting BLE tag and a passive RAIN RFID/UHF tag with QR access to its conference identifier. The technical-programme chairs confirm the completed conference, but no recipient ledger, handoff report, final artwork licence, or individual device-state record is published.
The completed January 2-4, 2026 IEEE engineering-and-technology conference at the Luxor in Las Vegas. Its official post-event badge page documents a 2026 badge project: all attendees received a bare, unpopulated PCB, while approximately five manually assembled advanced units were prototyped. The source makes the attendee-versus-prototype split explicit and does not support a claim that all attendees received a working electronic badge.
The April 7-10, 2026 Kernelcon event in Omaha, with the main conference on April 9-10 and an official off-grid ESP32 weather badge with quest and crank-power behavior.
The independent 2026 Laser* Tag Badge DS BadgeLife release for DEF CON 34, whose maker page documents the electronic game platform and whose public late-July update says boards are in hand and final assembly/flashing is underway. Pickup and play are announced for DEF CON week, but the badge remains a pre-event independent project rather than an official DEF CON admission credential.
The May 23-24, 2026 LayerOne Pasadena edition whose official Hardware Hacking Village and wrap-up sources document attendee and speaker electronic badges assembled in the village: a three-button keyboard with blinkies and a self-printed UV-resin artwork layer, plus a narrowly documented electrical-repair response.
The completed first NaClCON hacker-history conference, held May 31-June 2, 2026 in Carolina Beach. Official registration included a NaClCON badge and Pirate Pieces of Eight CTF access, while the official schedule listed a CTF and Badge Intro. A founder announcement called the badge 3D printed/NFC, but the reviewed post-event sources do not directly confirm final badge fabrication, issuance, or technical implementation.
The June 2026 Onion DAO year-two four-week Chicago builder festival, whose official site describes hardware, AI, cybersecurity, and blockchain programming. The organizer says every accepted attendee gets a hardware badge at registration, with most components already on the board and a final soldering step. The official site links to OnionDAO's public badge repository, which documents an ESP32-S3 design and its open hardware/software sources; public sources do not establish an exact recipient ledger, completed handoff, or final population of every attendee unit.
The July 17-19, 2026 Open Sauce technology and creator festival in San Mateo. A post-event designer source archive documents a physical Arduino MKR Zero-compatible electronic badge and SAO ecosystem, while an independent attendee firmware archive corroborates badge hacking during the festival. Official Open Sauce pages establish the event, but do not directly publish the source archive or a distribution ledger.
The planned August 6-9, 2026 Payment Village return at DEF CON 34. Its official site confirms four days of talks, workshops, competitions, and hands-on payment-security demonstrations, while its volunteer notice says volunteers will receive conference access via a village badge. The public notice does not identify the planned credential's form, technology, allocation, or handoff and does not connect it to the earlier Vulnerable ATM Badge.
The planned November 6-7, 2026 PhreakNIC edition, currently seeded from the public PhreakNIC site and Tyler Crumpton's PN26 project-owner writeup; the site promotes preregistration and challenge coins while final PN27 MK.II badge details remain unreleased.
The May 5-7, 2026 Temporal Replay developer conference in San Francisco whose official MIT-licensed badge.temporal.io repository documents an ESP32-S3 badge with Doom, MicroPython, and IR boop networking.
The August 6-9, 2026 Robotic Hacking Community DEF CON 34 programme at the Las Vegas Convention Center. Its official pages describe an AI-Connected physical badge, on-site registration and pickup, an experimental firmware-reversing CTF, and a controlled API simulation; its post-event official badge documentation and MIT firmware repository now supply an inspectable STM32U073 hardware and software record without proving individual pickup or final allocation.
The June 9-10, 2026 RVAsec 15 edition whose official registration/package pages listed a limited Custom Hack.RVA Electronic badge and whose post-event HackRVA badge2026 repository publishes firmware, simulator, app-source, and UF2 release evidence.
The planned October 27-30, 2026 SAINTCON edition in Provo, Utah, whose official current site confirms badge pickup, a main badge with MiniBadge sockets on the 2.54 mm grid, Electronic Badge sponsor-ticket classes, and an exclusive Speaker MiniBadge while final board and firmware details remain unreleased.
The September 18, 2026 OKC Cybersecurity Conference edition whose official ticket page documents a limited PCB badge with CTFs and features for the first 180 registrants.
The June 4-5, 2026 SecretCon edition at the InterContinental Saint Paul Riverfront whose official registration listing advertised a Digital / Circuit Badge ticket tier with an interactive circuit-board PCB badge. The official FAQ says badges and pre-ordered merchandising could be redeemed and picked up at registration, but no final hardware, post-event delivery, or technical archive was recovered.
The announced August 6-9, 2026 Telecom Village return at DEF CON 34. Its official organizer site names PCBWay as Badge Sponsor, and its official organizer account has revealed an all-new badge and lanyard after saying the badge package had been received. The event remains pre-event, with no technical specification, allocation, credential, or attendee-handoff record published.
The completed June 1-4, 2026 Workday developer conference at Resorts World in Las Vegas. Workday's current event page says the main stage is closed, while a public post-event app archive identifies a Pimoroni Blinky 2350 badge as distributed at the event. The official Workday sources do not directly identify the badge's allocation, event-specific hardware or firmware, maker, or image rights.
Lifecycle
The application repository documents a conversational assistant with local model switching, LLM integration, MCP support, hardware interfaces, and a medical-assistant prompt example.
IOActive's build series documents a key-fob badge / SAO for DEF CON 32 CHV with dsPIC33CK32MP502, CAN transceiver, NeoPixels, touch buttons, IR, 125 kHz RFID receive, and 433 MHz transmit surfaces.
The public CTF archive ties the Speedometer SAO to rock-paper-scissors behavior, CAN messages, firmware reversing, and LCD output used in the challenge.
The repository includes multiple `badgechal` application files and firmware documentation stating that the custom C modules are required for CTF challenges.
The CTF page places the CTF.ae challenge leg online and onsite at the Bug Bounty Village in LVCC room W326, running from August 8 to August 10, 2025.
The Puzzled Hackers Team says the top 50 participants had Free Badge Redemption attached to their CTF accounts before its final puzzle announcement. It does not publish the leaderboard, account criteria, rank calculation, redemption count, code-delivery mechanics, challenge archive, score review, anti-abuse process, or proof that every eligible participant collected a physical badge.
The public pinout and firmware define 32 WS2812B / NeoPixel LEDs on IO21, with firmware files dedicated to pixel behavior.
The official badge page and manual document a Raspberry Pi Zero W at the center of the badge, paired with a custom SAINTCON board and badge image.
The second badge is documented around a VoCore/RT5350F module running OpenWRT with Wi-Fi, two Ethernet ports, USB host/storage goals, and heatsink work.
The project page says the ToorCon 14 badge used the same radio circuit as the IM-Me, turning IM-Me-style firmware customization into a USB badge workflow.
The product page and pinout describe two CC1101 modules, and the firmware maps separate A/B CC1101 SPI and GDO0 pins around a default 433.92 MHz RF workflow.
The top-level README lists NRF24L01 as part of the badge technology stack.
The badge natively receives and displays nearby aircraft using 1090 MHz ADS-B signals, with an onboard PCB antenna and optional external antenna path.
The badge shipped with RfCat firmware so attendees could connect over micro USB, run `rfcat -r`, and control the sub-1 GHz transceiver from an interactive Python shell.
The badge used 13 LEDs to represent the 13 evenly spaced Wi-Fi channels in the 2.4 GHz band, while also detecting Bluetooth, ZigBee, microwave ovens, and other in-band emitters.
The listed kit includes a top SAO PCB with pre-soldered lights plus three SAOs and a connector set containing six unsoldered NeoPixels; the maker says those NeoPixels are sufficient to populate one included bottom SAO. No public connector pinout, SAO standard confirmation, or electronic design is claimed.
The listing says the badge has an SAO v1.69bis connector with I2C and includes one Pac-Man Ghost SAO in one of four colors. It does not disclose the connector's electrical characteristics, pinout, voltage, companion firmware, color allocation, compatibility test results, or reuse rights for the companion artwork.
The listing calls both ports fully connected and 1.69bis-compliant, with dedicated GPIO, UART, and I²C connections per port. It does not publish pinouts, voltage/current limits, board layout, test results, or compatibility evidence for every SAO.
The public Speedometer SAO firmware repository is MIT-licensed and says it includes CTF problem and notes material built on a display library.
Call Center Village's official shop describes a $5 pickup-only Solder-It-Yourself Telephone Booth SAO Kit for the DEF CON 34 badge. Its current public Badgelife roster row separately lists a $5 kit and $10 pre-soldered option. These source statements establish offered configurations and planned event context, not final inventory, payment, assembly, pickup, shipment, delivery, refund, replacement, or support outcome.
A separate Pfarrside Creations listing offers the badge with two SAOs for $140. The source establishes the optional bundle but does not identify the SAOs' electronic design, pinout, compatibility, software, or final allocation.
The official Join Us page says attendees had to secure a badge ahead of time and that BSidesLV would no longer accept walk-ins for the conference.
The hardware list includes one 1.69bis SAO port plus conductive pads, 3.5 mm lead, elastic band, lube, custom lanyard, spare batteries, and battery clip.
The official DC34 SAO specification documents 3.0 V VDD, 100 mA tested total supply across both SAOs, GPIO pins, I2C devices at 0x3C and 0x19, and mirrored unkeyed 6-pin SAO headers.
The badge documentation identifies I2C expansion configured as DEF CON SAO plus USB terminal access for I2C and SAO sensor interfacing.
The badge includes an SAO connector that supports I2C, UART, CAN Bus, and more; the DC33 release explicitly adds Aerospace Village DC33 SAO support.
The README lists a Shitty Addon connector, making the badge compatible with the wider SAO-style add-on ecosystem.
The MiniBadge standard defines I2C read/write initiation, button, text, score-update, and brightness messages, while warning that microcontrollers need to track state across repeated starts and stops.
The minibadge notes define I2C address coordination plus polling, button, text, pixel, timed-pixel, custom-data, score-update, and brightness-change messages.
The CHV SAO spec provides 3.3 V and ground while replacing normal SAO I2C with CAN TX and CAN RX for vehicle-network add-ons.
The public MiniBadge standard supplies the shared connector and I2C protocol context for SAINTCON MiniBadges, while this record keeps per-board firmware claims limited to recovered 2021 evidence.
The public MiniBadge standard supplies the shared connector and I2C protocol context for SAINTCON MiniBadges, but this record does not claim every 2023 entry implemented active I2C behavior.
The public MiniBadge standard supplies the shared connector and I2C protocol context for SAINTCON MiniBadges, while this 2020 record keeps per-board behavior limited to recovered source evidence.
The public MiniBadge standard documents +VBATT, 3V3, GND, SDA, SCL, CLK, PROG, and NC pin guidance, including +VBATT voltage caution and do-not-connect rules for reserved pins.
The official 2026 activities page says attendees must present a BSidesKC badge for entry to the afterparty. It does not say whether that means a paper/card credential, lanyard, wristband, QR/barcode, RFID/NFC credential, or the distinct 2025 electronic hardware.
The official ticketing page calls the Participant ticket general admission to the conference, and the registration page says badges are required for entry. Training Ground listings say a Participant Badge is required separately for those classes. These access descriptions do not establish material construction, electronic behavior, individual handoff, or transfer rules for every badge.
The Roanoke InfoSec Exchange Inc ticket listing offers General Admission w/Badge and says the ticket includes a T-shirt, badge, and lunch.
The CFP provides one paper-badge guest admission for a selected speaker and says a guest who wants an electronic badge must purchase a ticket.
The official registration pages say the issued badge gave access to all talks and workshops.
The official first-timer guide says students should bring valid student ID to registration and do not need to preregister.
The Safe Mode badge was a real cassette tape in a jewel case, with side A/B markings, label art, and audio content that formed part of the challenge.
The assembly guide documents a 555 timer, photoresistor, capacitor, resistors, LED, AAA battery holder, and wiring; testing confirms the LED blink speed changes with light exposure.
The official badge was a playable vinyl record, making audio playback and record inspection part of the badge-hacking surface instead of firmware or active electronics.
The radio badge used RF gain control, a small transistor amp, mono audio sent to both headphone channels, and a hackable AM tuner path.
Builders could adjust the potentiometer to control how dark it needed to be before the badge lights turned on.
The early project post says the maker intends to do drops and make receiving a badge part of the experience; it also says a second variant is necessary for the interaction. It does not publish quantities, price, sales channel, dates, selection method, pickup or shipping terms, allocation, recipient list, completed drop, or final count of variants.
The Team says that after the paid cap is reached, distribution moves to random giveaways during the events. It does not identify giveaway quantity, timing, eligibility, selection method, organizer, physical allocation, handoff site, recipient list, or completed result.
The repository says winners of the 2026 Beverage Chilling Contraption Contest receive copies while stock lasts, and BCCC's official page locates the contest at DEF CON 34. This does not prove award recipients, winner quantity, qualification rules beyond the contest page, stock allocation, event outcome, or that the marketplace presale and winner copies are the same final unit run.
The storefront says each badge unlocks a live hacking challenge and frames progression as completing stages to climb a scoreboard. No reviewed source identifies challenge rules, format, tooling, endpoints, account model, scoring method, prize, operational schedule, data collection, accessibility, or a post-event archive; no software is inferred to run on the physical artifact.
Matt Aragon announced two custom-built interactive NaClCON experiences: an NFC Scavenger Hunt Pieces of Eight and a Pirates vs British Navy NFC social-networking game. The announcement does not identify which physical event artifact participated in either experience.
The checkout lists Linq 3535 / Circle Bar pickup on Wednesday August 5 and Thursday August 6 from 7–10 PM PT and says there is no shipping. It says a receipt and offline QR claim code are sent after checkout; the Team says a badge must be collected at a meetup or by separately arranging DEF CON handoff, and the QR may be given to someone else. Those terms do not confirm venue access, checkout completion, code delivery, identity verification, handoff, or redemption outcome.
The organizer announced green attendee badges and purple sponsor/speaker versions. No reviewed post-event source publishes final colors, populations, quantities, eligibility records, or completed delivery for either variant.
The author says that most listed capability categories will not be ready out of the box and that only LED colour/brightness adjustment, a hidden software CTF or scavenger hunt, and NFC read/write are available on DEF CON day 1. That is an announced capability boundary, not a public firmware release, working demonstration, final event outcome, or guarantee of feature availability for every unit.
The official about page describes the merch bundle as a shirt, electronic badge, and sticker bundle, supporting an electronic-badge classification while leaving component details unknown.
SOLDER LVL2, SOLDER LVL3, SOLDER LVL4, and Puzzle Badge entries document a tiered soldering and puzzle MiniBadge trail designed by Rushan.
The project page describes an automated-assembly-oriented design and manual population using solder paste, a stencil, reflow, manual pick-and-place, and post-assembly rework, with exposed-pad and 0.5 mm fine-pitch assembly constraints.
The 2023 data includes through-hole and surface-mount difficulty notes, parts lists, LED/resistor builds, and acquisition guidance, while the official FAQ encourages newcomers to learn MiniBadge design.
The guide covers LED orientation, two-position headers, through-hole and SMD soldering, reverse-mount LEDs, RFID sticker placement, motor/fan parts, hot glue, cable-test behavior, and ATTiny programming for selected MiniBadges.
HeatSync Labs brought acrylic backs, coin batteries, LEDs, resistors, and badge lanyards so attendees could solder a working LED badge at the booth.
The assembly guide says attendee conference bags contained the badge PCB, passives, fuses, headers, D1 Mini ESP8266 board, USB battery, and exchange token for HHV display parts.
The forum narrative says the team used solder paste, a hotplate, and manual display insertion to finish about 500 functional badges before the party.
LayerOne's Hardware Hacking Village page says both attendee and speaker badges were electronic and had to be assembled in the village.
Attendees assembled their badges at soldering stations with peer help and minimal official guidance before staff flashed firmware.
The assembly guide steps through resistor, photocell, LED, switch, MOSFET, potentiometer, and battery-holder installation with orientation and test reminders.
The assembly manual documents the LiPo battery, PowerBoost 500C, cable routing, custom board mounting, acrylic shield, screws, standoffs, and lanyard hardware needed to complete the badge.
Hackaday describes attendees receiving a bag of components and assembling the badge in the Hardware Hacking Village soldering environment.
A unique 3D-printed QR code on each case led attendees to a configurator for frame selection, name text, size, and position before firmware generation.
The official festival page says every accepted attendee gets a hardware badge at registration, with most components already on the board and a little soldering needed to bring it alive.
The badge added a piezo buzzer for simple tones, including circus-themed and button-feedback jingles.
The public firmware archive includes ToneChaser examples for musical modes while the project writeup documents audio games and badge sound output.
The public archive includes a SoundBoard example mapping sounds to three capacitive touch pads through the XT_DAC_AUDIO library.
The README lists a MAX4466 microphone module, and the firmware samples A0 to choose mouth frames based on detected voice volume.
The event report documents I2S audio hardware, a 2-watt speaker amplifier, and a microphone pre-amplifier for the voice/audio experiment path.
The README documents the badge microphone, special microphone driver, and AudioStreaming example with netcat/aplay receiver notes.
The live DC801 page lists the badge at $120, says local-pickup scheduling emails were planned for July 20, targets remote shipping by July 27, and warns that orders placed after July 23 may arrive after DEFCON. These are seller terms and targets, not proof of inventory, payment, manufacture, shipment, pickup, arrival, refund, replacement, support, or event-time handoff.
The organizer said there would be no additional circuit-board badges after the initial event order. That records intended scarcity context only; it does not establish order count, sales, manufacturing quantity, stock, ticket cutoff outcome, fulfilment, or recipient delivery.
The official Uber Badge page says badge-challenge victories are one path to a one-of-a-kind Uber Badge with lifetime BSides Tampa admission, but the current registry does not list a 2026 awardee.
The official page links the WWHF 2025 badge CTF to Meta CTF and says challenges could be solved from badge behavior or firmware.
The board exposes seven WS2812B RGB LEDs and a button set using IO0 plus a PCA9535 I2C expander for six additional controls.
The README identifies a 74HC595 plus nine single-color LEDs, one RGB wing, and dual USB CDC roles. No schematic, PCB, wiring, electrical limits, display, button map, or final component-population documentation was recovered.
Official registration pairs the NaClCON Badge with Pirate Pieces of Eight CTF access, and the official opening schedule lists a CTF and Badge Intro. The sources do not publish a per-badge challenge mapping, scoring mechanism, reward, or final results.
mmca's Hackaday.io log documents an official blinking LayerOne logo add-on for the 2018 L1 badge and its 3.3 V, GPIO2, and ground connector path.
The first-hand write-up documents a custom blinky board by Luke Jenkins and Klint Holmes that extended the badge-hacking experience.
The DOOM SAO log documents an ATSAMD21G18A add-on with ST7789 display, USB-C, serial terminal, bus sniffers, virtual EEPROM identity, and SAO 1.69bis logical integration with DC27 badges.
Hackaday frames the ESP32CAM eye add-on as the camera and face-recognition surface for the Voight-Kampff human-or-replicant test.
The article shows a hobby-servo eye add-on as one of the mechanical extensions for the badge's add-on header.
The official speaker page describes Ox-Vox as an add-on for that year's unreleased BSides PDX badge, tying the badge to a pre-release add-on hacking workflow.
The official badge page and manual preserve MiniBadge support, official MiniBadge and unofficial MiniBadge pages, and visible add-on presentation through the attendee badge.
The firmware used the integral accelerometer for gravity-style simulations and input mechanics that sat behind the public puzzle and demo behavior.
The badge exposed an onboard BASIC interpreter with badge-specific commands for display, LED, audio, GPIO, serial, and program storage experiments.
The MIT-licensed firmware exposes a Doom port running on the ESP32-S3 badge.
The badge runs a MicroPython environment for attendee apps and experimentation on the ESP32-S3.
The attributed Glyph README describes the distributed Blinky 2350 as running badgeware MicroPython with an app launcher. This records an independently documented runtime surface, not an official Workday statement about included apps, event firmware, participant configuration, or support.
The badge's camera was not decorative: Supercon included a film-festival category for movies and media produced with the badge camera.
The public app tree includes menu, settings, schedule, Tetris, analog clock, battery monitor, system monitor, and other badge applications.
The badge used a 16-bit PIC24FJ256GA704 to simulate a 4-bit educational processor with visible registers, flags, ALU, stack, memory state, and instruction execution.
The official product page says BENDER hacking challenges will appear on the CTFd-hosted server at 10:00 Vegas time on Friday, August 7 because the badges are part of a DEF CON Contests & Events challenge, with activation instructions promised for the same day.
The 2016 interview says the badge focus shifted toward CTF challenges.
The official guide documents a mystery encrypted message, D-pad decryption-method selection, classic-cipher basics, and advanced Base32, XOR, AES-128, and ChaCha20 challenges.
The 2019 badge challenges used blinked binary, silkscreen encoding, badge-role variants, SSRF, and a Docker-hosted challenge app.
Eight hardcoded 4-byte UIDs map to village and event markers (HW Village, Talks1, Talks2, Solder Village, Blue Team, Vendor, CTF, Check-In); scanning a matching tag collects it and lighting all four LEDs blue requires all eight.
The official badge page says AvengerCon IX's badge carried a small four-challenge CTF contest.
The released documentation identifies a Konami-code challenge, a snake-style game, registration QR behavior, and serial-only challenges. The event CTF's final operation and individual results remain unrecovered.
The README says a very partial RubberDucky 2.0 script interpreter is commented out in the code and tied to a single-prize badge competition.
The badge doubled as a scavenger hunt where attendees collected codes to light the LEDs.
The firmware encodes two static flags (a plaintext constant and a Ghidra-disassembleable byte-assembled string) plus a hash-based unlock that celebrates a specific UID-derived LED combination.
The guide says Badgey Bodgerton uses a supplied bodge wire plus a user-installed 3 mm LED, 1 kΩ resistor, and polarized buzzer in challenge work. It describes the parts and their badge-local challenge context without revealing answers or proving every badge shipped with identical parts, that a participant completed the work, or that any assembly is safe or successful.
The public challenge archive documents main-badge CAN enumeration, a physical-inspection flag under the battery pack, random traffic, and a UART Python REPL path.
The ShenLabs footer states that the fictional site was created for the BSides Roanoke 2026 badge challenge, using clearance and decryption framing; it does not establish that the web experience ran on, or was physically encoded into, the attendee badge.
HackRVA's recap documents games and puzzles as part of the 2018 hardware badge experience.
The official trading page says the build guide covers submitted MiniBadges that people designed and brought to the conference, including all official MiniBadges.
The DEF CON 32 entry documents multi-layer PCB construction, a 3D assembled design, and red and blue LED eyes.
BSidesROC announced a contest for best hacked badge with prizes awarded, tying the reprogrammable badge to on-site modification rather than only event identity.
The Makefile, project files, and flashing command target an ATTiny4313 AVR powering the spinning POV badge firmware.
Hackaday describes the base LayerOne 2019 badge as a small ATtiny2313 board rather than an ESP32 badge core.
The project bill of materials names an Atmel ATxmega128A4U microcontroller as the badge's controller.
Hackaday identifies the 2018 LayerOne badge around an ESP32-WROOM-32 module with Wi-Fi and Bluetooth-capable microcontroller hardware.
The hardware specification identifies the ESP32-WROVER-E-N8R8 as the badge controller with 240 MHz dual-core CPU, 8 MB flash, and 8 MB SPI RAM.
The first-hand writeup and public firmware document an ESP8266 badge that advertises `BadgeBuddy` while scanning nearby WiFi networks.
The README names a PIC16F1455 badge core, and the firmware configures USB clocking, interrupts, generic HID, and keyboard HID behavior.
The Hackaday.io project describes a battery-powered blinky badge using PSoC4, ESP8266 Wi-Fi, WS2812B LEDs, I/O ports, and 3.3 V logic with LED level-shifting work.
The project description lists PSoC 4 as the controller for the 2016 badge platform.
The badge-team details page names STM32F446/F405/F415-class LQFP64 support as the controller direction for the 2017 badge.
The Eagle 5 README identifies an nRF52840-QIAA controller and SX1262 LoRa radio. It does not state frequency configuration, regulatory region, antenna characteristics, actual transmit behavior, final board revision, or a complete radio/power design.
The Fox Pick talk identifies the badge as ESP32-S3 based, with Bluetooth Low Energy and 2.4 GHz Wi-Fi capability.
DEF CON's July 31 official reveal names Bunnie Huang as the badge creator and says the badge features his open-source, fully inspectable Baochip; it does not announce final firmware, board files, or distribution details.
The official FAQ says average yearly MiniBadge volume is well over 17,000 and that roughly 8-10 percent of attendees bring their own MiniBadges to trade.
The official page invites attendees to make each Patches badge unique with interchangeable limbs, LED choices, and personal flair.
The BYOB log documents using the microSD card for custom RAW 16-bit 565 bling assets, including ffmpeg conversion and the `/SDCard/BLING/` folder workflow.
The DEF CON 33 entry documents a cyberpunk owl design with glowing pink LED eyes, detailed mechanical artwork, and metallic blue-gray finish.
The DEF CON 27 entry documents a skull-shaped PCB with steampunk mechanical design and LED eye illumination.
The official archive identifies The Original as the first Recon Village badge and foundation of the village badge tradition.
The DEF CON 30 entry documents a circular radar design with world-map overlay, compass markings, and coordinate markings.
The badge used an 8x8 LED matrix for bouncing-pixel animation and a falling-code pattern once enough nearby BadgeBuddy networks were detected.
The HHV exchange path provided a MAX7219 LED driver IC and two 4-digit LED modules, with the BOM and soldering notes documenting sockets, headers, display color options, and resistor selection.
The README lists an OLED display as the badge's attendee-facing display surface.
The red 128-LED matrix was the main visual surface for animations, gravity simulation, messages, Tetris, challenge feedback, and blinky badge hacks.
The badge used a 5-by-19 LED matrix for user-customizable vertically scrolling text, with a default DEFCON 15 message and separate text-entry and scroll-speed states.
The badge combined a 2.9-inch 128x296 eInk screen, six side-view RGB LEDs beside the display, and twelve additional full-color edge LEDs.
The README maps six LED outputs to left ear, left eye, left mustache, right ear, right eye, and right mustache positions.
The official event page says the small electronic badge kit was included with the admission price and contained basic components plus batteries.
The Registration FAQ documents room-block participant badges plus donor, sponsor, volunteer, speaker, student, local, and other badge-allocation paths, with separate on-site badge-type queues.
The first-hand writeup says 300 CactusCon PCB badges were made and given away at the HeatSync Labs booth.
The quick guide documents a photocell, potentiometer, MOSFET, resistors, battery holder, and four LEDs used to light the spider eyes based on darkness level.
Hackaday.io documents an exposed add-on header as part of the badge's expansion and badgelife compatibility surface.
Hackaday documents a five-pin add-on header carrying power, PWM, and I2C for the 2019 badge's expansion boards.
The event report notes GPIO breakout pads for attendee hacking and experimenting beyond the default badge behavior.
The board documents two standard six-pin SAO connectors with I2C and GPIO access. A public launch announcement separately says a planned add-on board can expose three more keys or an I2C display; final add-on distribution remains unconfirmed.
The designer README describes optional SAO headers and says add-ons could be found at Open Sauce, while the attendee archive reports several basic LED SAO modules handed out at the event. This does not prove universal availability, exact module count, connector compliance, power compatibility, safe attachment, or final event configuration.
The current kit list includes a 2×3 SAO connector with wrong-way prevention. The archived assembly guide describes fitting the polarized six-pin header on the top PCB. Neither source publishes a final 2026 pinout, voltage, current budget, connector compatibility matrix, or tested accessory list.
Connecting a terminal over USB exposed a text adventure about scavenging parts to rebuild a relay-based computer in a missile silo.
The official wrap-up describes the completed badge as a three-button keyboard with blinkies and a self-printed UV-resin artwork layer.
Public creator material says DC33 was a non-electronic badge year, making optical interaction and material design the documented hack surface instead of firmware.
The official call for badge designers stated that DC31 would return to a non-electronic physical badge after two consecutive electronic badge years.
The official about page documents eight achievement levels that unlocked LED patterns and CTF flags.
The ARG and retrospective logs describe the Badge Enabled Non Directive Enigma Routine as a serial text-adventure challenge spanning hardware hacking, reverse engineering, cryptography, wireless capture, badge actions, and social collaboration.
The walkthrough documents Badge Enabled Non Directive Enigma Routine v2.0 as an embedded text-adventure challenge involving software exploitation, firmware clues, hardware interfaces, crypto, radio, and social steps.
Rehrig describes the 0xC badge theme as Contra and the core functionality as a conference-wide laser-tag game.
The public DEFCON 32 Badge Game repository contains GB Studio project files and graphical assets for the badge's LVCC-themed game.
HugQuest v1.5 stores HUG tokens, supports mining and sending HUGs, tracks names, and displays token state through the SMART Response XE interface.
The hunt loop moves a hunter sprite, tracks laser direction from input pins, draws a Bender sprite, and increments score on hits.
The 2019 badge post documents base-station laser-tag behavior and point collection plans.
The README describes a Stroop-effect color game where positive or negative shock reinforcement can be configured before play.
The wagon loop draws wagon and mountain sprites, prints the current banner, and increments a displayed score in miles.
The conference badge game used Wi-Fi beacons scattered around Plexpod Westport for attendee discovery and exploration.
Stock firmware challenged attendees to navigate an 8x8x8 maze using the three potentiometers for Z, X, and Y movement.
The listing describes a 13-chapter Ritual with story, screen, and LED animations; six side-quest challenges; and Bling, The Corrupt Ritual, R'lyeh Arena, Another Adventure, Exploit, and Rick Roll unlockable modes. No firmware archive or full game-rule source is published.
Official preview material documents IR, LCD, LED, audio, and input surfaces intended for badge applications and games.
HackRVA documented Badge Monsters and Maze as 2019 badge activities.
The event page says the badge had enough protoboard area for Arduino Micro or Nano compatible boards, with Arduino Micro compatible boards and boost converters available as donation rewards.
The 2015 build post documents unpopulated surface-mount pads and a reset-header option for connecting into the board.
HackRVA described standard USB as a way to make post-event reflashing easier.
The preview describes a bootloader and micro-USB programming path as a goal for post-event hacking.
The build guide lists a button and 10K resistor, and the Arduino examples include button-reading behavior for the workshop badge exercises.
The badge's onboard accelerometer triggers hacker-themed Magic 8-Ball responses when the attendee gives it a firm shake.
The Q badge used a full-color custom membrane keyboard with embossed keys, LED windows, and a layout tailored to the conference ARG.
The README maps five capacitive touch pads to right, up, left, down, and select controls.
The official page describes pairing with other LHC badges, after which the badge reveals a QR code on the Meshtastic channel.
Official sources document IR communication and badge-to-badge game behavior in the 2013 badge lineage.
The USB descriptor and keyboard source expose a keyboard HID interface, scan-code conversion, report sending, and button-triggered output including the default `LayerOne 2023` string.
In Party mode, the badge's RGB LED reacted to audio input volume and frequency from the onboard amplified MEMS microphone.
Two QT100 capacitive sensors controlled the five operating states, including text display, text entry, scroll-speed selection, persistence-of-vision, and sleep.
The official badge page says the BBV Badge 2025 has four buttons with four corresponding LEDs, and the visible goal is to light all four LEDs.
Rabbit-Labs and repository sources document a 1 inch I2C OLED, five-way directional switch, UART flashing pins, and SD card reader configured for SDIO mode.
The badge combines a TFT display, joystick, buttons, NeoPixels, accelerometer, SAO connector, SD card, battery charging, and status LEDs around the maritime protocol circuitry.
The hardware source documents a 128x64 I2C OLED using SH1106 or SSD1309 plus a five-way d-pad for badge navigation.
The badge uses an 8x32 LED matrix and three buttons to show SAINTCON, a custom message, Hacker Challenge score, Hacker Challenge ID, brightness, Wi-Fi status/configuration, and minibadge controls.
The RTFM documents SYM/ALT key chords for movement, quit/back, delete, special characters, and Bling Rager mode on the BlackBerry keyboard interface.
The writeup says the badge's first screen scrolled Bluetooth device MAC addresses.
The firmware imports CapacitiveSensor and defines two capacitive sensors across pins 3/2 and 3/4, with capacitive readings changing the alternate animation resolution.
The BHV guide describes a non-touch e-ink main display, left-side up/down buttons, right-side enter button, and e-ink drivers controlled through the microcontroller and Raspberry Pi 5 side.
KiCad comments and schematic sheets document five input buttons, two rotary dials, two SPI OLED paths, and an I2C OLED path.
The Cisco write-up says the badge included a roughly 2.25 inch LCD screen plus several buttons for attendee interaction.
The four RGB LEDs represented open pathways, portals, keys, and wall/death states around the player's current maze position.
The BOM lists an OLED screen and two navigation switches, while the Eagle files expose I2C display/front connector paths and switch wiring.
The documentation describes a Game Boy-like badge layout with OLED display and six push buttons for attendee interaction.
Official sources describe a 2.8-inch TFT display plus SNES D-pad and buttons, while the assembly manual documents the PiTFT Plus 320x240 display and button-board hardware.
The badge operated as a playable musical keyboard and synthesizer with instrument behavior, display, speaker, and challenge mode tied to note entry.
The hardware writeup documents two reverse-mount RGB LEDs, three individually addressable RGB NeoPixels, one reverse-mount red LED, and five input buttons.
The firmware README maps SAO SDA/SCL, SPI MOSI/MISO/SCK, USB D-/D+, left/right switches, RGB PWM, and row outputs for badge hacking.
The CAD archive and schematic-sheet names preserve screen and control surfaces, including an SPI TFT with touch and input-button hardware context.
The Project-CC13 board comments identify an SPI TFT with touch, two input buttons, and one rotary dial.
The official hardware description lists a TFT display and 25 addressable LEDs as the documented visual interfaces.
The firmware maps monochrome tail, back-foot, front-foot, and nose LEDs plus one RGB eye LED and groups them for badge display modes.
The BOM lists D1-D35 plus DNOSE as 36 yellow 0603 LEDs, while the schematic preserves the LED array around PWM0 and PWM1 control nets.
The BOM lists 12 yellow LEDs and four RGB LEDs, while `led_mapping.csv` maps icon LEDs including mountain, coffee, rain, bridge, sasquatch, book, train, beard, bike, donut, rose, and beer.
After troubleshooting, the badge displayed visible Wi-Fi SSIDs and signal strength in the attendee writeup.
Jonathan Singer's Hackaday.io project classifies the badge as a simple discrete marquee badge given to BSides Orlando attendees as a kit.
The retrospective and Hackaday review describe the switch from WS2812B pixels to an IS31FL3736 common-anode RGB LED driver controlling 31 RGB LEDs plus screen LEDs around the Bender eye artwork.
The project page documents HQ19-2333RGBC RGB LEDs, an IS31FL3741 controller, full LED matrix behavior, LED-backlit light pipes, and glow-in-the-dark capacitive-touch presentation.
The CactusCon 12 board archive preserves WS2812B LED footprints and LED schematic material.
The LED schematic and board archive preserve WS2812B lighting evidence for the CactusCon 14 badge hardware.
The organizer calls Electric Fist its third EFF BadgeLife design for DEF CON and says reruns of NSA "All Your Data" Eagle and Privacy Badger can be added at checkout. It does not document component changes, quantities, physical variants, or whether every listed option is ultimately fulfilled.
Infrared transceivers implement a boop system for badge-to-badge interaction documented in BoopSystem.md.
The WCH CH585 integrates an ISO 14443A NFC reader supporting REQA, WUPA, anticollision, RATS, APDU relay, NTAG215 dump, and low-power card detect over the CH585 NFC peripheral.
Official firmware documentation says AI Interactive Mode accepts line-based JSON commands over the CH340 USB serial link. The related public control repository adds MCP, Claude-skill, web, and HTTP host tooling.
The project page documents CR2032 power, power-on LED self-test, button wake/sleep behavior, automatic sleep after several minutes, and a low-battery reset symptom.
DC540 first-hand coverage documents that a SAINTCON 2020 badge package arrived for the virtual edition and included the badge itself.
Sending BOOTSEL over the USB-CDC serial console jumps into the WCH ISP bootloader for reflashing, complementing the flash station bulk-provisioning tooling.
The official village description says participants could program the badge through Arduino IDE to send automated keystrokes for harmless rubber-ducky experiments.
The Trick-or-Treat README points to controller code for generating game files and flashing badge-specific storage contents.
The log says the badge carried 8-bit art plus many codes in many places while withholding the exact meanings and Gerber artwork.
The LULZCODE log describes a LOLCODE-derived badge language extended for microcontroller peripherals, with high memory usage that drove the ESP32-WROVER external-RAM choice.
The scripting log documents TCLish language support plus badge-specific graphics, LED, button, timing, file, and GPIO commands for day-one badge hacking.
The public CharlieX repository preserves ATtiny source material for the badge and documents ESP32 camera-board firmware context without treating the camera board as the main badge controller.
The app tree includes Badge Monsters, Maze, Lunar Lander, Smashout, Spacetripper, Slot Machine, Cube, Game of Life, Ghost Detector, Hacking Simulator, and other app examples.
The development logs describe CAN logging, ECU reflashing experiments, J2534-adjacent PC software, NES emulator memory access over CAN, and PC-versus-badge gameplay ideas.
The linked CharlieX repository preserves an ESP32 Alexa experiment source trail derived from MakerAsia work, which the catalogue records without claiming a complete deployed production voice-assistant service.
The app tree includes AA Gunner, Badgey, Battlezone, Clue, Moon Patrol, Rover Adventure, Tank vs Tank, and other badge apps/games.
The repository includes Asteroids, Battlezone, Clue, Pong, Tank vs Tank, Magic 8 Ball, Badge Monsters, Maze, and other apps/games.
The release firmware maps four P2 inputs to up/down/left/right behavior, text entry, logo selection strings, an elite LED state, and a Konami-style `99 LIVES!` path.
The project details say PSoC routines were back-ported from a PC lightserver and left able to receive patterns or blocks of RGB values over UDP from another Wi-Fi device.
The all-at-once log reports that the LEDs were being controlled from a PC over Wi-Fi after ESP8266 orientation, reset, GPIO, noisy-power, and capacitance debugging.
The README calls the Banglet a fully functional Bluetooth recon device, and the main firmware starts scanner behavior while advertising a BLEUART service.
The main loop cycles between wagon, hunt, and party modes when the mode input changes, keeping the badge centered on local interactive display behavior.
After the relay-computer game path, the badge became an emulator for a vintage time-sharing operating system where attendees could write code.
The retrospective and Hackaday review document the micro-USB CP2102N path used to expose the serial console for the B.E.N.D.E.R. game after the DC25 wireless terminal experience.
USB serial access at 9600 baud exposed tesserHack map and help views for playing the maze with clearer coordinate feedback.
Hackaday documented USB CDC serial behavior at 115200 baud and a terminal mode, while project logs describe a shell for badge control and extra interactions.
The official write-up identifies the Hayes SmartModem as the badge's visual and command-set inspiration for the late-1980s/early-1990s event theme.
The badge was described by an attendee as a practical, battery-powered WiFi signal-strength meter rather than a decorative-only blinky.
The DEF CON 31 entry documents LED illumination, a speaker badge variant, and a custom Recon Village lanyard.
The DEF CON 26 entry documented two badge designs: the classic spy silhouette and a detailed skull variant.
Badge Pirates documents participant, speaker, organizer, volunteer, sponsor, and pirate badge designs for the 2019 BSidesKC badge family.
The public guide frames The Shattered Shard as a ten-chapter rune-restoration quest with sequentially unlocked progress and per-badge state. It establishes a planned game surface, not a full challenge archive, final scoring system, prize, winner record, completion ledger, event deployment, or permission to reproduce solutions or probe anything beyond an assigned badge and its advertised services.
The creator write-up says each badge represented one of 26 rotor notches and that attendees connected rings of 26 badges to receive and advance challenge messages.
The application source documents an SX127x-class 915 MHz LoRa mesh and a PingMessage carrying sender name, RGB theme color, latitude/longitude, and a short status; the product calls its mesh self-healing with minimal configuration. It does not prove final RF parameters, privacy choices, message authentication, interference behavior, or regulatory suitability in every jurisdiction.
The IR transmitter and TSOP receiver used a UART-oriented protocol with per-badge serial addressing, enabling challenges and user programs to exchange data optically.
Hackaday and the firmware README document badges joining topic channels, sending LoRa messages, and repeating received frames with TTL limits across nearby badges.
The BOTNET log describes a badge-only wireless game where activated badges could act as badge-net repeaters while players managed services, firewalls, exploits, points, XP, and attacks against other AND!XOR badges.
The product and forum sources describe a main badge that uses onboard controls and supports robot fights against other badges.
The maker names Acolyte, Glyph, Elder God, and redacted Cthulhu badge types. Its Séance description says four badges complete a circuit and beacon to nearby badges, without identifying radio hardware, a wireless protocol, role counts, or on-site distribution confirmation.
The guide documents Bluetooth LE co-op mode for interacting with other attendees plus a secret shaking-sequence Easter egg tied to an ultimate flag and rainbow bunny-eye goal.
The bottom connector enabled inter-badge progress, with public notes documenting Human-to-Human and Human-to-Goon interactions that changed movement or game state.
The README says Down broadcasts the current pattern/palette over ESP-NOW, with nearby badges cascading up to about three hops and rate/interaction safeguards. A five-second Down hold disables wireless until reset or power cycle; no BLE protocol is claimed for the default application.
The wiki says the fourth button sends an IR blast to nearby badges, making their lights flash and motor vibrate.
The badge docs describe IR exchanges that send clue and contact information, receive someone else's card/contact data, and verify cryptographic signatures on clues.
The DEF CON 16 badge could transfer attendee-selected files from an SD card to another badge over infrared, creating a PDA-style social exchange mechanic.
Badges communicated over infrared and could report encountered badge identities through a serial terminal, turning attendee movement and mingling into puzzle state.
Hackaday frames the Cube as a mesh network of badges and says code written inside the emulated environment could be deployed to other badges.
The badge used an RFM69W module and 433 MHz coil antenna for peer/chat and social radio behavior, with project logs documenting radio startup failures and bootloader timing fixes.
An RJ12 6P6C connector and cable linked Q and C badges so attendees could exchange digital tokens and advance the ARG across badge types.
The badge included multi-badge communication through a wired interface, and the role shapes also formed a seven-piece physical puzzle.
The project page describes an IoT Bluetooth mesh where badges connected over USB serial could join the conference network and remotely execute badge commands within the badge-game framing.
The official CFP says accepted speakers and mentors receive a special conference badge and a participant badge for a designated plus-one. This record preserves that named distinction without claiming the special badge's design, technology, recipient count, issuance, or relation to the participant-badge artifact beyond the CFP wording.
WIRED documented the black Uber badge as a more elaborate artifact with a hand-assembled mechanical watch, exposed aging copper, and one-time-pad puzzle relevance.
The official workshop hardware summary and repository README document USB-C, two Qwiic ports, a microSD slot, battery management, and battery connector support.
The badge outline was designed so the arms and legs could be broken out or used as LAN taps.
The writeup describes the badge head as a USB 3.0 breakout section.
The component notes describe socketed LED matrices and ESP8266 modules, header-pin quantities, 3xAA battery testing, USB power as a fallback, and a stated USD 9.44 per-badge cost.
The standard reserves PROG pins for builder use and lists optional AVR ISP, ST-Link SWD, PIC ICSP, and UART pin mappings.
Hackaday documented four included starter petals: capacitive touch wheel, spiral LED petal matrix, blank protoboard, and CH32V003 I2C microcontroller proto-petal.
The Euphoria CTF page directs players to register a Shady Tag at the Shadytel Experience Center before starting the badge challenge.
The badge page documents assembly into a regular-mouth canning jar with a CR2032 holder, six LEDs, resistors, and an MSP430G2211 controller.
The DC540 write-up ties the package to HC CTF badge material, but this record does not infer unrecovered challenge hardware, firmware, or scoring details.
The same attendee report says each badge arrived with one pre-installed clue and could connect to other badges so participants could exchange clues while solving puzzles, ciphers, games, and hacks.
The same public source says participants could hack the badge and bypass the contest altogether.
The write-up documents special Commander badges used by SAINTCON Committee members to help Agent rings progress through later challenge stages.
Datko says Matt Lorimer found one of the SAINTCON secrets by examining the badge source code, tying the badge to the Hacker Challenge trail.
Hackers Challenge, Tamper Evident, Scavenger Hunt, Vault Badge, and HACK-IN-THE-BOX entries preserve reward paths tied to game masters, contest completion, enough collected items, or event participation.
The guide includes Hackers Challenge, HACK-letter, Scavenger Hunt, and other game-adjacent MiniBadges with acquisition paths tied to game masters, challenge completion, or BadgeLife community interaction.
The README describes the BLE game and high-level Wargames-themed challenge access through UART with SAO context. The catalogue deliberately does not reproduce challenge procedures, values, answers, credentials, or operational details.
The badge challenge used six lanyards carrying Lewis Carroll Nyctograph symbols and Poe Gold Bug cipher material that translated into early-stage secret messages.
One sold-out $150 storefront option adds the separately-made Laser* Tag Badge DS from Dani.pink, which the maker says can be picked up alongside the Monorail badge. This records a bundled purchase/co-pickup statement, not shared hardware, firmware, manufacture, ownership, event affiliation, or a guarantee of either badge's delivery.
The teardown documents 115200-baud serial output, BLE-readable messages, hash clues, and firmware strings analyzed with Ghidra.
The README and changes document an RNode-oriented modem integration and Reticulum mesh context on the documented board. This is an archive-level capability statement only; the record does not state a frequency, configuration, deployment, coverage, legal authorization, field result, or operating procedure.
The curated Hackaday.io list preserved attendee-built cases, Atari and Apple-like emulators, games, music, QR generation, Morse code, Bluetooth chat, and plotter firmware hacks.
The thread clarifies that the forum badge was a separate extra badge for forum-member recognition, not a sticker or overlay for the official DEF CON badge.
The 2023 data export includes event and community entries such as RFID Rocket, Minibadge Community Badge, LAN Party, Hardware Hacking, Fox Hunt, The Keep, and Hallway Talks.
Hackaday documented thousands of custom DEF CON 25 hardware badges, a badge-maker meetup, and shared API work among makers, making the simple official badge historically important by contrast.
Community ROM work showed the badge running custom Game Boy ROM code and controlling all nine LEDs beyond the default controls.
The guide lists AppSec, Circuit Assembly, Hardware Hacking, Healthcare, HomeLabs, IoT, Lockpicking, RFID/NFC, Scavenger Hunt, SMD Challenge, and Learn 2 Solder style badges acquired through community areas, booths, challenges, or presentations.
The official page documents Red Team Community, RFID/NFC, Hardware Community, Lock Picking, Tin Foil Hat Talks, and related MiniBadges with acquisition tied to community events or interaction.
The BIC Pick page says the badge can be spotted on village volunteers, leaders, and supporters throughout the con.
Hack Your Lives' current listing is sold out and says each assembled-badge order includes an additional blank PCB offered for in-person DEF CON 2026 pickup; uncollected blanks would ship with the assembled order. It says paid orders will be assembled and shipped by September 30. These seller statements do not establish paid-order count, completed assembly, shipment, delivery, pickup, replacement, refund, or that every order receives an identical final unit.
The same project archive includes a backpack-mounted open access point and four-matrix scoreboard that counted unique connecting clients during the conference.
The official home identifies Time Travel: Capture the Flag as the June 6 event's hands-on CTF context. It does not say the fun badge runs, unlocks, contains, or is required for the CTF.
Packet Hacking Village's official programme lists the completed Saturday Friend or Foe presentation at DEF CON 34. It links the documented project to a completed village programme but does not say the village made, distributed, sponsored, sold, or endorsed badges, or that attendees received one.
The official Badge Project page says every 2026 attendee received a bare PCB with no components.
The flyer lists a fun badge in a package for youth attendees alongside lunch, snacks, a T-shirt, and prizes. It does not establish adult or chaperone inclusion, exact eligibility rules, physical form, technology, individual issue, or delivery.
InfoconDB preserves Badge Intro context for the 2017 event, tying the artifact to attendee-facing badge material.
InfoconDB preserves a Badge Intro session on the RVAsec 2021 schedule.
The listing names a configuration PWA and USB-C updating. The firmware README describes one RPC registry exposed through web, USB serial, and BLE, including settings, saved messages/locations, OTA update, and system functions. The companion PWA repository is public but unlicensed and does not establish a deployed service, credential, or data-retention model.
The README says Wi-Fi settings are hard-coded and must be updated in wifi.h before building the watch firmware.
The badge README and firmware document a Wi-Fi configuration mode where the badge displays an SSID and password, then hosts a configuration flow for network settings and the custom message.
The public talk describes USB-C, a CH340 USB-UART bridge, battery-voltage monitoring, and onboard charging/protection circuitry.
Returning badge features included capacitive touch buttons, 2.4 GHz connectivity mostly as a Wi-Fi node, remote connectivity via IRC, and a serial interface.
Challenge solvers could receive a Challenge Accepted SAO; the writeup says only two were awarded, one for crypto and one for the counterfeit-badge contest.
The 2023 data export lists contest-category entries including Lockpick Village, Tamper Evidence, and Hackers Challenge records, preserving acquisition routes tied to challenge activity.
The listing names a pre-flashed ATMEGA328, 16 MHz crystal, two capacitors, resistor, two through-hole tactile switches, power switch, and AAA battery holder. It says three AAA cells are required but not included, without publishing wiring, voltage, charging, or a complete assembly guide.
The seller says Submarine interacts with BigTaro's Gunslinger-B-Gone for extra fun. It does not say whether that interaction is electrical, infrared, radio, software, physical, optional, bilateral, safe, interoperable across revisions, or available at the scheduled drop.
The official site offers remaining 2025 E-Badges through 2026 ticketing and instructs buyers to pick them up at the April 2026 conference.
Badge Pirates said it ported a Lunar Lander contest to last year's BSidesKC badge for the April 2026 Ad Astra programme, told owners to bring that badge, and expressly said there was no new hardware. The announcement does not prove an individual badge was reflashed or used at the event.
The Euphoria CTF page says the first challenge is on the badge after Shady Tag registration at the Shadytel Experience Center.
Badge.Life's live DC34 Village Schedule lists Masonic33 Badge — heal at 10:30 AM Friday August 7 and 11:00 AM Saturday August 8, 2026. It supports a planned current recurrence of the named artifact, not a new board or revision, price, allocation, stock, official DEF CON issue, admission, completed handoff, or reusable-image term.
The current public roster lists an $80 price, a Venmo acquisition note, 25 SAO slots, and 360 by 360 mm for the Update to Existing entry. It does not establish final price, payment method availability, inventory, material, dimensional tolerance, board revision, production completion, sale, pickup, shipping, or delivered-unit configuration.
BigFuckingBadge advertises the Portal Badge at $120 before DEF CON 34 and $150 through hackerwarehouse during the con, while its live page says presale is open and quantities are limited. This is a maker-stated current offer, not proof of a completed order, payment, manufacturing run, stock count, hackerwarehouse availability, pickup, delivery, refund, replacement, or post-event sale outcome.
The live Brooke's Bytes listing displayed $10, 10 remaining, 20 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop. Badge.Life separately lists Brookes Bytes Badge and SAOs in its Friday 4 PM schedule slot. These time-sensitive statements do not establish a completed payment, final inventory, production run, product-to-slot allocation, completed drop, pickup, shipment, delivery, refund, replacement, or post-event outcome.
The live Brooke's Bytes listing displayed $10, 17 remaining, 33 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop. Badge.Life separately lists Brookes Bytes Badge and SAOs in its Friday 4 PM schedule slot. These time-sensitive statements do not establish a completed payment, final inventory, production run, product-to-slot allocation, completed drop, pickup, shipment, delivery, refund, replacement, or post-event outcome.
The live Brooke's Bytes listing displayed $60, 19 remaining, 11 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop. Badge.Life separately lists Brookes Bytes Badge and SAOs in its Friday 4 PM schedule slot. These time-sensitive statements do not establish a completed payment, final inventory, production run, product-to-slot allocation, completed drop, pickup, shipment, delivery, refund, replacement, or post-event outcome.
The live Tw0nkus listing displayed an $80 price, five remaining, four sold, and a Defcon34 drop label. Badge.Life separately schedules Bread Badge by Tw0nkus in its current Friday DC34 village programme. These are time-sensitive availability and schedule statements, not proof of a completed payment, final stock count, production run, exact drop location/time, pickup, delivery, refund, replacement, or post-event outcome.
The reviewed official event home, HOPE Wiki main page, schedule, and ticket listing do not identify a HOPE 26 physical or electronic conference badge. The known digital admission ticket is retained as an identity artifact rather than upgraded into hardware.
Payment Village's official 2026 programme schedules Introduction to the Vulnerable ATM Badge on Friday and Saturday. This identifies an ongoing instructional reference only; it does not state that the 2025 object will be issued again, demonstrate its final 2025 configuration, or connect it to a 2026 volunteer credential.
The Build-A-Badge software lets users choose images, configure LED patterns, set a badge name, program the device, and upload WASM applications.
Hackaday described the badge as a prototyping board or PCB canvas where builders removed the placeholder grid and added electronics they had on hand.
A June 6 commit changes the default badge identity title in the repository source to 2026. It is direct evidence of a 2026 software revision, not evidence that the current tree was flashed or run on a particular physical e-badge.
The Eagle schematic and board preserve SWD, UART, I2C display/front connectors, jumpers, and a four-pin right-angle header for badge hacking and add-on work.
The schematic maps J1 to VCC, GND, RST, PWM0, PWM1, CAP0, and CAP1-related nets, preserving a six-pin header trail for programming or badge hacking.
DAP mode presents the badge as a CMSIS-DAP probe for pyOCD, OpenOCD, Keil, and SWD target debugging while keeping a CLI serial interface available.
The DEF CON media server published badge add-on specifications and test-fit assets for building physical customizations around the DC31 badge.
The badge tested cable continuity and ordering through head and remote LED banks while activities showed how to make the remote removable.
The FAQ documents USB-C Ethernet access and SSH to root@192.168.100.1, with Wi-Fi and USB-C platform caveats called out separately.
The repository description and README document 2024 badge firmware and emulator/simulator build paths.
The repository documents a simulator build target for local badge software development.
The README documents an SDL simulator build for local app development and debugging.
The README calls for VS Code, Python, mpremote, and a boot-select flash procedure, using a Raspberry Pi Pico 2 on a breadboard for current firmware development rather than documenting a final deployed attendee workflow.
The public README documents building a Posix-style SDL simulator for app development and debugging on a computer before flashing badge hardware.
The maker lists two 0.96-inch 80x160 color IPS screens, an RP2040 dual-core Arm Cortex-M0+ described as running at 200 MHz, 264 kB SRAM, and 16 MB Quad SPI flash. The listing does not publish a board schematic, display part number, clocks, or electrical measurements.
The retrospective documents the 220x176 LCD upgrade, 40 MHz SPI and SD-card behavior, double-buffered display goals, and reduced frame-rate decisions caused by SD-card constraints.
Project details describe a 2.2 or 2.4-inch DMA-driven SPI TFT display with ILI9341/45 support and SPI SD card storage.
The release firmware includes PCD8544/Nokia LCD initialization, cursor movement, character printing, contrast, and image drawing paths.
The organizer-linked design documents a 24-pin J4 socket for e-paper or TFT SPI display modules, with GPIO, reset, busy, data-command, chip-select, clock, and MOSI details.
The party loop displays the BLE banner, flips display inversion, and periodically chooses random scroll directions.
The hardware documentation maps two SPI screen headers with separate DC, reset, chip-select, and display-enable control signals.
The README requires SSD1306 128x64 configuration, and the firmware initializes an Adafruit_SSD1306 display at I2C address 0x3C.
The badge page states that only 50 units were available, shipping was not offered, and pickup was at DEF CON 33 with possible in-person sales if any were left.
The official page says limited BIC Picks were available at DEF CON 33 through direct inquiry, limited purchase, or trade.
The README says the badge was sold at the Hacker Warehouse vendor booth during DEF CON 33 and that half of profits went to the Tor project.
Somerset Recon's README says 400 badges were distributed at BSides San Diego 2024 and describes a wireless Bluetooth LE rock-paper-scissors game. The count is a source-archive claim, not a recipient ledger or proof that every attendee had an identical unit.
The official badge page says short lead times limited the assembled run to about 200 badges, while attendees who did not sign up for the assembled option still received a PCB.
Official RVAsec 15 pages list a limited Custom Hack.RVA Electronic badge as part of the hotel package.
Official RVAsec pages list the Custom Hack.RVA Electronic badge as part of a limited guaranteed hotel package.
The repository description and firmware comments frame the mask as a BSides 2020 presenter gift rather than a general attendee badge.
The DC33 community schedule lists a Hack 'em Crack 'em Robots badge drop by 2PAC in the Badgelife Community area.
AND!XOR says its limited philanthropy sale reserves a badge for supporters while helping manufacture additional badges to give away; it says more than 84 percent are planned for free distribution through convention challenges, contests, and events.
Source initializes SD-card SPI and DAC/DMA sound playback at 22,050 Hz, with a no-SD state, amp-enable pin, and on-chip fallback settings. Separate flash-state code records diode, SAO, badge-to-badge, game, and sphere unlock flags. The sources do not establish installed media, speaker/amplifier hardware, volume, content rights, storage-card provisioning, power/runtime behavior, or final event software configuration.
The README separately lists a companion SAO PCB, a six-pin male header, and four RGB LEDs, then says its LEDs light when connected to the main badge's six-pin female header. It does not establish an SAO version, pinout, voltage/current limits, LED model, electrical protection, hot-plug behavior, compatibility with any other host, assembly quality, or final distribution.
The README says included slides or other RFID tags can be scanned to change what appears on the round display and mentions additional images intended for sharing or trading. It does not identify RFID frequency/protocol, tag type, reader configuration, stored content, data collection, authentication, access control, privacy practices, security properties, final gameplay rules, or a confirmed live event deployment.
The designer README calls the badge's T-piece Arduino Sopracciglio and Arduino MKR Zero-compatible, while the independent attendee archive also describes a custom board based on Arduino MKR Zero. The record does not infer a chip-level bill of materials, exact board revision, supply behavior, or final population beyond the published statements.
The README identifies a CH32V003 F4P6 RISC-V MCU and describes 3.3 V SAO-host input stepped to 5 V plus an automatic boost-disable path when USB-C 5 V is detected. It does not publish finalized USB-C hardware, board power budget, current/thermal measurements, fault behavior, host limitations, or safety/compliance results.
The board source contains a CR2032 holder footprint, a through-hole LED footprint, one 6 mm button, a through-hole SPDT slide switch, and a resistor. The source frames these as an experimentation surface, not a finalized populated circuit, power-budget guarantee, battery-included promise, or validated electrical configuration.
The Eventbrite listing says an appropriate mode can show deauthentication activity or nearby Flipper Zeros. The archived `camera_badge_rev01` source filters Wi-Fi management/data traffic, counts deauthentication frames while hopping channels, and performs BLE scans that increment a count for two source-labelled Flipper MAC prefixes. That is a source trail, not a validated 2026 alerting, identification, accuracy, privacy, or RF-compliance claim.
The current list names a screen, an `ESP23 Dev Board /w connector`, switch, PCBs, and headers. The archived DC32 parts/assembly documentation identifies a 1.28-inch 240×240 GC9A01 round TFT plus an ESP32 Lite V1.0.0 / ESP32 REV1 Type-C Wi-Fi/Bluetooth board with LiPo connection and charging circuit. The sources do not map that documented platform to a verified final 2026 production revision.
The public README lists one PCB, ESP32 Dev Module, round LCD, RFID reader, microSD reader/card, slide switch, Schottky diode, RGB LED, six-pin female SAO header, battery holder, four AAA batteries, foam tape, stand, slides, and RFID sticker tags. It documents a project inventory, not a verified finished unit, component variants, electrical design, safe assembly/operation result, quantity, allocation, or completed event handoff.
The design document says a connected Portal Gun SAO, a two-badge USB connection, and a back-side soldered diode can unlock features. Current source implements 9,600-baud serial status handling, portal-SAO and badge-to-badge counters, a retained I²C pin setup, and a directional diode check. It does not publish a final compatible accessory, connector pinout, USB electrical design, I²C behavior, voltage/current budget, or test matrix.
The project describes an infinity-mirror LED ring whose blue/cyan water effect follows gravity with damping, with selectable modes, dim/off behavior, motion wake, inactivity handling, watchdog recovery, and sensor-fault indication. This describes public intended software behavior, not final LED optics, battery runtime, motion accuracy, accessibility, production-firmware parity, or operation of a distributed badge.
The README says palette and effect indices persist in CH32V003 flash memory and identifies a PD3 effect button and PD2 palette button. It does not establish a final firmware build, power-loss behavior across all revisions, input accessibility, user guide, release process, or recipient experience.
The design document describes Standby, Game, and Nyan modes plus a four-level puzzle in which spheres move through portals while users avoid or extinguish fire. The committed source contains standby, nyan, game, Simon, fire, display, random, and unlock modules. Design notes include TBD/possibly-change language, so this is a documented pre-event design and implementation trail rather than proof of final gameplay or attendee instructions.
The firmware defines 85 24-bit LED pixels and fourteen active-low input positions labelled for four personality spheres, four portals, radio, camera, Nyan, Aperture, turret, and cake. The design document calls these button/touch interactions. The sources do not confirm the final physical input technology, LED package, enclosure, brightness, current draw, or accessibility behavior.
The README consistently specifies eighteen side-emitting addressable LEDs, while using `WS2812-2020` in the overview and `SK6812D-EC3210R` in its feature list. The record retains the shared count and source labels without deciding which part number, brightness, color order, current draw, or final layout was manufactured.
The committed PlatformIO configuration targets `genericCH32V303CBT6` using the `ch32v` platform and `ch32v003fun` framework; firmware configuration enables the CH32V30x family and declares 128 KiB flash. No source identifies a final flashed event binary, board configuration, toolchain lockfile, test report, or recovery path.
The repository publishes starter scripts, a helper library, and code-challenge material for the named Cyber-Cat project. The release page reports no releases. This provides a public educational source trail, not a final installed event image, a configuration or operating guide, a supported update path, a source-to-device mapping, or a code/media reuse authorization.
The June announcement and August event-week guide identify a programmable circuit-board badge with five LEDs, three buttons, a mini screen, Wi-Fi, and USB programming. The partner archive gives a public hardware/software reference, but neither source independently audits every final board or recipient handoff.
Winglet OS 2.0 added ADS-B range and reliability work, Map Scope, GPS View, flight-board improvements, SD-card custom media, Wi-Fi scanning, USB-host reliability fixes, optional 3 A charging, and DC33 SAO support.
The Rust firmware exposes a Rhai scripting engine over USB serial, with bindings for system, inputs, SAO, display, LED, accelerometer, battery, Trx/Rx, and CAN behavior.
The case was printed in three PLA pieces, used integrated PCB slots and snap clips, and avoided screws or extra assembly hardware.
Pips801 publishes drawings, front/back PCB and test-jig directories plus firmware and UI trees; the Software README names an older PlatformIO build/erase/filesystem/upload path. The current public archive does not itself establish final production parity, a stable release, a complete build environment, a warranty-safe flashing path, an explicit license, or permission to republish source media.
Handler staff badges distributed missions and a chill-room base station reported aggregate progress, turning the badge game into a venue-wide social challenge.
The official schedule says attendees needed a 0xC badge for entry to the THOTCON 0xC party at Ravenswood Event Center.
The official storefront says entry is badge-only and that every attendee needs a valid event badge for venue access. It does not explain credential validation, name transfer, whether the listed product alone is sufficient, age/guest/sponsor conditions, venue capacity, door policy, or whether this party badge has any relationship to a DEF CON registration credential.
The Eagle 5 repository calls itself the HTH 2026 conference-badge firmware, and its publisher has a multi-year HTH badge archive. The official HTH organization previously forked the publisher's 2025 badge source. Together this supports a conservative badge-team association, not an assertion that HTH owned the 2026 repository or administered all distribution.
BSides Orlando's official site links the GitHub organization, whose profile calls itself the official GitHub organization for Security BSides Orlando and describes its Badge repositories as electronic badge firmware and designs. That organization published the public 2026-badge project. This establishes an organizer-published planned badge-design trail, not attendee inclusion, production completion, a credential function, or delivery.
Official Open Sauce pages establish the July San Mateo festival. Caleb Marting's archive names the 2026 badge, and an independent attendee archive calls itself replacement firmware for the 2026 Open Sauce badge. This supports a strong physical-event association without saying the organizer owned either repository or issued the board as a universal credential.
The attendee report lists Electronic Badge Assembly as one of the BSides Tampa 2018 activities for the more-than-750-attendee event.
The creator announcement directed attendees to spot clues around the convention and visit the Arts & Entertainment booth to participate in the badge challenge.
The 2024 Hardware Challenge Village description ties the badge to a competitive badge CTF contest and hands-on electronics tinkering.
Supercon ran badge-hacking awards for blinky, deadbug, over-the-top, and crypto-solving work, with public presentations and prize recognition after the event.
Post-event coverage records custom cartridges, enclosures, C demos, color-palette animation, splash screens, and a Linux-on-badge SDRAM cartridge project shown through the ceremony and hack list.
Post-event coverage documented camera, printer, charging, VR, thermal, time-lapse, and 3D-printer projects built around the official badge.
The 2009 contest drew 32 official entries, with Zoz's anti-surveillance system, Team Hack the Badge's sound-fearing blimp, and 501d3r Guy's multifunction dialer/voice amplifier taking the top three places.
The 2007 contest drew seven official entries, including Team Slackers' pGina single sign-on generator and Team Osogato's winning hardware/firmware line-level meter.
Grand Idea Studio hosted a badge-hacking contest for obscure or mischievous badge hacks, including synthesizer control, TV-B-Goon, multicolor LEDs, flame effects, and Morse-code firmware.
The 2025 Hardware Challenge Village description frames the badge activity around electronic tinkering, programming, and competitive CTF play.
The Supercon 8 Add On Contest pushed entrants toward functional SAOs using I2C, GPIO, sensors, displays, radios, and other active peripherals.
The challenge required collecting musical faceplate measures across multiple badge colors and using the combined melody to unlock later phone, URL, and friend-code stages.
The badge and surrounding event materials carried clues, hints, mini-puzzles, easter eggs, and the start of a weekend challenge rather than firmware or electronics.
Challenge writeups document suit symbols, 3-bit binary values, pi/e/Gray-code/LFSR ordering, program text, floor graphics, and badge comparisons feeding the badge-contest solution path.
The badge was a required tool for DEF CON's largest contest, connecting cryptology, social engineering, programming, and attendee interaction to the official entry badge.
Zoom, Intigriti, HackerOne, and CTF.ae challenge legs each produced binary flags that could be entered into the badge.
Hackaday documented a Sunday badge-hacking ceremony after roughly 78 hours of hacking, with categories for badge-only Vectorscope work and Vectorscope plus external hardware.
The pre-event CTF announcement says all challenges would be on-premise, purchase would not be necessary to compete, and five CHV badges would be available specifically to CTF participants. The scheduled event dates have elapsed, but final allocation and CTF operation remain unreported.
RVAsec layout and CTF sources place badge hacking and badge-challenge material in the 2018 CTF conference flow.
The official RVAsec 13 layout places badge hacking in the event context.
The official badge page and registration manual tie the badge to Hacker Challenge participation and document pairing the badge with the challenge server.
The registration guide says Hackers Challenge registration prompted for a badge ID and that the badge could show the current game score from the last 30 seconds.
Attendees visited a Hut 6 station with a teleprinter-style receipt printer to receive intercepted messages for Enigma decoding.
LayerOne's HHV challenge list tied the badge to Open Sauce badge work, ESP32 BluTag JTAG, RP2040 timing-attack exercises, and a custom shadetree companion-hardware target.
The official schedule says BSidesPDX 101 covered CTF, contests and events, badges, and more, and the speaker page says the panel discussed the thing around attendees' necks.
The official schedule says BSidesPDX 101 covered CTF, contests and events, badges, and more on Friday morning.
The official BSidesPDX schedule places Electronic Taxidermy: Badger Hacking in the workshop track with Michael Leibowitz on October 16, 2015.
The Calagator listing says Security BSides Portland had PCB badges, T-shirts, and bags to give away, with donors receiving them first.
BIC's 2025 event summary says badges and merchandise sold out and that proceeds helped raise funds for future programming.
The badge hosted a BENDER CTF variant playable directly on the badge while mirroring interaction over an RS232 serial connection.
The DEF CON 27 badge game used near-field magnetic induction badge interactions and role-specific badge types to advance through DEFCON letter levels.
The badge puzzle combined firmware, hieroglyphic shapes, binary codes, lanyards, venue clues, program material, and social interaction into a secret-society narrative.
The repository documents the Attribution Game clue/card workflow plus a Trick-or-Treat variant where attendees trade digital candy and cash it in for real candy.
The public late-July update announces DEF CON-week pickup points and a wearable multi-day infrared tag game, while final assembly and flashing remain in progress.
The badge could display the conference schedule, live Hacker Challenge score, and current location zone within the venue.
The official RVAsec 6 layout placed badges from HackRVA in the James River Terrace area.
The official agenda tells attendees to check in and pick up their conference badge and materials during the registration window.
The official challenge page tells attendees to inspect the badge and other neck-worn materials for clues, while keeping the 2026 challenge intentionally vague and hint-free.
The challenge expanded beyond the skull PCB into lanyard data, room keys, standee glyphs, DEF CON media-server files, conference CD material, and program equations.
Public writeups and attendee recaps describe DEF CON 23 key-card material as part of the noir-themed badge challenge trail.
The 2026 activities guide describes venue kiosks, SCAN mode, crank-built charge, printed clues, tasks, and LED animation rewards.
The official page says the CTF source became public, but this catalogue keeps that as event context because the source trail does not tie the CTF repository to badge firmware or badge hardware.
The official schedule and wiki describe a Badge Clinic where attendees could get help with assembly, features, repairs, hacking, and historical badge questions.
The guide points builders to Hardware Hacking Village equipment and personnel, and the event page says attendees could put their badge together there for the duration of the conference.
The badge was designed around CactusCon 11's Nightmare House theme and home-automation interaction rather than a generic blinky-only board.
The organizer ticket listing advertises a $30 optional BSidesFW 2026 e-badge add-on for the June 6 event. This establishes the offer and price snapshot, not order count, payment, manufacture, inventory, pickup, shipping, physical receipt, replacement, or attendee-wide distribution.
The current official venue and FAQ pages place BSides Tampa 2026 at the USF Marshall Student Center, 4103 USF Cedar Circle, Tampa, with participant check-in and registration context.
FirstBuild's public repository identifies a DefCon 34 washer/dryer badge and a FirstBuild / GE Appliances context, while DEF CON's own event source separately identifies the Baochip Human badge. Separately, a public Reddit author says they will give away 100 badges from a stated GE Appliances IoT Village booth. No reviewed official organizer source confirms that booth arrangement, and the sources do not say this washer/dryer project is a Human badge, is included with registration, grants admission, is issued by DEF CON, or has completed event availability.
The official BSides Maine account calls the main attendee badge a hackable lighthouse with a pulsing beacon.
HackNWA promoted a CTF, ASMb1337, Solder Village, and Badge/Hardware Hacking activities for the conference. The sources do not identify the VIP Assembled Badge as their subject, interface, prerequisite, prize, or device platform.
The public 2023 event listing says Circuit Board Medics would help participants solder and transform their conference badge, while the contemporaneous BSidesGVL announcement says the badges could become Wi-Fi analyzers and the team would be on hand with soldering stations.
The MiniBadge standard documents extender pins introduced for the 2019 Enigma badge and warns that unverified I2C hardware may be treated like a MiniBadge.
The badge used a bottom connector for minibadge holder boards, I2C port expanders, individual minibadge power control, and chaining of up to eight boards.
The official badge page and README document twelve minibadge spots, included female minibadge headers, and expanded minibadge support for the 2018 event.
The project file list exposes artwork archives, KiCad PCB material, Gerbers, and paste files for builders who wanted the shared visual identity.
Forum follow-up documented a 3x5 badge size and a practical color-copy plus lamination path for making the extra forum badge before or during the event.
The project linked an OSH Park shared board so remote participants could order boards rather than receive a centrally distributed official badge.
The badge exposes differential receiver and injector circuits, switched voltage references from 0 V through 4 V, high-impedance mode, and operation up to 5 MHz.
The badge docs expose voltage-glitch and crowbar controls, setup commands, trigger workflows, and target-voltage tuning through the GLiTCh BadgE CLI.
The official badge page lists RS485/Modbus RTU, CAN/CAN FD, 10BASE-T1S with an onboard physical-termination switch, and 10BASE-T1L as the field-interface set for OT, ICS, and automotive research.
JawnCon describes settling on pulsed infrared laser marking for the front labels, with about 45 seconds per badge and explicit open-air laser PPE warnings.
The README and firmware document `/leds` and `/leds/` routes for status, all/none/blink/chase/twinkle modes, individual LED state, and RGB color updates.
The official page names FreeWili Porpoise Purpose Firmware, USB serial terminal access, and OneWili API support for Rust, C/C++, Python, rThon, and WASM; it does not link a firmware/source archive or license.
The repository provides MicroPython application source and firmware documentation that describes compiled C modules and CTF challenge support. No reviewed release, tag, post-event guide, or device record verifies the production image or an owner-support path for 2026 units.
The designer archive describes its Bop It firmware and says at least two people hacked badges Saturday night and showed four new games Sunday. The independent attendee README calls the original a Bop It-style game and documents a replacement project. The record preserves the outcome at a high level without reproducing game, programming, or modification instructions.
The repository provides MicroPython application source, `flash.py`, esptool/mpremote prerequisites, separate firmware and application deployment paths, and host-side unit tests. The visible repository root has no explicit license and no tagged release is asserted here.
The listing describes SkittyOS graphics demos, scrolling text, font/character settings, independent screen modes, and flash-persisted settings, and announces future firmware with new graphics and puzzles. No firmware release, source, binary, flashing guide, or license is linked.
The source tree preserves app/game modules, CLI code, display buffers, platform HAL files, and generated image assets for the RVAsec 2026 badge software.
The public repository preserves firmware source for the low-power firefly LED behavior and links the hardware/software archive from the project README.
The 2014 badge firmware source was publicly released by RVAsec and preserved in HackRVA's GitHub repository.
The README says image-folder artwork is 12 pixels high and 1-bit, then converted into C headers for the firmware's bitmap display routines.
The badge exposed fading, freeze, binary blink, rave, and looping-animation modes through the badge button.
Writeups documented that entering the Konami Code on the badge buttons unlocked LED-eye behavior and serial text, even though the visible code path was not the final puzzle answer.
The firmware watches a pull-up mode button and triggers a named animation routine that ramps the center LED before stepping the grouped LEDs.
five-oh-BEE.ino implements display-backed message buffers, keyboard input, RF reads, RF byte writes, and byte-3 submission delimiters for simple pager/chat behavior.
The firmware defines two PWM pins and repeatedly writes sine/cosine-derived brightness values, giving the LED badge a simple animated lighting pattern.
The badge enumerated over USB and exposed an interactive retro text adventure whose ASCII-art map mirrored the physical PCB face.
The public code repository defines a PlatformIO `ch32v` / `genericCH32V003F4U6` / `ch32v003fun` environment and provides C implementation material. It does not publish a final binary, release notes, version mapping, programmer details, full build prerequisites, flashing/recovery steps, signed update path, security review, support policy, or explicit license grant.
Badge Pirates' selectable BSidesKC 25 manifest names version 1.0.0 and an ESP32-S3 bootloader, partition, and firmware-binary path for browser flashing. It does not publish source code, a signed release, or a mapping to the 2026 Lunar Lander continuation.
The official guide specifies ESP-IDF v5.5.x with the Arduino core, an ESP32-S3 target, CH340 USB serial flashing, auto-reset, and a manual BOOT/RESET recovery sequence.
The talk describes Arduino C++ as the shipped development environment and demonstrates settings, Bluetooth scanning, Wi-Fi time synchronization, and NeoPixel status behavior.
The project links a compiled `DerbyCon7BadgeFirmware.bin` file and describes custom C firmware upload as part of the build.
The archive links basic blinky, seven-LED scanner, and grab-and-go sketches for the TDI 2020 off-the-shelf badge workshop.
The `thotcon-examples` repository preserves cleaned-up Arduino/ESP32 examples for touch input, LEDs, audio modes, display output, menus, mini-game placeholders, and credits.
Dustin Firebaugh's public repository preserves a C interpreter intended for the 2019 badge.
HackRVA discussed low-frequency serial transmissions from the speaker to nearby badge LED sensors.
The repository documents menu-driven badge apps, button handling, IR callbacks, LCD drawing, assets, and app templates.
Community firmware work modified the official source to broadcast as multiple badge types and complete other badges through spoofed interactions.
The firmware README documents a custom MicroPython 1.26.0 image with compiled badge-challenge modules and a Russ Hughes GC9A01 C display driver.
The repository provides a GPLv3 root license and README statement for the firmware. That source-license record is kept separate from any physical badge, manufacturing, branding, image, or support claim.
The repository README documents entering DFU mode and flashing provisioned human badge binaries; Hackaday.io discussion records bootloader and NAND flash loading paths.
JawnCon says the badge used RetroWiFiModem to simulate Hayes-style AT commands and control the LEDs.
Rabbit-Labs links RocketGod's full-functionality firmware for LCD, LED, and CC1101 access plus a zRCrackiiN/JBOHack alternate firmware described as limited LED-only Blinken Lights functionality.
The main firmware builds unique device names from Portland-style street and direction arrays so Banglets present local-flavored BLE identities.
The firmware repository describes firmware intended to emulate a car on one PCB, with C and Python areas, verification files, RP2040 flashing workflow, and socketcan/cansniffer output.
The current main script selects HiLo, DTMF, Kode, and Rock-Paper-Scissors games, updates associated LEDs, registers buttons, and restores a random idle blink mode.
The technical archive links the badge source-code tarball and labels the code as public domain.
The v1.0.0 release publishes VillaHacker.hex for badge reprogramming, while the README says badges come with pre-installed firmware.
GitHub Releases publishes the v2026.2 UF2 binary plus a v2026.2-ctf prerelease binary for the 2026 badge.
The firmware repository is detected as MIT and documents PlatformIO `hardware-v3` and older-revision environments; v4.0.0 publishes v3 and v2 binary assets. The source depends on a side-by-side local `esp32-utilities` repository and does not establish a supported update path for every physical unit or a released v1 v4 binary.
The July source archive includes firmware code for a badge CLI, LED animations, BLE-related components, and CTF state material. The catalogue records the published source context without giving operational, radio, flashing, or challenge-completion instructions or claiming a deployed production image.
The project page says attendees could ask Great Scott Gadgets for help reflashing the badge firmware.
The repository preserves a simple sample firmware and an advanced configurable hotkey firmware guide for post-event customization.
The README requires Adafruit NeoMatrix, Adafruit NeoPixel, and Adafruit GFX libraries, while the sketch uses NeoMatrix drawing primitives for scrolling text and pixel mouth images.
Gigawatts documented burning an Arduino Leonardo bootloader over ICSP with a Bus Pirate so the badge could accept Arduino IDE sketches over USB.
The repository guide documents Earle Philhower RP2040 board-manager setup, required Adafruit libraries, 2 MB sketch/filesystem partitioning, upload, and copying data files after first boot.
Forum and reversing sources document booting into mass-storage/BOOTSEL behavior and using picotool or chip-off workflows to dump or replace firmware.
DEF CON's archive announced C-style badge code and a badge-hacking-file torrent so attendees could continue writing and studying badge software after the conference.
Great Scott Gadgets documents entering bootloader mode from RfCat, using `bootload.py`, erasing, and downloading properly linked RfCatDonsCCBootloader firmware images.
The badge writeup documents onboard CH340N USB serial access plus wireless firmware-pull behavior used during the conference.
The badge guide frames the device as a CircuitPython learning platform after the conference, with USB serial/Python CLI access and editable `code.py` storage contents.
The project documents BOOTSEL entry, a CircuitPython UF2 copied to `RPI-RP2`, library and Python-file copy steps, and source-level paths for remapping keys, patterns, colours, and states.
The README documents holding the button while plugging in USB for DFU mode, Zadig/WinUSB setup, dfu-util upload, 454hex2dfu conversion, and Pickit fallback programming if the bootloader is overwritten.
The watch badge firmware used Arduino IDE, the ESP8266 Arduino core, ArduinoJson, Generic ESP8266 Module settings, and serial flashing.
The wiki points badge hackers to an ESPHomeBadge path as an alternative way to write firmware for the HOPE XV badge.
The Handorf guide says firmware would be loaded by staff at the info booth after assembly.
The firmware template exposed camera, accelerometer, button, OLED, timing, and filesystem helpers so attendee applications could reuse the stock badge services.
The repository README describes MicroPython setup over serial terminal, Thonny, or VSCode, with boot.py/main.py demos and memory-style I2C read/write patterns.
The wiki documents erasing and flashing ESP32-C3 MicroPython firmware, using serial console access, running scripts with mpremote, and copying code to run at boot.
MicroPython, front-panel buttons, joystick control, filesystem access, and mpremote/Thonny/VSCode workflows let attendees write and store custom vector demos on the badge.
The quick-start workflow let attendees copy compiled HEX files to MicroSD and use the onboard bootloader, with PICkit programming as a fallback path.
The firmware README documents ATTinyCore board settings, external programmer needs, micronucleus USB bootloader use, and command-line flashing steps.
The upload-code guide documents HHV Raspberry Pi flash stations, CH340G driver setup, esptool.py flashing, `latest-spiffs.bin`, and Lua upload tools such as nodemcu-uploader and ESPlorer.
The DEF CON media-server badge directory published hardware, firmware, game, music, asset, and later FREEWiLi firmware files for post-event hacking.
The VoCore notes document OpenWRT buildroot setup, LuCI and USB-storage package choices, sysupgrade flashing, first-login password setup, SSH/telnet access, and opkg package work.
DEF CON's media-server update and forum-curated notes documented flashing the PIC32MM0256GPM048 with MPLAB X IPE and PICkit 3 or 4 to reach newer firmware versions.
The badge update pipeline patched one-bit 240x96 image data and a hash into a base firmware image, then reflashed the badge with cc-tool and CC Debugger hardware.
Parallax and DEF CON published firmware, schematic, top-level objects, LED examples, VGA/PS2 examples, and conference-DVD materials for post-event badge hacking.
Great Scott Gadgets documents compiling R8C code with a GCC cross-compiler and flashing through a 3.3 V FTDI serial interface plus DJ Delorie's flash tool.
The README documents STM32CubeProgrammer DFU flashing, separate STM32 and FPGA HEX files, TEST-pin bootstrapping, and first-boot test mode.
The badge could save and load programs over serial to another badge or computer and store programs in internal flash slots for later recall.
Grand Idea Studio documents a static serial bootloader for in-the-field firmware upgrades and links the CodeWarrior source archive.
The repository preserves esptool.py commands for restoring stock firmware plus a workshop PDF used for THOTCON 0xA badge hacking.
Forum and field-report sources document firmware updates through USB storage/UF2-style workflows and role-specific challenge firmware behavior.
Microchip adapted a bootloader so the badge appeared as a HackABadge USB disk where attendees could drag compiled HEX files for flashing.
The public CAD archive documents USB-to-serial programming context, CH340N evidence, and MicroSD support.
The CC13 archive comments document USB-to-serial programming, MicroSD, and buzzer hardware context.
The CAD tree includes USB connection sources and board evidence for a USB-C and CH340N serial programming/debugging path.
The PCB silkscreen records ATtiny1614 Arduino instructions pointing builders toward the megaTinyCore workflow for the microcontroller family.
The maker post says there is only a small batch, the badges are not for sale, and they will be given away randomly throughout ‘the con.’ It does not establish a quantity, eligibility rule, selection method, exact times/locations, reservation system, partner, recipient list, actual handoff, shipment, replacement, or post-event result.
The public r/Defcon author says another 100 free badges are planned at the stated GE Appliances booth in IoT Village and that an unspecified number will be given away each day. The statement does not give a daily split, distribution dates or hours, eligibility, queue or pickup process, recipient list, completed build count, final physical stock, completed handoff, or official organizer confirmation.
In a public comment, the author says the badge was designed in-house at FirstBuild and that employees created the artwork, PCB design, and software. This preserves a narrow public provenance statement without identifying individuals, establishing the author's employment or authority, independently verifying every contribution, assigning image rights, or extending the statement into a formal FirstBuild, GE Appliances, or DEF CON attribution.
The README documents flashing badge2022_c.uf2 through the Pico/RPI-RP2 USB mass-storage path.
The README says to hold the small button beside the screen while connecting the badge over micro USB, then copy the UF2 firmware to the mounted RPI-RP2 filesystem.
The README documents building firmware.hex and programming the badge over USB with bootloadit tooling.
The README tells builders to use USBasp udev rules, add the 5ohBee board package to Arduino, install the SmartResponseXE library ZIP, compile sketches, and upload.
The README says holding the center of the left wagon wheel while power cycling enters programming mode for Arduino SDK upload.
The Badge Pirates shipping update says badge purchasers would be emailed after customs clearance and could choose pickup at later events or mailed delivery.
The package included a coupon for a custom MiniBadge, preserving a virtual-year path from shipped badge kit to personalized MiniBadge fulfillment.
After the bundle closed, organizers said they had begun bulk ordering shirts and badge supplies and hoped to ship bundles soon.
The home page describes the badge bundle as a pre-order shipping a few weeks after the conference, with orders closing on the last conference day.
The listing says BadgeLife proceeds support EFF's mission, and its FAQ says the project is officially affiliated with EFF but organized independently by H4r0ld and V3rbaal, with EFF aware of and supportive of the fundraising efforts. The source does not publish financial or donation-accounting terms.
The public roster says code or firmware will be available after the con, but provides no URL, release date, source license, binary, build instructions, hardware target, flashing method, support channel, or evidence of a completed release.
The README and firmware document `/flag` and `/flag?newflag=...` behavior, with source code initializing the default flag as BADGERMASTER.
The public repository lets badge hackers modify the FPGA SoC, bootloader, Initial Program Loader, SDK, example apps, and peripheral blocks instead of only writing firmware on a fixed MCU.
The project describes a mini prototyping area with 3.3 V rail, battery rail, and PSoC4 I/O broken out so attendees could add their own components.
The hardware repository visibly contains KiCad board/schematic/project material, BOM/position files, front/back/order Gerbers, and acrylic directories/files. The published tree is traceability evidence, but this pass did not reconcile it to a final 2026 populated board, fabrication order, component sourcing, acrylic process, assembly/test procedure, host connector/power design, or explicit license.
The reviewed snapshot preserves KiCad, Gerber, BOM, and Arduino-style source material. The README says conference badges used earlier firmware than later source behavior, so the archive is not treated as an exact event-day deployment image.
The badge README documents an ESP32 Wi-Fi module running MicroPython, and the repository preserves the source tree and binary image used to operate the badge.
The maker lists an ESP32, USB-C, rechargeable Li-Po, ten LEDs, a screen, and one button. It describes short presses as scrolling and long presses as selecting, but does not publish component variants, circuitry, pinout, power details, or electrical documentation.
The BOM lists an ATTINY85-20SUR microcontroller and the Eagle schematic instantiates U1 as a Tiny85-20-SMT device.
The firmware README describes the badge as ATTiny861-based, and the BOM lists an ATTINY861A-XUR / ATTINY861-class SOIC-20 controller.
The badge used an ATmega32u4 with four RGB NeoPixels, three potentiometers, micro USB, and two CR2032 holders.
Hackaday and the build guide identify the reverse-side microcontroller as an ATtiny841 / ATTINY841-SSU.
The repository BOM lists an ATtiny85-20SUR microcontroller and 24 blue side-view LEDs as the badge's main active components.
TechGirlMN's hardware guide centers the remote badge build on an Arduino Nano mounted to a solderable breadboard-style PCB.
The README describes the BSidesPDX mask modification as using an Arduino Pro Micro-class board with ATmega32U4 and USB Micro instead of the original Arduino Nano approach.
The project page and postmortem document a Rigado BMD-300 module based on Nordic nRF52 with ARM Cortex-M4F, 512 KB flash, 64 KB RAM, integrated antenna, Nordic S132 SoftDevice, TFT display, WS2812B LEDs, sensors, and microSD.
The repository BOM lists a BMD-300 module and the Eagle schematic exposes the Nordic/BMD-300 pinout, SWD pins, NFC pins, and power connections.
The project page identifies the DC27 badge core as a Rigado BMD-340 module with Nordic nRF52840, paired with power regulation, capacitive touch, SWD/Tag-Connect, USB-C, and SAO 1.69bis hardware surfaces.
The official badge guide identifies the badge as a Cyberpunk Bunny PCB powered by an ESP32 and packed with cryptography, wireless hacking, and hidden secrets.
Rob Rehrig describes the 0xB badge as an ESP32-based design in an NES-controller and circus-ticket form factor.
Hackaday.io and the repository README document an ESP32-compatible badge architecture with capacitive touch-wheel input, center button, TFT display, buzzer, LEDs, and LiPo power context.
The HOPE wiki documents an ESP32-C3 badge core with 16 WS2812-class RGB LEDs and attendee-facing light-pattern controls.
The commit-pinned BOM identifies the ESP32-C3-MINI-1-N4, buttons, red and blue LEDs, switch, display/driver footprints, six-pin SAO connector, 3.3 V regulator, and three 1×AA battery-holder footprints. It does not establish final population, battery wiring, or uniform delivered hardware.
Badge Pirates identifies the central controller as an Espressif ESP32-S2 WROOM with 2.4 GHz Wi-Fi for the badge's IoT behavior.
The CC13 KiCad archive comments identify an ESP32-S3 WROOM N16-class badge core with Wi-Fi/Bluetooth LE context.
The CactusCon-12 CAD archive identifies an ESP32-S3 WROOM core for the ProjectNeoRogue badge hardware.
The public CC14 CAD/archive evidence identifies an ESP32-S3 WROOM core for the conference badge hardware.
The project page and retrospective document the move to ESP32-WROVER for WiFi/Bluetooth, external RAM, LULZCODE memory needs, and faster display/SD-card paths after the DC25 BMD-300 badge.
A contemporary Hackaday.io project log describes the ShmooCon 2018 badge as basically an ESP8266 with serially addressable LEDs.
The firmware source includes ESP8266 Wi-Fi, WiFiClient, ESP8266WebServer, and mDNS support and serves a BSides PDX 2015 Badger web UI.
The hardware README describes a Raspberry Pi RP2040 badge design derived from the Seeed XIAO 2040 with 16 MB SPI flash.
The hands-on coverage and project-owner comments identify an STM32F103CBT6 ARM Cortex-M3 controller running at 72 MHz with the badge firmware built through STM32Duino-style tooling.
The repository README identifies the THOTCON 0xA badge base as a SparkFun ESP32 Thing Dev board.
The README directs builders through SparkFun nRF52832 Breakout Arduino compatibility and variant-file changes for the badge target.
Hackaday identifies the badge controller as a TI CC2640R2 with ARM Cortex-M3 core and Bluetooth capability, paired with a Holtek HT16D35B LED controller.
The writeup identifies the badge as a tiny Wi-Fi and Bluetooth scanner made from a WemOS board.
The sketch README describes the Banglet board as a Feather-style nRF52/Bluefruit design modified into a wrist-worn form factor.
The official store says the board's intended SAO connectors are wired mirrored and are not functional with a standard SAO, with no time to correct the layout before the convention. This is a source-specific compatibility limitation, not a generalized claim about all Gothcon or DEF CON hardware.
The guide documents an RP2040 microcontroller / Raspberry Pi Pico board manager for button inputs, LED control, battery charging/status, and power management.
The hardware repository visibly contains a KiCad PCB and schematic plus BOM, position, Gerber, backup, and layout files. The published tree is useful for traceability, but this pass did not reconcile it against a final populated board, fabrication output, BOM sourcing, test procedure, connector pinout, power design, or any explicit source license.
The hardware repository visibly contains KiCad board/schematic/project material, BOM/position data, front/back/prototype Gerbers, backup files, and a PFC161 datasheet. The published tree is traceability evidence, but this pass did not reconcile it to a final populated unit, fabrication order, component sourcing, test procedure, connector/power design, or explicit license.
The current repository includes V4 documentation for an ESP32-WROVER platform with LEDs, buttons, accelerometer, LiPo/power circuitry, display headers, buzzer, and expansion pads. Its 2025 wording and old schematic link keep this as context rather than a claim about every optional 2026 e-badge unit.
The technical archive publishes schematic and Gerber documentation and states that the documentation is Creative Commons Attribution licensed.
The post-event teardown identifies the badge core as an ESP32-S3-WROOM-1 and documents firmware extraction using ESP32-S3 tooling.
The badge exposed waveform-generator outputs, scope inputs, and through-hole prototyping space for filters, curve tracers, oscillators, analog video experiments, and external signal hacks.
The badge exposed both Type A and Type B SAO connectors, with community notes tying SAO behavior and add-ons into the badge challenge trail.
The badge page documents two Shitty Add-Ons ports on the top corners of the badge and says the ports had no rotation.
The Supercon version added proto-board support and documented GPIO, I2C, serial, and SAO-style expansion paths for attendee-built peripherals.
The badge exposed I2C, UART, GPIO, ISP, TTL232, and prototyping surfaces for shields, sensors, and direct hardware experiments.
The README and writeup document Adafruit Feather mounting on the back with pins broken out to test points for user-added electronics.
The 40-pin cartridge slot and prototype cartridges with onboard flash let attendees build removable hardware and software modules for the badge.
Remaining GPIO pins were broken out, and a separate development board was available at the Hardware Hacking Village for extra components or functions.
The hands-on article documents 11 GPIO pins plus RX/TX, DIO, RST, power, and ground breakouts as hardware-hacking surfaces.
The badge exposed a GoodFET-compatible programming connector for installing or replacing the bootloader, plus test points for spring-pin access.
The official badge site documents labeled voltage, ground, audio, headphone, and jumper pads plus unlabeled prototyping pins.
The public design archive preserves MicroSD, buzzer, and Badgelife SAO v1.69 expansion evidence for badge hacking and add-on use.
The README documents an optional Vishay TFBS4711 IR transceiver path, debug LEDs, UART/test points, expansion pins, and WS2812 data access for further hardware experimentation.
The CactusCon 12 board file includes a Badgelife SAO v1.69 footprint for add-on expansion.
The BOM and board pinout document an SAO v2 connector plus SAO I2C and GPIO assignments available to firmware and badge hardware experiments.
The main badge exposed six SAO connectors with individually accessible GPIO and split left/right I2C buses for experimenting with add-on peripherals.
The front and back of the badge left space intended for a Teensy expansion.
The large badge-hacking kit supplied the components needed to turn the ToorCon 13 badge into an Ubertooth-capable passive Bluetooth monitoring device.
Attendees received PS/2 adapters and a VGA connector and could add them in the Hardware Hacking Village to turn the Propeller badge into a small computer system.
BSidesSLC lists Micro-USB or three-AA power, three mini-badge expansion slots, a UART point, reset and flash buttons, and a USB/battery power switch. The source does not establish final electrical limits, safe modification procedures, or every delivered configuration.
The hardware guide documents two 10-pin side ports with power, ground, and GPIO for external modules, lanyards, or hardware modifications.
The board source contains two footprints labelled Header_SAO, 3 mm mounting holes, and unassigned plated through-holes; its own board text says users can customize the badge with their own circuits and mount rear LEDs through bare substrate. It does not establish an SAO version, pinout, voltage, host compatibility, included peripheral, or safe modification procedure.
The winning contest entry connected badge LED behavior through a stereo plug into an analog synthesizer as event generators and added piezo debug output.
The official page explicitly notes that hacking the hardware to turn all LEDs on would probably also deserve the cool swag.
The FTDI log documents the badge's FT2232H channel split, with one channel for UART/JTAG/SPI/I2C/bit-banging hardware work and the other for the badge SoC serial terminal.
The public firmware maps 44 WS2812B LEDs to IO10, directional buttons to IO4/IO3/IO0/IO2, and identifies separate BOOT and RESET flashing controls. The store names ESP32-C3 with 4 MB flash; the repo does not establish every production-board part or measurement.
A Veritas attendee report describes the 2024 HCV badge as an integrated-circuit electronic badge with a four-line LED screen and joystick, powered by battery or USB-C.
The badge exposed infrared transmit/receive hardware, touch-pad buttons, LEDs, USB programming, and accessible I/O so attendees could interact during the event and keep hacking afterward.
DEF CON 18 coverage documented USB connectivity as part of the badge's intended hackable interface.
The maker describes a beginner-friendly kit in which the bridge and back-layer NeoPixels are pre-soldered and the builder solders header pins plus through-hole chip parts. The listed board set is the back layer, bridge, top SAO, city, water, and frame PCBs.
The work-in-progress BOM lists USB-C connector and protection parts, a charge-controller section, power switch, AA connectors, regulator parts, and charge/status LEDs without documenting the final board or battery assembly.
The BOM documents alternative display modules, an RP2350 section, and an ESP32-S3-WROOM-1-N8R8 option, while the separate pinout is explicitly for an ESP32 version. These are development choices, not a confirmed final badge configuration.
Raspberry Pi's article and the PamirAI user guide identify the badge around a Raspberry Pi Compute Module 5 platform intended to run local, private, interactive edge AI.
The Hackbat README documents the ESP32-C3 WROOM module as the badge core, with 2.4 GHz Wi-Fi, BLE 5.0, and Arduino IDE or ESP-IDF programming paths.
The workshop page describes the supplied hardware as an ESP32 badge board, and the board README documents an ESP32-S3 demo board for Aranya Embedded.
The official page lists Heltec Wireless Tracker V1.1 hardware with ESP32-S3FN8, SX1262 915 MHz LoRa, UC6580 GPS, TFT display, user button, RGB LED, buzzer, and 450 mAh battery.
Village-sold Differential Destroyer boards were documented as Pico 2-compatible and bundled with a Pico 2 flashed with current firmware.
The README and firmware document a Raspberry Pi Pico / RP2040-class badge with two AAA batteries, TFT display, buttons, LEDs, DAC drive, current/voltage monitoring, and electrode output hardware.
DEF CON described the DC32 badge as the first RP2350 board, while Raspberry Pi sources document the badge as powered by RP2350.
FREE-WILi documents the badge around a Raspberry Pi RP2350A controller and ESP32-C6 Wi-Fi interface, with standard USB bootloader update support.
The RTFM BOM documents an STM32F412RET6 badge with a 0.96 inch OLED, ST7735 128x160 TFT, APA-102C LEDs, USB-C, BlackBerry Q10 keyboard, and coin-cell holder.
The companion hardware repository includes KiCad project/schematic/PCB material, Gerber and production directories, board variants, position data, acrylic DXF/SVG files, and manufacturing-oriented archives. Recent commits include board bug fixes and acrylic SVG work. GitLab shows no detected license, and the source does not establish a final approved BOM, build instructions, production completion, or safe redistribution/assembly permission.
The PCB repository publishes hardware artwork and errata under a CC BY-SA 3.0 statement attributed to Sprite_tm / Jeroen Domburg.
The repository preserves Eagle board/schematic files, generated Gerbers, LCD and RJ45 component documentation, and graphics assets for the historical badge archive.
The repository preserves KiCad project files and Gerbers so builders could fork or fabricate the unofficial Remoticon board.
The Hackaday.io project published the badge as a KiCad design with regular 0.1 inch pad-grid space intended for user-added circuitry.
Alex Glow's June 15 public archive includes a KiCad 9 project, custom footprint library, Gerber CAM outputs, drill files, and job file for the badge. It provides a useful design/fabrication trail but does not prove a completed build run, final bill of materials, assembly process, test result, or event-issued unit.
The archive contains native KiCad PCB and schematic files plus footprint and asset directories. The catalogue links that research value without representing the current archive as a guaranteed exact production package, a ready-to-manufacture record, or a safety-validated build.
The repository preserves Eagle board, schematic, and library files for the DC503 2018 Banglet hardware design.
Hackaday and the project files describe a MicroMod carrier-board variant, with later logs showing hand-soldered spacers, joysticks, USB through-hole pins, screen, and a RISC-V MicroMod module.
The activity guide identified R1, R2, and C2 as the 555 astable timing parts and encouraged attendees to change oscillation speed.
The maker says the SAO was created for DEFCON 33, then separately says a few leftover units can be pre-ordered for pickup at DEF CON 34 or BSidesLV. The live page showed $15, five sold, zero remaining, and a free Saturday August 8 BadgeLife Village pickup label. This documents a later leftover listing, not a record of original 2025 distribution, sale, recipient allocation, or completed 2026 handoff.
The official product page identifies SAO Many SAOs as a DEFCON 33 badge, while the July 2026 roster explicitly calls it Update to Existing. This preserves the later maker listing without creating a second DEF CON 34 artifact. Neither source proves the original DEF CON 33 handoff, a 2026 new board, event authorization, purchase, pickup, shipment, or delivery.
Red Team Summit's official history calls the 2025 Redmond artifact the first Red Team Summit with an electronic badge. The statement confirms an event-specific electronic badge but does not describe its design, allocation, or use.
redactd's listing introduces Dante's Inferno just in time for DefCon 32. This establishes a maker-stated independent 2024 event association, not DEF CON issuance, registration inclusion, a Human-badge replacement, admission, organizer endorsement, quantity, or completed handoff.
The DEF CON 33 Creator Events List schedules a Friday BadgeLife Community Table 1 Badge Drop naming Submarine Badge, FrogStar Badge, and FightDystopia Badge, with Jeff “BigTaro” Geisperger named as creator. This establishes a publicly scheduled 2025 FightDystopia activity, not attendance, inventory, sale, recipient allocation, completed handoff, organizer issuance, or admission function.
The DEF CON 33 Creator Events List schedules a Friday BadgeLife Community Table 1 Badge Drop that names the Submarine Badge, FrogStar Badge, and FightDystopia Badge, with Jeff “BigTaro” Geisperger named as creator. This establishes a publicly scheduled 2025 FrogStar activity, not the number made, attendance, sale, handoff, recipient allocation, completed distribution, organizer issuance, or admission function.
The recovered DEF CON 33 schedule lists a 10:30-10:59 PDT BadgeLife Community Masonic33 Badge drop credited to Heal-Hak4Kidz. This establishes published 2025 creator activity, not organizer issuance, attendance entitlement, confirmed stock, completed handoff, recipient allocation, or admission function.
The DEF CON 33 Creator Events List schedules a Friday BadgeLife Community Table 1 Badge Drop naming Submarine Badge, FrogStar Badge, and FightDystopia Badge, with Jeff “BigTaro” Geisperger named as creator. This establishes a publicly scheduled 2025 Submarine activity, not attendance, inventory, sale, recipient allocation, completed handoff, organizer issuance, or admission function.
The Hacker Couture DEFCON 33 Product List names a Gunslinger-B-Gone Badge by BigTaro at $140. This establishes a published 2025 DEF CON vendor-list association, not a BadgeLife drop, organizer-issued item, attendance entitlement, confirmed stock, completed purchase, handoff, or attendee allocation.
The official shop displayed free pickup at DEF CON, U.S. shipping priced at $20–$30 plus tax, and contact-based global shipping, with order caps. The current page now hides ordering and displays a no-payment second-run interest form because all first-run inventory is sold out. These past/current storefront terms do not prove buyer handoff, event pickup, shipment receipt, future rates, or a completed second run.
Hak4Kidz Lab's live same-name Tindie listing calls v2.2 an upgrade from a 2019 v1 and says it was made for DC31; it currently displays $30. The roster's current DEF CON 34 row instead says new and approximately $35 at Hacker Warehouse. The sources do not say whether those sales paths use identical stock, components, finish, packaging, installation parts, price, or revision.
MakeItHackin's live $30 Tindie listing, repository, and tutorial describe a differently named Tricorder SAO, including separate rechargeable-battery and badge-powered forms. The current roster calls its $125 artifact an Original Series Tricorder badge with various sensors. The sources provide no formal revision, parts, behavior, price, or stock mapping between the two products.
NilbinSec's DC32 repository lists two 470-ohm resistors, three flashing RGB LEDs, one cloudy red LED, and a 2×3 shrouded SAO header, with Gerber files and assembly orientation notes. It supplies a traceable older design surface but does not prove that every planned 2026 unit uses the same PCB, component values, LED speed/colors, header, finish, or behavior.
`chv_badgetools` provides `chv-candump`, `chv-cansend`, automatic USB-port discovery, and a `python-can` interface plugin for the DEF CON 34 CTF badge.
The repository documents a Python MCP server and Claude skill plus a local web control panel and HTTP API that send JSON/event commands over the badge's UART connection.
The host README and firmware document HID writes that stage data in RAM and commit it into flash for later keyboard/macro output.
The official wiki says each attendee received one Shadybucks wristband at registration and activated it at Shadytel.
The current official FAQ says every participant gets access to all tracks plus a BSides Tampa shirt, badge, lanyard, and happy-hour access.
The Wikimedia Commons documentary photo shows a physical BSides Tampa 2018 badge/lanyard artifact, now published as a cropped WebP derivative with CC BY-SA provenance.
The Commons description identifies the photographed object as the badge issued at the tenth Hackers On Planet Earth conference.
DEF CON forum feedback describes the standard DEF CON 25 badge as a rubber or plastic admission artifact rather than a powered electronics platform.
The official event and first-timer pages say students with a valid student ID attend free with a paper badge and no electronic badge.
The badge used a persistent low-power 128x32 display and role-colored variants for human, vendor, speaker, contest, goon, press, and uber-style identities.
The assembly guide documents the People Badge with attendee, staff, volunteer, and speaker status color variants and says everyone gets an attendee badge.
The archived page lists attendee, staff, committee, VIP, and speaker MiniBadges, including attendee badges in registration materials and VIP badges handed out by Jup1t3r.
JoeSchmuck posted a PSD/JPG forum-avatar badge template with blank space for a username or nickname and invited forum members to use or modify it.
The game repository references ST77xx display libraries, NimBLE, QR-code support, and a buzzer-oriented sound module. It does not publish a stable radio protocol, user-consent model, player-data practice, safe electrical design, final UI, host compatibility matrix, or proof that these modules ship together in a DEF CON artifact.
The NilbinSec announcement and product page describe two included SAOs, red and blue fighters, with game data and hidden interactions carried through EEPROM.
The listing says the badge comes bundled with an exclusive Pirate Flag SAO and stickers. It does not publish the SAO's components, pinout, power draw, host compatibility, circuit, firmware, license, standalone availability, final delivery, or image-reuse permission.
The same first-hand source says a MiniBadge was included with the 2020 badge package, without recovering enough public detail to describe its electronics or designer attribution.
If no SD card was inserted, the transmit state used the infrared path for TV-B-Gone-style remote-control power-off behavior.
The MIT-licensed OpenLASIR repository defines a NEC-inspired 38 kHz, 32-bit infrared interoperability protocol and identifies the 2026 Laser* Tag Badge DS as a first-party supporting badge.
The reveal and firmware docs document a custom keyboard, TCA8418 keyboard matrix controller, wide LCD, LVGL MicroPython UI pages, and function-key app workflows.
The MK9 is a nine-switch 3×3 mechanical macropad with N-key-rollover USB HID output; the published badge mode maps it as a numpad when connected to a host.
The README documents three capacitive touch sensors for wheel input plus a center capacitive button, matching the touch-wheel interaction model described in the project writeup.
The public firmware documentation describes nine per-key WS2812B LEDs and six SK6812 edge LEDs, plus tilt-reactive colour changes, shake-to-cycle patterns, and per-key ripple effects using an MSA301-compatible accelerometer.
The related Jr Hacker badge used an ESP8266 platform with IR tag gameplay, speaker, vibration motor, and WS2812 hit counter, with source material preserved under shark-badge.
The current kit inventory and DC32 guide enumerate three addressable LEDs, five blue LEDs, one bright white LED, eight 47 Ω resistors, three capacitors, a 3.7 V / 1,200 mAh LiPo, battery adhesive, JST/PH wiring, and board-to-board headers. The guide calls for through-hole assembly and battery wiring, not a safe modification or battery-service authorization.
The Hacker Couture DEFCON 33 list repeats Dante's Inferno Badge at $100 with the core three-board, sixty-LED, CR123A, and one-SAO-port description. This is retained as a later vendor-list recurrence of the DEF CON 32 artifact, not a duplicate DC33 badge, scheduled drop, organizer-issued item, confirmed stock, completed purchase, handoff, or attendee allocation.
The maker page describes online leaderboard score syncing over LoRa if RF conditions permit, with QR-code encoding of game data as the documented fallback.
The repository includes an Apache-2.0 license file for its published source tree, while this catalogue still leaves the hero image empty until a specific reusable photo or upstream render is cleared.
The Hackbat documentation lists four WS2812 smart LEDs on the badge board.
The organizer's post-event account says only about five manually assembled advanced badges were prototyped after the planned automated-assembly path did not result in a fully assembled badge for every attendee.
The WWHF e-badge page says the 2025 electronic badge was sponsored by Antisyphon Training.
HackRVA describes the RVAsec electronic badge programme as a recurring badge-team effort with schedules, games, and surprises.
Official and EFF event pages anchor HOPE X as the tenth HOPE in New York City on July 18-20, 2014, giving the physical badge a clear place in the HOPE lineage.
U.S. Army coverage identifies the 2024 8-8-8 badge as AvengerCon's first electronic badge.
Cisco's 2015 write-up frames SAINTCON's show-badge program as having run across the prior two years, supporting 2014 as part of the event's early badge lineage.
AoSC describes Micro-USB, one large touch pad, three NeoPixel groups, a small speaker, and no battery. The linked Coin M0 profile instead describes native USB-C, three capacitive touch pads, three RGB-NeoPixel groups, and a speaker. The shared lighting/audio concepts are source-backed, but the exact connector, touch count, board revision, LED count/current, speaker part, power path, and final 2026 configuration remain unresolved.
The source maps a left multi-press mode selector, right Attack/Trigger switch, four color-coded status LEDs, optional 9600-baud UART debug output, and ATtiny1614 serialUPDI programming context. The README gives an avr-gcc/ATtiny device-pack/avrdude outline and says a later convention reflash may happen, but no supported end-user programmer, fuse configuration, tagged release, update package, recovery guide, or warranty is published.
Cisco Connected Mobile Experiences data supplied the venue-location context used to personalize badge behavior and analyze attendee movement.
The README says Mode 1 cycles GPIO1/GPIO2 on the left badge port. The current source drives four two-bit patterns, releases the lines, samples them, and then listens for edges. NilbinSec explicitly warns that this mode may harm a main badge depending on its GPIO configuration, so the source does not establish a safe, supported, or authorized use on any connected device.
The README describes Mode 2 as triggering the open-drain CPU wake-up interrupt on GPIO4 of the right SAO port. The source holds its configured GPIO line low while the Attack/Trigger switch is pressed, then releases it to high impedance. This documents the public implementation, not a safe/authorized use, final badge compatibility, or successful challenge result.
The README broadly says Mode 3 cycles 0x00–0x7F while listening as an I²C slave. The source instead documents passive bus observation over 0x08–0x77 and explicitly skips 0x19 and 0x3C. It says it does not drive SDA/SCL or ACK, but this is still not a guarantee of target compatibility, complete address coverage, bus safety, or authorized testing.
The sources name an ATtiny1616, five reverse-mounted addressable LEDs, rear ambient-light LED, handle setup LEDs, two physical controls, CR2032 power with polarity protection, a more efficient 3.6 V boost converter, and external MOSFET gate. They do not establish final PCB/schematic/BOM, exact LED or power configuration, current draw, runtime, electrical limits, fabrication, test result, safety validation, or that all delivered units use the documented REV1 design.
The repository README calls Beelzebub a holder for five minibadges, while the store says the board is assembled except for minibadge headers and an optional battery holder, and excludes shown minibadges. Those statements do not establish the exact slot layout, header/pinout, MiniBadge standard, power/clock/data behavior, soldering skill or safety requirements, attachment force, mechanical fit, contents of every unit, or compatibility with a particular minibadge.
The repository README calls Krampus a holder for six minibadges, while the store says the board is assembled except for minibadge headers and an optional battery holder, and excludes shown minibadges. Those statements do not establish the exact slot layout, header/pinout, MiniBadge standard, power/clock/data behavior, soldering skill or safety requirements, attachment force, mechanical fit, contents of every unit, or compatibility with a particular minibadge.
The vendor list says CTF challenges unlock extra features and bling modes, names Drinking Roulette, and calls the product fully programmable. No source publishes game rules, age/access policy, challenge/solution path, reset path, player scope, score service, firmware, configuration, content rights, data handling, or security review.
The vendor PDF says the Sheriff SAO supports laser-tag play that makes friends' badges light up and that an IR blast can power down TVs. It does not identify transmitter/receiver parts, carrier/protocol/code set, range, target compatibility, consent/safety boundaries, power, regulatory context, tests, or a guarantee that any third-party badge or television will respond.
The Sheriff guide lists the Sheriff SAO, CR2032 or LIR2032 battery, magnet battery holder, sticky pad, soldering iron, and flush cutter; it describes soldering battery wires, using the holder's independent switch, selecting Sheriff batt mode, and magnet-mounting it through clothing. It says an LIR2032 may last longer but the badge does not charge it. The source does not replace battery-safety, charging, thermal, medical-device, magnetic-interference, or assembly-risk guidance.
The source release includes a UF2, user-preferences delta, build notes, provisioning GUI/script, and hardware-independent tests. It names a Meshtastic `event/defcon34` relationship and documents its own source-published configuration boundary, but it is not treated as a post-event support commitment, exact delivered-unit inventory, or a general-purpose flashing procedure.
The v1.1 release says some pre-sale 1.0 or 1.01 badges should flash the update to fix an unspecified issue, and says `enable, sh ver` can check that the badge is on the 1.1 build. It does not identify the issue, affected count, unit identifiers, changelog, validation, rollback, installed population, or update outcome.
The reviewed maker release contains the v1.4 KiCad project, DRC/ERC reports, Gerber archive, BOM/placement/netlist production files, board documentation, populated-board media, and NanoVNA tuning material. The repository calls its production outputs the exact files from which its run was built; the catalogue preserves that as a maker statement rather than independent manufacture, quality-control, or field-performance proof.
The maker describes left, center, and right dial positions for 2.4 GHz channel monitoring, RSSI foxhunting, and local browser firmware flashing. The source uses a rotary input to choose operating paths, but does not establish mode reliability, range, scan completeness, update success, accessibility, safe use, or that every sold unit has identical configuration.
The Exploitee.rs announcement says a new Hacker Pager revision is being brought to DEF CON 34, describes online availability windows, BadgeLife Village pickup, and no on-site sales. It does not publish a final inventory, price, order ledger, vendor authorization, completed sale, pickup, delivery, refund, replacement, or post-event availability result.
coryallegory says the unit is fully assembled, uses a standard 2 by 3 SAO header, and has cycling multicolor LEDs that light the keyboard. No source supplies an LED count/part/current, controller, voltage/current limits, pinout, orientation, power budget, circuit, schematic, BOM, PCB files, dimensions, safety guidance, or host test matrix.
The listing says the Sphere SAO works with upside-down SAO ports and the High Roller SAO has blinky lights. The source does not provide a pinout, electrical requirement, LED count/type, firmware, published design, host test matrix, or general compatibility guarantee.
AoSC says a confirmed $100-or-greater donation to a youth-STEM-supporting charity may receive a 2026 eChallengeCoin by U.S. mail or DEF CON pickup, and says the first 20 recipients are intended to have brass blanks created by students from a local high-school engineering program. These statements do not establish charity status, tax treatment, donation validation, privacy/retention practice, quantity awarded, recipient eligibility, shipping, pickup, school identity, manufacturing quality, payment, or final delivery.
HogFillet describes a 555 timer clocking a ten-bit ripple counter, eight counter outputs driving eight LEDs, and an onboard trimmer controlling the timing rate. The source does not name component variants or values, flash-rate range, LED current, supply limits, power draw, electrical protection, schematic, BOM, PCB files, or final unit test results.
The product page says the speaker SAO plays monorail-themed sounds and has a mini SD card for adding MP3 files. It does not identify audio hardware, controller, firmware, MP3 limits, file workflow, source audio, media license, volume/safety behavior, or final shipped implementation.
The maker says the badge has three pre-programmed sound effects with accompanying light shows, including a gong effect. It does not identify audio hardware, firmware version, sound files, copyright/recording rights, controls, runtime, accessibility, configuration, or final shipped behavior.
The listing says two analog inputs are tuned precisely to unlock a hidden LED pattern, and solving four puzzles unlocks the badge's full potential. It does not publish the inputs, sequence logic, calibration range, solutions, reset behavior, accessibility path, scoring, or outcome evidence.
The maker says the 2026 coin presents as a serial device when connected to a computer and hosts the Sara and the Missing Artifacts terminal text adventure. It also says new firmware can support other adventures. No public game source, binary, command reference, release/version mapping, host test matrix, reset/save guide, accessibility documentation, or support policy was recovered.
The project page describes a Game Boy-inspired top-down adventure with 30-plus CTF puzzles, while the live listing describes 35-plus CTF and puzzle challenges. Both frame the badge as a playable adventure with unlockable bling; no public challenge archive, final count, solution policy, ruleset, scoring system, accessibility review, or completed game behavior is published.
The project page says badges can link up to 50 units, while the live listing says participants can create more than 1,000 unique words and phrases with other badges. Neither source publishes the transport, pairing, range, privacy/security model, player-data handling, protocol, connectivity requirement, interoperability, or final event behavior.
The README says the badge lets users display an estimate for when the AI singularity will occur, with front buttons that shift that estimate, eight seven-segment displays, and a real-time clock. It documents a source-project interaction concept, not an assembled unit, final screen/readout behavior, calibrated clock, usability result, event challenge, prize, or completed distribution.
The maker says a frog-themed CTF unlocks GIFs, bling, and secret surprises, and that a frogger-like game is built into the badge. No source provides challenge rules, release dates, solution path, scoring/leaderboard, content source or license, offline/online behavior, telemetry, personal-data handling, security model, or preservation archive.
The seller describes an underwater world where CTF challenges deliver packages to DEF-SEA inhabitants, potentially with other players, plus pirate battles, underwater cults, and a hidden Atlantis. No source provides rules, release timing, solution path, challenge inventory, player count, score validation, server/network behavior, content provenance, archive, or accessibility information.
The Spectre Sniffer listing says one included Pac-Man Ghost SAO comes in one of four colors. It does not name those colors, explain random or selected allocation, provide variant photos with reuse rights, map colors to the 1,000-unit giveaway, or establish identical artwork, PCB, components, behavior, or mechanical compatibility across all artifacts.
A direct NilbinSec Bluesky reply says a Spectre Sniffer purchase includes a PAC-MAN Ghost SAO and helps fund over 1,500 free SAOs for Vegas. This is a product-bundle statement, not proof that the included companion is the same board, color, quantity pool, or configuration as the separately announced 1,000-unit giveaway.
The roster says touching the gun's end changes animated colors and that it interacts with the PORTAL Badge; the maker page describes blue portal, orange/red portal, and off modes and calls it a companion to the year's Portal Badge. Those claims do not publish a final interaction protocol, connector/pinout, input/output voltage/current budget, compatibility matrix, required Portal Badge revision, test results, or guarantee that any two units interoperate.
The product page says configuration and messaging use the Meshtastic app over BLE and that each unit has its own BLE PIN printed on its bag. The catalogue does not store PINs, identify a pairing workflow, claim a privacy/security review, or describe shared mesh traffic as private.
The listing names an onboard ATtiny814 connected to two RGB LED eyes, with power from the SAO connector or an included CR2032 battery. It does not publish default firmware, LED electrical data, power budget, battery runtime, voltage limits, connector pinout, host matrix, or final behavior.
The listing says v1.0 changes labeling and swaps I2C and GPIO pins from v0.1. It explicitly says the SAO does not support SAOv3 ARP or hot-plugging features. This does not establish final firmware behavior, electrical hot-plug safety, backwards compatibility, host-specific behavior, completed testing, or a full SAOv3 implementation.
The maker lists an ESP32-C3 and 24 RGB LEDs. The source does not identify the exact module, board revision, LED package/layout, power budget, radio configuration, antenna, electrical characteristics, or test results.
The listing names an ATtiny1616-S, two-character fourteen-segment display driven through shift registers, RGB LED, timer-based non-hardware-PWM behavior, and reprogramming through a separate UPDI adapter. It does not publish final firmware, exact parts/configuration, code, flashing instructions, electrical design, display/LED behavior contract, or support policy.
The live listing names an RP2350 with 4 MB flash, 16 RGB addressable LEDs, and a 128x128 grayscale display; the maker project page calls the display a 128x128 OLED. The source does not identify exact part numbers, wiring, final layout, revision, component list, schematic, PCB, test data, or a complete screen/LED specification.
The listing names seven orange reverse-mounted LEDs, an ATtiny824, and reprogramming with a separately obtained UPDI adapter. It does not publish exact LED electrical data, power budget, controller configuration, final firmware, wiring, flashing instructions, or a board-revision test record.
The product and repository describe configurable matching against BLE and Wi-Fi identifiers such as MAC/OUI/manufacturer/device-name/service/SSID fields, with LED, vibration, screen-wake, and scan-setting choices. They do not publish detection range, radio state timing, false-positive/false-negative rates, rule precedence, actual target databases, data retention, export, device consent, security controls, or a universal detection guarantee.
The source tree documents USB-C, UF2, SWD pads, a rear 2x3 SAO header, and a claimed SAO v1.69bis fit. It does not establish a pinout or electrical limit for every host, a supported-host matrix, a safe user workflow, or a general compatibility guarantee.
The technical release documents a four-layer board, chip-antenna feed/match design, u.FL test points, SAO-or-USB-C power mux, no battery, and source-published tuning data. Its claimed measured and power-budget context remains maker evidence, not a blanket electrical-safety, host-compatibility, or performance guarantee.
The maker says the Crown is fully soldered and assembled, names one SAO connector, three flashing red LEDs, and three resistors, and says it needs no separate battery or programming. The listing says only to use a compatible badge; it does not identify the connector standard, pinout, supply range, current draw, flashing circuit, LED/resistor parts, polarity/protection, host matrix, or safe attachment result.
The maker describes twenty-four NeoPixel LEDs, an ATtiny 814, USB-or-battery power, and custom or pre-programmed themes. The public firmware defines four eye and twenty wing LED arrays plus color/mode code. The sources do not establish LED model/current, exact final color order, controller package/fuses, USB/power implementation, power budget, battery type, safety, or final production parity.
The maker describes five NeoPixel LEDs, an ATtiny 814, development-pin access, USB-or-battery power, and custom or pre-programmed themes. The public firmware defines a five-element LED array plus color/mode code. The sources do not establish LED model/current, exact final color order, controller package/fuses, development-pin or USB/power implementation, power budget, battery type, safety, or final production parity.
The maker names an ATtiny1616, two 10 kΩ potentiometers, eleven independently controlled LEDs, and a UPDI-compatible one-wire programming interface. It does not publish circuit or pinout documentation, LED electrical characteristics, controller configuration, programmer settings, firmware, or electrical-safety validation.
The maker says an ESP32-S3-based device uses two custom PCBs with a screen sandwiched between them for a retro-TV aesthetic. No source supplies the module/flash/antenna, screen/display controller, radio configuration, power system, circuit, schematic, BOM, PCB files, dimensions, assembly, testing, safety, or compliance details.
The maker listing and later Hacker Couture list describe three connected boards, special two-color solder mask on the top two boards, sixty LEDs, an included CR123A battery, and one populated SAO v1.69bis port. They do not identify the controller, LED or battery characteristics, power design, SAO pinout, electrical limits, circuit, schematic, BOM, Gerbers, or safety validation.
The maker lists a Hacker Boba PCB badge, keychain, power switch, CR2032 holder, included CR2032, three flashing RGB LEDs, and three resistors. It says the kit arrives unsoldered and needs basic soldering supplies. The listing does not establish a final board/BOM, part specifications, holder polarity/protection, LED current, runtime, power budget, switch rating, soldering quality, test process, or safe assembled result.
The project page lists two SAO V1.69bis ports, while the maker listings say FrogStar supports two SAOs and is fully programmable. No reviewed source supplies port pinouts, orientation, I2C/GPIO behavior, voltage/current budget, hot-plug safety, host matrix, electrical protection, programming interface, or implementation details for the fully-programmable claim.
The listing advertises display/LED animations, UPDI ping/erase/flash functions with raw HEX loading from internal storage, I2C tools, and voltage/current/power sensing. It documents claimed capability at a high level, not an audited firmware build, target-safe programming procedure, access-control model, data integrity guarantee, complete toolchain, user guide, release, or support commitment.
The project owner says the firmware is signed and each badge has its own key pair. No public material identifies the signature/key algorithm, trust anchor, key generation/storage/backup/rotation/revocation model, hardware security boundary, verification path, source, binary, build provenance, update procedure, or external review.
The README says the firmware targets an ESP32-C3 driving a 240×320 ST7789 IPS panel with a capacitive touch controller at I2C 0x15, controlled by swipes and taps with no buttons. It does not identify exact modules, panel/controller variants, PCB integration, power path, touch calibration, gesture thresholds, final unit behavior, or hardware test results.
The listing says the custom PCB is 4.25 inches tall with black solder mask and white silkscreen and runs from included AAA batteries through a 4.5 V input. It does not identify the battery holder, power path, regulator, current draw, runtime, protection, board thickness, materials, mechanical test, or compliance evidence.
The team says the CTF lives in firmware, is multi-stage and not solo-completable, uses real protocols, and unlocks backend pages through progress. No code, binary, challenge archive, protocol specification, endpoint, scoring system, access policy, data policy, or final running service is published in the reviewed sources.
The seller lists a super-bright round display, over six buttons, a SAO port, extra exposed GPIO, and a fully-programmable claim. It does not state controller, display details, pinout, power budget, voltage/current limits, electrical protection, GPIO function, programming interface, SAO compatibility, circuit, schematic, BOM, PCB files, or testing.
The maker lists an RP2354A, INA3221 I2C voltage/current/power monitor, ST7789 SPI display, six WS2812 RGB LEDs, navigation joystick/back button, and breadboard-compatible prototyping platform. The listing does not establish schematic/BOM/revision, component configuration, monitor calibration, exact breadboard fit, power/current limits, test results, or safe operation.
The live listing says that soldering additional components unlocks CTF challenges. It does not identify the components, modification points, tools, difficulty, required safety precautions, challenge behavior, allocation, assembly instructions, or support scope.
The official Standard description calls Clip-Boy a wrist-mounted ESP32-S3 electronic badge and says the Standard enclosure is 3D printed in gunmetal gray. The maker says Pro and RAD editions have the same features, with different color/edition presentation. No reviewed source supplies the final PCB, mechanical drawings, enclosure material/process parameters, component list, dimensions, power system, antenna design, or production revision.
The seller names a CH32V003, 12-LED Charlieplexed matrix, single-layer circular board with exposed traces/no protective enclosure, hand-soldered two-AA configuration, and a 16 KB flash / 2 KB SRAM claim. It does not publish a circuit, parts list, board files, dimensions, battery chemistry, voltage/current limits, power or protection design, component values, assembly/test method, safety guidance, or measured runtime.
The maker says GPIO 1 and GPIO 2 each have separate hardware, switches, LEDs, and button-input options, independent of the animation engine and I2C controls. It says a host can drive an LED path or receive button input, with selectable logical polarity. No schematic, safe-voltage/current envelope, host-pin map, test matrix, or compatibility guarantee is published.
The listing calls the header standard 2 by 3 SAO and says the LED lights when connected to the DC34 badge with no adapter needed. It does not publish connector orientation, voltage/current limits, pinout, host matrix, protection circuitry, test result, or a universal compatibility guarantee.
The listing says a button can be shorted to the odd or even GPIO of the DEF CON badge SAO header and that the outcome depends on the attached badge. It also explicitly says the SAO has no firmware and no I2C handshake. No source publishes the exact host pin map, circuitry, switch behavior, voltage/current limits, or a tested result on a particular badge.
The maker's release names an exact source-published UF2 version, `event/defcon34` relationship, CLIENT_MUTE role, 10 dBm configuration delta, and per-unit provisioning material. It does not prove that every offer or collected item used that exact image, and it is not a post-event update or support guarantee.
The sources name capacitive touch, a 10 kOhm potentiometer, buzzer, microphone, hall-effect sensor, LSM6DS3TR IMU, ambient-light sensor, internal temperature sensing, and input-voltage monitoring. They do not publish final calibration, microphone privacy behavior, sensor accuracy, environmental limits, sampling policies, current build completeness, or user safety guidance.
The seller says a CTF with Windows Vista-era throwbacks and hardware/software puzzles unlocks bling and GIFs, and names twelve RGB LEDs with custom light patterns. It does not publish the challenge rules, source/licensing of content, LED part/current, score/service path, solution/reset method, privacy/data handling, or final behavior.
The team says the project consists of two objects with ESP32-S3, IR, NFC, BLE, and a buzzer; one transmits while another was built to counter it. The source does not identify exact modules, electrical design, radio configuration, protocol, range, antenna, power system, test method, final revision, or delivered behavior.
The maker describes a BLE number-station puzzle, red-versus-blue proximity game, autonomous social/dance mode, expressive BLE MIDI instrument, tamper-evident mode, Setup menu, and optional hardware CTF. The source does not describe BLE services, radio range, pairing, player/account data, game protocol, MIDI mapping, tamper condition, CTF rules, security controls, or final behavior.
The Standard product description advertises customizable LEDs, a theremin, and more than 90 collectibles; the shop's social metadata also names a 3D-code scanner. No reviewed source explains the underlying components, collectible encoding, scanner modality, data storage, interoperability, game rules, accessibility, privacy, service availability, or post-event preservation. These are maker-described features, not a verified technical specification.
The listing names UART, UPDI selected by a DPDT slide switch sharing the UART port, I2C, 5 V, 3.3 V, internal RP2350 debug, and external debug breakouts. It does not publish a pin map, connector type, voltage/current envelopes, target matrix, switching isolation, debugger implementation, electrical protection, or safe integration instructions.
The maker says v2 has either blue or yellow LED colors, is a kit requiring soldering, and uses components that are 1206 or larger. It does not publish LED count/model/current, circuit, resistor values, BOM, PCB files, assembly order, required tools, soldering/ESD precautions, battery safety, runtime, test procedure, firmware, or electrical-safety validation.
The maker says v1 has either blue or yellow LED colors, is a kit requiring soldering, and uses components that are 1206 or larger. It does not publish LED count/model/current, circuit, resistor values, BOM, PCB files, assembly order, required tools, soldering/ESD precautions, battery safety, runtime, test procedure, firmware, or electrical-safety validation.
The maker says the unit is fully assembled, uses a standard 2 by 3 pin header, and its red eye glows when powered through the SAO header. It does not publish LED current, circuit, controller, power budget, voltage limits, pinout, host matrix, schematic, BOM, PCB files, dimensions, final revision, safety guidance, or test data.
The maker lists SGP40 VOC and SHT4x temperature/humidity sensors, a raw-reading option, and a relative VOC-index algorithm with an approximately ten-minute warmup. It expressly says no accuracy claims are made and the device must not be relied on for accurate air-quality measurements. The source does not publish calibration, environmental test, threshold, exposure, health, safety, or certification evidence.
The maker explicitly says the kit has no microcontroller or firmware to configure and says a back QR code opens a Google Maps Boba Shop search. It documents a narrow no-code and convenience feature only; it does not publish the exact QR payload, application terms, data behavior, source/design files, search accuracy, service availability, or a support commitment.
The maker describes a custom VHS-style lore box plus embroidered patches, themed lanyard, and three exclusive vinyl stickers. It does not establish the exact contents of every unit, package revision, artwork rights, recipient allocation, completed shipment, pickup, or resale state.
The listing says the badge comes in a full-color custom-printed box with a laser-cut foam insert and unique lanyard, and says it ships ground in the United States with the battery removed for air shipping. It does not confirm which purchaser or event recipients received every listed component, final packaging variant, shipping availability, completed shipment, or battery compliance outcome.
The product page says it includes a silkscreen replication of the Whose Slide gong artwork, a design mentored by Blenster, and custom rear artwork by 1DarkOne. The source does not provide source-art files, authorship chain, individual reuse permissions, a production-art proof, or a cleared hero-image asset.
The product says Luna is approximately 57 mm by 50 mm, fully assembled and tested, with a yellow LED in the forehead. It does not identify the LED, circuit, controller, component values, materials, power budget, production method, final revision, electrical test method, or safety information.
The maker describes a small monorail on a track, a clip for storing a paper monorail ticket that is not included, and a three-SAO structure. No source identifies the final materials, mechanics, SAO layout, connector pinout, manufacturing method, dimensions, transit-ticket compatibility, or final unit photographs as reusable documentation.
The maker calls v2 either an oversize minibadge or a standalone lanyard-pinned badge and says standalone use is powered by a CR2032. The roster instead calls the offering a standalone small badge or Saintcon minibadge. Neither source settles the final form, dimensions, attachment method, battery holder, polarity, on/off control, minibadge standard, connector/pinout, electrical interface, host compatibility, or which configuration a buyer receives.
The maker calls v1 either an oversize minibadge or a standalone lanyard-pinned badge and says standalone use is powered by a CR2032. The roster instead calls the offering a standalone small badge or Saintcon minibadge. Neither source settles the final form, dimensions, attachment method, battery holder, polarity, on/off control, minibadge standard, connector/pinout, electrical interface, host compatibility, or which configuration a buyer receives.
The maker says the FPC tongue contains functional USB pads and can act as a USB cable when folded for tension, alongside a USB-C connector. It says the tongue is durable but may crumple with repeated use. The source does not publish cable-current limits, orientation details, USB signal testing, cycle testing, mechanical precautions, device compatibility, or warranty/support terms.
The listing says the cedar was grown on a creator farm in Tennessee, milled at home, and paired with the PCB by hand; it also says the header pins break out to labelled solder pads on both sides. The source does not give wood treatment, dimensions, mechanical durability, fire-safety, sourcing chain, production count, assembly instructions, or final quality-control information.
The listing names sixteen side-emitting XL-1606SURC red LEDs shining through FR4 PCB material and includes a lobster-clasp lanyard. It does not publish LED current, placement drawing, board dimensions, materials details beyond FR4, power budget, schematic, BOM, PCB files, final revision, or production-quality record.
The marketplace describes a roughly 100 mm beer-cup SAO with a waterproof temperature sensor on an approximately 200 mm lead and an included 180-degree adapter for DEF CON 34's upside-down host ports. The source does not provide final board outline, connector mechanical drawing, probe ingress/sanitation rating, adapter circuit/pinout, force/strain limits, physical compatibility matrix, or confirmation that all units use the same parts.
The maker says the canary can run from the SAO connector or an included CR2032 battery. Its v1.0 note says hardware I2C was disconnected from the SAO connector and separate lines were used to reduce the chance of sensor-bus collisions. It does not identify voltage/current limits, battery runtime, connector pinout, I2C electrical characteristics, multi-device test data, or universal host compatibility.
The maker lists a rechargeable LiPo via USB-C and a fully addressable SAO port. It does not publish battery capacity, chemistry/protection details, charger/power path, voltage/current limits, runtime, thermal data, connector pinout, SAO version, supported devices, electrical test matrix, safety guidance, or universal compatibility guarantee.
The maker says one tactile button cycles effects, the last effect persists after host power loss or disconnection, the input range is 2.7–3.7 V, and visual patterns include fast/slow flashing, heartbeat, and breathing/fade. No controller, timing range, memory mechanism, regulator design, host test matrix, electrical protection, or optical-safety information is published.
The maker lists a regulated 3.3 V supply powered by two AAA batteries. It does not identify battery chemistry/brand, holder, polarity protection, regulator, current draw, runtime, charging behavior, voltage limits, thermal behavior, transport guidance, certification, or safety documentation.
NilbinSec's public roster says 1,000 PAC MAN Ghost SAOs will be given out for free, with drops announced through social media and a supply transferred to villages. The event had not yet occurred in this source pass, so it does not establish manufacture, quantity completed, village transfer, exact drops, allocations, recipient count, completed handoff, replacement, or support.
NilbinSec's public roster row says the Power Glove Re-release is free and that 500 Power Glove SAOs will be given away at DEF CON, with drops announced on social media and at the Badgelife Village. The event had not yet occurred in this source pass, so it does not establish manufacture, inventory, drop schedule, village handoff, recipient count, completed distribution, replacement, or support outcome.
Hak4Kidz Lab's public roster says Star Trek SAO Phaser v2.2 can be purchased from Hacker Warehouse at DEF CON for approximately $35. DEF CON 34 had not yet begun in this source pass, so this does not establish Hacker Warehouse inventory, booth location, payment terms, units, event-exclusive configuration, completed sale, buyer allocation, pickup, fulfillment, support, or a relationship beyond the maker's own sales-channel statement.
MakeItHackin's public roster says the Original Series Tricorder badge will be available on-site at DEF CON through Hacker Warehouse for approximately $125. DEF CON 34 had not yet begun in this source pass, so the statement does not establish venue inventory, booth location, units, payment terms, event-exclusive configuration, completed sale, buyer allocation, pickup, fulfillment, replacement, support, or a relationship beyond the maker's own sales-channel wording.
AoSC says the 2026 edition is a limited release with a plan for 40 brass eChallengeCoins, each weighing 46 grams. It does not establish a finished quantity, serialized allocation, component parity, production date, inventory, recipients, shipping/pickup outcomes, replacements, resale, or post-event availability.
The listing says a CH340E USB-to-serial converter can program UPDI devices such as ATtiny microcontrollers and names configurable 3.3 V or 5 V UPDI voltage. It does not publish wiring, driver requirements, target support, protocol configuration, level validation, fuse/lock-bit handling, recovery procedure, or a safe universal programming guarantee.
The maker says the SAO implements Rare Circuit's proposed SAOv3 I2C interface, exposing vendor/product IDs, port and custom-command information, generic LED control, and its own lighting modes. It does not publish a final protocol version, command schema, IDs, host implementation, interoperability result, standard-ratification status, or broad compatibility guarantee.
The marketplace and README describe IR send/receive plus a 13.56 MHz RFID/NFC component, while the diary discusses a planned short-message interaction over infrared. The sources do not establish a final message format, range, pairing/discovery rules, encryption/authentication, collision handling, data retention, interoperability, regulatory status, or user-consent model.
The current roster says the re-release will be posted to NilbinSec GitHub on DEF CON Day 1. Before the August 6 event, the reviewed account already had only the older DC32 Power Glove repository, so no 2026-specific source, firmware, release, revision note, licence, or final production mapping was available.
The product page says Submarine includes hardware and software puzzles plus a few soldering challenges. It does not list a component kit, soldering steps, temperature/safety guidance, challenge prerequisites, tooling, board revisions, troubleshooting, reset path, solution policy, or completed event-support record.
The listing says the badge detects a user-defined list of BLE MAC addresses to give a heads-up about what is around the user. It does not say whether behavior is passive or active, which address types/advertisements are used, how a list is configured or stored, range, cadence, false positives, logging, network use, consent, retention, security, or regulatory context.
The maker's v1.4 source identifies an nRF52840 on a RAK4630, a Semtech SX1262 LoRa radio on US 915 MHz, and Johanson chip antennas for 915 MHz LoRa and 2.4 GHz BLE. It includes board, component, and measurement sources, but does not amount to a certification, independent RF assessment, universal host result, or final-unit inspection.
The official product description says the badge has Wi-Fi and Bluetooth analysis tools and a deauthentication detector. The seller says shipped units are passive and listen-only; no configuration, range, accuracy, traffic handling, target-identification, privacy, RF, legal, or operating procedure is published here. This dossier does not provide use instructions or describe the badge as suitable for any particular environment.
The product and maker post describe bare-metal/pure RISC-V assembly on CH32V003 and a custom UART puzzle at 115200 baud; the product describes fourteen stages, Davies-Meyer, SPECK-128/256, a constant-time MAC, and an 8 MHz low-power mode. These claims do not substitute for matching released firmware, binaries, build or flash instructions, test vectors, benchmark method, security review, recovery process, or proof that any shipped unit matches the description.
The sources describe games, puzzles, screensavers, messages, user modification through USB-C, a compiled C library, and an evolving Python/C++ two-core arrangement. No reviewed material supplies a tagged final firmware, end-user build/flash guide, challenge archive, stable UI specification, release hashes, update policy, test report, or final behavior guarantee.
The maker says the board holds up to 25 SAOs, has a notch beside each port for tethering, includes keyhole-compatible leash-ring rectangles, and exposes outer white LEDs linked to the top-left slot; the product page says the separate SmartAO SAO is required for the outer LEDs. It does not publish slot pinouts, port layout, connector orientation, current per port, SmartAO protocol, LED circuitry, compatibility matrix, mechanical load test, or user safety guidance.
The maker README describes local DJ mixes played through headphones and a music-linked light show. This documents a stated badge experience, not a particular playlist, licensed media set, audio level/safety result, event programme, radio broadcast, attendee allocation, final firmware configuration, or confirmed conference deployment.
The README says two badges can use infrared to converge on track position and light timing, while the firmware notes document revision-specific infrared context. This is a high-level maker-published interaction claim, not an interoperability guarantee, protocol specification, privacy/security assertion, reliable-range result, safe operating instruction, or evidence of an event-wide synchronized session.
The maker says the Gunslinger combo includes an SAO connector, directs the user to solder it to the Gunslinger with the notch side up, then to set the Sheriff power to SAO mode. The source does not publish the connector pinout, electrical limits, orientation drawing beyond prose, hot-plug guidance, strain relief, compatibility with other SAOs, verification steps, or troubleshooting.
Public documentation identifies an RP2040, microSD/local media, LiPo power path, 3.5 mm audio chain, addressable LEDs, USB-C, infrared components, and an SAO header. It records a high-level technical surface rather than a verified final BOM, pinout, voltage/current budget, cell specification, charger protection result, electrical test, compatibility matrix, compliance record, or safe-modification guide.
BigTaro lists a Raspberry Pi RP2350, 1.28 inch GC9A01 240 by 240 round LCD, addressable WS2812B RGB LEDs, infrared receiver, and six onboard buttons. The source does not state component counts beyond the six buttons, wiring, memory, power, battery, electrical limits, schematic, BOM, PCB files, or test results.
The maker targets DC34's right SAO port, identifies a 2 by 3 SAO 1.69bis header, and describes 3.0 V badge or USB-C power. This is an implementation-specific maker statement, not a universal fit, rail budget, hot-plug, electrical-safety, or compatibility guarantee.
The maker describes one badge as an uplink/display XIAO ESP32-S3 and two XIAO ESP32-S3 scanners that share one scanner image but receive BLE-primary and Wi-Fi-primary roles at runtime. It is a source-described architecture, not proof of a universal production revision, board provenance, field reliability, or authorized radio deployment.
The guide identifies I2C address 0x50 and documents built-in-mode selection, all-off control, raw discrete and RGB LED writes, plus a two-byte status response. It says malformed raw writes are rejected without partial state changes. This is a published operating interface, not a warranty of host compatibility, electrical safety, bus arbitration, command support by a particular badge, or a software library.
The README says the badge has two pre-installed 18650 batteries, can run from USB, battery, or barrel power, and provides about 30 mA when all SAOs are run from USB/barrel or about 300 mA at 3.3 V when batteries are charged. It also claims surge protection. It does not publish the circuit, cell specification, charging algorithm, fuses, voltage/current limits, measurement method, thermal behavior, fault testing, or safety certification.
The project describes passive observation of nearby broadcast RF evidence and a USB-C Android companion for live views, display controls, and diagnostics. It does not establish detection accuracy, identification certainty, legal authority, range, data retention, user consent, secure transport, a cloud-free operation in every mode, or a safe field-use procedure.
The guide says the badge exposes a local Wi-Fi/browser quest interface and includes an explicit assigned-badge-and-advertised-services boundary. The catalogue preserves that narrow interaction fact without publishing connection identifiers, credentials, local addresses, hidden resources, browser instructions, or exploitation details, and without treating a CTF surface as general conference infrastructure or a production security model.
The guide identifies an ATtiny1616, ten addressable RGB pixels, eleven discrete LEDs, fifty animations, a button, and non-volatile USERROW storage for a favorite and last-played animation. It describes tap and hold behavior, but does not supply firmware source, a binary release, electronics test data, a battery/runtime profile, or final-unit verification.
The Player Guide names a CP2102 programming connector, a serial-terminal chapter, an LED-panel observation, and one physical task using only labelled SAO GPIO1/GPIO2 contacts. It does not establish connector wiring, pinout, voltage/current limits, toolchain, serial-command set, safe procedure, firmware image, general compatibility, or permission to attach hardware outside the assigned-badge context.
The public README and handoff describe GIF channels, a device puzzle, settings, USB-drive loading, and the V4-to-V5 firmware history. This preserves the published software surface without making a safe flashing, recovery, support, security, or source-to-unit version claim.
The maker repository says to power the badge, open a serial connection at 1200 baud to force boot-select mode, mount the resulting USB drive, and drag a released UF2 firmware image onto it. Pre-sale badges with acrylic require manual boot-button access while powering on. The source does not identify the controller, serial device behavior, bootloader implementation, erase/recovery model, verification, signed-image process, support path, or safety implications.
The README describes a camera, display, and microSD-based image surface within the planned badge. It establishes the intended project concept, not functioning capture, encoding, storage, display, interoperability, data handling, privacy, final firmware, event operation, or a delivered-unit result.
The README describes separate carrier boards for a radio module as part of the planned SSTV concept. The catalogue records that high-level design claim without reproducing setup, configuration, frequency, transmission, or radio-operation procedures, and without asserting a tested assembly, authorization, license status, performance, safety, or compliance outcome.
The maker page labels Firmware v1.0, links a FrogStarFirmware1.0.uf2 file, and says to flash by copying the firmware file to the badge. It does not state the release date, changelog, source code, license, checksums, signing, toolchain, bootloader steps, target-board configuration, rollback, recovery, or support policy.
The hardware guide publishes a board BOM, single-board and panel Gerber jobs, and a battery-cage STL, and says the DEF CON run used a three-radio ESP32-S3 arrangement with external patch antennas. The files are preservation evidence, not a safe construction guide, a current supplier quote, a complete editable design-source release, or final-unit evidence.
The pre-event README names an off-the-shelf ESP32, a 240×320 ILI9341 TFT panel, wiring, and two batteries. This establishes a maker-stated parts surface only; it does not prove a PCB, enclosure, wearable form, final board/module, battery chemistry/capacity/protection, power budget, or an event-unit configuration.
The repository publishes KiCad/fabrication material, MicroPython-based firmware, a native MP3-decoder path, and a prebuilt universal UF2. This supports a public technical trail, not an audited/reproducible build, signed release, source-to-device mapping, third-party dependency audit, installation instruction, event-installed media package, warranty, support channel, or security review.
The PCB repository preserves Eagle board and schematic files, a project library, scripts, OSH Park design rules, and multiple Gerber ZIP archives.
Badge Pirates publishes CC13 Gerbers, KiCad sources, documentation outputs, and an MIT repository license.
Badge Pirates publishes Gerbers, BOM exports, an interactive BOM, ESP32-S3 reference material, and BasicCodeForQA for the CactusCon 12 badge.
The repository README documents compressing the production files and using the centroid and BOM files to order boards through JLCPCB.
The repository preserves the Multnomah KiCad PCB, schematic, project, netlist, footprint table, symbol table, and local footprint directory.
The repository preserves BSidesPDX_2018 KiCad board, schematic, project, libraries, local footprints, and Gerber/drill outputs.
The repository preserves OpenTaxus KiCad schematic, board, project, footprints, logos, and dock files for hardware review and reproduction.
Badge Pirates publishes KiCad files, schematic PDF, interactive BOM, Gerbers, STEP exports, and STL/3MF enclosure parts for manufacturing and review.
The official write-up says the badge shells were printed on one Prusa MK4 over about a month and a half with full-plate front/back batches.
Public sources document ICSP programming with pogo pins and a clothespin pogo-clamp workflow used during badge production.
OSHWA and repository documentation describe CAN 2.0B/NMEA-2000, NMEA-0183, and Modbus RTU transceiver modes with software-controlled half- and full-duplex behavior.
The README describes ADC streaming over a serial interface and frames the badge as a basic 12-bit logic analyser for low-rate signal inspection.
The hardware archive includes several `iflfu-sao-spacer` model-file variants in OBJ, MTL, and 3MF forms. Their presence documents an accessory-design trail, not a shipped spacer, a particular revision, a compatible host, printed-material safety, fit, durability, included accessory, or permission to republish model or image assets.
Hackaday describes the badge as a cube constructed from PCBs soldered along their edges, with a run of over 400 units assembled by hand.
Hackaday's customization article points attendees to STEP, DXF, and SVG front-panel models so the non-electrical front PCB can be replaced with CNC, laser-cut, or 3D-printed panels.
The listing says parts are customizable and interchangeable. The Wayfinder-CAD repository describes a one-piece clamshell case, rails/keyway, snap-on accent plates, compliant-mechanism cautions, knobs, Fusion360 source, and STL files. The repository has no detected license and its author warns the CAD is incomplete/complex, so it is a documented trail rather than a blanket redistribution or safety authorization.
The 3D-print README documents soft flexible and hard hinged bangle shells for holding the electronics, with magnets, hinge wire, and heat-shrink retention.
The production path moved from a two-material ABS and PC enclosure concept to a single clear polycarbonate housing so the PCB color and LED passthrough could work within the tooling schedule.
The same Hackaday.io log identifies the enclosure as an injection-molded rocket shell and credits Jaycon Systems for the production path.
The public repository includes 3d_Prints model/STL material and a Project-CC13 STEP export for mechanical reference.
A June 4 commit adds a 2026 3MF badge file plus screen-cover and rounded/squared battery-case STL files under STLs/2026. The files establish published mechanical-source material, not a fabrication run, final print settings, assembly result, or image-reuse clearance.
The Hack-Master badge used a dual-PCB assembly and two RGB LEDs as backlights for a custom image reel.
Folded liner notes and the cassette audio carried track-list, color, character, tone, and number-station-style clues for remote badge solving.
The badge splits flash into code and filesystem partitions and exposes a USB mass-storage volume where users copy 128x160 TGA images into `blingpic/` for display on the badge.
The official home page says the badge bundle contained a CarolinaCon T-shirt, shot glass, sticker, and Conference PCB Badge.
The official page says the merch bundle included a kit with all parts needed to make the year's badge.
The badge ships with the LHC channel preprogrammed, while the LHC guide documents QR-code onboarding and Meshtastic channel setup.
The same source identifies the controller as an ATtiny84 and warns that incorrect orientation leaves the badge non-functional.
Datko and Hackaday describe the SAINTCON 2014 badge as an Arduino clone or Arduino-compatible badge built for attendee hacking.
The public guide identifies the D1 Mini ESP8266 development board as the badge compute module and documents header orientation and USB flashing behavior.
The smartphone-integration log documents the AND!XOR Android app terminal, Nordic nRF Toolbox compatibility, nearby badge scanning, BLE terminal commands, script buttons, and maintenance-mode behavior.
An accelerometer was added and paired with the buzzer to create a tone-generator/synthesizer controlled by badge tilt.
The firmware documents a hall-effect sensor interrupt, RPM calculation, and timing loop used to align the POV output with spinner rotation.
The badge maker frames Patches as part of the Voodoo Heart badge series and says it combines with last year's badge and next year's final piece.
Carolina Code Conference names Circuit Board Medics as its badge partner, and that organization published the matching public source archive. This establishes a bounded partnership and source-publication trail, not a complete design, manufacturing, fulfilment, or image-rights attribution.
The badge provides GPS own-ship position on a moving map, and the FAQ documents manual coordinate fallback when GPS lock is unavailable.
WyrdWyrks describes GPS plus Wi-Fi geolocation for indoor/outdoor finding and a WS2812B LED compass ring. The repository documents GPS coordinate/status traffic, saved waypoints, navigation wiring, and v3 61 LEDs, but does not provide final location accuracy, geolocation-service terms, indoor performance, or range validation.
Cisco describes the SAINTCON show badges as purpose-built Wi-Fi enabled badges carried by about 550 attendees and tied to Cisco CMX infrastructure.
The firmware defines BadgerNet as both preferred infrastructure SSID and hotspot basename, with retry behavior before badge-hosted service fallback.
The official badge page identifies the active conference artifact as a Minew MTB11 ambient-light-harvesting BLE tag, custom printed for IEEE RFID's twentieth anniversary.
The official 2600 listing offered a $250 HOPE 26 In-Person Pass and said digital admission tickets would be generated asynchronously and emailed before the event. It describes the tickets as non-refundable but transferable.
AoSC links CircuitPython's Bradán Lane STUDIO Coin M0 build specifically for the eChallengeCoin. CircuitPython says Coin M0 has an ATSAMD21G1A with 4 MB flash and supports CircuitPython or Arduino plus USB serial, MIDI, HID, and disk uses; AoSC suggests a one-button macropad after the game. The sources do not prove final 2026 firmware, every-unit compatibility, user-safe reflashing, or a detailed implementation/license trail for the eChallengeCoin game.
The official page says each passive tag used a unique 96-bit custom conference/demo identifier, sequential rather than GS1 retail EPC, and not containing personal attendee information.
The official page says the tag broadcasts a unique 48-bit identifier, battery voltage, and temperature in BLE advertisement packets when sufficiently charged from ambient light.
The official site lists an ESP32-S3, SX1262 LoRa radio, 192×64 LCD, microSD, USB-C, rechargeable LiPo, buttons, speaker, vibration motor, 48 addressable LEDs across RGB/UV groups, resin body, acrylic panels, and related package items. It is a published platform description, not a verified 2026 per-unit configuration, electrical test result, or safe operating specification.
Badge.Life documents a USB CDC serial CLI and a DFU/BOOTSEL path for copying a correct firmware.uf2. It is a public documentation trail, not a published firmware release, a source-to-badge mapping, an integrity guarantee, a complete recovery package, or a recommendation to modify hardware.
CypherCon's registration listing says the Analog / Plastic Entry Pass includes a lanyard and physical plastic entry pass with a digital program. This records a source-described non-electronic ticket artifact, not a final print design, credential technology, completed redemption, or proof of an admission-control implementation.
The official badge page identifies a custom-printed passive RAIN RFID/UHF tag associated with a QR code as the second conference artifact.
CypherCon's registration listing describes the Extreme Badge as a premium offering with a unique collectible electronic badge and an exclusive upgraded PCB. The source does not say whether those terms describe the same object, a variant of the Digital / Circuit Badge, multiple objects, a final design, or a completed delivery.
The same 2026 registration listing describes the higher Extreme Badge tier with unique collectible electronic-badge and exclusive upgraded-PCB language. It does not say whether that tier used a distinct board, a modification of the Digital / Circuit Badge, a non-electronic collectable, a final production configuration, or a completed delivery.
Badge.Life lists an RP2354 with integrated flash, eight addressable RGB NeoPixel LEDs, three buttons, an infrared receiver, two Simple Add-On v2 headers, USB-C, and a single-cell 18650 battery with charging and protection circuitry. This is a published platform description, not a complete schematic/BOM, a final manufactured configuration, an SAO compatibility guarantee, or an electrical-safety result.
Official BSides Maine posts frame the badge as a puzzle for exploration, collaboration, experimentation, and hacking; the agenda later asks whether anyone solved it.
CypherCon's FAQ says ticket purchase is recorded and merchandise is redeemed at the event rather than mailed. It does not identify a particular pass tier, prove a successful collection, define handoff controls, state inventory, or show the final plastic pass.
SecretCon's FAQ says ticket holders may redeem and pick up their badge and/or pre-ordered merchandising at the registration desk during the event. It does not identify a specific ticket tier, verify a successful pickup, state an inventory, describe handoff controls, or prove the final physical Digital / Circuit Badge.
The official site says the Pager runs Meshtastic-powered software for standalone messaging with Meshtastic-compatible devices and optionally pairs with the official mobile application. The description does not establish default radio enablement, channel/key configuration, data practices, performance, legal operating context, or a final DEF CON 34 firmware image.
The CypherCon FAQ calls the limited VIP form an Extreme/Ultimate badge, while the official category listing separately shows the 2026 Extreme Badge as sold out. These pages do not establish final quantity, purchaser count, price, priority benefit delivery, badge allocation, pickup, shipment, replacement, or final stock reconciliation.
SecretCon's registration listing says the 2026 Digital / Circuit Badge tier includes an interactive circuit-board PCB badge and a printed physical program, alongside listed conference-access benefits. This records the organizer's ticket-tier description, not a final board identity, component set, completed purchase, delivered program, attendance record, or technical behavior.
CypherCon's registration listing says the 2026 Digital / Circuit Badge tier includes an interactive circuit-board PCB badge and a premium printed physical program, alongside listed conference access. This records the organizer's tier wording, not a final board identity, component set, completed purchase, recipient identity, final program, or technical behavior.
The maker's update page calls 2.7.26.pager the latest Hacker Pager firmware release and adds a DEF CON 34 label. It does not identify every code change, cryptographic release verification, hardware-revision mapping, installed-unit population, successful update record, support outcome, or permission to reproduce update steps here.
Red Team Village's official page places the Village at DEF CON 34 on August 6-9 in the Las Vegas Convention Center Red Team Village area and announces workshops, activities, swag, and more. It does not state that RTV D20 is included with registration, used in a workshop/CTF, issued to all attendees, or grants access to any Village or conference space.
LayerOne's official Hardware Hacking Village round-up says soldering and rework stations plus volunteers were available for attendees who wanted to tinker with the badge.
The project's licensing declaration assigns CERN-OHL-S v2 to hardware, GPLv3 to firmware, and CC BY-SA 4.0 to listed documentation and creative works. This supplies a clear technical-source trail, but its itemized scope does not by itself establish a cleared publication basis for each repository photo or a final event-unit configuration.
Rehrig documents total-internal-reflection lens work intended to focus emitter output and shape the optical behavior needed for the laser-tag game.
The badge placed an IR receiver in the center and IR emitters on the center-left and center-right of the board for laser-tag interaction.
The guide suggests attaching a buzzer or anything else to BZ1 and notes the badge can become a tripwire alarm when pointed at with a laser.
The registration page pairs the electronic badge with a custom RVAsec challenge coin in the guaranteed package.
Badge Pirates says non-electronic participants received an electrically same PCB with clues for a crypto challenge, preserving participation without overclaiming electronics for every attendee artifact.
BSides Seattle's 2026 patron-benefit list includes a Special badge at the event. The source does not identify the artifact's material, technology, form, maker, allocation, or actual handoff.
The Shadybucks page documents optional external burner-wallet linking plus QR-code wallet setup, sponsorship transfers, and spending at camp.
The unofficial section lists WiCyS, USA, Gadsen, Matrix, Eduroam, Private LTE, CompuNet, and Radiation badges with booth, sponsor, contact, or personal handoff acquisition notes.
The export includes personal and community-designed badges such as Cryptid Minibadge Expansion Board, SAO Adapter, Delicate Arch, Infinity, and other designer-attributed entries.
The personal category explains that creators brought their own badges for trading or networking and that those badges were not directly supported by conference staff.
The sketches use EEPROM for stored names and HugQuest token/infection state, keeping the pager identity and game state across restarts.
The official program describes 0.040-inch commercially pure titanium pieces fabricated by waterjet, tumbled for deburring, and kiln-oxidized for an aged puzzle-game appearance.
The README lists microphone, tactile button, three red LEDs, battery holder, optional two 6-pin SAO headers, and a 2-pin battery-only header. It also describes microphone, accelerometer, button, and touch actions. This is a source-backed feature outline, not a complete production, power, electrical-safety, or compatibility specification.
Gothcon's store describes a bat-shaped custom PCB with 44 independently controlled RGB LEDs, removable laser-etched acrylic logo shield, custom DEF CON 34-color lanyard, and a pre-order package containing the PCB, shield, screws/nuts, lanyard, 2,000 mAh LiPo, and mounting tape.
The DEF CON 21 badge used hidden PCB metal and interconnected paths that attendees could discover with a multimeter, making a non-powered board behave like a puzzle circuit.
DEF CON 24 solving notes used badge backs, hidden traces, common encoded text, badge-type-specific silkscreen strings, and visible printed codes as puzzle material.
The lanyard carried unusual character strings and is identified by official forum and writeup sources as one of the challenge surfaces included with the badge.
Mar Williams described the DC33 badge as interacting with 3D images and layered art around the con through different lenses and lens combinations.
DEF CON's badge news previewed the badge through its SAO slot and framed the badge as having room for attendee customization.
The build notes document custom PCB design plus laser-cut acrylic and 3D/2D files for the badge enclosure and presentation form.
The official page frames the BIC Pick as a red, green, and gold Afro-pick-shaped badge celebrating BIC Village's five-year anniversary.
The official event page says every attendee will receive the BSides Nashville 2026 challenge coin and repeats that each attendee badge includes it.
FREE-WILi publishes a dedicated DB15 pinout for the badge, while the reviewed source does not provide full schematic-level connector or transceiver documentation.
The roster says SR-71 is only winnable and that the ACR team will host a CTF at its Aerospace Village booth and on its Discord. It does not publish the CTF rules, eligibility, schedule, task set, venue authorization, winner count, badge quantity, pickup process, or completed award outcome.
The maker labels Not Just a Crosswalk a Simple Add-On designed for DEFCON 34 and says it is SAO V1.69bis/V2.0 compatible. The repository does not provide a final unit, a standard-specific test report, a host-badge matrix, connector orientation proof, electrical budget, or universal interoperability guarantee.
The public plan sketches badge stations for hardware hacking, puzzles, games, a photo booth, or similar event-specific interactions.
SAINTCON's MiniBadge page says the 2026 conference badge's MiniBadge sockets use the standard 2.54 mm grid.
The team says the badge contains a TCG-type game using NFC peer-to-peer and NFC reader modes, and that a full card collection enters an attendee into a raffle for Lockheed Martin and ACR swag. The listing does not identify whether NFC lives in the badge, cards, phone, or booth hardware; it also omits game rules, card count, persistence, scoring, raffle terms, odds, prizes, or security controls.
The project-owner plan calls out UART or wireless communication so stations can update badge state or behavior without reflashing a full image.
The official page says that a DEF CON symbol will be printed on a Black Hat badge at check-in when the registrant bought a DEF CON ticket through an eligible Black Hat pass. The statement does not establish the badge's material, technical function, eligibility outcome, or completed printing for a particular person.
The next-version plan keeps the self-service update-station idea that was not fully reliable enough for PN26 field deployment.
The 2026 Call for Papers says accepted speakers receive an exclusive Speaker MiniBadge.
The distribution guide says physical-badge firmware should map to a permanent GitHub release with source, notices, relinkable objects, hashes, and installation information. The public releases surface had no release or tag on 2026-08-05, so the guide is recorded as a planned compliance path, not evidence of an installed final binary, completed distribution, or production traceability.
The PN26 writeup lists EEPROM storage for image data as the first improvement target for the next version, avoiding PN26's full-firmware-patch workflow.
The 2026-badge root holds native KiCad PCB, schematic, project, project-local, footprint-cache, and backup material. The archive is a design snapshot rather than a BOM, Gerber release, manufacturing order, assembled-unit record, or final revision declaration.
The team describes crew members as roaming live transmission zones, fixed but unmapped Cure Stations, and hidden 3D-printed medkit props. This is a planned game surface, not proof of venue approval, final locations, staff participation, accessibility, safety review, implementation, participant effect, prize, or event outcome.
The schematic identifies D1 as a Breathing 3mm LED and D2-D4 as Fast Blink 3mm LED, all on 3 mm LED footprints. It does not identify their color, supplier, current draw, blink pattern, intensity, population outcome, or field behavior.
The official instructions say staff will inspect the Black Hat badge with DEF CON symbol, hole-punch it as proof of pickup, and then hand over a separate DEF CON badge. This is a scheduled verification workflow, not proof that a recipient completed the pickup or that the marked Black Hat badge itself performs access control.
The schematic names a Keystone 3002 1x2032 holder footprint, an MST22D18G2 125 power-switch component, and a 2x3 2.54 mm vertical socket. These source design elements do not establish an included cell, battery runtime, connector role, pinout, host compatibility, electrical limits, polarity protection, safety result, or populated final board.
GrrCON's terms say that if selected to volunteer, a person will be given a GrrCON staff badge. The same terms say dismissal results in revocation of that badge. The wording does not identify a specific unit, physical form, ticket relationship, access mechanism, pickup procedure, or completed handoff.
The maker says hardware documentation and a stub firmware will be provided after the conference. That is a public future-release statement, not a currently available repository, license, binary, final firmware, completed design release, or guarantee of timing/scope.
The 2026 sponsor prospectus distinguishes sponsor-ticket rows marked Electronic Badge from rows marked Non-Electronic.
The post-event Arduino-style source contains Wi-Fi, local web-server, SPI, preferences, and ILI9341 display code. The catalogue records this high-level source context without publishing connection details, credentials, URLs, endpoints, challenge answers, access steps, or a claim that the visible code was deployed at the event.
After AC9, the official badge page published four booth/village unlock codes for people who missed them during the event.
The public repository calls the devices owl badges of the SecretCon 26 convention, and its commit-pinned README says it exists for SecretCon 26 attendees. This is a narrow community post-event signal, not an organizer-defined artifact name, a ticket-tier map, a delivery count, a hardware or firmware specification, a use recommendation, or evidence of completed handoff for any individual.
The organizer's public feed re-shares an attendee thanking BSides Nashville and SkillBit for coins after the event. This corroborates attendee-side coin receipt but does not establish all-recipient delivery, a coin count, maker role, material, or variant inventory.
A public attendee activity message says the attendee made a Wi-Fi analyzer at BSidesGVL, corroborating that the advertised conversion occurred for at least one reported participant.
The official organizer feed reposted a report of smooth badge handout and badge engagement, while Jeff Shouse publicly reported helping make the badge with an active badge team.
The manual provides a post-conference conversion path for turning the badge into a RetroPie device after the event.
The public timeline mirror preserves CypherCon's repost of a message saying CypherCon badges were programmed, tested, and packaged before the event, and records opening and wrap messages for CypherCon 9. The repost does not identify a device, badge tier, firmware, test criteria, quantity, production entity, or successful attendee handoff.
Hackaday documented that the badge could identify as a USB HID keyboard and operate as a configurable macro pad after the event.
The official wrap-up says riverside and Holly helped fix an electrical issue with all badges by hand, without identifying the fault, exact repair, or attendee impact.
Lepi Labs' repository named 5-dc34-canary-badge contains native KiCad board/schematic material and a PlatformIO Arduino source tree with components matching the source-described Canary. The source is useful technical provenance, but no reviewed maker page links it directly to the sold product, and its release page reports no releases. It is not treated as a final v1.0 event firmware, final board revision, calibration record, safe operating guide, or source license.
Project details and build logs document two CR123A cells, diode reverse-polarity protection, battery tests, WS2812B failure observations, and boards chainable by VCC, ground, and LED data output.
The user guide documents battery connection during setup, USB Power Delivery charging with a 9V/3A minimum, SSH access, RGB LED shutdown behavior, and 3D-printing button-tolerance troubleshooting.
The badge page documents BAT CON jumper behavior and warns users not to keep the coin cell connected while the badge is plugged into a computer.
NilbinSec lists a protected 18650 battery and lanyard. The listing does not identify capacity, cell make/model, protection circuit, charging method, charger, connector, runtime, electrical limits, safety testing, or replacement procedure.
The CAD archive records 14500 battery-holder, TP4054-class charging, and MAX17048 fuel-gauge evidence.
The hardware README documents AA battery power through a boost converter, USB-C power through a regulator, and a switch between USB and battery power.
The BOM lists a CR2032 battery holder and ALPS power switch, and the schematic links the battery holder through the switch into the 3V3 path.
The BOM lists a CR2032 battery holder and DPDT slide switch for the badge's portable power/control hardware.
The BOM lists a CR2032 battery holder and the Eagle schematic carries BT1 as a CR2032 holder tied into the badge power rails.
The board archive and README point to power and MAX17048 schematic material, with dual 14500 battery-holder and fuel-gauge evidence preserved in the CAD tree.
The CC13 KiCad comments identify LiPo charging, dual 14500 battery holders, and fuel-gauge hardware.
The README and firmware document a pushbutton that toggles microphone power and clears the display for standby/low-power behavior.
The official badge announcement lists interactive power management and a 12 V 1.5 A power supply, without documenting the underlying design, safety limits, or supported external equipment.
Hackaday describes an 18650 cell and charging circuit as part of the badge hardware package.
The maker lists an included 2,000 mAh LiPo, BQ24072RGT battery-management controller, TPS63051RMWR 3.3 V buck-boost supply, thermal monitoring, and up-to-1.5 A fast-charging support. The public listing does not include a battery specification, charger settings, measurements, operating guide, or independent safety verification.
The SAO spec states that the badge is powered by two AA batteries and that USB-C power-bank operation keeps the badge continuously on.
The README lists a two-AAA battery holder as the badge power hardware.
The maker says buyers may select DEF CON pickup this year or shipment by early August, with pickup location/time to follow. The source does not establish a final pickup schedule, venue authorization, customer notice, shipment posting, customs handling, delivery receipt, replacement policy, or a completed handoff.
The live listing shows $10, six sold, 44 remaining, on-site-only DEF CON 34 pickup, and tentative Friday/Saturday BadgeLife Village times. These seller statements do not prove final inventory, paid orders, actual schedule, pickup, delivery, refund, support, or venue authorization.
The live listing shows $20, 20 sold, ten remaining, a free Saturday DEF CON 34 BadgeLife Village pickup label, and pickup wording for DEF CON 34 or BSidesLV. These seller statements do not prove final inventory, payment, schedule, handoff, shipping, refund, or event authorization.
The live page shows $20, eight sold, 92 remaining, DEF CON 34 BadgeLife Village, LineCon, and Queercon Mixer drop labels, plus post-DEF-CON CONUS shipping. These seller-published terms do not prove final run size, paid orders, onsite allocation, pickup, shipment, delivery, refund, replacement, or event authorization.
The official checkout lists $20 including tax and says all online stock allocations are exhausted. The Puzzled Hackers Team says paid sales were capped at a break-even point. Neither source publishes a unit count, payment ledger, production total, in-person stock, completed sale, delivery, refund, replacement, or post-event availability result.
The live product page lists $24 and a seller state of 19 sold from a listed total of 23, plus two stated DEF CON 34 Badge Life Booth pickup times. It says a missed drop can be mailed or refunded. These seller-published terms do not prove final inventory, payment, pickup, shipment, delivery, refund, venue authorization, or event outcome.
The live Lepi Labs product page shows a $25 price, 25 sold, zero remaining, and a DEF CON 34 drop label. The team separately announces scheduled BadgeLife Village drops. These time-specific states do not prove final run size, paid-order ledger, physical stock, exact drop allocation, handoff, delivery, or post-event outcome.
The live Lepi Labs product page shows a $35 price, seven sold, zero remaining, and a DEF CON 34 drop label. The team separately announces scheduled BadgeLife Village drops. These current source statements do not establish final run size, paid-order status, physical stock, exact drop allocation, handoff, delivery, refund, or post-event outcome.
The live Lepi Labs product page shows a $45 price, 11 sold, zero remaining, and a DEF CON 34 drop label. The team separately announces scheduled BadgeLife Village drops. These time-specific source states do not prove the final run size, paid-order ledger, physical stock, timing, handoff, delivery, refund, or post-event outcome.
The observed live product payload reports $45, 150 total units, 28 sold, 122 remaining, `presale: true`, no shipping options, and two announced DEF CON 34 BadgeLife Village pickups: Friday August 7 at 1 PM and Saturday August 8 at 1 PM. This is a time-specific maker marketplace snapshot, not proof of paid-order count, completed manufacture, venue authorization, onsite inventory, pickup, delivery, refund, support, or final availability.
The live MakeItHackin page lists $50 and a seller state of 15 sold from a listed total of 100, plus drops labelled BSides Las Vegas 2026 and two Linq Circle Bar nights. These time-specific seller figures do not prove final run size, paid-order ledger, onsite allocation, collection, shipment, delivery, refund, event authorization, or post-event support.
The live listing shows $50, 43 sold, 57 remaining, and a DEFCON34 drop label. The repository and project diary describe online sale and intended August handout/pickup. These sources do not prove final run size, paid-order ledger, exact drop allocation, production, attendee handoff, shipment, delivery, refund, or post-event support.
The live product payload reports a $120 100-unit presale with 41 sold, a DEF CON 34 pickup option, and a seller-published $140 at-con plan. This is a time-specific maker marketplace snapshot, not proof of final production, paid orders, finished units, onsite inventory, booth authorization, pickup, shipment, delivery, donation, refund, or customer support outcome.
The live product payload identifies a $55, 125-total pre-sale for DEF CON 34, currently reports 125 sold and zero remaining, lists no shipping options, and directs collection to the Darknet-NG contest booth. This preserves a time-specific maker marketplace state, not evidence that the total run is manufactured, paid, assembled, collected, delivered, or supported after the event.
Red Team Village's public DC34 Badgelife response labels RTV D20 as a new badge, says it will be available on site at DEF CON through RTV, and gives an $80 price. The statement does not prove inventory, payment, manufacture, final price, sale location/time, venue authorization, pickup, recipient allocation, refund, support, or a completed handoff.
The maker page says preorders are sold out and may have a few extras to trade in person. The current payload marks its $65 base, $150 Laser* Tag bundle, and $80 voluntary-extra-payment options unavailable. This is a current storefront snapshot, not proof of a sale count, physical inventory, finished build, payment, trade, pickup, delivery, refund, or post-event support outcome.
The maker says about 55 badges had been made with roughly ten boards left, a few may be given to the first roughly five signal-intel puzzle solvers, most or all RGB units are accounted for, a few non-RGB units may be sold at cost, and some RGB blank boards may be given away. These comments do not establish a production ledger, final build count, exact price, payment, eligibility, pickup site/time, receipt, donation, assembly, delivery, support, or post-event outcome.
The official current inventory endpoint lists 86 $120 Standard, 25 $130 Pro, and five $140 RAD first-run units—152 total—all with zero current availability. The shop says the first run is gone and all 152 shipped, while the present form only gauges interest in a possible second run. This is a current storefront snapshot, not a production audit, proof that every buyer received a unit, or a second-run promise.
The maker's product page says only 100 badges are planned at $75 each. Its public Shopify payload currently marks the single variant unavailable, but emits no inventory quantity. This records a stated limited-run plan and time-sensitive unavailable state, not proof that all 100 units exist, sold, shipped, or reached buyers.
The roster gives MF Doom SAO v2 a $20 Coming soon entry, while the maker's Reddit thread says preorders will be handled by direct message and describes local handoff near the Las Vegas Convention Center. The public statements do not prove final stock, price, manufacture, payment, venue authorization, exact meeting point, pickup, shipment, refund, replacement, support, recipient allocation, or completed delivery.
DEF CON's official badge-alert post says DEF CON 34 is an electronic badge year, that the badge comes from a hardware hacking legend, and that the SAO spec sheet is early support for add-on projects.
The organizer says orders are currently DEF CON 34 pickup at Demo Labs from 10 AM to noon on Friday and Saturday, online orders only with no onsite sales. It says unclaimed orders will be donated to a broke hacker; neither source confirms completed pickup or recipient outcomes.
The listing says pickup only, no shipping, with drops at BadgeLife Village and announced LVCC locations on a published schedule; it says missed drops are donated to a hacker at closing ceremonies. At the August 3 source pass, the listing displayed 80 sold and zero remaining.
At the August 3 source pass, the $150 product is marked PRE with 5 sold and 95 remaining. Its drop options are DC34 Reddit Meetup Wednesday, DC34 Reddit Meetup Thursday, DEF CON 34 BadgeLife 1, and DEF CON 34 BadgeLife 2; no shipping option or location/date detail is present in the reviewed product payload.
BTV lists a $120 assembled badge with lanyard and a $60 intermediate-to-advanced soldering kit, for in-person pickup only during DEF CON in Las Vegas. The listing directs buyers to the West Hall second-floor W213-215 Infobooth during Friday-Sunday village hours and says no refunds after August 10; these terms do not establish completed handoff or fulfillment.
BigFuckingBadge's page presents a limited DEF CON 34 presale and an unlabeled $20 OffensiveSAO card, while the public Badgelife response names that artifact DFIU SAO and likewise gives $20. These published statements do not prove current inventory, payment, final price, manufacturing completion, shipment, pickup, event sale, refund, replacement, support, recipient allocation, or a completed handoff.
The BigFuckingBadge page supplies a limited DEF CON 34 presale setting and an unlabeled $20 OffensiveSAO card, while the public Badgelife response names IFLFU SAO as an update to an existing item and gives $20. Those source statements do not prove current inventory, payment, final price, manufacture, shipment, pickup, event sale, recipient allocation, refund, replacement, support, or a completed handoff.
BigFuckingBadge's page provides a limited DEF CON 34 presale context and a $20 Portal-gun companion card, while the public Badgelife response names the new PORTAL gun SAO and likewise gives $20. These statements do not prove inventory, payment, final price, completed manufacture, shipment, pickup, event sale, recipient allocation, refund, replacement, support, or a completed handoff.
The K Badges Tindie page displays a $29.99 price and an out-of-stock state, says a new order is coming, and says the maker hopes to bring some to DEF CON. The maker's Reddit post separately offers to arrange pickup/refund shipping for buyers. Neither source proves inventory, production completion, payment acceptance, arrival, pickup scheduling, handoff, shipping, refund, support, or delivery.
The official v2 product page displayed $12 and available in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory count, paid order count, manufacture, pickup email/location/time, completed handoff, shipment, refund, replacement, support, or post-event availability.
The official v1 product page displayed $12 and available in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory count, paid order count, manufacture, pickup email/location/time, completed handoff, shipment, refund, replacement, support, or post-event availability.
The official product page showed $45 and sold out in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory history, payment, manufacture, drop location/time, email notice, completed pickup, shipment, refund, replacement, or support outcome.
The official product page showed $45 and sold out in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory history, payment, manufacture, drop location/time, email notice, completed pickup, shipment, refund, replacement, or support outcome.
The official product page lists the FloridaMan 2026 Badge at $90 and currently marks it out of stock; its short product context says it is no longer shipping and directs attendees toward DEF CON. This is a listing-status snapshot, not proof of order volume, sale completion, shipped goods, pickup, refund terms, remaining inventory, or an eventual handoff.
The listing says v1.0 boards were ordered and that if v0.1 issues remain or later problems cannot be resolved before DEF CON, buyers could receive a full refund or have their SAO shipped after the event. This is a contingency statement, not evidence that any issue was resolved, a final revision shipped, a refund occurred, or a delivery obligation was completed.
The organizer says it is locking in print deadlines, badge runs, and village build-outs starting in summer. The statement establishes pre-event production planning without identifying a design, material, vendor, quantity, schedule, final build, quality check, completion, or delivery outcome.
The organizer account said its package had been received and badges were secured before the public reveal. It does not provide a manufacturer, quantity, final inspection result, unit configuration, distribution plan, or evidence that any attendee has received a badge.
A December 13 SEAL-Embedded snapshot frames a Raspberry Pi Pico W BLE interest-matching project as an IEEE Rising Stars Conference badge and includes `aioble` advertising/scanning code. A later repository README describes an ESP32 redesign, not an event-unit release.
The maker says v1.1 boards were ordered and lists CH340E decoupling, power-select, UPDI-select, GPIO, CR2032-holder, and FPC-fuse corrections from v0.1. It says unresolved prototype issues or later pre-event problems could lead to a full refund or shipment after DEF CON. These are maker-described plans, not proof of final validation, shipped v1.1 units, correction outcome, refund, or delivery.
The official party page schedules FloridaMan Party 2026 for Thursday, August 6, 2026 from 9:00 PM to 1:00 AM PT in Las Vegas, Nevada, and says the location is provided upon purchase. The page does not establish a final venue, pickup/entry process, actual attendance, or a completed party outcome.
DC801 + 801 Labs' public Badgelife response labels Helgatchi as a new badge for DEF CON 34 and supplies approximate pricing and feature wording. It is a visible maker/team submission, not a DEF CON organizer issuance, venue authorization, registration inclusion, Human-badge replacement, access entitlement, or completed distribution record.
The official 2026 prospectus includes Logo on Badge in its sponsorship matrix. It does not publish the final logo placement, graphic treatment, sponsor selection, badge artwork, medium, technical configuration, audience, number of units, or proof that any branded badge was ultimately produced.
Telecom Village's official organizer account announced an all-new Telecom Village badge and lanyard for DEF CON 34. The reveal does not identify the badge's material, hardware, artwork rights, recipient group, or collection procedure.
The organizer lists Adversary Village badges with a volunteer T-shirt or hoodie, goodie bag, recommendation letter, and networking opportunity. It says only a limited number of volunteers will be selected. The source does not say whether every selected volunteer receives a physical item, how an item is issued or retained, what it identifies, or whether any current applicant was selected.
Payment Village says volunteers will receive conference access through a village badge, alongside a village T-shirt and learning opportunities. The source does not say whether all applicants are accepted, whether every volunteer receives a physical item, how access works, when or where a badge is issued, or whether it is retained after the event.
Great Scott Gadgets credits OSH Park sponsorship and the repository preserves the badge hardware designs and kit photo trail.
Badge Pirates documents a batch of 250 fully electronic badges built around ESP32 boards with touch screens, Wi-Fi, and SD card slots.
The tariff writeup records customs scrutiny, opened packaging, delayed delivery, and roughly a 20 percent tariff hit on the production order.
The Army article says Capt. Richard Shmel personally developed and made more than 300 electronic badges for AvengerCon VIII.
A late GPIO0 buffer design caused battery-powered badges to enter Download boot mode until the team fixed DTR with an R19 pull-up resistor before conference shipment.
An attendee report says factory firmware left LEDs blindingly bright, requiring all badges to be reflashed just before the conference.
Mog noticed the exposed pad spacing lined up well enough with DB9/DE9 connector pins, leading to a pogo-pin cable and CC Debugger flashing workflow.
The Wi-Fi and pick-and-place log documents CR123A cells and holders, diode validation, stencil-holder work, eight early hand-built badges, and pick-and-place setup six days before the conference.
The official post documents panelized boards, solder-paste stencil work, reflow, inspection, through-hole soldering, and testing.
The building-badges log says kits were made, speaker and staff badges were built, and LED badges were being assembled with a TM-220A pick-and-place shortly before the conference.
The first-hand writeup names Xometry as the injection-molding partner and describes design-for-manufacturing tradeoffs around wall thickness, sink marks, lens geometry, and schedule pressure.
The preserved DEF CON 33 programme calls the Vulnerable ATM Badge the largest badge at the conference that year and says it simulates ATM attack surfaces in a physical form factor that can be carried with two hands. It does not provide an operating procedure, board or module inventory, safety assessment, or proof of a final attendee-owned unit.
The badge-team notes describe USB device support, USB host, HID or CDC behavior, and ST-Link V2/SWD programming expectations.
The official page identifies the ATTINY85 pin mapping for SAO data pins and names the Amphenol programming-port and male-connector parts with 1.27 mm pitch.
The README documents Microchip Studio or avr-gcc build paths, `L12024POV.hex`, avrdude flashing to `t4313`, and Kraken or Arduino ISP programmer options for attendees.
The hardware-hacking guide documents AVRISP wiring and commands for initialization, target identification, flash reads/programming, and fuse access.
The badge could be programmed through an FTDI header, giving attendees a direct Arduino-style code-loading path.
The repository publishes public design/source directories, names HotGlewd for PCB/sticker/promotional artwork, BitAssembly for pixel artwork, and declares the work CC BY-SA 3.0. The marketplace separately credits the SCP-1471 source. These statements provide traceable project provenance but do not clear a particular product image, confirm every dependency's licensing, or prove that every third-party lore asset may be republished.
The public `bunnie/dc34-image` README identifies a Python utility for uploading a black-and-white 128×128 image to a DC34 badge over USB serial. It documents a customization path, not physical display technology, a selected shipped image, a final embedded firmware build, or event-unit parity.
The public `bunnie/dc34-bio` README identifies a Python utility for loading a BIO program to a DC34 badge over USB serial, with documented SAO-I/O selection and clock configuration. It documents a user-side tooling path, not complete embedded firmware, final connector mapping, safe settings, a supported end-user workflow, or event-unit parity.
The source tree documents a versioned `thermometer-v1.1.0.uf2`, USB BOOTSEL flashing, `flash_and_test.py` serial verification, and soak-log/report scripts for batch programming. Those tools demonstrate a public intended workflow, not a signed release, independently audited production test, all-unit pass record, final factory process, repair policy, or guaranteed recovery path.
CPEC's companion repository says it contains design files for SAO plug-in modules for the CPEC DC 34 badge. Its commit-pinned source tree contains KiCad project, PCB, and schematic paths for fist, gatling, laser, missile, panel, and sword-named variants, an Arduino source file, and BOM/placement artifacts. The catalogue records that scoped design-source availability without inferring a populated board, hardware behavior, wiring, pinout, firmware result, safe electrical envelope, standard/version match, or working connection to a CPEC badge.
The maker-linked Penzz-HM repository includes the Arduino sketch, ESP32-S3 build outputs, a Gerber archive, enclosure STL files, and a root MIT license. It supplies a practical preservation and modification trail, but does not establish a complete schematic/BOM, reproducible production build, release-to-device mapping, every-dependency license, image-reuse selection, support commitment, or warranty.
The product links an Ouroboros How It Works PDF and a GitHub repository. The repository describes a distinct AVR-assembly ATmega328P authentication framework and GitHub marks its license field Other; it is not a released CH32V003 badge firmware, board, build package, or clear license grant. The linked PDF similarly does not establish a reusable media or source license.
The published ESP32 sketch enables promiscuous mode, sets a selected Wi-Fi channel, and increments a packet counter that it displays through the dial-style interface. It does not document capture filtering, persistence, encryption handling, packet content storage, channel coverage, sampling accuracy, traffic authorization, privacy handling, lawful-use context, test results, or RF performance.
The sketch scans nearby Wi-Fi networks, lets the user lock a selected access point by BSSID or SSID, and periodically displays the matching access point's RSSI. This documents a source-level tracking surface, not a validated locating tool, a guarantee that a BSSID belongs to the intended device, permission to scan or follow third-party equipment, a precise distance measurement, or a privacy-safe deployment.
The repository says core 0 samples DS18B20 temperature about every second and updates the display buffer, while core 1 multiplexes three digits at about 333 Hz; revision 1.3 or later cycles four brightness levels. It does not establish the exact binary deployed to every sold unit, final timing/accuracy under load, error handling, field behavior, update cadence, or supported configuration matrix.
The README documents Arduino-compatible firmware and PlatformIO profiles for normal, demo, and factory-test builds, including tests for LED order, orientation, and shake sensing. The code and documentation do not establish a public tagged event release, production test log, safe user modification path, support obligation, or actual configuration in an assembled badge.
The public PFC161 source defines a four-entry color buffer, blue/orange/off state values, touch initialization, a 470 pF touch-capacitor note, thresholded button logic, and timer-driven LED updates. This is source-level evidence for touch-controlled animated-color behavior, not a claim about the physical LED model/count/order, touch sensitivity, final modes, brightness, latency, power draw, safety, accessibility, or behavior of every produced unit.
The public C source includes PFC161 headers, configures active-low PA4/PA5 LED outputs, keeps separate LFSR state per channel, derives individual delay targets, and flashes channels from its main loop. This is source-level evidence for a two-channel randomized-light implementation, not proof of the exact final illuminated words, distribution of outcomes, timing, brightness, physical LED population, or behavior of every produced unit.
The public firmware declares ten LED modes, button-driven cycling, per-pixel color output, and pins labelled for minibadge clock control. This documents a possible firmware interaction surface without claiming that all current units expose the same button, pins, timing, modes, firmware revision, programming path, accessibility behavior, or support.
The public firmware declares ten LED modes, button-driven cycling, per-pixel color output, and pins labelled for minibadge clock control. This documents a possible firmware interaction surface without claiming that all current units expose the same button, pins, timing, modes, firmware revision, programming path, accessibility behavior, or support.
The source initializes touch ADC support, reads PD2 through `ReadTouchPin`, starts audio after a threshold, and updates the source-declared D/F/I/U and display LED outputs from timer-driven code. This is source-level evidence of the intended interaction, not a claim that every physical unit behaves identically or that its touch sensitivity, sound volume, audio content, LED population, timing, accessibility, or reliability has been independently tested.
The public documentation names exposed UART pins for an XMODEM bootloader and describes a rapidly developed codebase with some unresolved bugs, while the repository exposes current source/firmware material. It documents an implementation and update trail without reproducing flashing steps or claiming a tagged/reproducible firmware release, verified binary-to-board mapping, secure update, rollback/recovery package, support policy, or safe owner modification.
The maker and README describe roughly five or six lighting programs, a favourite-colour setting, motion enable/disable, random or sequential program selection, a handle program button, and rear setup button. The README describes a star touch sensor but says it might not work by DC34, and describes the SC7A20H accelerometer while separately documenting a REV1 motion-interrupt limitation. This preserves high-level source claims without promising final program count, touch behavior, motion reliability, or user experience.
Call Center Village's public source calls this a phone-booth-shaped, power-only SAO v2: one 1206 LED and one 330 ohm current-limiting resistor are wired in series from VCC to GND, with no microcontroller or I2C and the SDA, SCL, GPIO1, and GPIO2 pins left unconnected. The repository includes KiCad project, schematic, PCB, connector symbol, BOM, placement, netlist, Gerber packages, and a CC BY-SA 4.0 license. It does not prove final kit or pre-soldered population, per-unit quality, current draw under an actual host, final production revision, DC34 electrical test result, user assembly outcome, or general host safety.
The maker's commit-pinned hardware tree contains native KiCad project files for a main badge board and separate carrier boards. This is a source-availability record only; it does not confirm a final design revision, Gerbers, component sourcing, fabrication, assembly, testing, safe behavior, production quantity, or DEF CON handoff.
The electronics repository publishes the PCB design in KiCad with schematic PDF and BOM exports, and its companion case repository publishes case/button/acrylic design files; both state CERN-OHL-S-2.0 for design files. Those releases document modifiable design sources, not a promise that every commercial unit matches them, a safe build recommendation, source-code license scope, or image-reuse permission.
The project's MVP note identifies the Arduino/C++ tree as the live implementation and describes visual/interactions work. This establishes accessible current project source, not a tagged release, reproducible build, compiled attendee image, device configuration, flashing/support workflow, final feature set, or proof that it ran on a distributed badge.
The repository identifies an RP2350B, 16 MB flash, USB-C, and a 1.5-inch 128 by 128 grayscale SSD1327 OLED. The listing says over fifty LEDs, while the diary describes two 24-device red-green LED banks. This creates a useful documented surface but not a final populated-unit specification, current budget, assembly record, or universal performance guarantee.
The post says only 100 would be available at a Sneakreaper Industries booth. In replies, its author gives $150 and Hall W4. The source does not document a checkout page, seller identity, order count, stock ledger, payment, refund/replacement terms, exact booth authorization, completed manufacture, handoff, delivery, remaining stock, or post-event outcome.
Circuit Board Medics' MIT archive documents CircuitPython 10.2.1, editable `code.py`, a preloaded launcher, tutorials, a serial-console guide, and samples. It does not establish a signed or immutable factory image, deployment record, security review, or support commitment.
The FirstBuild repository publishes a schematic PDF, firmware tree, and MIT license for software and associated documentation. These sources establish a valuable design and software trail, but do not automatically cover credited artwork, photographs, trademarks, every third-party dependency, a final hardware manufacturing package, or a selected reusable badge image.
The repository specifies an RP2350A QFN-60, W25Q16 2 MB flash, USB-C for programming and serial debug, RUN/BOOTSEL/brightness buttons, and a three-pin SWD header. The marketplace adds 3.0 V tolerance and says non-power SAO pins are routed to the RP2350. These sources do not establish a final board revision, voltage/current budget, level shifting, overload protection, SAO standard conformance, electrical testing, or universal host compatibility.
The source tree names a DS18B20 one-wire sensor on GPIO 16 and three common-anode seven-segment displays multiplexed through a 74HC595, while the listing describes a waterproof probe and triple display. The firmware source says a missing DS18B20 produces a display fallback and logs die temperature to USB serial. No reviewed source provides temperature calibration, traceability, environmental limits, response time, error bounds, food-contact certification, or a suitable-use guarantee.
The README points to an Arduino 1.8.5 firmware directory and says stock AVR chips need a one-time bootloader step before normal Arduino flashing. This preserves an implementation trail without reproducing programming commands or claiming a safe procedure, final fuse/programmer configuration, reproducible build, tagged firmware, deployed badge binary, recovery path, support, or warranty.
The README names an STM32G031F8P6 Cortex-M0+ controller, MXC6655XA I2C accelerometer, and eight SK6805SIDE-G-003 side-emitting RGB LEDs as the current production target. It is source-backed design intent, not proof that this exact hardware was manufactured, placed on every board, tested, or distributed.
The README's BOM names an ATmega328P-PU, PCF8523T real-time clock, three pushbuttons, seven 2×3 SAO connectors, a 9 V jack/battery path, regulator parts, LEDs, display components, and an ISP port. It identifies a design inventory, not a verified final board, complete/electrically accurate BOM, component availability, safe power path, SAO pinout/current budget, host compatibility, or tested build.
The public repository calls the project a MidWestCoast Badge for a MidWestCoast Party and its firmware README labels the code DEF CON 34 badge firmware. These labels establish a publisher-supplied pre-event association, not party operation, organizer affiliation, date or venue, DEF CON endorsement, on-floor authorization, allocation, sale, pickup, attendee entitlement, or access control.
The RSSI sketch and HugQuest command path scan channels 11 through 26 and display channel signal-strength readings on the SMART Response XE screen.
RadioFunctions.h initializes the ATmega128RFA1 2.4 GHz transceiver and constrains channels to 11 through 26 for packet send/receive and RSSI reads.
The official BSidesSLC page identifies a custom ESP32-S3-WROOM electronic badge with a LoRa module and custom Meshtastic firmware.
DEF CON's official ticket page says preregistration guarantees a DEF CON 34 Human badge when the ticket is redeemed onsite in Las Vegas.
The official organizer-linked Eventbrite page now labels the event completed and sales ended. It preserves event context but not ticket-class details, sales count, purchaser list, pickup terms, receipt data, replacement policy, or fulfillment record.
Official registration guidance documents Sunday early registration for pre-registered donor-drive badge holders and Monday-Wednesday main registration with separate queues for different badge types. It establishes a current pickup workflow rather than a complete allocation ledger or a claim that every badge type has the same form or access rights.
The Friday and Saturday registration schedule pages say volunteers issued a printed badge or an electronic badge depending on ticket type.
The Arizona LoCo notes say CactusCon 2018 required tickets because the event was growing and had moved to Mesa Convention Center.
The default firmware mapped buttons for Hack Live website launch, voting, sabotage, hint, and live audience commands.
The commit-pinned README names an RP2040 microcontroller, MPU-6050 gyro/accelerometer module, thirty WS2812 RGB LEDs, and MicroPython. It does not establish a complete board design, exact component variants, power design, final manufactured revision, individual-unit functionality, performance, safety, or compatibility.
The repository description and README frame 5ohBEE as a SMART Response XE-based pager project with board setup through an ATmega128RFA1 development-board profile.
The stock firmware included a Z80 emulator running CP/M with classic software hooks such as Zork and Sargon, turning the badge into a tiny retrocomputer.
The immutable README describes an ESP32-S3, color touch display, LoRa radio, storage, buttons, LEDs, sound, expansion, and two-AA or USB-C power surface. It is a documented design summary, not a final-batch bill of materials, final hardware revision, safety claim, or configuration guide.
The first public source-release commit preserves KiCad 8, schematic, and fabrication files whose paths identify 2024_def_con_badge_v1. This demonstrates a source-published hardware archive without proving the date of manufacture, board quantity, assembled population, test results, physical distribution, or a right to manufacture derivatives.
The repository's public releases visible in the reviewed source pass are dated July 2026, after the 2024 event. They establish a later public software trail without identifying software installed on any 2024 unit or a current supported operating path.
Retia's current repository name says DefconBadge2026, but its metadata calls the project a Retia 2024 DEF CON badge and the immutable first source-release commit/README explicitly say 2024. This records the source conflict and 2024 provenance without treating the repository label as a 2026 event association.
The page says the badge can be used as a normal Meshtastic node after the event, keeping the artifact useful beyond DEF CON 33.
The badge reused surplus ZBD 55c-RB / EPOP55 electronic shelf labels with CC1110 control hardware and a bistable LCD that keeps its image without power.
Human, Goon, Press, Speaker, Vendor, Contest Organizer, and Uber badge shapes could be placed together as a puzzle, and Smitty & The Minions / Team Halibut earned honorable mention for combining all seven badges with modified firmware animations.
Attendee feedback explicitly called out the lack of an official badge challenge, so the record treats DEF CON 25 as a non-puzzle standard-badge year.
Grand Idea Studio links post-event research into over-the-air remote code execution against the badge's NFMI subsystem.
Tindie calls FrogStar a Defcon pickup preorder and says leftovers would be posted after the con. A separate live Uberflux listing shows $80, seven sold, 23 remaining, a DEF CON 34 drop label, and $11 USPS Flat Rate shipping. These seller contexts do not prove common inventory, an original DC33 allocation, final stock, payment, pickup, shipment, refund, replacement, or completed fulfillment.
The product and Hacker Couture list show $125, while the Hak4Kidz Lab profile says all proceeds support its mission and ethos. These statements do not establish inventory, payment, quantity, fulfillment, the amount or destination of any particular proceeds, tax treatment, charitable accounting, or completed donation outcome.
The seller page shows $100, an out-of-stock notice, and wording that the product has been sold out since September 13, 2025. This seller state does not establish shared inventory with the $140 Hacker Couture list, production quantity, buyers, payment, pickup, shipping, refunds, replacements, support, or completed delivery.
The seller page shows $150, an out-of-stock notice, and a statement that it has been sold out since August 11, 2025. This seller state does not establish production quantity, number of purchasers, buyer identity, recipient allocation, payment, pickup, shipment, refund, replacement, support, or party-benefit outcome.
The listing names a XIAO ESP32S3 and calls the badge's EMF detector live, saying it actively samples electromagnetic fields and renders a real-time spike graph. It does not identify the sensor, calibration, display/indicator hardware, sample rate, accuracy, or operating limits.
The listing names ESP32-S3, custom four-layer PCB, 128×128 OLED, five Cherry MX-compatible switches, and a tactile encoder. The firmware README documents an ESP32-S3 v3 variant with 128×128 SH1107 OLED and separately describes four face buttons plus an encoder; no final offered-board revision or full BOM is mapped by the sources.
NilbinSec describes a Spirit Box with a randomized word bank whose output rate is driven by its stated EMF signal, plus one- and two-player arcade games. The source supplies neither the implementation nor game, signal, audio, or firmware documentation.
The specification documents a LIS3DHTR accelerometer, LiPo voltage monitoring, DW01A protection, TP4056 charging, TPS63060 buck-boost conversion, and a PWM buzzer.
The badge exposes BME688 gas/pressure/humidity/temperature sensing, MQ-3 alcohol sensing, XYZ position, infrared receive/transmit, RTC, buttons, LEDs, speaker, and full-color display for ICS exercises.
The badge page documents CP2102 USB-to-UART access, /dev/ttyUSB0 discovery, PuTTY, and 9600-baud serial connection guidance.
The upstream Baochip-1x repository publishes open-source chip-hardware elements, taped-out RTL, VexRiscv configuration, simulation/FPGA material, and a CERN-OHL-W-2.0 license. It documents the announced chip context rather than a complete DC34 badge board or firmware image.
BadgeBuddy counted unique nearby BadgeBuddy BSSIDs every 30 seconds and adjusted the animation density to reflect nearby badges.
LosT's forum note framed the badge as a security token, curiosity device, and conference-participation prompt meant to get attendees interacting without the time burden of the Mystery Challenge.
The SDK branch documents hardware, audio, camera, e-ink, SAM LED, ASR/VAD, TTS, optional Whisper, native display, package, and Debian installation modules for the CM5 platform.
The root LICENSE is MIT and names David Prows with a 2025 copyright. The catalogue records that source license while keeping the separate requirement for a selected image's source URL, reuse basis, attribution, and processing notes before publishing a badge hero image.
The public project exposes Arduino-sketch, SD-card-asset, hardware, and license areas, while the root MIT license names slash128 for repository software/documentation. The README also refers to a driver installer and third-party Arduino board/library dependencies. This is a source-access record, not an endorsement, audit, binary provenance confirmation, build reproducibility result, final event firmware, support/recovery promise, or license statement for every bundled/external dependency.
Coruscant Productions says Clip-Boy ships in passive listen-only mode, while an optional research build with additional capabilities may be loaded by the user for authorized testing. The public sources do not provide the build, a final image/hash, a flashing process, support policy, compatibility matrix, rollback/recovery method, feature list, or license. The statement is preserved as a high-level boundary rather than a user guide.
The repository preserves user-app directories for games, screensavers, spectrum analysis, text adventure, air-quality, hardware-monitor, app-manager, and other MicroPython examples.
The README documents interpreter commands for IR, LEDs, note output, buttons, D-pad, framebuffer drawing, flash read/write, and source-buffer execution.
HackRVA's later interview describes audio from USB through the badge speaker path.
Official docs describe FREE-WILi GUI support, ESP32 WebSocket interface, USB serial console API, WASM scripting examples, host Python API, FAT filesystem, and WASM control of device features.
The repository stores emulator, tutorial, examples, manuals, and firmware paths so the badge can be studied or programmed beyond the original event floor.
The public tools repository preserves Python assembler and disassembler scripts plus pseudo-op support for writing Voja4 programs outside direct binary entry.
The 2023 status table marks audio output working on both badge hardware and simulator while audio/jack input remains not implemented.
The HackRVA recap documents two-channel audio behavior on the 2018 badge.
Attendees could build a bonus track with standoffs, headers, jumper wires, and a detect-pad bridge, then insert it into the badge for racing.
The official activity guide documents a small PCB kit that lets attendees harness the badge crank output to charge devices through USB-A.
The builder log says the ToorCon badge incorporated an SMD Challenge with eight LEDs, including one smaller 0201 LED.
The badge incorporated an SMD soldering challenge circuit credited to MakersBox, turning part of the board into a small assembly exercise.
NolaCon's badge page says the badge had been a conference Learn to Solder centerpiece for the past three years and presents Patches as the 2025 continuation.
The repository's visible history has an event-period README before the October 25 conference, while the main Arduino source appears in a November 21 post-event commit. The chronology preserves public evidence without equating the later checkout with a dated event binary or documented final artifact.
The public repository preserves firmware, Gerbers, SPI tooling, troubleshooting notes, a flash-image archive, and Apache-2.0 license metadata after the CTF window.
The listing says Science Dog is now Coder Dog and calls its keyboard-lighting behavior AI magic. It does not name a model, inference, application, network, controller, firmware, sensor, or programmable feature. This retains the maker's wording without converting it into an artificial-intelligence or software claim.
The team announces a brain-in-a-jar SAO and says tapping it causes something to happen to transmission objects in range. The source does not publish connector/pinout, electrical requirements, host compatibility, radio or proximity mechanism, availability, final behavior, safety guidance, or technical archive.
The listing says the SAO is inspired by Maria, the art-deco automaton from Fritz Lang's 1927 Metropolis, and uses AI in the product title. The technical description identifies only a powered red LED and does not describe a model, application, inference, sensor, network, or programmable behavior.
The listing frames #NOICE around the maker's stated concerns about immigration enforcement and says a portion of proceeds goes to the Immigrant Defenders Law Center. It does not publish the amount, percentage, accounting, transfer date, recipient confirmation, formal partnership, campaign terms, or outcome.
The repository points to a DEFCON34 MICD source and says the badge's SAO port is installed upside-down from the cited standard orientation, with a 3.0 V supply and 100 mA maximum-current context. It also says the MalO header can be inverted with a switch and jumper. This is a source-reported design consideration, not an official defect finding, a complete electrical specification, or proof of safe interoperability.
Telecom Village's official site displays PCBWay as Badge Sponsor for DEF CON 34. This supports a public sponsorship relationship but does not establish design, fabrication, assembly, funding scope, technical responsibility, or image-rights authority.
The official checkout calls the physical item a limited-edition LED badge. It does not identify a PCB, programmable controller, LED count/color, power system, firmware, radio, connector, or any other engineering surface, so the record preserves the narrow source classification rather than reconstructing electronics.
The post names an ESP32-S3-MINI-1-N8 with Wi-Fi, Bluetooth, 13.56 MHz NFC, and programmable LEDs. It does not provide a schematic, BOM, antenna/NFC design, power path, interface specification, final revision, performance measurement, safety guidance, or proof that every proposed unit has that exact hardware population.
The official Furry Village schedule says a DEFCON Furs badge was required for the group's 2026 event space, while the store says the badge does not get someone into DEF CON. Those published statements distinguish the community-event access claim from DEF CON admission; they do not disclose a technical access mechanism, prove an individual access result, or establish an ongoing credential.
The notice explicitly says Adversary Village badges do not give access to the con. In a separate paragraph, it says the village hopes to offer DEF CON badges to volunteers if availability permits, but cannot guarantee that result. These are distinct source statements and do not establish an access role, pass allocation, or a relationship between any future DEF CON badge and the named Adversary Village badge.
The `.ino` source uses Arduino APIs and the README credits MegaTinyCore as a foundation. It establishes a published firmware lineage, not an exact MCU selection, tagged event release, reproducible build, source-to-unit mapping, open-source licence, support commitment, or permission to reuse the source.
The public Arduino sketch defines 15 addressable RGB pixel positions and comments that the original badge has three PTC touch nodes; it changes its visual mode through the source's touch-handling path. This records a code-level interaction surface, not exact LEDs or electrodes, tested hardware, final installed behavior, or a safe operating procedure.
The CPEC repositories publish menu, pilot-record, game-state, display, sound, and game modules, and the earlier repository calls its code a non-final second iteration. Those sources establish an in-progress planned interaction surface, not final gameplay, player outcomes, a completed CTF, physical controls, accessibility behavior, or a deployed event experience.
The README says UPDI is exposed on the SAO header for reprogramming. It does not provide or establish a pinout, voltage levels, programmer compatibility, access-control policy, safe procedure, supported recovery path, final-board implementation, or successful event-unit result.
The notice says volunteers are expected to work approximately five hours per day, with hours assigned closer to the conference. It provides programme context for the stated village-badge benefit but does not determine a badge's physical form, eligibility outcome, schedule, access scope, use conditions, or completed contribution.
The game repository's PlatformIO configuration targets an Adafruit Feather ESP32-S3 no-PSRAM board with Arduino and a LittleFS configuration. This records an intended development target only; it does not identify a final badge PCB, assembly, controller population, storage, boot flow, power design, or a manufactured event unit.
The CFP promises every selected speaker a speaker-colored electronic badge and free admission.
The first-hand writeup describes DerbyCon's black badge as the event's lifetime-ticket equivalent and frames this build as the Legacy Black Badge artifact.
The sponsor category records badges designed by or for sponsors, including Arctic Wolf, Check Point, CompuNet, UETN, and Valcom entries with sponsor-booth acquisition framing.
The badge manual documents calibration plus steering and wobble modes that affect perceived left/right balance through conductive electrode pads.
The ticket page lists Basecamp ($300), Camp Muir ($500), and Columbia Crest ($1,000) under its 2026 patron section. It does not explicitly map the Special badge to one tier rather than another or document individual purchase and collection outcomes.
The module guide documents a CC1101 SPI radio option for 315, 433, 868, or 915 MHz matching-network variants, powered through the peripheral rail.
The module guide documents an optional NS4168 I2S amplifier and SPH0641 PDM microphone sound module on the side-port hardware.
distinctm1nd's public archive contains matching badge documentation, KiCad PCB/schematic files, and a Meshtastic-derived source tree. The event does not directly link it, so it supports hardware and firmware discovery without proving final production or deployed software.
The DC32 repository publishes Arduino sketches, setup/compile/upload scripts, KiCad project files, Gerbers, CAD/fabrication material, a parts list, and assembly instructions under an MIT repository license. Its documentation also notes a then-precompiled CTF library, and no reviewed source establishes that every current fundraiser unit ships a specific repository commit or complete CTF source.
DEF CON's August 7, 2025 news notice says attendees in the cash line were receiving paper badges because the main badge shipment was delayed.
Make It Hackin publishes one STL intended to be printed twice as a two-piece capture ring that lets a wearer suspend the official DC34 badge at different rotations, using user-supplied M3 hardware or zip ties and a dual-clip lanyard. The maker says its geometry was photogrammetrically derived and is not an official DEF CON drawing; this is a design file, not a shipped, tested, or DEF CON-approved accessory.
Uberflux maker `bud-lightbeer` lists a $4 180-degree SAO adapter for the DEF CON 34 ports, which the maker describes as upside-down relative to the intended SAO 2.0 orientation. The listing says the adapter does not change the badge's 3.0 V supply and warns complex SAOs may not tolerate it; its current marketplace snapshot shows 593 sold, seven remaining, and Friday/Saturday Badge Life Booth pickup. This is a third-party compatibility product, not an official finding of a port defect or a universal compatibility guarantee.
Mainak Sarkar's Glyph project is a public companion app for the described Blinky 2350 and references battery, button, and case-light state. It is not represented as official Workday software, preinstalled content, an attendee-wide deployment, or the event's base firmware.
The listing says a standard USB wall brick or portable battery pack can power the Power Back, that an SAO totem can run multiple SAOs, and that it runs three #NOICE or Not Just a Crosswalk SAOs where a regular CR2032 does not have enough power. It does not publish a pinout, USB-C or USB-PD behavior, cable requirements, regulator/protection design, output-current limit, voltage tolerance, heat test, electrical-safety certification, tested SAO matrix, or universal compatibility result.
caelyb's Uberflux listing describes a USB-C-to-SAO Power Back with maker-described 5 V-to-3.3 V conversion that lets SAOs run without a host badge, including desk or shelf display. As reviewed on 2026-08-04 it showed $7, 59 sold, 81 remaining, DC34 BadgeLife Village/LineCon/Queercon pickup labels, and post-DC34 CONUS shipping. It is a third-party standalone SAO companion associated by the maker with DEF CON 34, not an official conference item or a main-badge-mounted add-on.
The official registration update says CactusCon had a free tier and an option to purchase an electronic badge.
The same notes say there was no cost to get in but attendees had to pay in order to get a badge.
The attendee writeup says CactusCon 2017 could be attended free or with a $45 package that included a badge, shirt, and swag.
The BSides Global event listing says the 2026 pre-sale package included a guaranteed PCB badge along with a T-shirt, swag bag, coffee, lunch, and happy hour.
The contemporaneous listing names a USD 109 VIP Assembled Badge category alongside USD 55 General Admission. It does not say what the badge was assembled from, whether it was electronic, whether it contained a kit or credential, how many were offered, or whether purchases were fulfilled.
The official BSides Maine account advertised a special-edition badge and swag as VIP perks before the event.
The official page lists MiniBadge trading hours from Tuesday through Friday, with Monday closed, making trading an explicit conference activity rather than an inferred side event.
Ninja Networks built the DC17 badge as the electronic invitation artifact for its DEF CON-adjacent party at the Artisan Hotel.
Badge Pirates documents an unofficial Pirate badge variant plus a counterfeit-badge challenge triggered after badge imagery leaked before the event.
Grand Idea Studio says the fully designed but unpopulated circuitry supported an MMA7260QT triple-axis accelerometer and an MC13191FC 2.4 GHz RF transceiver for motion and ZigBee-class experiments.
Hackaday documented direct programming through tactile front-panel buttons and 272 LEDs that showed CPU state, data memory, opcodes, operands, and execution progress.
The workshop page calls out a large RGB notification LED and a large tactile button as the board's attendee-facing interaction surface.
The maker talk identifies an SSD1309 display and capacitive touch controls as the badge's user-facing interface.
The CAD-OuterBoard tree preserves attendee, Mafia, speaker, staff, and generic outer-board KiCad variants.
The project documents twin 1 Mbps CAN buses, two transceivers, external CAN headers, MITM or dual-logging breakout, and CAN-side badge focus.
The official CHV page documents the 2024 main badge with an RP2040, four CAN networks, a dry CAN connector, and four SAO connectors, while the public board tree preserves KiCad and production files.
Car Hacking Village's official badge announcement lists DB9 CAN 2.0/CAN FD support for the DEF CON 34 badge.
The official 2025 schedule says the village hosted a competitive CTF using a badge designed specifically for the Hardware Challenge Village.
The official 2024 schedule says the Hardware Challenge Village used a specially designed village badge for HCV.
The official schedule says each Hardware Village participant would receive a pre-assembled badge, with limited badges available while supplies lasted.
The Maker Village archive links an off-the-shelf virtual badge in Tinkercad so remote participants could inspect or simulate the project.
The report documents six surface-mount buttons and 16 RGB LEDs on the main badge face.
`main.c` maps 12 LED bits to AVR ports and the README describes words and patterns displayed through persistence of vision while the fidget spinner turns.
The Hackster materials list names 224 Adafruit 0805 LEDs, four 74HC595 shift registers, and sixteen 2N3904 transistors for the visual badge surface.
The project description names a 5x4 WS2812B LED array, and the development log says the design uses 20 LEDs rather than the earlier 25-LED expectation.
The README names WS2812B/SK6812 LEDs, while the firmware maps RC3 as the WS2812 output and cycles color-wheel and slow-fade LED effects.
The teardown documents four upper and four lower LEDs used for binary output, followed by a Morse-code light sequence.
The schematic labels top, left, right, and center LED groups with ten LEDs total, while the firmware drives three three-LED arms plus a center LED.
Hackaday describes the WarGames-inspired display surface as a dozen colored LEDs plus eight RGB LEDs.
The badge used reverse-mount RGB LEDs behind the THOTCON letters, single-color reverse-mount LEDs near capacitive buttons, and an IS32FL3731 driver for animation without heavy CPU load.
The public sources identify an ST7789 240x320 TFT display and six LEDs as the badge's main visual surfaces.
The BOM and wiring chart document seven LEDs with 220 ohm resistors mapped across Arduino digital pins D2 through D8.
The parts list and wiring notes document a flexible 8x8 WS2812 LED matrix connected to 5 V, ground, and Arduino A3/digital 21 for mouth and banner output.
The sketch README says A0 is the only data pin and goes straight to the NeoPixel strip; the main firmware defines NeoPixel output on A0 with 12 LEDs.
HugQuest includes WANNAHUG transmission, infected-state persistence, a displayed ransom-style HUG-token prompt, and an unlock command requiring HUG tokens.
The firmware advertises 503WAGON and exposes a BLE service and writable characteristic UUID 0503 that updates the on-screen banner text.
The README describes hidden party modes on BLEUART, while the BLEUART interaction sketch exposes list, rainbow, patriot, and off commands.
The project says the ESP8266 worked before the conference and exposed GPIO connections to the PSoC4 so the chips could interact and the PSoC4 could reset the Wi-Fi module.
Hackaday reports that Russell Handorf and Mike Kershaw used the badge as a simple low-part-count reference design during their hardware design workshop.
Attendees were expected to compile, configure, deploy, and modify an Aranya distributed wireless messaging application on the workshop board.
Operational history
2026-specific source changes are recorded precisely, while older hardware and guide material remains labelled inherited context rather than silently upgraded into a production claim.
The catalogue keeps the generic 2026 admission badge distinct from the 2025 electronic hardware and avoids a duplicate or fictitious 2026 board record.
The record uses the historical account for lineage context only and does not transfer prior-year specifications into the 2026 entry.
Readers can see the dated seller snapshot without treating an announced 2026 pickup as a completed distribution or as a change to the artifact's stated DEF CON 33 origin.
The record preserves the RF and navigation limits without implying universal aircraft tracking or software-selectable ADS-B bands.
The catalogue records the named cycling LED behavior without turning marketing language into an AI, software, security, or open-source claim.
The catalogue does not turn branding or creative language into an artificial-intelligence, software, security, or open-source claim.
No shop artwork, collectible art, static graphic, or media thumbnail is treated as a cleared factual image of the physical badge or copied into the public catalogue.
Hardware and firmware features are kept to repeatedly corroborated repository and guide statements instead of overstating uncertain generated prose.
The catalogue does not misrepresent the volunteer artifact as a DEF CON-issued credential, an admission pass, a substitute for registration, or proof of a delivered DEF CON badge.
The catalogue preserves the maker's exact high-level feature claim without presenting it as a privacy-safe, legally cleared, reliable, covert, or generally appropriate tracking capability.
The entry preserves the stated radio and sensing surface without implying an attendee-tracking deployment, a privacy guarantee, secure implementation, a particular collection practice, or a supported software workflow.
The dossier records the advertised research/detection surface without claiming reliable identification, safety, legal compliance, privacy preservation, target classification, or suitability for surveillance, counter-surveillance, or emergency use.
The record does not claim wireless interoperability, participant tracking behavior, a safe game design, data practices, live puzzle availability, or an authorized security-testing target.
The catalogue records the game behavior without implying broader real-world botnet capability beyond the AND!XOR badge network described by the project owners.
The catalogue records a source-documented village electronic badge without representing it as DEF CON's main badge, a guaranteed attendee item, an access credential, or a completed transaction.
Public source links remain available for inspection without labeling CAD/PWA material as open licensed, copying imagery, or implying a deployed/maintained companion service.
The catalogue records the published battery and shipment wording without treating it as a complete safety, transport, charging, or replacement-battery procedure.
The catalogue avoids merging the online CTF archive into the badge record without source-backed badge integration evidence.
The catalogue retains the public community-acquisition context without supplying private account details, challenge content, player data, unsupported redemption mechanics, or badge-software claims.
The catalogue treats these as source-described interactive features rather than asserting a verified challenge system, live service, privacy posture, or preserved gameplay archive.
Schedule and announcement context remains discoverable without attributing badge design to the game host or scheduled organizations, or inventing a finished challenge system.
The catalogue can document the simple published design and its source files without calling the generic SAO v2 description a verified DC34 electrical match, a universal host compatibility result, a safe assembly procedure, or a completed unit/fulfillment record.
The record preserves a justified DC32-source lineage without asserting an undocumented new DC34 board revision, a byte-for-byte 2026 firmware identity, or an error-free production BOM.
Readers can follow the historical public trail without treating the re-release label as proof of unchanged design, 2026 manufacture, backward compatibility, or a new engineering revision.
The record can link an especially useful implementation trail without falsely assigning a definitive prior event release, treating a `dc33` repository label as a DC33 artifact record, or claiming that 2026 units are new/unchanged/equivalent to the archived files.
The record preserves the maker-stated 2024 origin and the separate 2025 listing without creating a duplicate DC33 badge or treating either listing as confirmed event distribution.
The catalogue preserves two time-specific maker statements without calling either a completed event sale, a current in-stock guarantee, or a new DEF CON 34 badge.
The catalogue treats the SMAO as an independent contest-associated add-on, not a DEF CON credential, admission artifact, organizer endorsement, or verified conference firmware distribution.
The record preserves its documented event-vendor association without equating a product list or sold-out state with a confirmed attendee handoff or completed distribution.
The record remains an independently published pre-event project associated by its source with DEF CON 34, not an official conference badge, party credential, organizer program, or access item.
The entry retains the factual seller framing while avoiding an inference that the named person, show, DEF CON, or any performer/rights holder authorized, sponsored, designed, endorsed, or licensed the SAO or its media.
The catalogue preserves the badge-culture artifact while avoiding universal distribution, official handout, or finished-product claims.
The record preserves the maker's narrow coin-cell and kit caution without becoming a soldering, battery, child-safety, electrical, or assembly endorsement.
The catalogue records the ESP32-WROVER migration as a deliberate capability upgrade while preserving the team's documented engineering tradeoffs.
Readers can identify the intended experimentation surface without assuming every host, GPIO mode, cable, orientation, or shared bus configuration is safe or interoperable.
The catalogue preserves the warning so the artifact is not mistaken for a harmless universal add-on. Do not infer electrical safety, non-destructive behavior, authorization, warranty coverage, or suitability for an unfamiliar badge.
The record preserves a real manufacturing and bring-up issue as part of the badge history rather than presenting the 0xB build as frictionless.
The catalogue keeps the future-posting statement useful without presenting it as an existing source release, a programmable behavior claim, a reproducible build, or a legal reuse grant.
The catalogue links the documented interface without presenting it as an open-source firmware release, reproducible hardware design, or supported integration package.
The catalogue does not present the product as a safe, legal, reliable, universally compatible, or acceptable means of controlling another person's badge or television.
The record does not turn a feature list into a privacy guarantee, secure messaging claim, surveillance assurance, or universally suitable interaction model.
The record retains both source statements instead of presenting the README range as an exact implementation or claiming coverage, reliability, safety, or compatibility for a final target I²C bus.
The record documents a real kit surface without representing it as electrically characterized, risk-free to assemble, safe for every CR2032 setup, or compatible with every minibadge/host.
The record documents a real kit surface without representing it as electrically characterized, risk-free to assemble, safe for every CR2032 setup, or compatible with every minibadge/host.
The catalogue does not turn an assembly guide or parts list into a battery-service procedure, electrical-safety endorsement, charging assurance, or sanctioned modification instruction.
The record does not present LoRa connectivity, leaderboard coverage, or all-vs-all IR play as guaranteed DEF CON 34 behavior.
The record does not represent the badge as a certified radio, private or secure messenger, accurate indoor locator, universally legal deployment, or a performance guarantee.
The badge record keeps those statements source-specific and avoids claiming a single verified final controller until the project publishes a reconciled BOM or final schematic note.
The catalogue documents the source's creative framing without inferring religious, fraternal, organizational, legal, or licensing relationships beyond that stated theme.
Readers should not select cables, infer a connector, design touch software, rely on a touch count, or assume final board parity from either page alone.
The catalogue does not turn the word NFC into claims about a powered electronic badge, a contactless credential, a specific radio protocol, personal-data handling, or a reproducible implementation.
The dossier preserves the maker's terminology while not asserting ownership, franchise relationship, sponsorship, endorsement, authorship, or permission to reuse artwork/photos.
The catalogue preserves the named bundle and cross-badge relationship without inventing an interface standard or claiming every companion unit will work together.
The catalogue describes the maker's published theme at a high level but does not represent the project as officially licensed, authorize reuse of themed art/audio, or make a legal conclusion about the source materials.
The entry retains factual source wording without claiming that a franchise rights holder, DEF CON, or any other party authorized, sponsored, designed, endorsed, licensed, or approved the SAO or its media.
The dossier preserves the maker's title and event context without asserting ownership, cultural/franchise relationship, sponsorship, endorsement, authorship, or permission to reuse artwork or photos.
The record distinguishes current CircuitPython documentation and documented hardware capability from an asserted shipping QMK configuration or final delivery configuration.
The entry retains the source's non-personal identifier wording without presenting it as a complete privacy assessment, a tracking/non-tracking guarantee, a reader protocol, a data-use policy, or a deployed-service specification.
The catalogue records the intended mesh-chat behavior without implying that every RF condition, channel plan, or conference-floor routing outcome was solved before the event.
The catalogue records the existence of those code paths as evidence only and does not provide operating instructions or imply that transmitting, jamming, or replaying RF signals is lawful in any jurisdiction.
The catalogue preserves the source-backed Village association without portraying RTV D20 as an official DEF CON credential, admission badge, universal attendee handout, or verified access token.
The record preserves a valuable public source trail without treating an archive filename as proof of a prior conference handout or claiming that the current listed unit is new, unchanged, or technically identical to the archived design.
The record preserves a valuable public source trail without treating an archive filename as proof of a prior conference handout or claiming that the current listed unit is new, unchanged, or technically identical to the archived design.
The record does not infer standard-wide interoperability, electrical safety, external-SAO compatibility, or a particular companion SAO configuration from a product-description sentence.
The record makes the stated add-on surface discoverable without converting a generic compatibility sentence into a universal electrical, mechanical, or safety guarantee.
The catalogue preserves a relevant source note without declaring the official badge defective, safe for hot-swapping, or universally compatible.
The record does not promote a proposal into a universal standard, treat an advertised feature family as cross-host compatibility, or imply safe hot plugging or ARP support.
The public source is available as a separately scoped development trail, but this record does not assign its Pico W code, later ESP32 code, BLE behavior, components, or authorship to a specific physical 2026 prototype or all-attendee bare PCB.
The catalogue records a source-backed build path without treating it as a complete safety procedure or an endorsement of every battery, body placement, or modification.
The dossier preserves source-published terminology and creative context without asserting ownership, franchise relationship, sponsorship, endorsement, sole authorship, or permission to reuse artwork, photos, or video.
The dossier preserves source-published terminology and creative context without asserting ownership, franchise relationship, sponsorship, endorsement, sole authorship, or permission to reuse artwork, photos, or video.
The catalogue records an explicit programming surface without presenting it as a risk-free, universally compatible, authorized, or supported reflashing path.
The catalogue treats Uber Badges as an award lineage attached to the challenge and avoids naming unverified 2026 winners.
The entry does not treat a playful indication or a sensor part number as an air-quality monitor, medical/safety device, exposure warning, or replacement for appropriate ventilation and professional guidance.
Readers can understand the documented research surface without treating it as permission to monitor or follow third-party wireless activity, a privacy-safe product guarantee, a precise locating instrument, or a validated security tool.
No live network, privacy, lawful-operation, battery-life, charging, or electrical-safety claim is inferred beyond the documented reference behavior.
The catalogue avoids implying that every 2019 badge had an onboard camera, Wi-Fi-capable core, or face-recognition hardware.
The catalogue can transparently preserve the maker's stated context without recasting it as an independently verified political, legal, charitable, or organizational claim.
The catalogue does not infer universal distribution, a guaranteed participant badge, a completed CTF, or a final allocation count from the announced CTF access route.
The catalogue does not infer a universal attendee issue, final recipient count, or completed giveaway from the planned distribution model.
The catalogue records a pre-sale package and observed attendee artifact without claiming universal distribution, exact production scope, or a named board designer beyond the event listing's Fox Pick attribution.
The record preserves the organizer's announced recipient distinction without claiming that all attendees, sponsors, or speakers obtained a particular final unit or color variant.
The dossier records a documented conference artifact without translating an availability statement into universal receipt, final distribution, continuous operation, or a complete fulfillment account.
The record does not describe the item as an attendee entitlement, a DEF CON-issued Human badge, a volunteer badge, a personal device, or a completed distribution run.
The record remains a documented passive conference artifact rather than an unsupported claim about every attendee, a specific physical format, identity credential, venue access, or completed fulfillment.
The record does not treat the product description as a circuit design, electrical integration guide, or safe compatibility guarantee.
The compendium avoids MCU, firmware, LED, battery, and circuit claims and records the audio, physical, lanyard, and printed clue surfaces instead.
The record captures the verified hardware/software surfaces without claiming complete CTF reconstruction or complete production logistics.
The record preserves the verified hardware and software surfaces while leaving deeper artifact archaeology for a later pass.
The record is classified as an identity/payment and CTF artifact instead of inventing electronics, components, firmware, or distribution details beyond the official wiki.
The record preserves a real announced companion artifact without upgrading it into a programmable, electrically safe, standard-compliant, or universally compatible electronic badge.
The catalogue models a real planned named artifact without inventing its physical or electronic form, operating characteristics, safety profile, or engineering completeness.
The record is modeled as a participant admission/identity artifact and does not infer a paper badge, electronic badge, or technical design.
The catalogue models the object as a presenter wearable/event artifact rather than a general admission badge or attendee-wide distribution claim.
The catalogue records verified hardware and social-game behavior while leaving firmware, challenge, and complete variant archaeology for a later pass.
The catalogue keeps the 2018 record as a paid-badge entitlement and avoids unsupported physical or electronic details.
The catalogue can preserve a real admission-artifact claim without upgrading it into an electronic conference badge or credential technology claim.
The catalogue preserves the artwork credit as source context while leaving the visual empty until a specific image can be cleared under the project image rules.
The catalogue does not turn a retail component list into a complete construction, operating, or electrical-safety guide.
The record keeps hardware claims tied to the assembly PDF rather than inventing design files or firmware surfaces.
The catalogue keeps the universal bare PCB and limited populated-prototype claims separate instead of presenting the five advanced units as the standard attendee badge.
The catalogue preserves the organizer's explicit attendee-badge statement without presenting it as a verified universal handoff or a completed configuration for every individual participant.
The catalogue records the verified analog badge surfaces and leaves complete audio forensics for a later artifact-level pass.
The catalogue records the organizer's availability and premium-tier wording, not a fulfilled VIP benefit, a guaranteed badge allocation, a final stock ledger, or an admission/access entitlement beyond the source's high-level ticket description.
The compendium records the artifact under DerbyCon while avoiding claims of general conference distribution or regular attendee-badge status.
The catalogue can distinguish documented interoperability and game intentions from unverified full-badge implementation or reproducible-build claims.
The record remains a source-backed event artifact rather than an unsupported universal-attendee, access-control, or electronic-hardware claim.
No local badge image is published; the record remains source-backed and image-free pending a factual artifact image or official upstream raster with complete reuse basis, attribution, and processing provenance.
The record should not imply that every attendee received the final physical art badge immediately at registration; the temporary paper credential is part of the event artifact history.
The record describes the participant badge and its documented access context without treating every 2026 badge label as identical, universally issued, or an interchangeable DEF CON credential.
The catalogue records practical handling behavior that matters for surviving badges and post-event hacking.
The catalogue does not turn the seller's protected-battery and EMF language into a safety endorsement, electrical-service guide, calibrated-instrument claim, or paranormal-detection claim.
The record does not convert component names or marketing language into an electrical-safety endorsement, battery-service guide, or safe-modification claim.
The catalogue does not turn public power or CAD material into a battery-service guide, electrical-safety endorsement, charging claim, or safe-modification authorization.
The record does not transform source component claims into an electrical-safety endorsement, battery-service procedure, or sanctioned repair/modification instruction.
The record does not convert a high-level power-budget statement into a battery-safety instruction, a guaranteed power supply, or a safe multi-SAO integration certificate.
The catalogue preserves the seller's limited power/SAO statements without treating them as safe-use instructions, universal host compatibility, a battery-safety endorsement, or an electrical specification.
The record retains source-named components without presenting the badge as electrically complete, radio-compliant, safe to charge/carry, or suitable for every configuration.
The record presents the badge as a real deployed event artifact with field power lessons rather than a frictionless reference design.
The record presents Winglet OS as publicly buildable and hackable while making clear that toolchain, USB, and access workflows are not frictionless for every host.
The record avoids inventing a fixed MCU, app set, puzzle, or firmware behavior for the base Remoticon.2 template.
The catalogue can document the declared challenge companion without claiming that it was firmware, a badge-hosted application, or a particular physical interaction.
The catalogue preserves the game and collaboration claims without inventing a final challenge count, protocol, network/privacy guarantee, completed event experience, or solution material.
The catalogue records the verified hardware and challenge surfaces while leaving full artifact preservation for a later pass.
The software record describes the intended and observed challenge surface without implying a completed public solve path for every attendee.
The entry keeps the challenge description narrow until an official or first-hand walkthrough appears.
The catalogue intentionally does not reproduce connection credentials, network or local-service details, flags, hidden resources, challenge hints, serial commands, reset steps, or exploit material; it also does not imply a privacy/security review, safe operational configuration, reproducible build, legal reuse, or ongoing support.
The record preserves a practical handling caveat without escalating it beyond the attendee report or claiming a formal recall/safety notice.
The catalogue preserves the MiniBadge ecosystem while keeping per-board authorship, distribution, electronics, and official/unofficial status boundaries separate.
The catalogue preserves the verified trading and collection surface while keeping per-board authorship, acquisition, electronics, and support boundaries narrow.
The catalogue preserves the verified BadgeLife surface while avoiding unsupported claims about universal distribution, per-MiniBadge electronics, or official status for every submitted design.
The catalogue preserves the MiniBadge ecosystem while keeping acquisition routes, creator roles, and support boundaries separate from main-badge distribution claims.
The catalogue treats the Tipsy Badge as an independent DEF CON 33 badgelife release while keeping the official DEF CON 33 badge record separate.
The catalogue treats it as an unofficial/community DEF CON 33 badge release, separate from the mainline DEF CON 33 badge and village-issued badges.
The catalogue records the published DEFCON Furs event-space boundary without inventing a technical access-control system or a record of individual access.
No unverified SAO is added and no Badge.Life image is copied into the public catalogue; the record remains source-useful while awaiting completed add-on and image-rights evidence.
The catalogue keeps the files attached to the MechBattle record as a source-published companion design trail without representing them as a plug-and-play accessory, a safe wiring or flashing guide, a completed add-on lineup, or a distributed DEF CON artifact.
The record avoids unverified controller, pinout, schematic, or production-detail claims.
The badge page preserves the contest lineage while leaving full per-entry reconstruction and media review for a later archive pass.
The badge page preserves the contest lineage while leaving full per-entry reconstruction for a later archive pass.
The catalogue preserves the maker's stated creative reference without republishing related art or inferring a license for the product image, board art, or source material.
The entry models the disclosed identity/access artifact without turning a generic access statement into an electronic-badge, tracking, authentication, or privacy claim.
The record preserves the named volunteer artifact without turning a generic badge statement into an electronic badge, tracking system, authentication method, privacy claim, or confirmed physical handoff.
Country and event pages can show the 2025 badge lineage without turning remaining-stock pickup into an unsupported new edition.
Readers can follow the useful same-maker historical context without treating it as an undocumented specification for the new DEF CON 34 badge.
The catalogue retains a time-specific independent maker offer and village context without treating it as an official credential, guaranteed handoff, or completed transaction.
The catalogue retains a time-specific independent maker offer and village context without treating it as an official credential, guaranteed handoff, or completed transaction.
The catalogue preserves a time-specific independent-maker listing and schedule association without turning it into a fulfillment report, guaranteed handoff, or completed transaction.
The catalogue preserves a time-specific maker listing and schedule association without turning it into a fulfillment report or guaranteed handoff.
Readers can trace the useful v1/DC31 history without assuming the current planned sale is a newly engineered board, an unchanged old run, or a fully mapped revision.
Keep the source note explicit and prefer archive/search snapshots or future official archive pages if a dedicated 2025 official page becomes available.
The event page uses the schedule/Calagator October 14-15 dates and preserves the mismatch as a provenance caveat instead of silently normalizing it.
The record can describe the listed components and pre-flashed-controller statement without claiming reproducible hardware, inspectable firmware, update support, or reusable design files.
Surviving-badge owners should preserve state before using the documented post-event firmware path or DFU flashing workflow.
The record avoids converting a project description into surveillance guidance, an identification claim, a privacy/security assurance, a supported update process, or a guarantee of behavior on any deployed badge.
Future work should recover an archived copy before adding additional lore, instructions, or imagery from the original project page.
The catalogue treats the board as an unofficial DEF CON-adjacent badgelife artifact and avoids implying it was the official DEF CON 28 admission badge or a universally issued attendee item.
The record documents a real event-linked electronic artifact without treating the existence of badges or a manufacturing account as proof that every attendee received the same finished device.
The record preserves documented sponsor and speaker paths without treating them as proof of every attendee's final conference artifact.
The record preserves the documented speaker and guest paths without claiming a universal attendee eBadge, a known variant inventory, or a visual color treatment.
The record can distinguish a documented conference-wide promise and a corroborated attendee report from a complete fulfillment or variant inventory claim.
The catalogue avoids implying every BSidesKC attendee had a fully electronic badge while still recording the verified electronic badge ecosystem.
No participant count, entitlement, price, purchase result, or universal issuance is inferred from a public source archive or a single attendee project's account.
The entry does not turn a public source archive or one attendee account into a distribution record or a claim that every conference participant received the same badge.
The badge is included as a source-backed village badge without claiming attendee-wide DEF CON distribution or a final production quantity.
The record preserves the limited-run status without overclaiming final distribution.
The catalogue records a source-backed BSidesPDX 2018 badge archive without overclaiming distribution scope.
The catalogue records the electronic badge without implying that every attendee received a fully assembled programmed unit.
The catalogue treats the artifact as a source-backed La Villa Hacker 2025 badge without implying every village attendee received one.
The record avoids claiming universal DEF CON, DC503, or BSidesPDX distribution and treats the artifact as a VIP/party wrist badge.
Claims are limited to a self-order/forkable hardware template and do not imply all Remoticon attendees received one.
The record preserves the verified distribution language without implying every DEF CON or BIC Village attendee received one.
The record avoids claiming universal 503 Party, DC503, DEF CON, or RainSec distribution and limits itself to the public repository's party-pager scope.
The catalogue records the source-backed BSidesPDX 2016 PCB badge without claiming that every attendee received one.
The catalogue records a source-backed BSidesPDX 2017 badge archive without overclaiming distribution scope.
The catalogue models the artifact conservatively as a BSidesPDX 2015 badge-hacking board archive rather than a universal attendee badge claim.
The catalogue records a source-backed BSidesPDX 2019 badge archive without overclaiming distribution scope.
The catalogue may state that the badge was given to attendees, but it does not claim final production quantity, ticket-tier mechanics, or exact replacement/spare counts.
Hardware and software claims stay tied to the current public documentation snapshot and should be revisited if FREE-WILi revises the page or publishes design files.
The entry is a narrow source-backed analog-artifact record, not a reproducible open-hardware or software dossier.
The catalogue retains the maker's concrete sales description without claiming a reproducible design, supported repair path, open-source release, or lifetime product maintenance.
The record remains useful for source discovery while preserving the limits of the public documentation.
Readers can see the source-published REV1 limitation without receiving an unsafe repair prescription or an unsupported claim about a later board revision, battery behavior, accelerometer reliability, or field fix.
Readers can distinguish the organizer's philanthropic request from financial, tax, legal, privacy, or data-security advice and should not assume a particular validation, deduction, confidentiality, retention, or delivery outcome.
The catalogue records a real named planned badge project and a source-published companion design trail, but does not turn source files into proof of physical, safe, completed, or distributed hardware artifacts.
The record remains image-free and does not reproduce draft lore, repository previews, screenshots, logos, board renders, or any generated/approximate badge image.
Readers see the two-source-backed badge designs without treating one board's hardware, firmware, or production state as universal to the other.
CactusCon 2012-2013 and 2015-2016 stay explicit negative coverage until primary event pages, ticket text, badge-team archives, photos with reuse rights, repositories, or other artifact-level public sources surface.
The record preserves a real build and repair constraint without inferring a root cause, systemic hardware defect, or attendee-facing failure beyond the official statement.
The commercial sponsorship label is preserved as context but does not turn this non-electronic coin record into an unsupported electronic-badge claim.
The paper record remains bounded to students, while the separately seeded speaker electronic-badge record captures only the allocation actually established by public sources rather than treating ticket marketing as a universal technical claim.
The catalogue records the narrow cross-event verification protocol without treating the marked Black Hat badge as a general attendee entitlement, a DEF CON admission badge, a technical access credential, or proof of delivery.
The catalogue retains precise maker-published components without treating a storefront specification as a fully reproducible design or universal SAO compatibility guarantee.
The catalogue records an event-specific hardware badge design without turning a creator's commission statement into proof that every attendee received it, that it was an official access credential, or that any particular physical unit was issued.
The badge is classified as an independent planned project associated with DEF CON 34, not an official conference badge, registration benefit, access credential, organizer-endorsed product, or confirmed distribution.
The catalogue preserves the exact public event label without presenting this small source project as an official DEF CON item, a confirmed BadgeLife artifact, a completed delivery, or an access credential.
The exact public event label remains discoverable without turning it into evidence of OWASP or DEF CON endorsement, a physical run, availability, a completed delivery, or a credential.
The catalogue preserves an exact event label without inventing official status, availability, ownership, attendee access, or a relationship to another Agency-themed record.
The catalogue treats the dated conference as completed and its badge platform as source-backed without representing the logistics plan as proof that a particular person received a particular unit.
The event edition is named by year and kept source-scoped rather than assigning an unsupported CactusCon edition number.
The record avoids turning a stale or mixed archive page into an incorrect precise date claim and leaves the date open for a dated official programme, ticket, or post-event report.
The entry separates source-backed plans, public interpreter code, and final-event uncertainty.
Manufacturer facts are labelled platform baseline only, and no retail configuration is presented as a universal or event-specific Workday build.
The entry preserves factual source language without claiming that any named/unnamed party authored, approved, sponsored, designed, endorsed, licensed, or consented to the message, artwork, or presentation.
The catalogue records the optional antenna path while preserving the modification risk and RF-protection context.
The catalogue avoids importing media from social/gallery/press surfaces while preserving source links for future review.
The catalogue records the stated visual control without presenting fast flashing as safe, suitable for every viewer, or a substitute for appropriate user caution.
The catalogue records the stated visual effects without presenting them as safe or suitable for every viewer.
The record presents the badge as a serviceable field device with operational constraints rather than a frictionless consumer gadget.
The catalogue preserves the documented architecture and declared licenses without asserting a particular part population, full standard conformance, reproducible attendee firmware, or a final supported release.
The catalogue preserves the real design/archive trail without treating a planning repository as proof of a final issued conference badge.
The record distinguishes open design capability from a claimed uniform production configuration or a complete inventory of event-issued variants.
Readers can inspect the source-supported circuit outline without treating a work-in-progress layout as a completed, safe, compatible, or reproducible attendee device.
The record preserves the documented design and component outline without calling it a fabrication recipe, safety assessment, universal compatibility result, or final production specification.
The catalogue preserves the narrow source-backed hardware outline without representing it as a complete build specification, safety assessment, compatibility guarantee, or fabrication recipe.
Readers can inspect inherited technical context without treating it as a safety validation, complete specification, compatibility guarantee, or reproducible final device.
Source-backed component and interface references remain a bounded design trail rather than a universal physical-badge specification, safety certification, performance claim, manufacturing record, or operating guidance.
Hardware claims stay tied to public source targets and documentation rather than becoming a final board specification, manufacturing result, complete build recipe, or evidence that any given unit contains a specific component set.
The dossier keeps the stated feature set intentionally narrow and does not promote it into a final reproducible engineering design or a manufacturing-quality claim.
The record documents intended and exposed firmware surfaces without implying that every listed protocol or feature was complete during DEF CON 33.
Readers can follow the open source trail while the catalogue avoids treating a default licence statement or development guide as final firmware provenance, a universal binary licence, or a deployment guarantee.
The catalogue keeps the strong official badge-guide evidence while avoiding unsupported claims about the unrecovered design files or shipped firmware internals.
The dossier distinguishes an accessible development-source trail from a complete reproducible event-unit release.
The catalogue links public code and fabrication material without claiming a secure updater, complete deauthentication detector, supported release, final feature set, universal license scope, or permission to republish every artifact image.
Source-level game and interface behavior remains discoverable without labeling the branch as a final, universally flashable, supported event firmware package.
Readers can locate the declared binary release without assuming it is open source, reproducible, authenticated, safe to flash on every variant, or supportable after failure.
The record treats the code as a valuable public archive without asserting a final official firmware release, production flash state, challenge outcome, or supported owner-update path.
The record intentionally avoids detailed firmware claims beyond USB-oriented hackability until stronger primary source is recovered.
GPLv3 source information is recorded for research, while any local photo asset remains blocked until its individual source, reuse basis, attribution, and processing record are complete.
The catalogue reports the valuable source and community-hacking trail without calling any checkout a final, authenticated, supported, or universally deployed badge image.
The dossier treats it as valuable code evidence without claiming the current checkout is the final deployed badge firmware or a supported update/recovery path.
The record can describe the maker's announced feature surface without claiming a released, reproducible, inspectable, or reusable firmware archive.
The game and flashing material remains valuable development evidence, but not a claim about production behavior or a supported owner-update path.
The catalogue can link the source project without turning development instructions into a recommendation to program hardware, treating visible files as a final/reproducible deployment, claiming legal reuse, or publishing a repository visual without complete image provenance.
The catalogue links public project material without treating source visibility as a completed firmware release, security guarantee, network/data practice, or reusable code grant.
The dossier records a concrete source release without asserting source-to-sale identity for every unit, a complete dependency/security audit, a warranty, or a safe user update path.
The catalogue can link the MIT source and named binaries without treating them as a universal, final, supported field-update package.
The record links the public workflow without representing it as a final reproducible, supported, audited, or universally deployed firmware release.
The public code is linked as evidence without being presented as licensed, supported, reproducible, safe to reprogram, or equivalent to a delivered event firmware image.
The dossier links the public work without presenting it as a finished end-user firmware or support package.
The catalogue can link the implementation without presenting it as licensed open hardware/software, a stable release, a reproducible final build, a safe reflashing process, or an ongoing support commitment.
The catalogue does not claim a released firmware archive, update path, reproducible build, API implementation details, or redistribution rights.
The record treats the repository and firmware documentation as living event artifacts rather than claiming a frozen pre-event production firmware state.
Readers can understand the advertised feature set without assuming it is open source, reproducible, supported, safe, or available in every unit/configuration.
Readers are not led to assume that the D20 name denotes an electronic game, an access pass, a CTF device, or any documented implementation.
The catalogue records the advertised activity and party-support framing without assuming open source, an ongoing service, rights-cleared content, a particular beneficiary, or a verified fulfillment of support.
The record does not convert a game announcement into a reproducible software release, operational service, security claim, data-handling guarantee, or solution guide.
The catalogue links a substantive public development trail without treating a branch label or bootloader documentation as a complete supported release, a safe flashing guide, a legal reuse grant, or proof of every event unit's firmware.
The catalogue records the published high-level feature surface without supplying programming steps, treating it as an audited firmware release, promising safe behavior on attached devices, or reusing marketplace media.
The catalogue can cite the public source archive without presenting it as a finalized event release, validated VOC algorithm, supported update path, secure deployment, operating instruction, or a code/artwork/media reuse grant.
The catalogue preserves the source-backed 400-distributed claim and technical tree without turning either into a universal allocation or event-day firmware assertion.
The record describes the maker-published audio/storage intent without asserting reproducible firmware, media-reuse rights, final playback behavior, or user-operation instructions.
The record describes the stated audiovisual/art surface without asserting reproducibility, software availability, audio/art reuse rights, final content, or support scope.
The catalogue does not characterize the badge as secure, audited, reproducible, open source, performant, or suitable for a security-sensitive purpose solely from maker marketing or an adjacent framework.
The catalogue links the public source archive without treating it as an audited or finished firmware release, authorizing users to follow its procedures, or treating the root license as broad hardware/media/image permission.
The dossier records the promise as a future source lead without asserting software availability, reproducible builds, final feature behavior, or reuse rights.
The record does not represent deferred or merely hardware-capable categories as shipped functions, supported workflows, secure behavior, or final user experience.
The catalogue records public code and documentation without asking readers to run installers, treating the project title as a security claim, or representing the repository as a complete/audited/reproducible event-firmware release.
The catalogue does not infer radio technology, cryptographic behavior, exploit mechanics, interoperable networking, source availability, or redistribution rights from promotional game language.
The catalogue does not translate a security-oriented maker claim into a cryptographic assurance, vulnerability claim, identity guarantee, or implementation recommendation.
Code and design material remain linked as evidence, while the record stays image-free and does not present the repository as an open-hardware, software, artwork, or media-reuse grant.
The catalogue does not turn a future publication promise, flashing LED component labels, or an old Gerber archive into a claim of programmable behavior, open source, reproducible current firmware, or licensed reuse.
The catalogue links a public implementation trail without converting marketing language into a legal reuse grant, reproducible build, supported reflashing path, final firmware release, or warranty.
The catalogue links a public implementation trail without converting marketing language into a legal reuse grant, reproducible build, supported reflashing path, final firmware release, or warranty.
Readers can understand the advertised interaction surface without assuming open source, completed service availability, reproducible behavior, or a verified security model.
The catalogue preserves the advertised interactive surface without assuming it is open source, reproducible, stable, fully documented, supported, or uniformly present in every unit.
The record does not offer configuration or operating instructions, claim secure or private interaction, assert a released firmware, or treat public code as a license grant.
The dossier does not infer programmable behavior, a user-update path, a released build, support obligation, open-source or open-hardware terms, or permission to redistribute repository files or visual material merely from public visibility.
Public source visibility is recorded without treating it as a finished event release, reliable operating path, security assurance, or permission to copy code, artwork, project branding, photographs, or screenshots.
The catalogue can describe a public editable software path without claiming a production-certified firmware release, uniform field deployment, long-term maintenance, or safe configuration.
The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.
The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.
The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.
The catalogue can link the public engineering trail without representing the badge as fully open source, reproducibly buildable, support-guaranteed, secure, licensed for reuse, or equivalent to every shipped unit.
The dossier links relevant public context without representing it as an available, reproducible, supported, or authorized Clip-Boy firmware package.
The catalogue does not treat marketing jokes as a reliability, security, firmware, or open-hardware claim.
Readers are not led to assume electronic behavior, firmware availability, open-source status, video-game functionality, or a supported modification path from the artifact name alone.
Readers can follow the documented update surface without assuming the badge is open source, reproducible, auditable, redistributable, or supported beyond the published high-level instructions.
The catalogue links the public archive and records the documented state transition without recommending installation, claiming that a later source tree exactly matches every badge, or presenting the token and QR features as independently validated or permanently supported.
The catalogue retains first-party product wording without turning it into a programmable-badge, open-source, reproducible-design, authorship, cultural-affiliation, endorsement, or reusable-media claim.
The catalogue retains first-party product wording without turning it into a programmable-badge, open-source, reproducible-design, authorship, cultural-affiliation, endorsement, or reusable-media claim.
The entry does not turn simple listed behavior into an open-source, programmable, or security-verified badge claim.
The record does not turn a documented blinky add-on into a programmable badge, released source project, reproducible build, or legal reuse grant.
The catalogue does not present a proposed sensor badge as a released software project, a programmable device, a privacy-reviewed tracker, a reproducible build, or a legal reuse grant.
The record makes the public documentation discoverable without turning it into an invitation to bypass challenges, a verified update path, a final firmware archive, or a supported modification procedure.
The catalogue links a substantive source and firmware trail but publishes no repository image or artwork and does not present a later source revision as a supported update or all-unit state.
The catalogue credits the public source basis without supplying unverified programming steps, device-specific firmware claims, a reproducible build, or reuse terms.
The catalogue links a real public project without implying that a labelled firmware build is complete, audited, installed on every unit, safe for a particular radio/data context, or accompanied by a support guarantee.
The catalogue records public behavior claims without exposing or inventing challenge content, protocol messages, source availability, update steps, or reuse rights.
The catalogue records the verified public badge surfaces and flags that the production and firmware story needs a deeper artifact-level chronology.
The catalogue records verified hardware and challenge structure while leaving full artifact preservation and firmware archaeology for a later pass.
The catalogue records verified hardware and hacking surfaces while leaving complete firmware and variant preservation for a later artifact-level pass.
The compendium records observed behavior and published challenge paths while avoiding unsupported claims about the badge's internal firmware architecture.
The badge page describes the published public-domain source and visible electronic invitation hardware without upgrading abandoned goals into production behavior.
The record preserves an operational caveat that matters for surviving badges and avoids presenting reflashing as a risk-free generic CC1111 workflow.
The project owner notes that interrupted flashing could leave a badge in a broken state; EEPROM storage is listed as a future improvement.
Software claims remain limited to user-supplied electronics and do not invent a Remoticon 2020 badge firmware platform.
The entry records the verified soldering badge and hacking surface without inventing software behavior.
The catalogue records verified hardware, game behavior, and recovery workflow while leaving full firmware preservation and challenge reconstruction for a later pass.
The software section records the verified staff-flashing workflow without inventing firmware behavior or challenge internals.
Software behavior is kept conservative until firmware or attendee documentation surfaces.
The record describes verified assembly and interaction evidence without inventing unrecovered firmware behavior or treating every MiniBadge as source-open hardware.
Software and protocol claims are kept to the public project statements rather than treating development notes as a complete release package.
The record preserves verified hardware/software surfaces while leaving deeper MSP430 firmware archaeology for later work.
The catalogue records the verified hardware and update workflow while leaving complete firmware archaeology for a later artifact-level pass.
The record treats manuals, firmware binaries, and repository artifacts as living owner-support evidence, not as proof that every recovered file represents a bug-free Pasadena production state.
The catalogue preserves the battery/USB safety erratum and does not treat all Hackbat boards as identical to the fixed public revision.
The catalogue records a current sold-out/interest state without calling every unit delivered, treating a signup as an order, or claiming a future run will occur.
The record presents real delivery friction and the announced later programme without implying frictionless 2025 distribution or universal 2026 participation.
The catalogue points to a public board platform without representing the shipped game or final coin as open source, reproducibly buildable, safe to reflash, supported, security-reviewed, or licensed for redistribution.
No board art, product imagery, source preview, or derivative is treated as a rights-cleared factual hero image merely because the code/design source is public or broadly licensed.
Readers should not assume that a purchased companion is the same as a free-drop item, that every color is available in every channel, or that all public claims describe one identical physical run.
The catalogue treats the PDF title as an edition-number wording issue rather than a separate 2012 event claim.
The record does not turn marketing references to hardware, firmware, or GPIO into an unverified electronic-badge specification.
The record retains documented engineering surfaces while withholding a complete implementation claim until Car Hacking Village publishes a final technical archive.
The dossier records the real electronic artifact without treating the term electronic, a ticket-page slogan, or social confirmation as a component-level technical description.
Component and firmware claims remain limited to the public product and announcement text, with no invented electronics or implementation details.
The catalogue records the named artifact and interaction wording without presenting a theme or generic electronic terminology as an architecture or hardware specification.
The record preserves the verified physical PCB form while withholding an electronic-device, firmware, component, or challenge claim until Fox Pick, BSidesNOLA, or another primary archive provides it.
The record remains an explicitly ticket-listed identity artifact rather than inventing electronics, software, CTF integration, or a finished construction from a tier name.
The record can show the documented development directions without collapsing alternatives into an invented production specification.
The record can name the published interfaces without suggesting that the badge is reproducible, electrically characterized, isolated, or safe for any specific live system.
The record presents the badge as a real hardware lab platform with documented errata rather than a polished reference design without caveats.
Surviving-badge hacking and firmware flashing should respect the documented power and flash-write constraints.
Published firmware detail is not represented as a complete open-hardware, production, or safety dossier.
The record does not transform source tree names and schematic/fabrication material into a verified production bill of materials, safety endorsement, repair guide, or field-operating recommendation.
The record retains supported feature families while avoiding a claim that the live offering exactly matches one repository branch, older board revision, or a complete production BOM.
The entry can point to a concrete design archive without presenting the SAO as electrically complete, interoperable with every host, safe for every power source, fabricated, tested, or compliance-validated.
Hardware claims stay limited to the product page, pinout text, and firmware constants without inventing board layout, production quantity, or undocumented circuit details.
The record can describe the documented board design while avoiding a claim that the public files are the exact final build, that every event badge carried the listed footprints, or that the design was manufactured and tested at scale.
The catalogue preserves the documented board-level surface without presenting a talk summary as a complete hardware specification, manufacturing record, safety assessment, or reproducible design.
The record links a real design trail without presenting it as a complete electrical specification, a validated battery/adapter recommendation, a universal SAO compatibility claim, a safe assembly guide, or a manufactured quality record.
The record does not turn a maker-described bare board and battery arrangement into a safe-use instruction, a battery-life guarantee, or a universal hardware-compatibility claim.
The record provides the documented hardware surface without becoming an electrical, radio, battery, fabrication, or repair endorsement.
The entry does not turn an availability comment into a complete BOM, safe battery-use statement, final product configuration, or engineering specification.
The dossier does not turn an open technical design into an accuracy guarantee, safe-use endorsement, electrical compatibility certificate, or universally compatible host accessory.
Readers can trace the available maker material without assuming that the host is fully documented, programmable, open source, reproducible, universally compatible, or licensed for redistribution.
The record can link a source-published design trail while withholding a final physical specification, safe battery-use claim, collision-free bus guarantee, or universal SAO compatibility assertion.
The public trail is useful for research and preservation without turning GigaGeiger into a universally safe, electrically characterized, regulatory-cleared, production-reproducible, or fully documented device.
The record retains high-level source-backed design claims without treating them as an electrical specification, a battery-safety statement, a radio-compliance claim, a universally compatible SAO result, or operational advice.
Public fabrication material and candid build notes remain discoverable without becoming a universal build, battery-service, radio-operation, or electrical-safety recommendation.
The catalogue records the source-published LED and connection context without claiming universal host compatibility, a ready coin-cell wearable, electrical safety, soldering safety, or a complete engineering specification.
The catalogue records the organizer ticket description and narrow community terminology without presenting either as a documented electronic architecture, programmed feature set, safety statement, or reusable hardware design.
The catalogue preserves the exact ticket and timeline language without presenting the record as a documented electronic architecture, released software project, safety statement, or reproducible hardware build.
Maker-published feature language remains traceable but is not treated as a reproducible build, released firmware, open hardware, free software, or permission to reuse technical or visual material.
The record provides a traceable hardware surface without representing it as an electrically complete design, radio-performance guarantee, or safety validation.
The catalogue retains a traceable physical surface without representing it as a complete electrical design, measured power profile, host-compatibility guarantee, or safety validation.
The record provides a traceable hardware surface without representing it as an electrically complete design, runtime guarantee, programming guarantee, or safety validation.
The catalogue does not promote a short product description into a general electrical-compatibility, reliability, or safety guarantee.
The record does not convert a direct-DC34 marketing claim into a general electrical or mechanical compatibility guarantee.
The record preserves the documented kit surface without converting it into an electrical specification, safe-build/use instruction, radio/RFID compatibility claim, battery-life estimate, or universal SAO-host guarantee.
The catalogue retains the seller's named surfaces without representing the kit as an electrically complete design, general compatibility guarantee, or safety validation.
The record retains a traceable physical assembly surface without representing it as a complete electrical design or general interoperability guarantee.
Readers can inspect the source-described hardware and its own caveats without treating it as a universal plug-and-play, electrically safe, or fully validated device.
The record does not turn product-level programming and cable claims into a universal target-support list, safe-voltage recommendation, USB certification, durable-cable guarantee, or complete electrical design.
The record retains a traceable hardware surface without presenting the coin as electrically characterized, safe for every cable/host, reproducible, compliance-tested, or suitable for unsupervised modification.
The record describes its source-backed interaction surface without turning it into a hardware specification, a safe connection/modification guide, a wireless-security claim, a universal SAO-compatibility result, or a validated physical-unit record.
The record does not turn product-level specifications into a complete electrical design, safe-use instruction, repair guide, certification claim, or universal SAO guarantee.
The record retains the documented components without converting them into a complete electrical design, power-safety claim, performance statement, production specification, or repair/build procedure.
The record preserves named hardware without turning it into a complete, electrically safe, interoperable, or production-verified design.
The record reports specific listed features without presenting the badge as electrically characterized, reproducible, or safe for any unsupported modification.
The dossier preserves the published technical nouns without treating them as a complete electrical design, interoperable standard, safe-use instruction, or confirmed production specification.
The dossier remains technically useful without becoming a reference design, external-target compatibility assurance, power specification, or hardware safety endorsement.
The dossier links an inspectable design trail without asserting that every source-derived board is electrically compatible, safely assembled, safe to attach, or suitable for unattended modification.
The record documents a real LED SAO design trail without presenting either the old or planned re-release as electrically characterized, safe for every host, mechanically compatible, or suitable for unsupervised modification.
The entry can point to a concrete archive without representing the SAO as electrically complete, interoperable with every host, safe for every power source, fabricated, tested, or compliance-validated.
The entry can point to a concrete archive without representing the SAO as electrically complete, compatible with every Portal Badge or host, safe for every power source, fabricated, tested, or compliance-validated.
The catalogue retains a useful hardware inventory without representing it as an electrically complete design, general host-compatibility guarantee, or safety validation.
The entry does not turn an LED-badge product label into a claimed circuit, operating behavior, repair path, certification, or safety assurance.
The entry keeps its useful electronic-design trail visible while avoiding an electrical guarantee, universal SAO compatibility claim, safety endorsement, or do-it-yourself operating instruction.
The record does not convert a maker-described lighting surface into a universal electrical compatibility or reliability guarantee.
The entry can accurately describe the released engineering material while withholding a universally safe host/power claim, compliance finding, independent performance guarantee, or repair/modification recommendation.
The record does not convert promotional/high-level descriptions into an electrical specification, RF certification claim, charging recommendation, repair/modification guide, or safety endorsement.
The dossier keeps precise seller-described features without turning them into a complete electrical specification, safety endorsement, repair guide, or RF/compliance claim.
The record does not promote a decorative power-on statement into a general electrical compatibility or reliability guarantee.
The entry reports the named firmware target and interaction surface without inferring a complete electrical design, reliable touch behavior, safe power path, or compatibility with external hardware.
The dossier does not convert a useful product and how-to description into an electrical integration certificate, universal host fit, or material-safety guarantee.
The record does not upgrade a reveal or sponsor label into a technical specification, software claim, challenge mechanism, safety assessment, or reproducible badge design.
The catalogue records the real high-level artifact without publishing operational payment-security instructions or turning programme language into a technical teardown, safety assessment, or reproducible design.
The record makes the organizer-published design intent discoverable without converting sales copy into a finalized, safe, interoperable, privacy-reviewed, or source-released device.
The compendium records the physical badge-conversion activity without inventing a circuit, analyzer implementation, radio behavior, data-collection practice, safe build procedure, or reproducible technical design.
The record preserves the verified artifact classification and v2 fabrication statement without inventing electronics, connector behavior, or electrical safety properties.
The catalogue records the badge as a real registration-tier artifact without upgrading it into a specific PCB platform or game badge.
The catalogue treats the BIC Pick as a physical commemorative and identity artifact, not as an electronic badge unless primary technical documentation appears.
The catalogue avoids unsupported claims about exact PCB assembly and distribution while preserving the source-backed ESP8266 watch firmware record.
The catalogue avoids claiming pinouts, radio firmware internals, LED counts, or final production files until an official or creator archive is found.
The catalogue records only the verified badge behavior and avoids inventing electronics beyond the public BBV Badge 2025 source.
The catalogue keeps the record as a source-backed kit badge and avoids inventing electronics beyond the published discrete marquee description.
The badge is modeled as a source-backed artifact without invented electronics or component claims.
The badge is a serious open FPGA platform, but catalogue readers should not treat the public PCB as a frictionless reference design without reading the errata.
The catalogue preserves both source trails and avoids asserting a single microcontroller family until a JawnCon-specific schematic, BOM, or firmware fork is recovered.
The catalogue records the verified firmware and challenge surface without inventing physical-form-factor, power, or hardware-design details.
User-facing wording documents capability without overstating permission or harmful use.
The catalogue treats this as a DC33 software/support/accessory refresh of the Aerospace Village ADS-B badge, not as a newly designed 2025 board revision.
The entry remains source-backed and image-free rather than copying article photos, event media, repository screenshots, or project images without full provenance.
The entry remains source-backed and image-free rather than copying article photos, event media, repository screenshots, or project images without full provenance.
The directory structure is recorded as a useful maker trail without treating it as a complete released hardware package or confirmation that all sales share one documented revision.
The catalogue records ESP32-S3, OLED, charger, LED, BLE, serial, and firmware-analysis details as teardown-backed rather than official board documentation.
The catalogue can now record the public technical archive while withholding an audited final BOM, manufacturing package, event firmware image/configuration, app settings, challenge archive, production count, and proof that every delivered unit matched the public tree.
The catalogue keeps hardware claims to verified public documentation and avoids inventing component identifiers or manufacturing details.
The record captures the source-backed artifact without inventing electronics or software behavior beyond the public evidence.
Hardware claims stay limited to the README programming workflow, nRF52832 target, SSD1306 display setup, I2C pin mapping, and firmware-observed inputs.
The catalogue records the real village artifact while avoiding unsupported component or firmware claims.
The catalogue records verified hardware and firmware configuration while avoiding unsupported custom-board or source-release claims.
The catalogue can document the firmware, simulator, and RP2040/Pico SDK workflow while keeping manufacturing-grade hardware claims open.
Future work should revisit ToorCamp and Shadytel archives for hardware details before adding component-level claims.
The record may preserve the maker-stated DEF CON 33 association while avoiding a stronger original-distribution, sale, allocation, or event-outcome claim.
The entry does not turn a historical promotional sentence into a 2026 electronics, firmware, challenge, compatibility, or delivery claim.
The compendium uses DEF CON for the series and event but preserves DEFCON in source titles where that is the original title.
The catalogue preserves cross-year educational continuity without inventing a 2026 hardware revision, reissue, allocation, or relationship among distinct Payment Village artifacts.
The dossier records source-described creative framing without asserting ownership, franchise/religious or cultural affiliation, sponsorship, endorsement, authorship, or media-reuse authority.
The dossier records source-described creative framing without asserting ownership, franchise/religious or cultural affiliation, sponsorship, endorsement, authorship, or media-reuse authority.
The record preserves the badge as a real production artifact with mechanical and optical compromises rather than treating the enclosure as a frictionless visual shell.
The catalogue records a conservative youth-attendee identity artifact rather than an inferred electronic badge or a more specific physical credential unsupported by the source.
The record remains a conservative patron identity artifact rather than an inferred electronic badge or a more specific physical credential unsupported by the source.
Readers can distinguish the documented plastic admission artifact from the event's electronic ticket forms without treating it as a PCB, smart credential, scanner workflow, or final physical specimen.
The entry now has a real rights-cleared documentary photo with source URL, license, attribution, and processing notes instead of a generated, placeholder, or uncleared image.
The public badge page, image archive, and API point at a real public-domain badge photo with source URL, license, attribution, and processing notes preserved.
The entry can show a real badge/lanyard artifact while avoiding generated art, unclear conference-gallery imagery, or social-media copies.
The catalogue now shows a source-licensed official upstream render without copying the Uberflux gallery, project-page media, social imagery, a screenshot, placeholder, or synthetic approximation.
The entry now has a rights-cleared original documentary photo without using generated, placeholder, or uncleared event imagery.
The entry now has a real rights-cleared documentary photo without copying article media, Hackaday.io photos, screenshots, generated art, or placeholders.
The public badge page, image archive, and API point at a real physical participant-badge photo with source URL, license, attribution, and WebP processing notes preserved.
The record now has a rights-cleared official upstream raster render with source URL, CC BY-SA 4.0 component license, attribution, local source preservation, and optimized WebP delivery while keeping the wiki's unlicensed front/back photos unpublished.
The entry now has a rights-cleared original documentary photo while preserving the rule against copying Grand Idea Studio all-rights-reserved project-page images, press imagery, generated art, placeholders, or social-media scrapes.
The entry now has a real rights-cleared documentary-photo derivative while avoiding generated art, placeholder imagery, and reuse of the rights-limited official DEF CON media-server badge photo.
The entry has a real rights-cleared documentary photo without introducing generated, placeholder, or uncleared imagery.
The catalogue can show a real DEF CON 21 badge-case photo while preserving the full source original and avoiding WIRED, Hackaday, or writeup photos without complete provenance.
The entry can show a real badge photo while preserving the project rule against generated, placeholder, press, video-frame, or uncleared writeup imagery.
The entry now has a rights-cleared documentary video-frame derivative while continuing to avoid The Register, Hackaday, writeup, attendee, social-media, generated, and placeholder imagery.
The entry now has a rights-cleared documentary video-frame derivative without copying attendee photos, generated art, placeholders, or all-rights-reserved gallery media.
The record has a real source image, attribution, license basis, retained local source original, and optimized WebP delivery file rather than generated, placeholder, social-media, or screenshot imagery.
The catalogue can show a real DEF CON 20 badge image while preserving the full source original and avoiding Parallax forum images, WIRED gallery images, generated art, or uncleared archive photos.
The entry now has a real rights-cleared documentary-photo derivative with source URL, license, attribution, and processing notes instead of generated, placeholder, article, project-gallery, or social-media imagery.
The entry now has a real rights-cleared documentary photo without copying Grand Idea Studio's all-rights-reserved project-page images, generated art, or placeholders.
The original North American Vectorscope record now has a rights-cleared physical-badge image with source URL, license, attribution, and processing notes while avoiding generated or placeholder imagery.
The public badge page, image archive, and API now point at a real upstream badge photo with source URL, license, attribution, and processing notes preserved.
The public badge page, image archive, and API point at an original repository photo with source URL, license, attribution, and processing notes preserved.
The record now has a rights-cleared official upstream raster render with source URL, license, attribution, local source preservation, and optimized WebP delivery while avoiding generated, placeholder, social-media, or OSH Park preview imagery.
The record now has a rights-cleared official upstream render with source URL, license, attribution, source-original retention, and WebP processing notes while avoiding generated or placeholder imagery.
The record now has a rights-cleared official upstream raster render with source URL, license basis, attribution, local source preservation, and optimized WebP delivery while avoiding generated, placeholder, screenshot, or social-media imagery.
The public badge page, image archive, and API can show a real repository badge photo with source URL, license, attribution, local source preservation, and optimized WebP delivery rather than synthetic or unclear imagery.
The public badge page, image archive, and API point at a real upstream badge photo with source URL, license, attribution, and processing notes preserved.
The record has a rights-cleared official upstream raster render with source URL, license, attribution, local source preservation, and optimized WebP delivery while avoiding generated or placeholder imagery.
The record remains image-free until a rights-cleared original photo or official upstream raster is available.
The catalogue records the repository license while leaving the visual slot empty until a specific image can be cleared under the project image rules.
The project remains image-free rather than publishing board previews, vector artwork, Gerber renderings, screenshots, source graphics, synthetic imagery, or an approximate badge image.
The entry remains source-backed and image-free rather than copying blog, SparkFun, Hackaday, or event media without explicit reuse permission.
The record remains source-backed and image-free rather than copying article or build-guide media without a clear reuse basis.
The entry remains source-backed and image-free rather than copying documentation photos or archive media without complete provenance.
The record remains image-free rather than copying Hackaday.io media, social posts, repository-adjacent screenshots, article images, or generated artwork.
The entry remains image-free rather than copying official-page photos, manual screenshots, GitLab Pages media, or social images without complete provenance.
The record remains image-free rather than copying blog photos, OpenGraph images, videos, screenshots, repository diagrams, generated art, or approximate badge artwork.
The record remains image-free rather than copying event-page images, blog photos, repository images, social previews, screenshots, generated art, or approximate badge artwork.
The record remains image-free rather than copying Hackster project media, screenshots, OpenGraph images, generated art, or approximate badge artwork.
The entry remains source-backed and image-free rather than copying Cisco blog, archive, or event media without explicit reuse permission.
The record remains source-backed and image-free rather than copying first-hand blog or archive images without explicit reuse permission.
The record avoids overstating final attendee software behavior beyond public sources.
Readers can see the intended collaborative game context without assuming that proximity effects, wireless behavior, data use, safety, or onsite logistics were implemented, authorized, or suitable for every participant.
The record documents an organizer-advertised identity artifact at a completed event rather than claiming individual issuance, successful admission use, or universal attendee fulfillment.
The listed source remains useful as a development snapshot while users are warned not to infer functional infrared/game behavior, safe operation, data handling, or a supported release.
The catalogue classifies the artifact as an independent contest-linked Simple Add-On rather than an official conference credential, access substitute, or confirmed universal contest prize.
The catalogue classifies it as an independent BadgeLife record rather than an official DEF CON Human badge or a substitute for conference registration.
The record is connected to DEF CON 34 for BadgeLife discovery while remaining distinct from the official Human badge and any general-attendee allocation.
The record remains a separately organized BadgeLife fundraiser linked to DEF CON 34 discovery, distinct from the official Human badge and from unverified allocation claims.
The dossier treats the Portal Badge as an independently sourced DC34 maker/project, not an official DEF CON credential or a substitute for registration.
The dossier preserves a completed event-associated electronic artifact without treating it as an official DEF CON Human badge, village credential, general attendee entitlement, or proof that any specific person received a unit.
The catalogue records a real independent maker-announced SAO while avoiding an official credential claim or an inference of artistic/trademark authorization.
The catalogue tracks a public independent event association without presenting the SAO as official conference hardware, an access credential, a registration benefit, a sanctioned village item, or proof of organizer endorsement.
The catalogue classifies the canary as an independent pre-event BadgeLife artifact associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or completed official distribution.
The catalogue tracks a public independent event association without presenting a maker sale as official conference hardware, a registration benefit, an access credential, an organizer endorsement, or a completed vendor commitment.
The catalogue classifies the Zombie Badge as an independent pre-event project associated with DEF CON 34, not an official conference credential, organizer-issued badge, admission item, or verified event activity.
The catalogue classifies Ouroboros as an independent BadgeLife offering tied to maker intent, not an official conference credential, organizer-issued badge, or access item.
The catalogue classifies this as an independently documented pre-event project associated with DEF CON 34, not an official conference credential, organizer-issued badge, attendee entitlement, or verified event activity.
The catalogue classifies the combo as an independent badge with a DEF CON 33 vendor-list association, not as an organizer-issued conference credential, admission item, or scheduled BadgeLife drop.
The catalogue classifies Vibe Coder Dog as an independent community SAO rather than an official conference credential, organizer-issued badge, or access item.
The record preserves a real independent BadgeLife event association without presenting Breadbadge as an official DEF CON credential or access item.
The catalogue classifies Wordweaving as an independent BadgeLife project associated with DEF CON 34, not an official conference credential, admission item, organizer-issued badge, or confirmed authorized sales presence.
The catalogue connects this independent maker artifact to its cited DEF CON 34 discovery/pickup context without presenting it as official conference hardware, an access item, a universal attendee benefit, or a completed organizer distribution.
The catalogue tracks a public independent event association without presenting a maker sale as official conference hardware, a registration benefit, an access credential, organizer endorsement, or a completed sales relationship.
The catalogue classifies HackThePlanet as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
The catalogue keeps the target relationship searchable while classifying this as independent BadgeLife hardware rather than official conference hardware, an access credential, a universal attendee item, or evidence of organizer endorsement.
The catalogue classifies Dante's Inferno as an independent badge tied to public DEF CON market contexts, not as an organizer-issued conference credential, admission item, or universal attendee handout.
The catalogue records a public independent event association without portraying the SAO as official conference hardware, a registration benefit, an access credential, a sanctioned village artifact, or proof of organizer endorsement.
The record retains a documented maker, public-project, and village association without presenting Agency Wand as DEF CON's official badge or an access credential.
The catalogue classifies FightDystopia as an independent BadgeLife artifact associated with DEF CON 33, not as an organizer-issued conference credential or admission item.
The catalogue classifies METROPOLIS AI SAO as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
The catalogue records a source-backed independent event association without presenting v2 as official conference hardware, an access item, a universal attendee benefit, or confirmed organizer distribution.
The catalogue records a source-backed independent event association without portraying the holder as official conference hardware, an admission credential, a universal attendee benefit, or confirmed organizer distribution.
The catalogue records a source-backed independent event association without portraying the holder as official conference hardware, an admission credential, a universal attendee benefit, or confirmed organizer distribution.
The catalogue classifies Root Access as an independent pre-event Simple Add-On associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
The catalogue records a real independent badge/event association without turning it into an official conference credential, organizer-issued hardware, access item, or universal attendee handout.
The catalogue classifies MalO as an independent pre-event Simple Add-On associated with DEF CON 34, not an official conference credential, organizer-issued badge, or access item.
The catalogue records a source-backed independent event association without presenting v1 as official conference hardware, an access item, a universal attendee benefit, or confirmed organizer distribution.
The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or a completed official distribution.
The catalogue classifies Luna as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
The catalogue classifies it as an independent commemoration associated with DEF CON 34 rather than an official conference credential, admission item, or organizer-issued product.
The catalogue presents a real independent event-associated badge offer without misclassifying it as an official conference credential, organizer product, admission item, or verified vendor-booth activity.
The catalogue classifies Masonic33 as an independent BadgeLife artifact associated with DEF CON 33, not as an organizer-issued conference credential, admission item, or universal attendee handout.
The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or completed official distribution.
The catalogue classifies SAO Many SAOs as an independent maker badge, not an official conference credential, organizer-issued item, or admission token.
The catalogue classifies the moth as an independent pre-event BadgeLife artifact associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
The catalogue classifies #NOICE as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
The catalogue classifies Submarine as an independent BadgeLife artifact associated with DEF CON 33, not as an organizer-issued conference credential or admission item.
The catalogue classifies the Firefly Jar as an independent pre-event BadgeLife artifact associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
The catalogue preserves the source's current event association and distinct project name without presenting it as an official DEF CON badge, an RM-Cyber-issued artifact, a guaranteed attendee benefit, an access credential, a completed release, or proof that any participant received one.
The catalogue records a documented independent physical DEF CON 34-associated maker badge, not an official DEF CON artifact, organizer-issued silent-disco credential, guaranteed attendee benefit, access pass, or completed conference distribution.
The record retains a source-backed completed independent event association without representing the add-on as an official Human badge, a conference credential, a ticket benefit, or an audited distribution run.
The catalogue records a real maker-announced DEF CON-associated BadgeLife artifact without representing it as an official Human badge, conference credential, completed transaction, or guaranteed handoff.
The catalogue classifies the artifact as a planned independent DC34-associated badge kit rather than an official DEF CON badge, a company-issued item, an authorized event activation, an access credential, or a completed distribution.
The catalogue records a named, technically documented independent project without presenting it as an official DEF CON badge, an attendee entitlement, a credential, a completed physical run, or proof that any participant received one.
The catalogue preserves the documented independent DEF CON 33 association without treating a maker listing or sold-out indicator as organizer issuance, a completed conference handoff, conference admission, or a universal attendee benefit.
The catalogue classifies this as an independent planned project associated with the event context, not an HRV-issued or DEF CON-issued badge, a guaranteed attendee benefit, a venue-authorized activation, a Human badge, an access credential, or proof that anyone received a physical unit.
The catalogue records the organizer's exact public relationship and benefit statements without presenting independent organizers as EFF staff, claiming an EFF retail product, or inferring unannounced donation details.
The record is connected to DEF CON 34 for BadgeLife discovery while remaining distinct from the official Human badge and from unverified role/allocation claims.
The record can sit under the DEF CON 34 event without confusing the independent BadgeLife project with the official conference-access badge.
The catalogue models a real Puzzled Hackers community badge associated with DEF CON 34 while keeping it distinct from official admission, organizer issuance, and verified event access.
The catalogue treats this as an independent themed badge, not a transit artifact, fare instrument, official DEF CON credential, admission item, or sponsored product.
The catalogue credits the named organization without assigning individual authorship, manufacturing responsibility, artwork ownership, or fulfillment responsibility from unexplained repository provenance.
The catalogue credits only the named event organization, source publisher, and attendee report without inferring individual design, production, distribution, branding, or image-use roles.
The dossier credits only the named organization and narrowly evidenced source contributions without inferring authorship, manufacturing responsibility, distribution control, or image permission.
The catalogue credits only named, source-supported roles without inferring sole authorship, production responsibility, distribution control, trademark authority, or image permission.
The catalogue separates shipped badge behavior from optional kit upgrades and does not imply that every attendee badge was fully populated as an Ubertooth.
The catalogue cites the source trail and technical claims but does not republish badge artwork, logo material, or repository imagery as a hero image.
The badge remains image-free and the code is linked as evidence rather than treated as a license grant, image-reuse permission, or complete open-hardware release.
The project is cited for artifact facts and fabrication context, but image and artwork reuse is withheld pending explicit license or permission evidence.
The catalogue may link the source archive and license while maintaining the separate image-rights threshold for any future local badge asset.
The record cites code and hardware sources but does not reuse repository artwork or social/event imagery as a hero image.
The catalogue cites the source archive but does not copy its badge photo, board images, code, fabrication files, artwork, logos, trademarks, screenshots, or a generated approximation.
The repository is used as evidence for badge facts, but no repository image or media asset is promoted into the public image archive.
The compendium keeps the US Supercon record separate while preserving the Serbian Belgrade design lineage and firmware evolution.
The compendium keeps the US Pasadena record separate while preserving the Serbian Belgrade design lineage and shared firmware roots.
The compendium keeps separate records for the US origin event and the Berlin reuse so country and event-history pages remain accurate.
This record covers the BSidesPDX 2018 conference badge archive in `badge-2018`; the DC503 Banglet is modeled separately as its own DEF CON-adjacent party-badge lineage record.
The record keeps the organizer-published challenge framing discoverable without assuring a particular technical experience, safe data practice, fair scoring, accessibility, availability, or a final public result.
The catalogue cites the original source URL and corroborates event and technical details through InfoconDB and GitHub while leaving full article archive recovery for a later pass.
The catalogue avoids inventing material, role, visual, puzzle, or electronic claims for the official DEF CON 12 badge until stronger public sources are recovered.
The dossier records direct maker claims while withholding a reproducible architecture, complete evidence trail, or independent technical corroboration.
The catalogue can cite the corroborating project-name trail without stating that u/ProfessionalPea2218 controls Cyb3rBytes404 on GitHub, authored all code, or holds any formal nonprofit, DEF CON, or media-rights role.
The catalogue preserves the primary assembly warning without presenting the project as beginner-friendly, reliably hand-buildable, safe to assemble, or proven across a finished production run.
Readers can find the direct maker claim without treating its quantity as an independently audited manufacturing total, a promise to a particular attendee, a distribution ledger, or proof that the event handoff occurred.
The catalogue records seller-provided state as date-sensitive availability context rather than merging prices, stock, and planned drops into a single proven distribution history.
The badge is recorded as an event artifact and AI interaction surface, not as a trusted medical device or medical-advice system.
Readers can identify a real electronic holder without treating it as universally interchangeable, electrically safe, mechanically compatible, or ready to use with every minibadge.
Readers can identify a real electronic holder without treating it as universally interchangeable, electrically safe, mechanically compatible, or ready to use with every minibadge.
Users should not infer standard-SAO compatibility or attempt undocumented rewiring/modification from the badge's intended connector footprint.
The record remains image-free rather than copying page media, archived media, or generating an approximation.
The entry remains source-backed and image-free rather than copying article photography without a clear catalogue reuse basis.
The record remains image-free rather than copying page media or generating a replacement.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying event-site artwork, LinkedIn images, repository previews, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States entry remains source-backed and image-free rather than copying repository files, Reddit media, store media, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying public photos or using generated placeholder imagery.
The entry remains source-backed and image-free rather than copying public photos without a complete image provenance record.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying marketplace photos, GitHub/Bluesky media, social previews, screenshots, placeholders, or generated approximations.
The current badge record remains image-free until a rights-cleared original photo or official raster render can be proven.
The Louisiana record remains source-backed and image-free rather than copying event media, social-media photos, ticketing graphics, screenshots, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying official page graphics, store imagery, repository screenshots, or generated imagery without complete provenance.
The entry remains source-backed and image-free rather than copying board files, sponsor logos, event-page imagery, social photos, screenshots, or generated visuals.
The planned record remains source-backed and image-free rather than copying event graphics, teaser media, or social content without complete provenance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying official page images, schematic screenshots, social posts, conference media, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying site artwork, repository renders, generated-looking imagery, ticketing media, social photos, or screenshots.
The record remains image-free rather than copying article media.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying Shopify photos/video frames, the Reddit preview, social-media material, screenshots, placeholders, or generated approximations.
The completed Maine record remains source-backed and image-free rather than copying social-media reveal media, event graphics, screenshots, or generated approximations.
The entry remains source-backed and image-free rather than copying blog or event imagery without a clear catalogue reuse basis.
The record remains image-free rather than publishing uncleared or synthetic visuals.
The record remains source-backed and image-free rather than copying site media, repository screenshots, renders, social-media photos, or generated replacements.
The Chicago record remains source-backed and image-free rather than copying event media, board screenshots, GitHub previews, social images, generated approximations, or an unclear-rights upstream raster.
The record remains source-backed and image-free rather than copying event graphics, ticket artwork, or social-media imagery without complete provenance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The current United States record remains source-backed and image-free rather than copying maker-site images, Reddit images, repository previews, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying the maker listing image, rendered revision imagery, Reddit media, screenshots, social posts, placeholders, or generated approximations.
The entry remains source-linked and image-free rather than copying project-page, press, or article images without complete rights clearance.
The record remains source-backed and image-free rather than copying repository PNGs, event photos, screenshots, or generated images.
The record remains source-backed and image-free rather than copying project images, article photos, screenshots, generated art, placeholders, or uncleared media.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains image-free until an explicitly reusable original photo or official raster render is recovered.
The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository WebP/PNG/SVG assets, KiCad/schematic renders, acrylic previews, screenshots, placeholders, or generated imagery.
The record remains source-backed and image-free rather than copying page media, documentation screenshots, article photos, social posts, or generated imagery.
The record remains source-backed and image-free rather than copying marketplace photos, video frames, social previews, screenshots, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying Reddit photos, previews, screenshots, social-media media, placeholders, or generated approximations.
The unofficial badge entry remains source-backed and image-free rather than copying article or project images without a clear reuse basis.
The entry remains source-backed and image-free rather than copying ticketing media, site artwork, social photos, screenshots, or generated media.
The record remains source-backed and image-free rather than copying repository photos, board graphics, event media, screenshots, logos, or generated/approximate imagery.
The record remains source-backed and image-free rather than copying storefront photos, Reddit media, GitHub PNG/PDF material, screenshots, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying repository screenshots, event-page images, social photos, product photos, or generated visuals.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than publishing generated renderings, SVG/PDF conversions, or uncleared project-page media.
The United States record remains source-backed and image-free rather than copying ticket-site images, conference media, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying Reddit media, repository graphics, code screenshots, social posts, thumbnails, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying vendor PDF, maker-guide, storefront, social-media, screenshot, placeholder, or generated imagery.
The record remains source-backed and image-free rather than copying Reddit media, previews, screenshots, social posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying repository, OSHWA, village, social-media, or attendee imagery without complete provenance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record stays source-backed and image-free rather than copying public photos or using generated placeholder imagery.
The record remains source-backed and image-free rather than copying the checkout photo, Reddit media, screenshots, social posts, thumbnails, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying event-page, schedule, social, or gallery media without explicit reuse rights.
The entry remains source-backed and image-free rather than copying marketplace media, screenshots, social posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying official event-page, wrap-up, or Hardware Hacking Village media without complete reuse rights.
The record remains image-free rather than copying event media or generated replacements.
The entry remains source-backed and image-free rather than copying logo, event-site, attendee, or social imagery without a clear catalogue reuse basis.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying public Hackaday media, Hackaday.io project media, or repository images without a complete image provenance record.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record stays image-free rather than using uncleared activity photos or schematic screenshots.
The record remains source-backed and image-free rather than copying maker renders/photos, game screenshots, marketplace images, social-media media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying repository sprites, image assets, social photos, generated art, screenshots, or placeholder visuals.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The virtual-event badge record stays source-backed and image-free.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free under the project image policy.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying official-page images, repository previews, article photos, or screenshots without complete provenance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying event-page graphics, sponsor avatars, social photos, or screenshots.
The record remains source-backed and image-free rather than copying project photos, CircuitPython board artwork, embedded video, form images, screenshots, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying repository screenshots, event-page images, social photos, article media, generated art, or placeholder visuals.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The planned record remains source-backed and image-free rather than copying marketplace photos, repository media, video frames, social previews, screenshots, placeholders, or generated approximations.
The entry remains image-free rather than using event-page graphics, screenshots, social-media photos, generated imagery, or placeholders.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record intentionally publishes no image rather than copying ticketing artwork, event graphics, screenshots, social media, a placeholder, or a generated approximation.
The pre-event record remains source-backed and image-free instead of copying Eventbrite media, screenshots, social-media photos, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The planned record remains source-backed and image-free rather than copying Reddit previews, roster-linked media, screenshots, placeholders, or generated imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry stays image-free rather than copying official news/support graphics, ticket media, media-server diagrams, social-media or press previews, repository screenshots, or generated badge art.
The record remains source-backed and image-free rather than copying marketplace photos, video previews, screenshots, social media, placeholders, or generated approximations.
The record remains image-free rather than copying repository graphics or generating a replacement.
The record remains source-backed and image-free rather than copying repository previews, GitHub user-attachment images, screenshots, social-media media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying repository PNGs, website gallery files, screenshots, or generated media.
The event badge remains image-free rather than publishing a branded repository render or any other visual without complete source URL, license or permission basis, attribution, and processing provenance.
The record remains source-backed and image-free rather than copying blog media, logos, screenshots, schematic snippets, generated art, or approximate badge imagery.
The record remains image-free rather than copying repository graphics or generating an approximation.
The entry remains source-backed and image-free rather than copying blog photos, screenshots, social media, or generated media.
The entry remains source-backed and image-free rather than copying blog, conference, video-thumbnail, or repository imagery without a clear license.
The pre-event record remains source-backed and image-free rather than copying PCB screenshots, vector artwork, GitHub previews, event graphics, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying blog photos, social media, screenshots, or generated media.
The source-backed record remains image-free rather than copying storefront/gallery media, raw GitHub images, launch-video frames, social posts, screenshots, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying storefront, repository, release, vendor-PDF, social-media, screenshot, placeholder, or generated imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The entry remains source-backed and image-free rather than copying official site media, screenshots, social photos, event graphics, generated art, or placeholders.
The pre-event record remains source-backed and image-free instead of copying storefront media, social posts, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying roster media, GitHub user-attachment images, Gerber previews, screenshots, social-media posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying article media, site-optimized photos, screenshots, generated art, or other unclear imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The pre-event record remains source-backed and image-free instead of copying marketplace photos, thumbnails, screenshots, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying official-page images, Hackaday CDN photos, video frames, or prototype screenshots without complete provenance.
The record remains image-free rather than copying article photos, wiki media, screenshots, or generated replacements.
The entry remains source-backed and image-free rather than copying project-page media or rendering KiCad files into approximate badge art.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying workshop media, repository board images, screenshots, or generated imagery without complete provenance.
The record remains source-backed and image-free rather than copying official page media, PDF imagery, screenshots, social-media images, or generated approximations without complete provenance.
The record stays source-backed and image-free rather than copying old forum, gallery, or template media without complete rights clearance.
The record remains image-free.
The pre-event record remains source-backed and image-free instead of copying marketplace imagery, screenshots, social-media media, placeholders, or generated approximations.
The planned record stays image-free rather than reusing PN26 article photos, generated art, screenshots, or speculative visuals.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying event media, repository previews, social-media images, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying storefront, schedule, social-media, screenshot, placeholder, or generated imagery.
The record remains source-backed and image-free rather than copying marketplace art, product media, screenshots, social posts, placeholders, or generated approximations.
The current record remains source-backed and image-free rather than copying Shopify product photos, roster-linked media, screenshots, social posts, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The electronic-badge record remains source-backed and image-free rather than copying event graphics, LinkedIn media, ticket artwork, or screenshots without complete provenance.
The current record remains source-backed and image-free rather than copying Shopify product photos, repository images, KiCad previews, screenshots, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying article or project-gallery photography without a clear catalogue reuse basis.
The record remains source-backed and image-free rather than copying article/project images, screenshots, video frames, generated art, placeholders, or uncleared media.
The entry remains source-backed and image-free rather than reusing generated, teaser, attachment, screenshot, or undocumented badge imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The current record remains source-backed and image-free rather than copying Shopify product photos, repository images, KiCad previews, screenshots, social media, placeholders, or generated approximations.
The entry remains image-free rather than copying Hackaday or personal writeup photography without provenance.
The entry remains source-backed and image-free rather than copying official site imagery, screenshots, social media, or generated visuals.
The record remains source-backed and image-free rather than copying the repository photo, social-media media, GitHub previews, logos, screenshots, or generated/approximate badge imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The United States record remains source-backed and image-free rather than copying event media, ticket graphics, screenshots, social-media photos, placeholders, or generated approximations.
The record remains image-free rather than copying article media.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The entry remains image-free rather than copying official preview images, vendor art, or attendee photography without complete provenance.
The record remains source-backed and image-free rather than copying listing photographs, repository images, screenshots, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The pre-event record remains source-backed and image-free rather than copying marketplace artwork, externally hosted README media, CAD screenshots, user attachments, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying the bee artwork, repository screenshots, social photos, generated art, or placeholder visuals.
The entry remains source-backed and image-free rather than copying event-page, social, wiki, or generated media without explicit reuse rights.
The United States pre-event record remains source-backed and image-free rather than copying shop imagery, GitHub media, social posts, screenshots, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying marketplace photos, repository previews, contest media, screenshots, social posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The record remains source-backed and image-free rather than copying event media, repository photos or renders, screenshots, social-media images, or generated visuals.
The entry remains source-backed and image-free rather than copying social photos, event media, repository artwork, screenshots, logos, or generated imagery.
The record remains source-backed and image-free rather than copying article, project, or fabrication-preview media without complete image provenance.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The 2026 record remains source-backed and image-free rather than copying store photos, repository previews, self-submission media, screenshots, placeholders, or generated imagery.
The United States record remains source-backed and image-free rather than copying repository diagrams, screenshots, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record uses firmware evidence but leaves the visual slot empty.
SR-71 remains image-free rather than copying roster media, event graphics, social posts, screenshots, stock imagery, or generated approximations.
The North Carolina dossier remains source-backed and image-free rather than copying official page graphics, social-media images, attendee photos, screenshots, event branding, or generated approximations.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The record remains source-backed and image-free rather than publishing generated, placeholder, screenshot, repository-cache, or uncleared page imagery.
The record remains image-free rather than copying repository media, code screenshots, event graphics, social posts, renders, placeholders, or generated approximations.
The pre-event record remains source-backed and image-free instead of copying storefront media, screenshots, social-media posts, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying maker-page, storefront, social-media, screenshot, placeholder, or generated imagery.
The record remains image-free.
The record remains source-backed and image-free rather than copying product art, project renders, prototype photos, screenshots, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The current fundraiser and its technical lineage remain source-backed and image-free instead of copying event-listing photos, documentation screenshots, repository media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying Army article media, event photos, social posts, screenshots, or generated visuals.
The record stays source-backed and image-free rather than copying product photos, forum images, social-media previews, or generated artwork.
The entry remains source-backed and image-free rather than copying event-page images, board files, repository artwork, social photos, screenshots, or generated visuals.
The entry remains source-backed and image-free rather than copying proceedings, attendee-report, or Hackaday.io project imagery without a clear catalogue reuse basis.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains image-free rather than copying source-site photos or diagrams.
The record remains source-backed and image-free rather than copying blog art, firmware-page imagery, screenshots, social photos, or generated approximations.
The Hack-Master record stays image-free under the no-generated/no-placeholder image policy.
The record stays image-free rather than copying schedule, social, gallery, or generated media.
The planned 2026 record remains source-backed and image-free rather than copying village media, roster-linked social material, screenshots, placeholders, or generated imagery.
The entry remains source-backed and image-free rather than copying the official page image, Army event photos, screenshots, social media, or generated visuals.
The current record remains source-backed and image-free rather than copying Shopify product photos, roster-linked media, screenshots, social posts, placeholders, or generated approximations.
The entry remains image-free rather than copying attendee or press photography without provenance.
The pre-event record remains source-backed and image-free instead of copying store photos, repository embeds, Imgur media, screenshots, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying board files, event-page imagery, social photos, screenshots, or generated visuals.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The entry remains source-backed and image-free rather than copying logos, board-art files, event-page imagery, screenshots, or generated visuals.
The record remains source-backed and image-free rather than copying the repository photo, README graphic, Reddit media, schematic preview, event graphics, screenshots, placeholders, or generated approximations.
The record stays source-backed and image-free rather than copying product photos, GitHub user-attachment images, social-media previews, screenshots, or generated artwork.
The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository PNGs/previews, schematics, screenshots, placeholders, or generated imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The United States record remains source-backed and image-free rather than copying event media, repository previews, social-media photos, screenshots, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying marketplace product media, screenshots, social posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying Shopify product photos, PCB/back images, gong/Aaron media, screenshots, social posts, placeholders, or generated approximations.
The record remains image-free.
The entry remains source-backed and image-free rather than copying board files, logos, event-page imagery, social photos, screenshots, or generated visuals.
The entry remains source-backed and image-free rather than copying gallery, board-output, screenshot, social, or generated media.
The record remains image-free rather than copying repository, event, or article media.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying Reddit media, previews, screenshots, social posts, thumbnails, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying storefront, schedule, vendor-PDF, social-media, screenshot, placeholder, or generated imagery.
The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository previews, KiCad/schematic renders, spacer-model previews, screenshots, placeholders, or generated imagery.
The entry remains image-free rather than copying official, press, or community photography without provenance.
The entry remains source-backed and image-free rather than copying repository screenshots or photos without complete catalogue provenance.
The entry remains image-free rather than copying press, forum, or personal writeup photography without provenance.
The record remains source-backed and image-free rather than copying official site media, screenshots, social posts, or generated imagery.
The record remains source-backed and image-free rather than copying storefront photos, repository JPG files, SVG sheets, screenshots, social media, placeholders, or generated imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The source-backed pre-event record remains image-free instead of copying repository previews, board exports, screenshot-like documentation material, Portal-themed art, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying repository photos excluded from the MIT license, screenshots, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying article or video imagery without a clear catalogue reuse basis.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The entry remains image-free rather than copying attendee, press, forum, or GitHub-hosted challenge photography without provenance.
The record remains image-free rather than copying page media or generating an approximation.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The record stays source-backed and image-free rather than copying social, article, video-frame, generated, placeholder, or uncleared media.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying the maker listing image, prototype/renders, Reddit media, screenshots, social posts, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying official page imagery, screenshots, social media, or generated visuals.
The record remains source-backed and image-free rather than copying marketplace photographs, promotional graphics, screenshots, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying project-page WebP photos without complete rights clearance.
The record remains image-free rather than copying source-labelled generated product art, social media, storefront screenshots, party graphics, placeholders, or synthetic approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying event graphics, page images, social photos, screenshots, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains image-free rather than copying creator, official, attendee, or press photography without provenance.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains image-free rather than copying Hackaday article photos, Hackaday.io images, or repository assets without a complete image provenance record.
The Tennessee record remains source-backed and image-free rather than copying event graphics, organizer-feed media, attendee photos, screenshots, storefront imagery, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying project-gallery or event media without explicit reuse rights.
The entry remains source-backed and image-free rather than copying maker-page, storefront, social-media, screenshot, placeholder, or generated imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying the maker listing image, prototype/renders, Reddit media, screenshots, social posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying product photos, site graphics, forum media, screenshots, or generated imagery without complete provenance.
The United States pre-event record remains source-backed and image-free rather than copying site imagery, social-media media, screenshots, placeholders, or generated approximations.
The entry remains source-backed and image-free rather than copying project-gallery imagery without a clear catalogue reuse basis.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains image-free rather than copying Hackaday article images or repository photos without a complete image provenance record.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The planned record remains source-backed and image-free rather than copying repository photos, README media, renders, screenshots, third-party posts, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying event graphics, social media, ticketing images, screenshots, placeholders, or generated approximations.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying product photos, repository asset images, PCB previews, screenshots, placeholders, or generated approximations.
The record remains source-backed and image-free rather than copying Eventbrite media, GitHub previews, repository logos, README assets, STL screenshots, schematics, generated art, or approximate badge imagery.
The record remains source-backed and image-free rather than copying DEF CON archive photography without complete rights clearance.
The record uses WemOS only as the source-backed board family reference and avoids pinout, controller, or firmware-specific claims.
The badge is modeled as a soldering and analog electronics badge rather than a programmable badgelife platform.
The record links to upstream files while leaving the hero image empty and avoiding local copies of sprites or image assets.
The catalogue records the stated no-MCU and QR-search feature without inventing firmware, treating the QR as an audited or privacy-neutral service, claiming an open design, or promising product support.
The catalogue models the badge as analog electronic hardware and does not infer firmware or software challenges.
The record treats this as an analog electronic badge and does not invent firmware, app, or hidden-code behavior.
The dossier models a real disclosed identity artifact without upgrading it into an electronic badge or inventing attributes of a paper credential.
The catalogue records the real event-specific coin without inventing its construction, appearance, value, access function, or technical behavior.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The catalogue preserves the major BSides Las Vegas badge lineage as an identity/access artifact without inventing electronics.
The compendium preserves the early physical credential without upgrading it into a circuit-board badge.
The catalogue records the badge challenge and physical identity artifact without inventing hardware.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The compendium preserves the first DEF CON credential artifacts without upgrading them into circuit-board badges.
The compendium preserves the pre-electronic artifact without inventing LEDs, firmware, microcontrollers, or a badge challenge for 2005.
The compendium models the badge as a PCB identity and puzzle artifact and avoids firmware, MCU, LED, or battery claims for the standard badge.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The catalogue avoids MCU, firmware, LED, battery, and circuit claims for 2011 while still preserving the badge's physical fabrication and puzzle significance.
The catalogue records the current participant credential as an identity/access artifact without inventing technical behavior or construction.
The compendium avoids adding imaginary hardware to a year whose badge significance is partly the contrast with unofficial electronic badgelife.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The compendium preserves the early conference credential without upgrading it into a circuit-board badge.
The compendium preserves the early physical credential without upgrading it into a circuit-board badge.
The catalogue can publish the selected image as a credited noncommercial reference asset, but downstream reuse should preserve the noncommercial restriction and attribution.
The catalogue records a real HTH 2026 electronic-badge source trail without claiming an organizer-owned repository, a formal event endorsement, or universal official issuance from affiliation alone.
The catalogue records a real event badge and public source trail without turning a convergent designer/attendee archive into an organizer-owned project or general credential claim.
The catalogue keeps the official-badge wording tied to the cited log and avoids claiming complete production ownership, final challenge rules, or released design files.
The catalogue records a real sold-out online offer without converting it into a complete production or fulfillment report.
The catalogue records the public open-hardware path while avoiding stronger claims about every production file until a deeper repository audit is done.
The catalogue can document the real e-badge offer without saying anyone purchased, received, used, or was universally issued the artifact.
The record separates the documented board capability surface from any claim that every workshop board shipped with every optional component populated.
The catalogue treats this as an independently documented event-associated badge, not an official DEF CON 32 attendee badge, credential, universal handout, completed distribution, or organizer-endorsed artifact.
The catalogue distinguishes attributed post-event device evidence from official organizer confirmation and does not promote the badge into an attendee-wide entitlement or a Workday-published hardware release.
The catalogue models a real maker-declared event-associated challenge artifact rather than presenting it as organizer-issued, attendee-wide, admission-bearing, or independently confirmed electronic hardware.
The record remains image-free rather than copying page media, repository assets, screenshots, social photos, or generated approximations without complete provenance.
The record is kept as a source-backed badge archive without overstating shipped attendee distribution.
The record preserves the competition hook without overstating the completeness of the recovered challenge material.
The catalogue records a DEF CON-adjacent independent party badge rather than representing it as conference registration, an official convention credential, or a substitute for a valid DEF CON badge.
The catalogue models the artifact as a DC503 party badge and keeps it separate from DEF CON, BSidesPDX, and later DC503 Banglet/5ohBEE lineages.
The catalogue models 5ohBEE as a DC503 party pager and game artifact while keeping official conference badge lineages separate.
The catalogue preserves a real organizer-published 2026 patron artifact statement without converting it into proof that every patron, or any particular patron, received a badge.
The compendium keeps the badge-history record separate from any operational payment-system use.
The record does not invent a PCB, microcontroller, firmware, lanyard, RFID/NFC, app, radio, or other device properties from the word badge alone.
The entry records a narrow source-backed electronic challenge-device outline without treating it as a reproducible build, a safe assembly guide, a uniform physical badge, or a completed production run.
The record does not turn a BadgeLife title, fundraiser context, or pickup plan into an electronic-badge claim, engineering specification, software feature list, or reusable technical archive.
The catalogue records the actual firmware trail without treating source pins or library use as a finished, safe, fabricated, standard-compliant, or plug-and-play add-on.
The catalogue retains a concrete design-file trail without representing it as a fabricated, tested, safe, standards-compliant, or plug-and-play accessory.
Readers can discover the exact source project and its limited publisher-reported hardware work without mistaking either for a completed, compatible, safe, manufactured, or distributed event artifact.
The data model preserves the ticket as an identity artifact and prevents an unsupported claim that HOPE 26 had an electronic or physical conference badge.
The catalogue records verified badge lineage and customization surfaces while leaving full physical artifact documentation for a later pass.
The catalogue records verified badge lineage and interaction surfaces while leaving full artifact photography and challenge reconstruction for a later pass.
The record does not infer an electronic PCB, active reader, passive tag, NFC chip model, radio placement, power budget, safety profile, or interoperability from high-level game wording.
The catalogue keeps the current entry factual and image-free until a source-backed artifact record and any necessary rights information are available.
The record remains a planned identity artifact rather than an inferred electronic badge, a specific physical credential, or a manufactured technical product.
The record preserves a concrete pre-event acquisition statement without treating it as a finished distribution, retail outcome, or attendee entitlement.
The catalogue records a real planned artifact system without representing it as manufactured, acquired, delivered, stocked, or experienced by a confirmed attendee population.
The record stays an identity artifact with a documented marking workflow rather than an inferred electronic badge or a more specific physical credential unsupported by the official wording.
The catalogue records the announced limited-run and philanthropic path without treating it as a completed sale, charitable outcome, manufactured quantity, or delivery report.
The record is deliberately modeled as a planned staff identity artifact rather than an electronic badge or a more specific physical credential unsupported by the organizer's public wording.
The catalogue records a concrete pre-event maker announcement without presenting it as a completed DEF CON sale, a guaranteed preorder, or an attendee entitlement.
Public design files are preserved as evidence of a planned artifact without being presented as proof of a fabricated, functioning, final, distributed, or event-deployed badge.
The catalogue can treat the official electronic Human badge as completed without implying that every registration produced the same physical unit, that every holder received or retained one, or that a public source proves a complete manufacturing and fulfillment record.
The entry remains image-free and keeps app-source licensing separate from badge, event, and media rights.
This remains an official advertised ticket-tier artifact record with a bounded community post-event signal, not a claim that every buyer received a particular board, that owl badges map to a specific tier, that tiers were technically distinct, or that fulfillment succeeded.
The catalogue preserves a documented hardware project and host tooling without converting a lapsed schedule into a fulfilled-badge, completed-CTF, or delivery claim.
The entry distinguishes a corroborated reported build from a comprehensive post-event technical, manufacturing, fulfillment, or image-provenance record.
The record preserves operational and add-on-design constraints rather than presenting the badge as a frictionless reference platform.
No power, interface, expansion, battery-life, electrical-safety, or universal peripheral-compatibility claim is inferred from source footprints and exploratory board text.
Public firmware behavior is not a battery-runtime guarantee, electrical-safety endorsement, factory-pass record, motion-accuracy claim, or safe-modification instruction.
The record does not convert a component/design narrative into a safety endorsement, universal host-power guarantee, electrical specification, or modification instruction.
The catalogue records a source-backed sold-out pre-event offer without changing sales counters into a completed fulfillment report.
The catalogue records announced game and logistics context, not a completed physical run, completed server activation, delivered firmware, or observed attendee experience.
The catalogue records the specific public 100-badge pre-event plan while treating the artifact as a distinct FirstBuild / GE Appliances project associated with DEF CON 34, not an official Human badge, universal attendee entitlement, registration credential, organizer-issued artifact, confirmed event availability, or completed distribution.
The catalogue records a real event-specific pre-event artifact without presenting it as an official DEF CON Human badge, a universal attendee benefit, a credential with known access behavior, or a completed handoff.
The record can preserve a concrete pre-event artifact claim without presenting planning language or an event-completion report as proof of universal delivery or a final production configuration.
The catalogue preserves a concrete event-associated BadgeLife listing without converting public self-description into organizer issuance, corporate endorsement, credential authority, or a completed distribution claim.
The catalogue records a currently evidenced independent project and announced pickup path, not a confirmed delivered run, attendance-wide issue, final recipient count, or post-event game outcome.
The catalogue records announced badge availability, not delivered hardware, a universal attendee allocation, or observed event use.
Station 562 is modelled as an independent pre-event BadgeLife project associated with DEF CON 34, not an organizer-issued Human badge, admission item, universal attendee benefit, or confirmed on-floor distribution.
The catalogue records a real public project without portraying it as a completed physical distribution, a universally available SAO, a confirmed sale/giveaway, or a completed DEF CON handoff.
Readers can distinguish an active maker listing and planned timeframes from a completed DEF CON distribution or a finished production report.
The catalogue can preserve the limited PCB badge announcement while keeping final distribution and field behavior open for a post-event source pass.
The catalogue can track the announced lineage while keeping all final hardware, software, distribution, and production claims open until post-event sources appear.
The catalogue preserves a real current offer without claiming a completed DEF CON distribution or fulfilled collector population.
The catalogue preserves current offer and remediation language without converting it into a completed DEF CON distribution report.
The catalogue retains current offer and remedy language without claiming completed distribution or a finalized production run.
The entry records a planned independent distribution model without presenting an announced free giveaway as manufactured stock, a confirmed recipient benefit, a completed DEF CON handoff, or a public fulfillment ledger.
The catalogue records a real, explicitly DC34-associated public design without upgrading it into an official badge, a conference credential, a completed physical distribution, or a sale/fulfillment claim.
The catalogue records a real organizer-published planned design without calling it an issued attendee badge, a registration credential, a guaranteed benefit, or a completed distribution.
The catalogue preserves a live maker offer and active DC34 design trail without turning either into evidence of units built, distributed, sold, collected, or received.
The catalogue records organizer-published plans without converting them into proof of manufacture, sales, party results, or beneficiary accounting.
The catalogue records an announced independent badge and pickup context, not a completed run, universal attendee issue, or confirmed post-event use report.
The catalogue preserves the announced distribution plan without converting it into a completed delivery or event report.
The catalogue records a documented pre-event marketplace run without converting sales-state evidence into a delivery report.
The catalogue records BTV's current terms and 501(c)(3) purpose without converting them into proof of fulfilled orders, completed donations, or a finished event.
The catalogue preserves a current pre-event offer without presenting it as a completed DEF CON distribution.
The catalogue records current seller-published marketplace terms without converting them into proof of completed manufacture, purchase, delivery, meetup attendance, or convention-wide distribution.
Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.
Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.
Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.
The catalogue preserves a current marketplace snapshot and intended pickup path without presenting either as completed production or delivery.
The catalogue preserves an observed marketplace state and intended pickup path without presenting it as a completed limited run or delivery report.
The catalogue preserves an observed marketplace state and intended pickup path without presenting it as a completed limited run or delivery report.
The catalogue preserves a current marketplace snapshot and intended pickup path without presenting either as completed production or delivery.
The catalogue records the maker's limited-run and currently-unavailable state without translating it into a sold-out claim or a fulfillment report.
The catalogue preserves the planned free giveaway without treating it as a completed run, confirmed attendee entitlement, universal handout, or delivered artifact.
The catalogue records an announced free distribution rather than a completed, universally accessible, organizer-provided, or delivered artifact.
The catalogue preserves a dated seller snapshot without converting it into a completed DEF CON or Hacker Summer Camp distribution report.
The catalogue preserves a current, well-documented planned artifact without presenting it as a shipped or universally received conference item.
The catalogue preserves public offer terms without implying that all orders or drops were successfully fulfilled.
The catalogue preserves a dated seller snapshot without treating it as a completed event or mail fulfillment report.
The catalogue preserves a dated seller snapshot without representing it as a completed event handoff.
A live/pre-event commerce snapshot is not presented as proof that badges were delivered, an access promise was honored, or the party/challenge happened as announced.
The catalogue records the seller's current marketplace state and stated policy without converting them into evidence of completed fulfillment or an event-wide distribution result.
The catalogue preserves both published price contexts without treating either as a completed transaction, guaranteed inventory, final price, DEF CON entitlement, or delivery outcome.
The catalogue records an announced acquisition path rather than a completed sale, guaranteed stock, organizer-provided benefit, or delivered item.
The dossier exposes the real planned badge surface while preventing teaser language and generic MiniBadge-standard documentation from becoming unsupported 2026 hardware or software claims.
The record does not promise a badge to applicants, describe it as a universal DEF CON attendee benefit, or claim that any volunteer received or used one.
The record does not promise a badge to applicants or claim that any volunteer received, used, or retained one.
The catalogue records both the observable availability snapshot and the maker-published production-file claim without translating either into a sold-and-delivered production report.
The catalogue preserves a documented corrective-update trail without claiming the issue's severity, universal applicability, successful remediation, or a risk-free flashing process.
The catalogue retains the seller's current acquisition terms without presenting them as a completed run, confirmed onsite sale, guaranteed shipping/pickup, or verified charitable transfer.
The catalogue preserves announced independent acquisition paths without converting a live counter or contest promise into a confirmed completed distribution.
The premium offering remains a distinct ticket-form record without being reconstructed as a particular electronic device, established board variant, released program, or source-backed technical upgrade.
The catalogue retains the current sold-out preorder and stated fulfillment window without calling it a shipped badge, a completed recipient allocation, a DEF CON Human badge, or a DEF CON admission credential.
The catalogue records source-provided seller terms without treating a planned pickup or retail price as a proven completed distribution.
The catalogue records a live sold-out and pickup-oriented source state without turning it into a confirmed fulfilled run or a guaranteed opportunity to acquire an extra.
The catalogue keeps distinct source snapshots instead of merging them into a single asserted price, inventory, or distribution history.
The catalogue keeps distinct seller/vendor snapshots instead of turning a displayed price or sold-out state into proof of event sale, recipient allocation, or fulfilled ownership.
The catalogue preserves a dated seller availability statement rather than treating sold out as proof that every unit reached the scheduled event or every buyer received a badge.
The catalogue keeps the published marketplace and mission wording without treating it as proof of sales, donation outcome, official fundraising, or final recipient delivery.
The catalogue preserves the public maker intention without presenting it as a completed charitable transfer, family endorsement, financial audit, tax determination, or quantified benefit.
The record treats the badge as a living event platform and avoids implying that every public firmware artifact represented a fully settled pre-production state.
The entry preserves real production and firmware bring-up caveats that matter for surviving badges and reproduction attempts.
The record preserves manufacturing and logistics context as part of the badge's historical importance rather than presenting it as a frictionless production run.
The record preserves production reality without overstating it into a failure or delivery controversy.
The record preserves the badge as a real distributed artifact with documented production yield and rework constraints rather than treating the design as frictionless reference hardware.
The catalogue presents the badge as reflashable while preserving the practical recovery boundary for surviving units.
The catalogue presents the badge as hackable and source-backed while preserving the practical hardware access needed to modify surviving units.
Badge updates were handled manually at the event with a Bluetooth barcode scanner, local script, CC Debugger, and programming jig.
Readers can see substantive development evidence without mistaking a working or revised prototype trail for a finished, safety-qualified production specification.
The catalogue avoids binding the record to a specific public preview photo until an exact production-badge image is cleared.
The catalogue records the source-backed architecture and car-hacking direction while avoiding unsupported claims about every final shipped component, firmware image, or quantity.
The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, production quantity, or assembled variant.
The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, firmware image, quantity, or attendee role.
The entry is a traceable public platform reference, not a reproducible manufacturing record, safety assessment, interoperability guarantee, or proof that every event unit matched the README.
The software description separates the recovered demo archive from the full shipped event firmware so the record does not overstate public source completeness.
The catalogue retains the exact published uncertainty instead of deriving a final volunteer commitment from inconsistent wording.
The dossier does not characterize the badge as a reliable detector, a complete Flipper identifier, a private/passive tool in every context, a regulatory-approved radio, or operational guidance for monitoring nearby people/devices.
The catalogue records high-level communications capability only and deliberately omits operating instructions, frequency/configuration guidance, challenge tactics, and claims about lawful or safe field operation.
The catalogue does not expose individual credentials or turn maker radio/network statements into legal, privacy, security, compliance, or operational advice.
The record documents the available hardware surfaces without endorsing RF transmission, replay, credential use, or unreviewed expansion hardware.
The dossier records a released badge platform without converting event and source-release evidence into a completed attendee-delivery ledger.
The catalogue keeps main-attendee, VIP, event-logistics, and contributor statements distinct instead of treating an advertised variant or a thank-you as universal allocation or sole authorship.
The catalogue does not treat repository main as a released production image, a firmware actually installed on badges, a reproducible event build, or a completed compliance archive.
The record models it as a remote-event input badge and avoids ordinary attendee-distribution assumptions.
The catalogue can link the technical trail without representing it as licensed open hardware, free software, a released production artifact, or a valid source of reusable images.
The catalogue links to the technical archive as evidence but does not copy its source files or images or infer a reuse license from public access.
The record stays image-free and avoids publishing repository badge images or firmware assets locally without explicit reuse rights.
The catalogue links the source trail for research while preserving the separate requirement for explicit reuse terms, especially for any future local image asset.
The record anchors claims to the CC14 README, event context, and CC14-named schematic/CAD outputs rather than inferring anything about earlier CactusCon badge years from carryover filenames.
The catalogue cites the repository for evidence but does not use repository images locally or claim a single reuse license for the whole project.
The catalogue cites the repository as evidence but does not republish repository media or treat the design files as reusable image assets.
The catalogue cites the repository as evidence but does not republish repository media or treat source files as a reusable image basis.
The catalogue cites the repository as evidence and a user-facing reference without treating its images, firmware, or hardware files as freely reusable beyond what the source itself permits.
The catalogue cites the repository as evidence but does not treat code, wiring diagrams, screenshots, or repository media as broadly reusable publication assets without explicit license coverage.
The catalogue cites the repository for source facts and tooling while withholding local image publication until a specific image license or permission basis is verified.
The catalogue cites those repositories as source evidence but does not treat repository images, board renders, firmware, CTF material, or documentation as broadly reusable publication assets without explicit license coverage.
The record links to the public archive while avoiding reuse claims beyond the visible source evidence.
The catalogue cites the public source trail as evidence but does not republish images or imply reusable licensing for the CactusCon 12 archive.
The catalogue can cite the repository as evidence, but it does not republish repository media or claim a blanket reuse license for hardware files, photos, or PDFs.
The catalogue records public firmware and customization surfaces conservatively while allowing the specifically reviewed Build-A-Badge render to carry explicit MIT provenance.
The repository is cited as public technical evidence, but its images and design files are not republished locally or treated as broadly reusable catalogue assets.
The repository is used as evidence, but images are not copied into Public/images.
The catalogue avoids broad image assumptions while publishing a specific audited source photo for the badge page.
The catalogue cites the repository as evidence but does not republish repository media or treat design files, PDFs, or images as reusable publication assets.
The catalogue cites the repository as evidence but does not assume reusable image, code, schematic, or PCB rendering rights beyond ordinary source citation.
The catalogue cites the repository as evidence but does not republish repository media or treat the design files as reusable image assets.
The catalogue cites the repository as evidence but does not republish repository media or treat the design files as reusable image assets.
The source is used as evidence, but repository images or documentation media are not republished as catalogue images.
The catalogue cites the repository as evidence but does not republish repository media or treat the design files as reusable image assets.
The repository is used as evidence, but images are not published in the catalogue.
The catalogue cites the repository as evidence while leaving images empty and avoiding license claims beyond the source text.
The catalogue treats the repository as evidence and a user-facing technical reference, not as a blanket permission source for republishing media, firmware, or hardware assets.
The catalogue records technical facts and outbound source links while withholding local images and avoiding license assumptions.
The badge is modeled as a proven electronic badge while exact final per-attendee hardware capability remains caveated.
Hardware claims stay limited to the SMART Response XE platform, ATmega128RFA1 radio path, USBasp/Arduino workflow, and the source files reviewed.
The record preserves the documented hardware/software trail without treating it as a complete electrical specification, safety assessment, support promise, security claim, universal compatibility result, or unit-by-unit production record.
The catalogue records the device as an event artifact and badgelife experiment, not as a safe consumer medical or therapeutic device.
The catalogue presents the badge as a real fault-injection and maritime-bus lab while preserving the primary-source caution around unsafe use.
The DEF CON 33 attachment rests on a documented scheduled activity without turning it into a universal attendee distribution, event outcome, or sale-allocation claim.
The DEF CON 33 attachment rests on a documented scheduled activity without turning it into a claim of universal attendee distribution or a completed event outcome.
The DEF CON 33 attachment rests on a documented scheduled activity without turning it into a universal attendee distribution or completed event-outcome claim.
The catalogue preserves a 2025 origin and planned 2026 recurrence without turning either schedule entry into a universal attendee distribution, completed event outcome, sale, allocation claim, or distinct DEF CON 34 badge.
Hardware claims use the current hardware specification text and repository tree instead of relying on the stale embedded link alone.
The record avoids inventing a sensor suite, electronic design, power path, safety state, accessibility behavior, or data-collection capability from the badge name or historical product association.
The record preserves the voice/audio ambition without overstating default deployed service behavior.
The catalogue preserves the seller-stated schedule and scope without converting it into confirmed pre-event or attendee delivery.
The entry does not turn the verified puzzle framing into unsupported CTF, firmware, networking, or credential claims.
The record preserves verified software-release context and leaves deeper artifact inventory as an archive task.
The record links historical source evidence without presenting a later archive as confirmed 2024 event software, a secure deployment, a supported modification workflow, or operational instruction.
The catalogue presents only the stated NFC game concept, not a defined communications protocol, software release, privacy practice, security guarantee, or safe operating guidance.
The catalogue can cite the software/documentation licensing trail while retaining image, artwork, logo, trademark, and dependency-specific rights boundaries.
The catalogue records verified hardware and firmware-access surfaces while avoiding unsupported claims about the badge's full event game or OTA backend.
The record keeps software claims limited to QA-code context and hardware-programming surfaces.
The catalogue records the verified hardware archive while avoiding unsupported claims about badge applications, games, OTA behavior, or event infrastructure.
The catalogue records verified hardware/manufacturing evidence while avoiding unsupported claims about badge software behavior.
The source-linked record retains the documented physical work without becoming a battery, soldering, USB, SAO, electrical, or repair endorsement.
The record keeps claims tied to the official archive page, Sched listing, venue page, and MiniBadge standard, and leaves the page image-free until a rights-cleared original photo or official render is available.
The record keeps hardware claims to official FAQ language, community data-export fields, and the MiniBadge standard instead of inventing missing per-badge technical detail.
The record keeps hardware/protocol claims to the MiniBadge standard and official trading-page wording, and leaves the page image-free until a rights-cleared original photo or official render is available.
The catalogue links the preservation source without misrepresenting it as a complete, current, supported, reproducible 2026 field-update package or a full release of every historic CTF component.
The catalogue records the concrete pre-event offer while leaving attribution, seller relationship, availability, sale, fulfillment, and event outcome explicitly unresolved.
The event and badge record follow the repeated official May 31-June 2 date while preserving the conflicting first-hand pre-event wording for future archive recovery.
The record may describe the publicly visible technical material but does not treat availability as a license to redistribute source, hardware, firmware, or images.
The catalogue uses the secondary listing narrowly for its captured ticket wording and price while preserving the absence of a primary artifact specification, maker attribution, delivery record, and reusable image authority.
The catalogue preserves a real source-documented electronic-badge project without presenting it as a delivered product, attendee issue, or verified physical run.
The catalogue does not expose connection or challenge details, claim a current working service, offer configuration guidance, infer a released event firmware, or treat public source visibility as a broad license or support commitment.
The record avoids stronger open-hardware or source-release claims until a complete repository or archive mirror is recovered.
The record cites the available project logs and model archive while avoiding stronger open-hardware/source-code claims until the missing repository or an archive mirror is recovered.
The record preserves verified public hardware and workflow facts without inventing unrecovered firmware internals, board-source details, or manufacturing data.
The record documents source-backed behavior while avoiding claims about open firmware availability.
The catalogue records the verified deployed badge and public manual without inventing unrecovered firmware internals or PCB-source details.
The catalogue retains the named maker project and its source-declared collaboration without promoting it into a DEF CON-issued Human badge, a ticket benefit, an admission item, a confirmed sponsor deliverable, an externally verified iFixit product announcement, or a completed attendee handoff.
The record preserves verified badge behavior and named-source context without inventing unrecovered electronics, firmware internals, component values, or manufacturing details.
The record stays anchored to the official write-up and upstream firmware repository without inventing exact board files, pin maps, or firmware modifications.
The record limits claims to visible physical-credential evidence and event context.
The record keeps hardware, USB, LED, and firmware statements tied to the recovered public repository while avoiding unsupported production-scale claims.
The record keeps controller, LED, fabrication, and firmware claims tied to the first-hand project page and avoids unsupported protocol, challenge, and source-release claims.
The record limits claims to visible physical-badge evidence and official event context.
The record limits claims to visible physical-credential evidence and event context.
The record keeps component and behavior claims tied to the recovered firmware, Eagle files, Gerbers, and event archive.
The catalogue records the real scanner badge while keeping technical claims limited to the public attendee writeup.
The record keeps hardware and software statements tied to public evidence while avoiding unsupported production-scale and final-firmware claims.
The record preserves verified behavior and integration claims without inventing components, radio details beyond Wi-Fi, PCB layout, battery design, firmware internals, or backend implementation.
The record keeps hardware and firmware statements tied to the recovered public repository and avoids unsupported production-scale claims.
The record avoids final component, firmware, interaction, and distribution claims until stronger PhreakNIC 27 sources appear.
The record limits claims to visible physical-credential evidence and official registration context.
The record treats SAINTCON 2020 as a conservative package-level badge entry instead of inventing unrecovered electronics, firmware behavior, or challenge mechanics.
The record limits claims to visible physical-credential evidence and event context.
The record avoids claiming a recovered schematic, BOM, final firmware tree, or complete CTF source.
The record limits claims to visible physical-badge evidence and event context.
The record preserves the real BSidesPDX badge without overstating production logistics or publishing unclear media.
The record limits claims to visible physical-credential evidence and event context.
The record limits claims to visible physical-credential evidence and event context.
The record is intentionally compact and should be revisited if Bug Bounty Village publishes post-event technical material.
The record limits claims to visible physical-credential evidence and event context.
The record limits hardware and software claims to the common-parts build guide and public code previews, with image publication withheld until rights-cleared provenance exists.
The catalogue records verified event, game, mechanical, and optical facts without claiming that the complete design archive is public.
The catalogue records verified hardware behavior and production context without claiming that the complete design archive is public.
The record keeps hardware, software, and add-on statements tied to public evidence while avoiding unsupported production-scale and final-firmware claims.
The record limits claims to visible physical-badge evidence and official program context.
The catalogue preserves the product evidence and explains the image gap without treating generated marketing art as a picture of the actual badge or as an allowed public image asset.
Source-code claims can cite the repository, while the badge image remains empty until a separately cleared original photo or official render is selected.
The entry may link the respective source archives and license statements while keeping physical-artifact, media, branding, downstream reuse, and local-image rights scoped rather than inferred.
The record cites project-owner logs and hands-on technical coverage while avoiding stronger open-source hardware/software claims until a repository or archive mirror is recovered.
Hardware and software claims remain tied to the public HHV page and Hackaday.io logs instead of treating planned source publication as recovered source.
The record remains image-free and source-conservative rather than treating open design files or promotional media as proof of exact 2026 unit parity or reusable catalogue artwork.
The record is useful as a source trail but should be revisited if official pages, ticket text, badge photos, or hardware archives surface.
The record preserves the source's 2024 identity and its catalogue placement without silently converting a later repository name into a 2026 badge, an official DEF CON classification, or a verified contemporaneous event artifact announcement.
Sprites remain source evidence for firmware behavior only and are not promoted into `Public/images/`.
The catalogue preserves dated seller and maker intent without representing the item as available, delivered, or confirmed for DEF CON.
The catalogue can cite the official archived event page for bundle contents without depending on a live store page that may change or disappear.
The dossier preserves source-named narrative and manufacturing context without assigning ownership, cultural/institutional relationship, approval, sponsorship, final manufacturing responsibility, or image rights beyond the published statements.
Readers should not treat the public source as a compatibility guarantee, a target-specific exploit claim, an endorsement to connect the SAO, or authorization to interact with another attendee's hardware.
The catalogue records the confirmed electronic-badge milestone without turning a one-sentence historical designation into an invented hardware, software, credential, distribution, or manufacturing dossier.
The catalogue can retain the maker's source-release statement while avoiding a fabricated repository link, open-source license claim, reproducible build claim, or unsupported source-code detail.
The catalogue records the verified artifact and hands-on event context without upgrading a visual or assembly description into unsupported electrical or software claims.
The record stays narrow and does not invent electronics beyond the official badge-kit language.
Hardware and firmware claims remain limited to the public repository files and official schedule/speaker wording.
The catalogue records the verified village badge and leaves hardware/software archaeology for a later source recovery pass.
Hardware and software claims remain limited to the public repository files and official all-digital event context.
The catalogue can describe observed user-facing badge behavior while leaving schematic, firmware, and manufacturing details for a later badge-team archive.
Hardware and software claims remain limited to the public repository files and official talk description.
The catalogue preserves the physical badge lineage while avoiding unsupported component-level or reproducibility claims.
The record preserves the artifact while avoiding unsupported claims about hardware design or firmware behavior.
Hardware and firmware claims remain limited to the public repository files plus event-context wording.
Hardware and software claims remain limited to the public repository files and official schedule/speaker wording.
Hardware and firmware claims remain limited to the public repository files and official schedule wording.
Hardware and firmware claims remain limited to the public repository files and official schedule wording.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
Hardware and software claims remain limited to the official badge-page text and avoid unsupported electronics or firmware behavior.
The catalogue records only the verified official badge scope and avoids unsupported hardware, software, and challenge claims.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
The catalogue records the verified 2025 badge artifact and avoids inventing unsupported electronics or firmware behavior.
The catalogue records verified badge behavior without inventing component-level electronics, source-release status, or shipped-hardware internals.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
The record keeps hardware and software claims at the official high-level classification.
The catalogue records the verified badge lineage without inventing component-level details or open-source status.
The catalogue records the verified chip-family flashing target and maker-announced continuation while avoiding unsupported board, firmware-source, challenge, and production claims.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
The catalogue records the verified artifact without inventing component-level electronics or source-release status.
The catalogue records an optional third-party mechanical design without treating it as an official accessory, a fit result, a port-orientation diagnosis, an electrical-safety conclusion, or a finished product. The source does not establish print material, assembly quality, mechanical loads, badge/port clearance, pinout/orientation outcome, safety validation, production, sale, delivery, support, or image reuse rights.
The catalogue credits named sources without republishing lore artwork, product media, or project images on an assumed license basis.
The catalogue records a source-backed third-party standalone SAO power/display companion without treating its maker-described 3.3 V conversion or multiple-SAO example as official main-badge support, a universal-compatibility claim, or a safety endorsement.
The catalogue records an organizer-confirmed planned artifact without treating it as attendee-wide inclusion, proof of individual receipt, admission credential, or final fulfillment record.
The catalogue records the advertised digital-ticket identity artifact, not a confirmed credential implementation, completed delivery, or successful event access.
The catalogue records a concrete advertised ticket tier without treating it as proof of completed production, distribution, inclusion with every attendee, or individual possession.
This is a documented completed-event ticket artifact, not a claim that every purchaser received a particular board or that the three ticket forms had a known technical relationship.
The catalogue describes the published interaction mechanism without making claims about usability, accessibility, sensory safety, audio licensing, annoyance, final behavior, or suitability in a particular venue.
The catalogue links the public preservation trail without presenting it as open hardware, free software, a licensed build kit, or a cleared source for images/audio/artwork.
The entry uses a handle-qualified index title and links the raw source while avoiding invented technical behavior, a formal release, a legal reuse grant, or a stronger creator claim than the evidence supports.
The catalogue classifies Clip-Boy as an independent BadgeLife artifact associated with DEF CON 34 rather than an official conference credential or admission substitute.
The catalogue classifies FrogStar as an independent BadgeLife artifact associated with DEF CON 33, not as an organizer-issued conference credential or admission item.
The compendium can show both the official DEF CON 27 badge and the community AND!XOR hardware without merging their lineages.
Country, event, and series pages can show the badge's historical importance without confusing it with the official 1o57 skull badge.
The compendium treats the artifact as a source-backed community badge template, not as the official event credential or a universal attendee handout.
The compendium can preserve the source-backed forum artifact without claiming it represents the main DEF CON 12 badge.
The compendium preserves the community hardware lineage without confusing it with the official DEF CON 25 rubber/plastic identity badge.
The catalogue includes it as an unofficial community badge artifact while keeping the official Mar Williams DEF CON 33 badge as a separate record.
The catalogue keeps it separate from the official Mar Williams DEF CON 33 badge while preserving its vendor-booth debut and public firmware evidence.
The compendium preserves the community hardware lineage without confusing it with the official DEF CON 26 text-adventure badge.
The compendium records it as unofficial badgelife and avoids implying GrrCON organizer publication, attendee-wide distribution, or admission-credential status.
The catalogue keeps Hackbat as an unofficial DEF CON 32 badgelife record separate from the official RP2350 DEF CON 32 Badge.
The compendium keeps the unofficial party-badge lineage separate from the official DEF CON badge series while preserving its badgelife significance.
The catalogue keeps the DC503 wrist badge separate from the official DEF CON 26 Tymkrs badge, the AND!XOR DC26 badge, and BSidesPDX 2018's conference-badge archive.
The catalogue records the expansion footprints as a design surface without implying that every attendee badge shipped with populated motion or RF hardware.
The record preserves the visible update/v2 trail without inventing a previous event, assigning an exact earlier version, merging unknown revisions, or treating the seller card as standalone proof of historical IFLFU distribution.
The catalogue keeps v2 distinct because its own listing is distinct while avoiding an invented hardware revision, size, Saintcon history, or universal compatibility claim.
The catalogue keeps v1 distinct because its own listing is distinct while avoiding an invented hardware revision, size, Saintcon history, or universal compatibility claim.
The record preserves the existence of hidden variants without overclaiming a complete catalog of DEF CON 19 badge shapes.
The compendium keeps the record under its own Social Engineering Community series while cross-linking the DEF CON context.
The record remains attached to the ICS Village event edition without confusing a village hardware project with a general conference-access badge.
The catalogue classifies it as a source-backed Blue Team Village fundraiser artifact rather than a substitute for conference registration or the official DEF CON badge.
The compendium keeps the badge under its own village lineage while preserving DEF CON event context and avoiding an attendee-wide DEF CON main-badge claim.
The catalogue models the badge as a virtual-conference workshop build and simulation artifact rather than upgrading it into an all-attendee production electronic badge.
The badge remains an electronic artifact, but its event-game behavior is kept narrower than the original hardware capability.
The catalogue records the organizer's explicit staff-badge commitment without treating it as a general-attendee badge, a verified access-control credential, proof of individual selection, or proof that any person has received a badge.
No contest, lottery, acquisition, ownership, prize, or delivery outcome is implied beyond the narrowly stated planned CTF and raffle concepts.
The record describes public ESP-NOW application behavior without claiming final radio performance, BLE functionality, a production firmware identity, or certification.
Readers can identify the announced wireless/NFC surface without treating the record as a sanctioned operational guide, a privacy guarantee, a compliance claim, or permission to use the badge against systems or media they do not own or control.
The catalogue records the game mechanics without implying a real-world botnet or harmful network capability beyond the badge ecosystem described by the project owners.
The catalogue does not provide guidance for active testing, characterize any security feature as safe or legal everywhere, or turn a seller disclaimer into a compliance determination.
Future archive work should seek official or creator permission before treating private Gerbers, puzzle art, or code meanings as publishable catalogue evidence.
The catalogue treats the board as a limited attendee-retained workshop artifact, not a village-wide or DEF CON-wide attendee badge.
The record avoids importing 2020 or 2022 technical details into 2021 without a year-specific source.
The record preserves a real organizer-published inclusion statement without turning it into proof that a particular youth attendee received an artifact or that it participated in the CTF.
User-facing wording preserves the practical safety boundary around operating surviving badges or reproductions.
