DEF CON 1 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.
Country dossier
Worldwide badge coverage for United States, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.
Seeded artifacts
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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'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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The BSidesKC 2025 badge was a Badge Pirates fully electronic conference badge documented through public production and fulfillment updates: 250 fully assembled ESP32 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.
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.
The BSidesSLC 2025 E-Badge is a source-backed electronic event badge built on the LilyGO T-Deck S3 and advertised by BSidesSLC with keyboard, trackball, 25 LEDs, ESP32-S3, LoRa support, Meshtastic readiness, and customization potential.
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.
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.
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.
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.
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.
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' 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
DEF CON's official preregistration copy guarantees an onsite DEF CON 34 Human badge, and the official media server publishes DC34 SAO electrical and mechanical specifications that make the 2026 badge a source-backed planned electronic-badge record.
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.
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.
The planned RVAsec 2026 badge is seeded from current official RVAsec 15 registration/package material listing a limited Custom Hack.RVA Electronic badge. Because the event is scheduled for June 9-10, 2026, this record is pre-event and does not claim shipped hardware, final firmware, production quantity, or attendee distribution outcomes.
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.
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 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 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 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 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 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 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 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 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 planned August 6-9, 2026 DEF CON edition whose official preregistration copy guarantees an onsite Human badge and whose public media-server badge archive already exposes DC34 electronic SAO electrical and mechanical specifications.
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 planned November 6-7, 2026 PhreakNIC edition, currently seeded only from the public PhreakNIC site and Tyler Crumpton's PN26 project-owner writeup that says a cooler MK.II electronic shelf-label badge is planned for PhreakNIC 27.
The planned June 9-10, 2026 RVAsec 15 edition whose official registration/package pages list a limited Custom Hack.RVA Electronic badge; final shipped hardware, firmware, and image evidence remain future monitoring work.
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.
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 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 public Speedometer SAO firmware repository is MIT-licensed and says it includes CTF problem and notes material built on a display library.
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 2020 record keeps per-board behavior limited to recovered source evidence.
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 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 registration pages say the issued badge gave access to all talks and workshops.
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 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 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.
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 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 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.
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 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 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.
The official badge page says AvengerCon IX's badge carried a small four-challenge CTF contest.
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 public challenge archive documents main-badge CAN enumeration, a physical-inspection flag under the battery pack, random traffic, and a UART Python REPL path.
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 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.
Connecting a terminal over USB exposed a text adventure about scavenging parts to rebuild a relay-based computer in a missile silo.
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.
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 official hardware description lists a keyboard, trackball, and 25 LEDs as attendee-facing interaction surfaces.
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 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 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.
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 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 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 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 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.
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 badge challenge used six lanyards carrying Lewis Carroll Nyctograph symbols and Poe Gold Bug cipher material that translated into early-stage secret messages.
The teardown documents 115200-baud serial output, BLE-readable messages, hash clues, and firmware strings analyzed with Ghidra.
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.
The same project archive includes a backpack-mounted open access point and four-matrix scoreboard that counted unique connecting clients during the conference.
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 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.
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 official site offers remaining 2025 E-Badges through 2026 ticketing and instructs buyers to pick them up at the April 2026 conference.
The Euphoria CTF page says the first challenge is on the badge after Shady Tag registration at the Shadytel Experience Center.
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.
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 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 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.
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 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.
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.
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 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.
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 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 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 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.
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.
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 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 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 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 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.
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 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 README documents flashing badge2022_c.uf2 through the Pico/RPI-RP2 USB mass-storage path.
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 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 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 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.
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 official BSidesSLC site says the 2025 E-Badge is built on the LilyGO T-Deck S3 platform.
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 guide documents an RP2040 microcontroller / Raspberry Pi Pico board manager for button inputs, LED control, battery charging/status, and power management.
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.
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.
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.
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 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.
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 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 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 NilbinSec announcement and product page describe two included SAOs, red and blue fighters, with game data and hidden interactions carried through EEPROM.
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 reveal and firmware docs document a custom keyboard, TCA8418 keyboard matrix controller, wide LCD, LVGL MicroPython UI pages, and function-key app workflows.
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 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 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 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.
Cisco Connected Mobile Experiences data supplied the venue-location context used to personalize badge behavior and analyze attendee movement.
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.
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 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.
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.
The record should be refreshed after June 9-10, 2026 for final hardware, firmware, attendee guide, production, and image provenance.
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.
The badge provides GPS own-ship position on a moving map, and the FAQ documents manual coordinate fallback when GPS lock is unavailable.
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.
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.
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 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 public plan sketches badge stations for hardware hacking, puzzles, games, a photo booth, or similar event-specific interactions.
The project-owner plan calls out UART or wireless communication so stations can update badge state or behavior without reflashing a full image.
Official RVAsec 15 pages list a limited Custom Hack.RVA Electronic badge as part of the pre-event hotel package.
The next-version plan keeps the self-service update-station idea that was not fully reliable enough for PN26 field deployment.
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.
After AC9, the official badge page published four booth/village unlock codes for people who missed them during the event.
The manual provides a post-conference conversion path for turning the badge into a RetroPie device after the event.
Hackaday documented that the badge could identify as a USB HID keyboard and operate as a configurable macro pad after the event.
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.
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.
Hackaday describes an 18650 cell and charging circuit as part of the badge hardware package.
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.
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 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 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 page identifies the badge's ESP32-S3 chip and LoRa support, framing the device as Meshtastic ready.
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 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 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 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.
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.
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 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 public repository preserves firmware, Gerbers, SPI tooling, troubleshooting notes, a flash-image archive, and Apache-2.0 license metadata after the CTF window.
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.
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.
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 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 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.
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
The record preserves the RF and navigation limits without implying universal aircraft tracking or software-selectable ADS-B bands.
Hardware and firmware features are kept to repeatedly corroborated repository and guide statements instead of overstating uncertain generated prose.
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 avoids merging the online CTF archive into the badge record without source-backed badge integration evidence.
The catalogue preserves the badge-culture artifact while avoiding universal distribution, official handout, or finished-product claims.
The catalogue records the ESP32-WROVER migration as a deliberate capability upgrade while preserving the team's documented engineering tradeoffs.
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 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 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 treats Uber Badges as an award lineage attached to the challenge and avoids naming unverified 2026 winners.
The catalogue avoids implying that every 2019 badge had an onboard camera, Wi-Fi-capable core, or face-recognition hardware.
The compendium avoids MCU, firmware, LED, battery, and circuit claims and records the audio, physical, lanyard, and printed clue surfaces instead.
The record preserves the verified hardware and software surfaces while leaving deeper artifact archaeology for a later pass.
The record captures the verified hardware/software surfaces without claiming complete CTF reconstruction or complete production logistics.
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 catalogue models the object as a presenter wearable/event artifact rather than a general admission badge or attendee-wide distribution claim.
The catalogue keeps the 2018 record as a paid-badge entitlement and avoids unsupported physical or electronic details.
The catalogue records verified hardware and social-game behavior while leaving firmware, challenge, and complete variant archaeology for a later pass.
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 record keeps hardware claims tied to the assembly PDF rather than inventing design files or firmware surfaces.
The catalogue records the verified analog badge surfaces and leaves complete audio forensics for a later artifact-level pass.
The compendium records the artifact under DerbyCon while avoiding claims of general conference distribution or regular attendee-badge status.
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 catalogue records practical handling behavior that matters for surviving badges and post-event hacking.
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 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 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 MiniBadge ecosystem while keeping acquisition routes, creator roles, and support boundaries separate from main-badge distribution claims.
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 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 treats the Tipsy Badge as an independent DEF CON 33 badgelife release while keeping the official DEF CON 33 badge record separate.
The record avoids unverified controller, pinout, schematic, or production-detail claims.
The badge page preserves the contest lineage while leaving full per-entry reconstruction for a later archive pass.
The badge page preserves the contest lineage while leaving full per-entry reconstruction and media review for a later archive pass.
Country and event pages can show the 2025 badge lineage without turning remaining-stock pickup into an unsupported new edition.
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.
Surviving-badge owners should preserve state before using the documented post-event firmware path or DFU flashing workflow.
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 catalogue avoids implying every BSidesKC attendee had a fully electronic badge while still recording the verified electronic badge ecosystem.
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 record avoids claiming universal DEF CON, DC503, or BSidesPDX distribution and treats the artifact as a VIP/party wrist badge.
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 record preserves the verified distribution language without implying every DEF CON or BIC Village attendee received one.
The catalogue records the electronic badge without implying that every attendee received a fully assembled programmed unit.
The catalogue models the artifact conservatively as a BSidesPDX 2015 badge-hacking board archive rather than a universal attendee badge claim.
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 records a source-backed BSidesPDX 2018 badge archive without overclaiming distribution scope.
The catalogue records a source-backed BSidesPDX 2019 badge archive without overclaiming distribution scope.
The catalogue treats the artifact as a source-backed La Villa Hacker 2025 badge without implying every village attendee received one.
Claims are limited to a self-order/forkable hardware template and do not imply all Remoticon attendees received one.
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 record remains useful for source discovery while preserving the limits of the public documentation.
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 event edition is named by year and kept source-scoped rather than assigning an unsupported CactusCon edition number.
The entry separates source-backed plans, public interpreter code, and final-event uncertainty.
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 record presents the badge as a serviceable field device with operational constraints rather than a frictionless consumer gadget.
The record documents intended and exposed firmware surfaces without implying that every listed protocol or feature was complete during DEF CON 33.
Hardware and software fields stay limited to the official SAO spec until DEF CON publishes final badge files or credible post-event technical documentation.
The catalogue keeps the strong official badge-guide evidence while avoiding unsupported claims about the unrecovered design files or shipped firmware internals.
The record intentionally avoids detailed firmware claims beyond USB-oriented hackability until stronger primary source is recovered.
The record treats the repository and firmware documentation as living event artifacts rather than claiming a frozen pre-event production firmware state.
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.
The entry records the verified soldering badge and hacking surface without inventing software behavior.
Software claims remain limited to user-supplied electronics and do not invent a Remoticon 2020 badge firmware platform.
The catalogue records verified hardware, game behavior, and recovery workflow while leaving full firmware preservation and challenge reconstruction for a later pass.
Software and protocol claims are kept to the public project statements rather than treating development notes as a complete release package.
The record describes verified assembly and interaction evidence without inventing unrecovered firmware behavior or treating every MiniBadge as source-open hardware.
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 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 record presents the badge as a real post-event delivery effort with documented logistics friction instead of implying frictionless on-site distribution.
The catalogue treats the PDF title as an edition-number wording issue rather than a separate 2012 event claim.
Component and firmware claims remain limited to the public product and announcement text, with no invented electronics or implementation details.
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.
Hardware claims stay limited to the product page, pinout text, and firmware constants without inventing board layout, production quantity, or undocumented circuit details.
The catalogue records only the verified badge behavior and avoids inventing electronics beyond the public BBV Badge 2025 source.
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 keeps the record as a source-backed kit badge and avoids inventing electronics beyond the published discrete marquee description.
The catalogue records the badge as a real registration-tier artifact without upgrading it into a specific PCB platform or game badge.
The catalogue avoids claiming pinouts, radio firmware internals, LED counts, or final production files until an official or creator archive is found.
The catalogue avoids unsupported claims about exact PCB assembly and distribution while preserving the source-backed ESP8266 watch firmware record.
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.
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 catalogue records ESP32-S3, OLED, charger, LED, BLE, serial, and firmware-analysis details as teardown-backed rather than official board documentation.
Hardware claims stay limited to the README programming workflow, nRF52832 target, SSD1306 display setup, I2C pin mapping, and firmware-observed inputs.
The catalogue keeps hardware claims to verified public documentation and avoids inventing component identifiers or manufacturing details.
The catalogue records verified hardware and firmware configuration while avoiding unsupported custom-board or source-release claims.
The record captures the source-backed artifact without inventing electronics or software behavior beyond the public evidence.
The catalogue records the verified official badge description while avoiding unsupported local firmware, challenge, or hardware-modification claims.
The catalogue records the real village artifact while avoiding unsupported component or firmware claims.
Future work should revisit ToorCamp and Shadytel archives for hardware details before adding component-level claims.
The compendium uses DEF CON for the series and event but preserves DEFCON in source titles where that is the original title.
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 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 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 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 with source URL, license, attribution, and processing notes instead of a generated, placeholder, or uncleared image.
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 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 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 now has a rights-cleared original documentary photo without using generated, placeholder, or uncleared event 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 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 real rights-cleared documentary photo without copying article media, Hackaday.io photos, screenshots, generated art, or placeholders.
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 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 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 can show a real badge/lanyard artifact while avoiding generated art, unclear conference-gallery imagery, or social-media copies.
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 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 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 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 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 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 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 point at an original repository photo with source URL, license, attribution, and processing notes preserved.
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 point at a real upstream badge 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 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 record remains image-free rather than copying Hackaday.io media, social posts, repository-adjacent screenshots, article images, or generated artwork.
The entry remains source-backed and image-free rather than copying blog, SparkFun, Hackaday, or event media without explicit reuse permission.
The entry remains source-backed and image-free rather than copying Cisco blog, archive, or event media without explicit reuse permission.
The entry remains source-backed and image-free rather than copying documentation photos or archive media without complete provenance.
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 source-backed and image-free rather than copying first-hand blog or archive images 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 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 blog photos, OpenGraph images, videos, screenshots, repository diagrams, 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 record avoids overstating final attendee software behavior beyond public sources.
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 project is cited for artifact facts and fabrication context, but image and artwork reuse is withheld pending explicit license or permission evidence.
The record cites code and hardware sources but does not reuse repository artwork or social/event imagery as a hero image.
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 Pasadena record separate while preserving the Serbian Belgrade design lineage and shared firmware roots.
The compendium keeps the US Supercon record separate while preserving the Serbian Belgrade design lineage and firmware evolution.
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 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 badge is recorded as an event artifact and AI interaction surface, not as a trusted medical device or medical-advice system.
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 DEF CON archive photography without complete rights clearance.
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 DEF CON archive photography without complete rights clearance.
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 DEF CON archive photography without complete rights clearance.
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 DEF CON archive photography without complete rights clearance.
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 old forum, gallery, or template media without complete rights clearance.
The entry remains source-backed and image-free rather than copying project-page WebP photos without complete rights clearance.
The entry remains source-linked and image-free rather than copying project-page, press, or article images 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 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 entry remains source-backed and image-free rather than copying repository sprites, image assets, social photos, generated art, screenshots, or placeholder visuals.
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 image-free rather than copying attendee or press photography without provenance.
The entry remains image-free rather than copying Hackaday or personal writeup photography without provenance.
The entry remains image-free rather than copying press, forum, or personal writeup photography without provenance.
The entry remains image-free rather than copying attendee, press, forum, or GitHub-hosted challenge photography without provenance.
The entry remains image-free rather than copying official preview images, vendor art, or attendee photography without complete provenance.
The entry remains image-free rather than copying official, press, or community photography without provenance.
The entry remains image-free rather than copying creator, official, attendee, or press photography without provenance.
The entry stays image-free rather than copying ticket graphics, registration art, media-server diagrams, social-media previews, or generated badge art.
The record stays source-backed and image-free rather than copying product photos, forum images, social-media previews, or generated artwork.
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 record remains source-backed and image-free rather than copying repository, OSHWA, village, social-media, or attendee imagery without complete provenance.
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 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 site media, screenshots, social posts, 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 official page media, PDF imagery, screenshots, social-media images, or generated approximations without complete provenance.
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 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 entry remains source-backed and image-free rather than copying official-page images, repository previews, article photos, or screenshots without complete provenance.
The entry remains source-backed and image-free rather than reusing generated, teaser, attachment, screenshot, or undocumented badge imagery.
The entry remains source-backed and image-free rather than copying blog, conference, video-thumbnail, or repository imagery without a clear license.
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 site media, screenshots, social photos, event graphics, generated art, or placeholders.
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 entry remains image-free rather than using event-page graphics, screenshots, social-media photos, generated imagery, or placeholders.
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 blog art, screenshots, social photos, or generated approximations.
The entry remains source-backed and image-free rather than copying site artwork, generated-looking imagery, ticketing media, social photos, or screenshots.
The entry remains source-backed and image-free rather than copying ticketing media, site artwork, social photos, screenshots, or generated media.
The record stays image-free rather than copying schedule, social, gallery, or generated media.
The record remains source-backed and image-free rather than copying event-page graphics, sponsor avatars, social photos, or screenshots.
The record remains image-free rather than publishing uncleared or synthetic visuals.
The entry remains source-backed and image-free rather than copying logos, board-art files, event-page imagery, screenshots, or generated visuals.
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 board files, event-page imagery, social photos, screenshots, or generated visuals.
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 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 repository screenshots, event-page images, social photos, product photos, 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 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 blog photos, social media, screenshots, or generated media.
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 event-page, social, wiki, or generated media without explicit reuse rights.
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 blog or event imagery without a clear catalogue reuse basis.
The entry remains source-backed and image-free rather than copying repository PNGs, website gallery files, screenshots, or generated media.
The entry remains source-backed and image-free rather than copying gallery, board-output, screenshot, social, or generated media.
The unofficial badge entry remains source-backed and image-free rather than copying article or project images without a clear 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 record remains source-backed and image-free rather than copying project images, article photos, screenshots, generated art, placeholders, or uncleared media.
The entry remains source-backed and image-free rather than copying article photography without a clear catalogue reuse basis.
The entry remains source-backed and image-free rather than copying article or project-gallery photography without a clear catalogue reuse basis.
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 entry remains source-backed and image-free rather than copying Army article media, event photos, social posts, screenshots, or generated visuals.
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 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 page imagery, screenshots, social media, or generated visuals.
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 page imagery, screenshots, social media, or generated visuals.
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 page imagery, screenshots, social media, or generated visuals.
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 project-page media or rendering KiCad files into approximate badge art.
The entry remains source-backed and image-free rather than publishing generated renderings, SVG/PDF conversions, or uncleared project-page media.
The entry remains source-backed and image-free rather than copying project-gallery imagery without a clear catalogue reuse basis.
The record stays 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 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 entry remains image-free rather than copying Hackaday article photos, Hackaday.io images, or repository assets without a complete image provenance record.
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 entry remains image-free rather than copying Hackaday article images or repository photos without a complete image provenance record.
The record remains source-backed and image-free rather than copying site media, repository screenshots, renders, social-media photos, or generated replacements.
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 article media, site-optimized photos, screenshots, generated art, or other unclear imagery.
The planned record stays image-free rather than reusing PN26 article photos, generated art, screenshots, or speculative visuals.
The record remains image-free rather than copying repository graphics or generating a replacement.
The record remains image-free rather than copying page media or generating an approximation.
The record remains image-free until an explicitly reusable original photo or official raster render is recovered.
The record remains image-free rather than copying article media.
The record remains image-free rather than copying article media.
The record remains image-free rather than copying page media, archived media, or generating an approximation.
The record remains image-free rather than copying article photos, wiki media, screenshots, or generated replacements.
The record remains image-free rather than copying page media or generating a replacement.
The record remains image-free rather than copying repository graphics or generating an approximation.
The record remains image-free rather than copying event media or generated replacements.
The record remains image-free.
The record remains image-free rather than copying repository, event, or article media.
The record remains image-free.
The record remains image-free.
The record remains image-free pending post-event source recovery.
The entry remains source-backed and image-free rather than copying repository screenshots or photos without complete catalogue provenance.
The Hack-Master record stays image-free under the no-generated/no-placeholder image policy.
The virtual-event badge record stays source-backed and image-free.
The record uses firmware evidence but leaves the visual slot empty.
The entry remains image-free rather than copying source-site photos or diagrams.
The record remains source-backed and image-free under the project image policy.
The record stays image-free rather than using uncleared activity photos or schematic screenshots.
The current badge record remains image-free until a rights-cleared original photo or official raster render can be proven.
The record remains source-backed and image-free rather than publishing generated, placeholder, screenshot, repository-cache, or uncleared page imagery.
The record remains source-backed and image-free rather than copying blog media, logos, screenshots, schematic snippets, generated art, or 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 record treats this as an analog electronic badge and does not invent firmware, app, or hidden-code behavior.
The catalogue models the badge as analog electronic hardware and does not infer firmware or software challenges.
The compendium preserves the first DEF CON credential artifacts without upgrading them into circuit-board badges.
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 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 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 compendium preserves the early physical credential without upgrading it into a circuit-board badge.
The compendium preserves the pre-electronic artifact without inventing LEDs, firmware, microcontrollers, or a badge challenge for 2005.
The catalogue avoids MCU, firmware, LED, battery, and circuit claims for 2011 while still preserving the badge's physical fabrication and puzzle significance.
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 avoids adding imaginary hardware to a year whose badge significance is partly the contrast with unofficial electronic badgelife.
The catalogue preserves the major BSides Las Vegas badge lineage as an identity/access artifact without inventing electronics.
The catalogue records the badge challenge and physical identity artifact without inventing hardware.
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 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 the public open-hardware path while avoiding stronger claims about every production file until a deeper repository audit is done.
The record separates the documented board capability surface from any claim that every workshop board shipped with every optional component populated.
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 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 compendium keeps the badge-history record separate from any operational payment-system use.
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 catalogue can document the planned Human badge and public electronic interface constraints now, but it must not claim final shipped artwork, firmware, badge-game rules, manufacturing quantities, or all attendee-role variants until post-event sources appear.
The catalogue can track the announced badge while keeping all final technical claims open.
The record preserves operational and add-on-design constraints rather than presenting the badge as a frictionless reference platform.
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 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.
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, firmware image, quantity, or attendee role.
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 software description separates the recovered demo archive from the full shipped event firmware so the record does not overstate public source completeness.
The record models it as a remote-event input badge and avoids ordinary attendee-distribution assumptions.
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 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 catalogue records public firmware and customization surfaces conservatively while allowing the specifically reviewed Build-A-Badge render to carry explicit MIT provenance.
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 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 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 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 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 public source trail as evidence but does not republish images or imply reusable licensing for the CactusCon 12 archive.
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 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 for source facts and tooling while withholding local image publication until a specific image license or permission basis is verified.
The catalogue records technical facts and outbound source links while withholding local images and avoiding license assumptions.
The catalogue avoids broad image assumptions while publishing a specific audited source photo for the badge page.
The record links to the public archive while avoiding reuse claims beyond the visible source evidence.
The source is used as evidence, but repository images or documentation media are not republished as catalogue images.
The repository is used as evidence, but images are not published in the catalogue.
The repository is used as evidence, but images are not copied into Public/images.
The catalogue cites the repository as evidence while leaving images empty and avoiding license claims beyond the source text.
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 assume reusable image, code, schematic, or PCB rendering rights beyond ordinary source citation.
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 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 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 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.
Hardware claims use the current hardware specification text and repository tree instead of relying on the stale embedded link alone.
The record preserves the voice/audio ambition without overstating default deployed service behavior.
The record preserves verified software-release context and leaves deeper artifact inventory as an archive task.
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 verified hardware/manufacturing evidence while avoiding unsupported claims about badge software behavior.
The catalogue records the verified hardware archive while avoiding unsupported claims about badge applications, games, OTA behavior, or event infrastructure.
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 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 record limits claims to visible physical-credential evidence and official registration context.
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 limits claims to visible physical-credential evidence and event context.
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 limits claims to visible physical-credential evidence and event context.
The record limits claims to visible physical-badge evidence and event context.
The record limits claims to visible physical-badge evidence and official program context.
The record limits claims to visible physical-badge evidence and official event context.
The record is intentionally compact and should be revisited if Bug Bounty Village publishes post-event technical material.
The record keeps hardware and software statements tied to public evidence while avoiding unsupported production-scale and final-firmware claims.
The record keeps hardware, software, and add-on statements tied to public evidence while avoiding unsupported production-scale and final-firmware claims.
The record keeps hardware, USB, LED, and firmware statements tied to the recovered public repository while avoiding unsupported production-scale claims.
The record keeps hardware and firmware statements tied to the recovered public repository and avoids unsupported production-scale claims.
The record preserves verified badge behavior and named-source context without inventing unrecovered electronics, firmware internals, component values, or manufacturing details.
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 treats SAINTCON 2020 as a conservative package-level badge entry instead of inventing unrecovered electronics, firmware behavior, or challenge mechanics.
The record preserves the real BSidesPDX badge without overstating production logistics or publishing unclear media.
The catalogue records the real scanner badge while keeping technical claims limited to the public attendee writeup.
The catalogue records verified hardware behavior and production context without claiming that the complete design archive is public.
The catalogue records verified event, game, mechanical, and optical facts without claiming that the complete design archive is public.
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 record stays anchored to the official write-up and upstream firmware repository without inventing exact board files, pin maps, or firmware modifications.
The record avoids final component, firmware, interaction, and distribution claims until stronger PhreakNIC 27 sources appear.
The record keeps component and behavior claims tied to the recovered firmware, Eagle files, Gerbers, and event archive.
The record avoids claiming a recovered schematic, BOM, final firmware tree, or complete CTF source.
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.
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 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 is useful as a source trail but should be revisited if official pages, ticket text, badge photos, or hardware archives surface.
Sprites remain source evidence for firmware behavior only and are not promoted into `Public/images/`.
The catalogue can cite the official archived event page for bundle contents without depending on a live store page that may change or disappear.
Hardware and software claims remain limited to the public repository files and official talk description.
The record stays narrow and does not invent electronics beyond the official badge-kit language.
The record preserves the artifact while avoiding unsupported claims about hardware design or firmware behavior.
The catalogue can describe observed user-facing badge behavior while leaving schematic, firmware, and manufacturing details for a later badge-team archive.
The catalogue records the verified village badge and leaves hardware/software archaeology for a later source recovery pass.
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 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/speaker wording.
Hardware and firmware claims remain limited to the public repository files and official schedule wording.
Hardware and software claims remain limited to the public repository files and official all-digital event context.
The catalogue preserves the physical badge lineage while avoiding unsupported component-level or reproducibility claims.
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 badge platform and production run while avoiding unsupported firmware, challenge, and component claims.
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 badge lineage without inventing component-level details or open-source 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 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 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 compendium can preserve the source-backed forum artifact without claiming it represents the main DEF CON 12 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.
Country, event, and series pages can show the badge's historical importance without confusing it with the official 1o57 skull badge.
The compendium preserves the community hardware lineage without confusing it with the official DEF CON 25 rubber/plastic identity badge.
The compendium preserves the community hardware lineage without confusing it with the official DEF CON 26 text-adventure badge.
The compendium can show both the official DEF CON 27 badge and the community AND!XOR hardware without merging their lineages.
The compendium treats the artifact as a source-backed community badge template, not as the official event credential or a universal attendee handout.
The catalogue keeps Hackbat as an unofficial DEF CON 32 badgelife record separate from the official RP2350 DEF CON 32 Badge.
The compendium records it as unofficial badgelife and avoids implying GrrCON organizer publication, attendee-wide distribution, or admission-credential status.
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 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 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 game mechanics without implying a real-world botnet or harmful network capability beyond the badge ecosystem described by the project owners.
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.
User-facing wording preserves the practical safety boundary around operating surviving badges or reproductions.