Play surface

Challenges & Games

CTF impact, badge puzzles, scavenger hunts, demoscene contests, game add-ons, and playful app ecosystems gathered from the compendium records.

Resources

Challenge and game links

2026 eChallengeCoin (DEF CON 34)

AoSC maker project page

2026 eChallengeCoin

Primary maker page for the 2026 planned 40-brass-coin statement, terminal text adventure, the page's Micro-USB/one-touch-pad/three-NeoPixel-group/speaker/no-battery/46-gram claims, Choose Your Own Charity context, U.S. mail or DEF CON pickup wording, and the linked CircuitPython build. Its product and promotional media do not state reusable-image rights.

2026 eChallengeCoin (DEF CON 34)

AoSC organizer form and fulfillment page

Choose Your Own Charity eChallengeCoin Submission

Primary organizer form explaining that a $100-or-greater youth-STEM-charity donation may receive a 2026 coin, with U.S. mail or in-person DEF CON pickup options. It contains an upload flow for donation proof but does not publish a privacy, data-retention, tax, charity-verification, delivery, or final-allocation policy.

FightDystopia 2025 Badge (DEF CON 33)

BigTaro Tindie product listing

FightDystopia 2025 Badge

First-party seller listing for the FD-party framing, $150 price, sold-out-since-August-11-2025 display, user-defined BLE-MAC-address detection claim, ESP32-S3/two-PCB/screen/12-RGB-LED surface, CTF/puzzle/bling/GIF/lanyard/sticker claims, and product name. Its images do not state a reusable license or explicit permission basis.

FrogStar Badge (DEF CON 33)

BigTaro Tindie product listing

FrogStar Badge

Seller listing that calls FrogStar an electronic badge, describes its CTF, game, round display, and two-SAO surface, and says it was a Defcon pickup preorder with leftovers to be posted after the con. The listing does not establish completed payment, pickup, shipment, attendee allocation, official issuance, or image reuse permission.

Submarine Badge & Pirate SAO (DEF CON 33)

BigTaro Tindie product listing

Submarine Badge & Pirate SAO

First-party seller listing for the $150 Defcon-pickup preorder language, underwater/CTF narrative, hardware and software puzzle framing, soldering challenges, round-display/button/SAO/GPIO claims, Pirate Flag SAO bundle, Gunslinger-B-Gone interaction, and product name. Its images do not state a reusable license or explicit permission basis.

FrogStar Badge (DEF CON 33)

BigTaro Uberflux product listing

FrogStar Badge

Live marketplace listing for BigTaro's FrogStar Badge. The reviewed listing gives the $80 / seven-sold / 23-remaining seller snapshot, DEF CON 34 drop label, USPS Flat Rate $11 shipping, and recurring CTF/game/two-SAO description. Product media have no stated reusable license or explicit permission basis.

Masonic33 Indie Puzzle Badge (DEF CON 33)

DEF CON 33 vendor product list

Hacker Couture DEFCON 33 Product List

Nineteen-page Hacker Couture product-list PDF headed DEFCON 33 that lists Masonic33 Badge at $125 and describes a cryptic analog-input/hidden-LED-sequence puzzle, esoteric 33rd-degree theme, custom package, and bonus merchandise. It establishes a vendor-list association, not completed sale, organizer issuance, or image reuse permission.

Masonic33 Indie Puzzle Badge (DEF CON 33)

Hak4Kidz Lab Tindie product listing

Masonic33 Indie Puzzle Badge - Hak4Kidz

Primary maker listing for the independent $125 Masonic33 puzzle badge, its ATtiny1616, two 10 kΩ potentiometers, eleven LEDs, UPDI interface, AAA power, four-puzzle/hidden-sequence claims, dimensions, and custom VHS-style package. Its images do not state a reusable license or explicit permission basis.

Puzzled Hackers LED Badge (DEF CON 34)

Puzzled Hackers Team community announcement

r/DEFCON Meetup Post #4 — Final Badges and Information

Contemporaneous announcement signed by the Puzzled Hackers Team. It corroborates the CTF-account free-redemption route, top-50 eligibility statement, capped paid allocation, post-cap giveaway intent, meetup/QR handoff terms, free badge-optional meetup model, location, dates, and the statement that an actual DEF CON badge is not needed for the Wednesday gathering. Reddit media is not a reusable image grant.

AND!XOR DC27 Badge

add-on documentation

AND!XOR DOOM SAO log

Primary add-on source for the ATSAMD21G18A DOOM SAO, SAO v1.69bis logical integration, serial terminal, DOOM Guy interface, bus sniffers, virtual EEPROM identity, and DC27-badge compatibility context.

Tildagon

app-store entry

EMFight app

App-directory entry for a badge fight game that lets EMF Camp badge holders challenge each other.

Tildagon

app-store entry

TILDENSTEIN 3D app

2026 app-directory entry for a Wolfenstein-style ESP-NOW multiplayer raycasting game.

DEF CON 23 Badge

article

DEF CON 23 record badge article

Contemporary article documenting LostboY / Ryan Clarke authorship, playable vinyl record format, role-color variants, secret alphabets, inner-groove markings, and analog puzzle clues.

DEF CON 21 Badge

article

Hackaday at DEF CON 21

Contemporary field report naming Ryan Clarke as badge designer and documenting the non-electronic-electronic PCB playing-card design, copper/soldermask/silkscreen artwork, XOR gate, and crypto challenge.

DEF CON 20 Badge

article

WIRED DEF CON 20 badge reveal

Contemporary article documenting Ryan Clarke's design goals, embedded game, cryptography, badge variants, IR interactions, free/open software, VGA expansion, and secret-society story.

LCA2017 IoTuz ESP32 Board

attendee technical writeup

IoTuz Arduino driver writeup

Marc Merlin's technical writeup documenting board bring-up challenges, TFT/touchscreen, APA106-style LEDs, I/O expander, IR receiver, joystick, BME280, accelerometer, rotary encoder, and full-demo driver work.

BSides Goa 2024 SecOps Hackable Badge

badge challenge page

SecOps Hack the Badge

Primary badge source documenting Hackable BCPen and CPen badges, BSides Goa 2024 booth/free-exam context, pre-programmed badge behavior, LED/button components, binary-code unlock path, and Vulnmachines challenge flow.

SAINTCON 2018 ESP32 Badge

badge documentation

SAINTCON 2018 badge README

Primary badge documentation for ESP32, MicroPython, 8x32 LED matrix, three buttons, twelve minibadge spots, rechargeable battery, flashing, charging, menu behavior, Wi-Fi configuration, Hacker Challenge score, and uPyCraft editing.

HITCON 2025 PCB Badge

badge guide

HITCON 2025 PCB Badge guide

Official 2025 badge guide documenting name editing, score display, Hacker Pet, Tetris, Dino, Snake, Red-vs-Blue tower capture, Re:CTF badge-ID binding, cross-board interaction, and BadUSB behavior.

AND!XOR DC28 Badge

badge manual

AND!XOR DC28 RTFM

Primary manual source for the STM32F412RET6, OLED, ST7735 TFT, APA-102C LEDs, BlackBerry Q10 keyboard, USB-C, battery holder, inspectAR workflow, key bindings, BENDERPISS CTF, and source-release links.

Bug Bounty Village DC33 BBV Badge

badge page

BBV Badge 2025

Official badge page documenting four buttons, four LEDs, sponsor challenge legs, binary flag entry, hardware-hacking acknowledgement, volunteer reward flow, and Discord support path.

JD-HITBSecConf2018 Beijing Badge

badge village page

HITB Beijing Badge Village

Official CommSec Village source for the special-edition HITB2018PEK badge, Badge Village hacking path, mini-games, hidden challenges, open-source statement, hardware notes, USD35 limited visitor purchase path, and JD Security Geek Village context.

NoNameCon 2019 NoNameBadge

badge-team writeup

NoNameBadge 2019 making-of

TechMaker badge-team post documenting the Ukrainian NoNameCon hardware badge budget, ESP32 platform choice, prototypes, production batch, assembly workflow, firmware/CTF story, solved counts, and post-event reset update.

DEF CON 29 Badge

challenge writeup

DEF CON 29 badge writeup

Science Viking Labs source documenting the pre-con clues, challenge hint flow, SAO and IR observations, Morse and serial material, and badge solving path.

Seasides 2026 Roulette Badge

commit-pinned maker documentation

Seasides 2026 Roulette Badge README

Primary maker documentation for the 300-plus live-assembly statement; ATtiny85, 74HC595, eight-LED, UART, EEPROM, animation, eight-stage CTF, and author claims. The README's voltage labels and build guidance do not establish a final production-unit power configuration, safety review, or distribution ledger.

Masonic33 Indie Puzzle Badge (DEF CON 33)

current BadgeLife Village schedule

DEF CON 34 BadgeLife Village Schedule

Badge.Life's live 2026 Village Schedule lists Masonic33 Badge — heal at 10:30 AM Friday August 7 and 11:00 AM Saturday August 8. It documents planned current village appearances, not a changed board or revision, price, allocation, official DEF CON issue, admission, completed handoff, or image rights.

Wordweaving Badge (DEF CON 34)

current maker marketplace product page

Wordweaving Badge live marketplace listing

Maker-controlled Uberflux listing and serialized public payload for the $120 100-unit presale, observed 41-sold snapshot, DEF CON 34 pickup / post-con shipping statement, source-stated at-con $140 plan, RP2350/4 MB/16-LED/display/LiPo/USB-C/SAO claims, game/multiplayer/soldering claims, and post-con documentation/stub-firmware promise. Product media has no stated reusable license or permission basis.

DEF CON 32 Badge

design and firmware assets

DEF CON 32 badge media-server directory

Official media-server source for assets.zip, Badge_Game_Music_v2.zip, badge_readme.txt, DC32 HW.zip, DC32BadgeGame.zip, DEFCON-32-BadgeFirmware-main.zip, and FREEWiLi firmware documentation.

NorthSec 2022 Badge

event lineage

NorthSec past editions

Official NorthSec source documenting 2022 as the return-to-in-person edition at Marche Bonsecours, with livestreamed conference and remote-first CTF with in-person option.

HITCON CMT 2017 MediaTek Badge

event page

HITCON CMT 2017 events

Official event page documenting HITCON Badge Challenges, MediaTek-powered electronic badge features, Hackermon and Snake challenges, conference-day badge sale language, and repair-station context.

X-CTF 2016 Badge

event page

X-CTF 2016 event page

NUS Greyhats page documenting X-CTF 2016 as a cyber-security competition at NUS School of Computing on June 18, 2016 after online qualifiers.

Hackers Teaching Hackers 2026 Eagle 5 Badge

firmware and hardware overview

Eagle 5 firmware README

Primary source for the nRF52840-QIAA, SX1262, 74HC595, nine single-color LEDs, RGB wing, dual USB CDC, RNode/Reticulum, CLI, LED-animation, CTF, and GPLv3 firmware statements. It also embeds a badge photo whose image-specific attribution/provenance is insufficient for local publication.

rad1o

firmware binaries

binary-cccamp2015

Binary package for flashing rad1o without the full dependency stack, including camp, HackRF, l0dable, font, image, and game assets.

X-CTF 2016 Badge

firmware repository

geekman/badger

Public firmware repository for the X-CTF 2016 badge, including Arduino-style ESP8266 code, LCD, Wi-Fi scanner, applet, challenge, and game modules.

BSidesPDX 2015 Badger Badge

firmware source

badger.ino

Firmware source for ESP8266 Wi-Fi includes, BadgerNet naming, embedded BSides PDX 2015 Badger web UI, HTTP handlers, LED pins, and CTF flag behavior.

H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)

first-hand H4irl1n3 M0gg3r5 project announcement

Zombie Badge Info Dump

A contemporaneous source authored by u/zer0patient and signed H4irl1n3 M0gg3r5. It directly names the two-object ESP32-S3, IR, NFC, BLE, buzzer, firmware-CTF, backend, team-roaming, Cure Station, medkit-prop, and brain-in-a-jar SAO claims for DEF CON 34. Its embedded images have no stated reusable license or explicit permission basis.

MF Doom SAO v2 (DEF CON 34)

first-hand maker announcement and pre-event sale thread

MF Doom SAO v2

Public post by the source-named u/Truth-Miserable that calls the item MF Doom SAO v2, says an original had a limited run the prior year, and says v2 parts will be surface mounted. Later comments state a $20 price plus direct-message preorder and local-handoff intent. The thread does not identify a full circuit, final product revision, final inventory, completed payment, completed handoff, or media reuse rights.

BSides Cape Town 2019 Badge

first-hand making-of writeup

BSides Cape Town 2019 Making a badge

Tony Mamacos first-hand post documenting the 2019 badge hardware, ESP32 processor, colour IPS display, touch buttons, 18650 battery, 3D-printed case, firmware architecture, game content, WiFi high-score flow, Bluetooth controller experiment, and post-event lessons.

BSides Prague 2025 Electronic Badge

first-hand organizer writeup

BSides Prague organizer retrospective

Hung Ngo organizer retrospective documenting the 2025 first-generation electronic badge, rotary-telephone inspiration, attendee chips, challenge XP, reversible chip software, interactive panels, nickname display, named badge creators, and more than 550 attendees.

RootedCON 2026 Pacman Badge

first-hand project-builder write-up

TechFrontiers RootedCON 2026 badge CTF write-up

David Melendez Cano's public TechFrontiers write-up describes building the PACMAN Ghost attendee boards, their color variants, ESP32-WROOM-32, LiPo/UVLO/USB-debug surface, ESP-NOW CTF architecture, and signed question/answer model. It is direct builder evidence, not an official RootedCON source release or a reusable-image grant.

Ouroboros Badge (DEF CON 34)

first-party K Badges Tindie product listing

Ouroboros Badge #BadgeLife

Maker-controlled product page for the $29.99 August 4, 2026 out-of-stock snapshot, tentative new-order/DEF CON statement, CH32V003, bare-metal RISC-V-assembly, UART-game, 12-LED Charlieplex, circular single-layer exposed-board, two-AA, and maker-described cryptographic/performance claims. Its product media has no stated reusable license or explicit permission basis.

Ouroboros Badge (DEF CON 34)

first-person maker announcement

Little Project Badge - Ouroboros Badge

Public r/Defcon post in which Material_Opinion_321 says they created Ouroboros as a CH32V003 pure-RISC-V-assembler project with a custom UART game, links the Tindie listing and technical explainer, and describes possible buyer-arranged DEF CON pickup. It does not establish a completed sale, delivery, official event relationship, access role, or reuse rights in Reddit media.

AND!XOR DC25 Badge

game documentation

AND!XOR DC25 BOTNET game log

Primary log describing the badge-to-badge BOTNET game, activation, badge-net repeating behavior, airplane-mode opt-out, services, firewall rules, exploits, XP, and points.

HITCON 2025 PCB Badge

hardware and firmware source

HITCON PCB Badge repository

Public repository documenting firmware, PCB, backend, base-station, game, web, and software project trees; README notes STM32CubeIDE firmware workflow, hardware-version selection, V2.2 2025 attendee hardware, IR, LED, button, and cross-board USART timer/DMA details, and BSD-3-Clause licensing.

X-CTF 2016 Badge

hardware repository

jellyjellyrobot/neander

Public hardware repository preserving Eagle board and schematic files, BOM notes, libraries, and sponsor image assets; no top-level GitHub license was detected during the 2026-05-21 recheck.

Div0 Tingkat eBadge (DEF CON Singapore 2026)

immutable firmware source

Div0 Tingkat eBadge commit-pinned firmware

The pinned source imports Raspberry Pi Pico SDK headers and exposes serial-menu, LED, OLED, and challenge modules. Its menu banner says SINCON 2026 BADGE, producing a material identity conflict with the DEF CON Singapore repository title. The source file is not treated as a final-unit firmware map or an instruction set for readers.

Div0 Tingkat eBadge (DEF CON Singapore 2026)

immutable maker documentation

Div0 Tingkat eBadge commit-pinned README

The pinned README calls the artifact Div0 Tingkak eBadge and says the repository contains source code and relevant files used in the badge. It documents old/new firmware wording, a USB/serial challenge context, artwork, source, SAO, and UF2 directories; it does not name the organizer, a distribution channel, final hardware, a completed handoff, or a license grant.

iFixit SAO (DEF CON 34)

immutable maker technical documentation

iFixit SAO 2026 commit-pinned README

The pinned README calls the project a 2026 iFixit Shitty Add On, documents its high-level LED, soldering-challenge, ATtiny1604, PlatformIO/Arduino, and KiCad surface, and names the source-declared collaboration. It is technical project documentation, not a final production, allocation, or operating-instruction guarantee.

2026 eChallengeCoin (DEF CON 34)

independent current-event index

DEF CON 34 Planning Highlights

DEF CON.outel.org's independently maintained planning index lists 2026 eChallenge Coin / eChallengeCoin entries among current DEF CON 34 items. It corroborates public current-event discovery only; it is not official DEF CON issuance, a complete technical source, fulfillment proof, or image-rights grant.

Masonic33 Indie Puzzle Badge (DEF CON 33)

maker and nonprofit profile

Hak4Kidz Lab Tindie profile

Public maker profile describing Hak4Kidz Lab as the research-and-development department of Hak4Kidz NFP, a 501(c)(3) public charity, and stating that proceeds support its mission and ethos. It does not establish product manufacturing, final distribution, technical completeness, or image reuse permission.

FrogStar Badge (DEF CON 33)

maker project and technical page

BigTaro's FrogStar 2025 Badge

Maker-owned page that calls FrogStar an unofficial DEFCON badge, lists its RP2350, GC9A01 round LCD, two SAO V1.69bis ports, WS2812B RGB LEDs, IR receiver, six buttons, CTF/game framing, and Firmware v1.0. Its images and artwork do not state a reusable license or explicit permission basis.

Submarine Badge & Pirate SAO (DEF CON 33)

maker project page

BigTaro's Submarine Badge

Maker-owned Submarine dashboard-like page that links the badge back to BigTaro's store and maker communication channels. It supplies project identity and a current maker-owned surface, but does not publish the electrical design, firmware, challenge system, distribution outcome, or reusable-image permission.

Cult of Cthulhu Indie DEF CON 34 Badge

maker storefront listing

Cult of Cthulhu Indie DEF CON 34 Badge

Pfarrside Creations' badge-only product listing for the independent DEF CON 34 badge. It states the ESP32, USB-C, rechargeable Li-Po, screen, ten-LED, one-button, story/game, badge-role, badge-to-badge, and seller-stated US-only shipping context. Product media is evidence only and carries no stated reusable-image permission.

PWNEDCR 0x08 Electronic Badge

named post-event account

Best of PWNEDCR 0x08

Fluid Attacks' named post-event account is the recovered artifact-level source for PWNEDCR 0x08. It documents the 2025 event context, a physical electronic badge that attendees hacked through the CTF, and hidden Easter eggs/challenges. It publishes no technical archive or badge-maker credit; its generic Unsplash skull visual is not a factual badge photo or reusable-image basis.

BadgeLife Village Badge (DEF CON 34)

official BadgeLife badge documentation

BadgeLife Village Badge DC34 documentation

Badge.Life's DC34 guide identifies Badgey Bodgerton, the RP2354/LED/button/SAO/infrared/USB-C/18650 surface, user-installed challenge parts, and high-level recovery documentation. It does not establish DEF CON issuance, allocation, final production, safe assembly, firmware availability, or image reuse.

NorthSec 2026 Badge

official CTF page

NorthSec 2026 competition page

Official competition page whose retained 2026 Solarpunk section says the hackable electronic badge was fully integrated into the CTF, with point-bearing badge challenges and on-site badge-firmware tampering among physical tracks.

2026 eChallengeCoin (DEF CON 34)

official CircuitPython board profile

Bradán Lane STUDIO Coin M0

Official CircuitPython profile linked by AoSC as the eChallengeCoin-specific build. It identifies ATSAMD21G1A/4 MB flash, three RGB-NeoPixel groups, three capacitive touch pads, one speaker, CircuitPython/Arduino support, and native USB-C—details that conflict with the maker page's Micro-USB and one-touch-pad wording rather than settle it.

h-c0n 2026 CTF BADge

official agenda page

h-c0n 2026 agenda

Official agenda page corroborating February 5 workshops, February 6 workshops and talks, and February 7 talks in the Madrid h-c0n 2026 programme.

h-c0n 2026 CTF BADge

official badge announcement

CTF BADge #hc0n2026

Official badge-specific announcement for the electronic CTF BADge, development-board claim, David Reguera / Dreg credit, pickup timing, CTF window, prizes, wait-list, and 10 EUR in-person extra-badge note.

Disobey 2026 Badge

official badge docs

Disobey 2026 badge page

Official badge page documenting delayed 2025/2026 badge arrival, care warning, power, controls, OTA setup, competitions, firmware, CTF station, web flashing, and third-party firmware links.

AvengerCon IX Electronic Badge

official badge guide

AvengerCon IX badge page

Primary badge source for the four-challenge CTF, A-C-9 blink behavior, BAT CON battery jumper, micro-USB path, CP2102 USB-to-UART serial access, 9600-baud PuTTY workflow, post-event unlock codes, and battery-safety instructions.

SAINTCON 2017 Raspberry Pi Badge

official badge page

SAINTCON 2017 badge page

Official badge page documenting the Raspberry Pi Zero W badge, custom board, TFT display, SNES-style controls, MiniBadges, Hacker Challenge registration, build-session framing, and post-conference RetroPie possibility.

THcon 2026 Badge

official badge page

THcon 2026 B.A.D.G.E. page

Official dedicated badge page documenting the ESP32-C6 electronic badge, the Badge3000 WiFi access point, the I2C OLED, and the BLE padlock and one-time-password challenges.

AND!XOR DC34 5N4CK3Y Badge

official badge project and distribution page

AND!XOR DC34 Philanthropist Badge

AND!XOR's official DC34 5N4CK3Y philanthropy-sale page. It establishes the real badge, limited philanthropy units, BENDER challenge schedule, planned activation-instruction timing, planned shipping/no-pickup terms, and stated giveaway model. Product imagery is evidence only, not a reuse license.

RVA5sec 2016 Badge

official badge-team interview

HackRVA 2016 badge interview

Official HackRVA interview documenting the 2016 badge, team process, production quantity, USB reflashing, CTF focus, and serial-transmission experimentation.

HackNWA 2026 VIP Assembled Badge

official conference page

HackNWA 2026: Holiday in Scambodia

Official event page for the April 17, 2026 Bentonville cybersecurity conference. It establishes the event and its advertised CTF, ASMb1337, and hardware-hacking context, but does not describe the VIP Assembled Badge ticket category or its contents.

THOTCON 0xD Badge

official contest page

THOTCON 0xD contests

Official contest source documenting Gold Badge-eligible contests and the badge contest instruction to read the program, solve the puzzles, and hack the badge.

NorthSec 2015 Team Hardware Badge

official event archive

NorthSec past editions

Official NorthSec source documenting the 2015 Bonsecours edition, 54 teams, team-of-eight CTF structure, and hardware badges used for network, IPv6, RF-monitoring, smartcard, and related challenge paths.

CypherCon 2017 Cube Badge

official event history

CypherCon history

Official CypherCon history source for CypherCon 2.0 dates, Discovery World venue, attendee count, Game of Life / Hacker Glider theme, The Cube badge, TYMKRS attribution, and badge-creator panel listing.

RVAsec 2018 Badge

official event layout

RVAsec 7 layout

Official RVAsec 7 layout source for Richmond Marriott event context, including HackRVA badge-hacking and CTF room placement.

Adversary Village DEF CON 34 Volunteer Badge

official event page

Adversary Village at DEF CON 34

Adversary Village's official current event page identifies the August 7-9, 2026 Las Vegas Convention Center setting, calls this its sixth year at DEF CON, and describes talks, workshops, demos, and CTF context. It establishes event context, not volunteer-badge form, technology, allocation, handoff, or credential mechanics.

RomHack Camp 2026 Badge

official event page

RomHack Camp 2026

Current public event page advertising the October 2-4, 2026 RomHack Camp at Flaminio Village and its unique hardware badge / collectible challenge.

THcon 2026 Badge

official event page

THcon 2026 official site

Official THcon source for the May 5-6, 2026 tenth edition talks at the Marthe Condat auditorium, Paul Sabatier University, Toulouse, with the on-site CTF on May 7 at ENSEEIHT.

h-c0n 2026 CTF BADge

official event page

h-c0n 2026 home page

Official Hackplayers h-c0n home page for the 5-7 February 2026 event dates, Hackplayers conference framing, and navigation to agenda, location, and ticketing.

Greycademy 2026 Hackbadge

official event recap

NUS Greyhats Greycademy 2026 recap

Post-event NUS Greyhats account of the completed program, collaboration with CSA's A.YCEP, two days of training, CTF work, 78 challenges, 60 finalists, and 3,526 captured flags. It does not document a specific badge unit or distribution ledger.

PhreakNIC 27 Planned MK.II ESL Badge

official event site

PhreakNIC website

Official PhreakNIC website used as the live event-lineage anchor while the planned PN27 badge remains pre-event; the current page advertises preregistration and challenge coins, not final PN27 badge specifications.

Hak4Kidz Chicago 2026 Fun Badge

official flyer

Hak4Kidz 2026 flyer

Primary official badge-specific source: the flyer says youth attendees receive a fun badge alongside lunch, snacks, a T-shirt, and prizes. It does not identify the artifact's material, technology, adult or chaperone eligibility, CTF linkage, individual issue, or delivery.

DEF CON 25 Badge

official forum feedback

DEF CON 25 feedback thread

DEF CON forum feedback source describing rubber badges, lack of an official badge challenge, badge-line experience, and short-lead-time production context.

h-c0n 2026 CTF BADge

official location page

h-c0n 2026 location page

Official location page for the Madrid venue trail, including Centro Cultural Sanchinarro at Princesa de Eboli 29 and Exe Madrid Norte workshop/hotel context.

Laser* Tag Badge DS (DEF CON 34)

official maker page

Laser* Tag Badge DS official maker page

Dani Weidman's project page for the 2026 DEF CON 34 Laser* Tag Badge DS. It documents the planned hardware, IR game, conditional LoRa/QR scoring model, pickup context, production caveats, and named project help. Its images are evidence only, not a reuse license.

Wordweaving Badge (DEF CON 34)

official maker project page

Wordweaving Badge

BigTaro's project page for the Wordweaving Badge, describing the Game Boy-inspired top-down adventure framing, 30-plus CTF puzzles, rechargeable battery, unlockable LEDs, multiplayer, RP2350, 128x128 OLED, up-to-50-badge link claim, and public links to Uberflux and Tindie. The page's badge images and game screenshots carry no stated reusable license or explicit permission basis.

BSides Nashville 2026 Challenge Coin

official organizer channel

BSides Nashville organizer updates

The official organization feed contains post-event 2026 activity and re-shares an attendee account thanking BSides Nashville and SkillBit for coins. It corroborates attendee-side coin receipt without supplying a complete distribution ledger or physical specification.

HackNWA 2026 VIP Assembled Badge

official organizer social announcement

HackNWA 2026 organizer announcement

HackNWA's official LinkedIn post announces the April 17 event, venue, CTF, Solder Village, and Badge/Hardware Hacking activity. It supports conference context only; it does not identify a badge design, ticket tier, or technical specification.

FloridaMan 2026 Badge

official party storefront

FloridaMan 2026 storefront

Official storefront branding FloridaMan 2026 as a Florida-themed party at DEF CON and stating badge-only venue entry plus a live hacking challenge/scoreboard. Its product media uses filenames explicitly labelled Gemini_Generated_Image and is not copied or published.

Puzzled Hackers LED Badge (DEF CON 34)

official team CTF checkout page

Puzzled Hackers DEF CON 34 LED Badge

Puzzled Hackers' own CTF checkout page naming a limited-edition LED badge for DEF CON 34, its $20 including-tax listing, August 5/6 Linq pickup labels, no-shipping requirement, receipt/offline QR claim flow, and sold-out online allocation state. Its badge photo has no stated reusable license or explicit permission basis.

SECCON 2026 PCB Badge

official ticket page

SECCON 2026 tickets

Primary official ticket source for VIP and individual pass inclusion of a PCB badge with CTFs and features, limited to the first 180 registrants.

NorthSec 2022 Badge

official writeup index

NorthSec competition write-ups

Official NorthSec write-up index rechecked for 2022; it preserves 2022 CTF writeups but this pass did not find a badge-specific 2022 firmware, event-guide, or conference-badge writeup.

DOJOConf Panamá 2026 Electronic Badge

organizer-controlled public update

ComunidadDOJO public organizer profile and CTF update

ComunidadDOJO's public company profile is the organizer-controlled source page through which the 2026 CTF update was recovered in this source pass. The update says the 2026 DOJOConf badge will be useful in the CTF. It does not disclose the CTF mechanism, firmware, challenge material, eligibility, pickup result, or image-reuse permission.

SAINTCON 2015 Wi-Fi Show Badge

partner badge write-up

Badges? We got badges!

Cisco source documenting SAINTCON's purpose-built Wi-Fi enabled show badges, 2.25 inch LCD screen, buttons, 550-attendee scale, Cisco CMX integration, schedule display, live Hacker Challenge score, and venue-zone awareness.

Open Sauce 2026 Badge

physical build, software, and event-hacking record

Open Sauce 2026 Badge README

Primary source for the Arduino MKR Zero-compatible badge, documented physical components, optional headers, Bop It firmware context, native source tree, and statement that attendees created four games after Saturday badge hacking.

Open Sauce 2026 Badge

post-event community firmware archive

Open Sauce attendee game examples

Designer-published folder referenced by the README for code from attendees who hacked badges during the festival. It corroborates a post-event community-hacking trail but does not identify each person's full role or a deployed production image.

h-c0n 2026 CTF BADge

post-event write-up

h-c0n 2026 CTF write-ups recap

Hackplayers post-event recap for the hardware-hacking CTF, naming badge co-creators, describing the repository's firmware/tooling scope, and linking the first three winner write-ups without providing reusable badge-image rights.

CPEC DC34 MechBattle Badge

primary in-progress badge source

CPEC DC34 MechBattle source repository

CPEC's public repository explicitly calls this the DC 34 MechBattle Badge and the second iteration of menu/game logic for a CPEC DC34 badge offering. Its README says the work is not final; the GitHub description calls it a DEFCON 34 Mech Badge by CPEC. It does not establish a physical board, allocation, final firmware, event authorization, or image-reuse basis.

CPEC DC34 MechBattle Badge

primary in-progress game source

CPEC DC34 MechBattle Game source

CPEC's public in-progress PlatformIO game repository targets an Adafruit Feather ESP32-S3 no-PSRAM board and contains display, BLE, QR, sound, menu, and game modules. Source code is evidence of intended software work, not proof that it was deployed on a physical badge, used at DEF CON, secure, privacy-preserving, compatible, or licensed for reuse.

AND!XOR DC25 Badge

project log

AND!XOR DC25 badge postmortem

Primary retrospective log for team expansion, design goals, BMD-300 selection, display/LED/regulator production context, S132 firmware base, activation code, bling, games, production quantities, and source-release caveats.

AND!XOR DC28 Badge

project page

AND!XOR DC28 Badge project

Project-owner Hackaday.io source for DEF CON 28 pandemic-cancellation context, distributed free badge-drop framing, bling, embedded CTF, MyBASIC hardware scripting, Slack/scoreboard links, team roster, sponsors, and project logs.

DEF CON 17 Badge

project page

DEFCON 17 badge project page

Primary designer page with MC56F8006, MEMS microphone, RGB LED, operating states, production quantity, role-shape puzzle, documentation, source-code, and contest details.

DEFCON China 1.0 Badge

project page

DEFCON China 1.0 badge project page

Grand Idea Studio project page documenting the first official international DEFCON badge, flexible PCB, tree game, USB, accelerometer, CR2032 power, 3,300-unit production, role variants, CC BY 4.0 design license, and documentation links.

Disobey 2026 Badge

project-author portfolio

CyberSlayer project page

Piia Alavesa's project page identifies CyberSlayer as a Disobey 2026 electronic-badge game and links the separate badge-game source repository.

THOTCON 0xD Badge

project-owner writeup

THOTCON 0xD Badge project

Hackaday.io source for Fourfold's 2,000-unit badge build, ESP32, ST7789 TFT, capacitive touch wheel, buzzer, six LEDs, LiPo battery, add-on header, firmware/game/challenge scope, production fixtures, packaging, and sub-$20 BOM target.

The Shattered Shard (DEF CON 34)

public badge challenge-player documentation

The Shattered Shard Player Guide

Primary public source for the badge/battery, local Wi-Fi/browser, data-USB, serial-terminal, labelled-SAO, LED-panel, sequential-quest, and assigned-badge-only interaction surface. It is intentionally linked as a player guide without repeating credentials, endpoints, flags, challenge hints, exploit steps, serial commands, or reset procedures in the catalogue.

BSides Newcastle 2025 Space Badge

public badge source archive

BSides Newcastle 2025 Space Badge repository

Punk Security's public repository identifies the Space Badge for BSides Newcastle 2025, explains its Morse-code venue game, and preserves board, schematic, EasyEDA, Gerber, artwork, firmware, manual, and sign material. It is a source archive, not a per-unit production, safety, or delivery ledger.

Portal Badge (DEF CON 34)

public design documentation

Portal Badge design document

The public project `design.docx` describes Standby, Game, and Nyan modes; the four-level sphere/portal/fire game; Portal Gun SAO, badge-to-badge USB, and solder-on unlock ideas; and associated sound/light behavior. It is design evidence, not a final production, licensing, or event-distribution specification.

h-c0n 2026 CTF BADge

public firmware and write-up repository

therealdreg/hcon2026hwctf

Public MIT-licensed repository for the HC0N 2026 hardware CTF, including the ctf.uf2 firmware, RP2350/RISC-V notes, serial and picotool workflows, debugging requirements, and winner write-ups.

Portal Badge (DEF CON 34)

public firmware repository

ch32fun-portal-badge

Public CH32V303 firmware project with PlatformIO configuration, C source, sound and game modules, August 2 final-code-check commit, and an embedded design document. GitLab reports no detected project license and no release is published.

The Shattered Shard (DEF CON 34)

public independent challenge-badge repository

BigDawgDave/The-Shattered-Shard

Public GitHub repository whose description calls it the public repository for a DEF CON 34 RM-Cyber challenge badge named The Shattered Shard. The reviewed root exposes a Player Guide only. It establishes a distinct source-backed pre-event challenge-badge project, not RM-Cyber, DEF CON, or organizer authorization; a complete hardware/firmware archive; manufacture; allocation; delivery; or image-reuse rights.

MF Doom SAO v2 (DEF CON 34)

public maker self-submission roster

DEFCON 34 Badgelife Form (Responses)

Public DEF CON 34 response from Rex that marks MF Doom SAO v2 as an update to an existing SAO, says Coming soon, gives a $20 price, and names u/Truth-Miserable as the Reddit contact. It supports a planned independent event association, not a final product specification, completed sale/delivery, official DEF CON issue, or image-reuse permission.

Masonic33 Indie Puzzle Badge (DEF CON 33)

public schedule mirror

Recovered DEF CON 33 schedule

Recovered public DEF CON 33 schedule PDF that records a 10:30-10:59 PDT BadgeLife Community Masonic33 Badge drop credited to Heal-Hak4Kidz. It establishes a published scheduled activity, not event issuance, stock, attendance, completed handoff, or image rights.

Aerospace Village DC34 SR-71 CTF Badge

public team self-submission roster

DEF CON 34 BadgeLife public roster

The publicly readable roster's 2026-08-04 SR-71 row is submitted under Lockheed Martin - Aeronautics Cyber Range (ACR). It calls the item a new Badge, says it is only winnable through an ACR CTF at the Aerospace Village booth and on Discord, describes the NFC TCG/card-collection raffle, and says code or firmware will be available after the con. It is a pre-event self-submission, not a DEF CON, Aerospace Village, or corporate authorization statement.

AvengerCon VIII 8-8-8 Badge

public-affairs article

AvengerCon VIII Army Cyber article

U.S. Army public-affairs source for the February 28-29, 2024 Georgia Cyber Innovation & Training Center event, first AvengerCon electronic 8-8-8 badge, scavenger-hunt behavior, LED-code path, hack-bypass path, more-than-300 badge build, and Capt. Richard Shmel credit.

REcon 2026 Badge

release page

recon2026-v1 release

Tagged release with pre-built firmware and release notes documenting the LoRa radar, chat, and flags, NFC flag-hunt, magspoof, Simon, USB CLI, hidden reversing challenge, and Konami-code easter egg.

HOPE XV Electronic Badge

schedule

HOPE XV schedule

Official schedule source for ongoing Electronic Badge Hacking and The Badge Clinic entries, presenters, village context, and badge-support framing.

GreyCTF Summit 2025 GreyBadge

setup and hardware guide

greybadge25 README

Repository README documenting GreyMecha/Army, CircuitPython setup, hardware ordering notes, FPGA tooling, repository structure, and links to badge manual/talk slides.

SAINTCON 2019 Enigma Badge

source

SAINTCON 2019 badge README

Raw README source for post-event challenge use, DFU flashing, STM32CubeProgrammer, ST-Link V2 development, firmware directories, FPGA Icestudio source, and warning that flashing erases badge memory.

REcon 2026 Badge

source repository

badge-recon-2026 repository

Electronic Cats repository for the REcon 2026 badge, with full KiCad hardware design under CERN-OHL-1.2 and firmware under AGPL-3.0, documenting the CH32V203 primary, RP2040 daughterboard, SX1262 LoRa, PN7150 NFC, SSD1306 OLED, and challenge surface.

BSides Des Moines 2026 Badge

source repository

bsidesdsm26 repository

iot-pwn repository for the BSides Des Moines 2026 badge firmware, published under GPL-2.0, documenting the CH585 RISC-V NFC badge, the flash station provisioning tooling, and the three-layer CTF.

CPEC DC34 MechBattle Badge

source-linked draft design document

M.E.C.H. Fighters draft game mechanics

The first CPEC repository links this document as game-play mechanics material. It supplies draft creative context only and does not establish final gameplay, technical implementation, event programming, distribution, or rights in any media.

Disobey 2026 Badge

third-party badge game

CyberSlayer badge-game source

Piia Alavesa's public, work-in-progress MicroPython game repository for the Disobey 2025/2026 badge; it documents gameplay, the board interface it uses, mpremote installation, and a development loader.

Disobey 2026 Badge

third-party firmware library

Disobey 2026 Rust badge library

MIT-licensed Rust support library for the Disobey 2026 badge with ST7789 display, GPIO button, WS2812 LED, backlight, vibration, games, demos, peripheral examples, and name-tag behavior.

DEF CON 24 Badge

writeup

DEFCON 24 badge writeup

Technical challenge writeup documenting room keys, standee glyphs, hidden traces, silkscreen strings, Konami serial dump, lanyards, conference CD, and program equations.

Lifecycle

Game, puzzle, and CTF surfaces

Fri3d 2024 Badge current/historical

BadgeLink game add-on

Big Flamingo Gun 9000

The Flamingo blaster uses an IR LED, two IR receivers, four WS2812 LEDs, a buzzer, trigger, team selector, LANA TNY module, and a 3.5 mm BadgeLink connector to turn the badge into a camp game peripheral.

Compatibility: Fri3d 2024 Badge and Flamingo blaster

Source

CAN SAO challenge

Speedometer SAO challenge

The public CTF archive ties the Speedometer SAO to rock-paper-scissors behavior, CAN messages, firmware reversing, and LCD output used in the challenge.

Compatibility: Car Hacking Village DC32 Main Badge and Speedometer SAO

Source
NorthSec 2015 Team Hardware Badge officially documented

CTF artifact

Team hardware badge challenge anchor

NorthSec's official archive says 2015 CTF participants were grouped into teams of eight and each had a hardware badge tied to the competition environment.

Compatibility: NorthSec 2015 Team Hardware Badge

Source
Hackfest 2019 Electronic Badge official CTF page backed

CTF category

Electronic CTF challenge category

The CTF page lists Electronic among the 2019 challenge categories, alongside Cloud, SDR, Web, and other challenge types.

Compatibility: Hackfest CTF 2019

Source

CTF challenge apps

Badge challenge applications

The repository includes multiple `badgechal` application files and firmware documentation stating that the custom C modules are required for CTF challenges.

Compatibility: BSides Fort Wayne 2025 Badge CTF

Source

CTF leg

CTF.ae onsite and remote leg

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.

Compatibility: Bug Bounty Village DC33 BBV Badge

Source
Puzzled Hackers LED Badge (DEF CON 34) team-announced pre-event eligibility

CTF-linked acquisition route

Top-50 CTF free-badge redemption statement

The Puzzled Hackers Team says the top 50 participants had Free Badge Redemption attached to their CTF accounts before its final puzzle announcement. It does not publish the leaderboard, account criteria, rank calculation, redemption count, code-delivery mechanics, challenge archive, score review, anti-abuse process, or proof that every eligible participant collected a physical badge.

Compatibility: Puzzled Hackers LED Badge (DEF CON 34)

Source

CTF/event integration

RomHack Camp CTF finals context

The separate RomHack Camp CTF page provides the event-side context for tracking whether badge hardware becomes part of on-site challenge play.

Compatibility: RomHack Camp 2026 Badge

Source

CTF/scavenger-hunt surface

Rabbit Chaos Adventure badge challenges

The event wiki describes Rabbit Chaos Adventure challenges on campus, laptop, and the badge, making the badge part of the game surface.

Compatibility: Easterhegg 2024 RCA Badge

Source

FPGA subsystem

ECP5U_25 FPGA challenge surface

The hardware tree includes an ECP5U_25 CABGA256 schematic and the firmware tree includes ECP5 projects, tests, and a UART coprocessor example with open FPGA tooling notes.

Compatibility: GreyCTF Summit 2025 GreyBadge

Source
MCH2022 Badge historical

Hatchery game app

Doom with sound

Henri Manson's app loads Doom on the ESP32 while using the FPGA for video and sound, turning MCH2022 into a handheld game-and-FPGA demonstration.

Compatibility: MCH2022 Badge

Source

SAO firmware lifecycle

Speedometer SAO firmware archive

The public Speedometer SAO firmware repository is MIT-licensed and says it includes CTF problem and notes material built on a display library.

Compatibility: Car Hacking Village DC32 Speedometer SAO

Source

admission identity artifact

General Admission badge package

The Roanoke InfoSec Exchange Inc ticket listing offers General Admission w/Badge and says the ticket includes a T-shirt, badge, and lunch.

Compatibility: BSides Roanoke 2026 Participant Badge Challenge

Source

alternative software

Tetris, TV-Bunny, and Ethersex software

The wiki preserves alternative software links for Tetris Sound Track, TV-Bunny, and Ethersex, showing the badge as a small AVR software target beyond the default firmware.

Compatibility: Easterhegg 2010 eHaserl

Source

analog badge

Cassette tape badge

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.

Compatibility: DEF CON 28 Safe Mode Badge

Source
DEF CON 23 Badge historical

analog challenge

Playable record clue surface

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.

Compatibility: DEF CON 23 Badge

Source
Puzzled Hackers LED Badge (DEF CON 34) team-announced and not outcome-confirmed

announced community distribution

Post-cap random giveaway intent

The Team says that after the paid cap is reached, distribution moves to random giveaways during the events. It does not identify giveaway quantity, timing, eligibility, selection method, organizer, physical allocation, handoff site, recipient list, or completed result.

Compatibility: Puzzled Hackers LED Badge (DEF CON 34)

Source
FloridaMan 2026 Badge official storefront statement

announced event challenge

Live hacking challenge and staged scoreboard

The storefront says each badge unlocks a live hacking challenge and frames progression as completing stages to climb a scoreboard. No reviewed source identifies challenge rules, format, tooling, endpoints, account model, scoring method, prize, operational schedule, data collection, accessibility, or a post-event archive; no software is inferred to run on the physical artifact.

Compatibility: FloridaMan 2026 Badge

Source

announced event-specific NFC experience

NFC Pieces of Eight and Pirates vs British Navy games

Matt Aragon announced two custom-built interactive NaClCON experiences: an NFC Scavenger Hunt Pieces of Eight and a Pirates vs British Navy NFC social-networking game. The announcement does not identify which physical event artifact participated in either experience.

Compatibility: NaClCON 2026 live-event context; not evidence of a specific badge chip, protocol, software release, or completed deployment.

Source
Puzzled Hackers LED Badge (DEF CON 34) official checkout and team announcement

announced handoff route

Meetup-only pickup and offline QR claim workflow

The checkout lists Linq 3535 / Circle Bar pickup on Wednesday August 5 and Thursday August 6 from 7–10 PM PT and says there is no shipping. It says a receipt and offline QR claim code are sent after checkout; the Team says a badge must be collected at a meetup or by separately arranging DEF CON handoff, and the QR may be given to someone else. Those terms do not confirm venue access, checkout completion, code delivery, identity verification, handoff, or redemption outcome.

Compatibility: Puzzled Hackers LED Badge (DEF CON 34)

Source
Sneakreaper Limited-Edition Badge (DEF CON 34) only three functions marked available day 1

announced software readiness

Source-starred DEF CON day-one feature boundary

The author says that most listed capability categories will not be ready out of the box and that only LED colour/brightness adjustment, a hidden software CTF or scavenger hunt, and NFC read/write are available on DEF CON day 1. That is an announced capability boundary, not a public firmware release, working demonstration, final event outcome, or guarantee of feature availability for every unit.

Compatibility: Sneakreaper Limited-Edition Badge (DEF CON 34) source-starred day-one feature set

Source
TiDAL historical

app-store ecosystem

TiDAL Hatchery app store

The EMF 2022 Hatchery API still lists TiDAL categories across event, game, graphics, hardware, utility, data, silly, unusable, and adult apps, preserving the badge as an app ecosystem rather than a one-off PCB.

Compatibility: TiDAL MicroPython app runtime

Source
Tildagon ongoing

app-store ecosystem

Tildagon App Directory

The live app directory makes Tildagon a post-event software platform, with badge, background, game, media, music, pattern, hexpansion utility, schedule, WiFi, and sensor apps published by community authors.

Compatibility: Tildagon OS

Source

application processor

RP2350 CircuitPython badge core

The repository setup flow flashes a CircuitPython UF2, then copies the RP2350 filesystem to CIRCUITPYTHON for the badge runtime.

Compatibility: GreyCTF Summit 2025 GreyBadge

Source

archive-derived platform note

ESP32 repurposing surface

Later writeups treated the 2019 badge as an ESP32-WROOM-32U board suitable for C# NanoFramework and ESP32 game/video experiments.

Compatibility: BSides Cape Town 2019 Badge

Source
SAINTCON 2021 MiniBadge Collection officially documented

assembly and puzzle ecosystem

Soldering and puzzle badges

SOLDER LVL2, SOLDER LVL3, SOLDER LVL4, and Puzzle Badge entries document a tiered soldering and puzzle MiniBadge trail designed by Rushan.

Compatibility: SAINTCON 2021 solder challenge

Source

attendee hack

Flipper Zero NFC quest emulation

The designer records that an attendee cracked the game by extracting tag IDs from firmware and emulating them with a Flipper Zero, which was encouraged.

Compatibility: DORS/CLUC 2025 Badge

Source
THOTCON 0xD Badge documented

audio firmware

Buzzer and musical tone demos

The public firmware archive includes ToneChaser examples for musical modes while the project writeup documents audio games and badge sound output.

Compatibility: THOTCON 0xD Badge

Source

award badge

Uber Badge award path

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.

Compatibility: BSides Tampa 2026 challenge awards

Source

badge CTF

Meta CTF badge challenge

The official page links the WWHF 2025 badge CTF to Meta CTF and says challenges could be solved from badge behavior or firmware.

Compatibility: Wild West Hackin' Fest Deadwood 2025 E-Badge

Source
NaClCON 2026 3D-Printed NFC Conference Badge official registration and schedule

badge activity and introduction

Pirate Pieces of Eight CTF and Badge Intro

Official registration pairs the NaClCON Badge with Pirate Pieces of Eight CTF access, and the official opening schedule lists a CTF and Badge Intro. The sources do not publish a per-badge challenge mapping, scoring mechanism, reward, or final results.

Compatibility: NaClCON 2026 attendee-program context; no specific NFC tag, reader, software client, or credential behavior is documented.

Source
AND!XOR DC27 Badge source-backed

badge add-on

DOOM SAO and SAO 1.69bis ecosystem

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.

Compatibility: AND!XOR DC27 Badge and SAO 1.69bis-compatible badges

Source

badge app

Accelerometer gravity simulation

The firmware used the integral accelerometer for gravity-style simulations and input mechanics that sat behind the public puzzle and demo behavior.

Compatibility: Hackaday Supercon 2016 LED Matrix Badge

Source
Temporal Replay 2026 Badge officially documented

badge app

Doom port

The MIT-licensed firmware exposes a Doom port running on the ESP32-S3 badge.

Compatibility: Temporal Replay 2026 Badge

Source

badge app

Pong and RPSLS badge games

The badge exposed unlockable games including two-player Pong and Rock/Paper/Scissors/Lizard/Spock badge-to-badge interaction.

Compatibility: BSides Cape Town 2016 Badge

Source

badge app

Warbadging WiFi scanner

A challenge-unlocked Warbadging mode scanned up to 30 nearby WiFi networks and displayed signal strength, ESSID, encryption type, and channel coverage.

Compatibility: BSides Cape Town 2016 Badge

Source
CHCon 2025 Badge source-backed

badge app and challenge

Minecraft 1.21.4 badge server

The badge implemented a Minecraft Java Edition 1.21.4 server on the ESP32-C3, with in-world levers mapped back to the 24 physical RGB LEDs.

Compatibility: CHCon 2025 Badge

Source
CHCon 2025 Badge source-backed

badge app and challenge

Minecraft server challenge stage

A later challenge stage used badge networking and elevated shell access to start the Minecraft server and solve the in-world lever puzzle.

Compatibility: CHCon 2025 Badge

Source

badge app framework

GameOn-derived badge game framework

The making-of post documents a colour GameOn-derived firmware with menu, single-player game, raycaster, voxel landscape, high-score JSON/WiFi workflow, setup screens, achievements, and debug screens.

Compatibility: BSides Cape Town 2019 Badge

Source
Disobey 2026 Badge source-backed

badge app framework

Social game firmware and miniapps

The badge page describes social-game firmware for badge-to-badge duels and asks miniapp authors to submit pull requests so apps can be built into shared firmware.

Compatibility: Disobey 2026 Badge

Source

badge app/event challenge

Camera capture and film festival

The badge's camera was not decorative: Supercon included a film-festival category for movies and media produced with the badge camera.

Compatibility: Hackaday Supercon 2017 Camera Badge

Source
HackConRD 2026 eBadge source-backed

badge applications

Badge game suite

The repository documents Doom Maze, Dino Run, Hackermon, and Star Invaders as bundled badge games with button controls.

Compatibility: HackConRD 2026 eBadge

Source

badge applications

MicroPython app suite

The public app tree includes menu, settings, schedule, Tetris, analog clock, battery monitor, system monitor, and other badge applications.

Compatibility: BSides Fort Wayne 2025 Badge

Source

badge challenge

Attendee chip challenge flow

The organizer retrospective says each attendee received a chip for event activities, challenges awarded experience points, and the chip software was reversible for hidden discoveries.

Compatibility: BSides Prague 2025 Electronic Badge

Source
AND!XOR DC34 5N4CK3Y Badge announced pre-event

badge challenge

BENDER contest activation

The official product page says BENDER hacking challenges will appear on the CTFd-hosted server at 10:00 Vegas time on Friday, August 7 because the badges are part of a DEF CON Contests & Events challenge, with activation instructions promised for the same day.

Compatibility: AND!XOR DC34 5N4CK3Y Badge

Source
THcon 2026 Badge officially documented

badge challenge

BLE padlock challenge

The official badge page documents a BLE padlock interaction as one of two badge challenges.

Compatibility: THcon 2026 Badge

Source
RVA5sec 2016 Badge source-backed

badge challenge

Badge CTF challenge hooks

The 2016 interview says the badge focus shifted toward CTF challenges.

Compatibility: RVA5sec 2016 Badge

Source

badge challenge

Badge-holder-only hardware CTF stages

The official badge page frames the electronic badge as a custom-designed hardware CTF with hidden puzzles and special stages only badge holders can access.

Compatibility: BSidesTLV 2025 Infinity Glove Electronic Badge

Source

badge challenge

Basic and Advanced crypto CTF tiers

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.

Compatibility: BSides San Diego 2026 Cyberpunk Bunny Badge

Source

badge challenge

Binary blink and Docker CTF

The 2019 badge challenges used blinked binary, silkscreen encoding, badge-role variants, SSRF, and a Docker-hosted challenge app.

Compatibility: Kernelcon 2019 K Badge

Source

badge challenge

Binary-code challenge unlock flow

The page documents limited-access and full-access challenges whose solved binary codes are entered through the badge buttons to blink different LED sets and unlock behavior.

Compatibility: BSides Goa 2024 SecOps Hackable Badge

Source

badge challenge

EEPROM-gated game unlocks

A one-byte EEPROM state byte at address 0 gates three hidden bonus LED animations, each unlocked by winning one of three single-player games (Stop The Light, Follow The Sequence, Find The Sequence), with matching two-player variants.

Compatibility: BSides Leeds 2026 Artie the Owl Badge

Source
Ruxcon 2017 HHV Badge source-backed

badge challenge

EasyFlag UART challenge

The first flag path used UART-visible boot/output behavior and per-badge material documented in the Darkglade EasyFlag writeup.

Compatibility: Ruxcon 2017 HHV Badge

Source
BSides Des Moines 2026 Badge officially documented

badge challenge

Eight-tag village-collection CTF

Eight hardcoded 4-byte UIDs map to village and event markers (HW Village, Talks1, Talks2, Solder Village, Blue Team, Vendor, CTF, Check-In); scanning a matching tag collects it and lighting all four LEDs blue requires all eight.

Compatibility: BSides Des Moines 2026 Badge

Source

badge challenge

Electronic badge CTF challenge

The current Hardware Village page says attendees can test their skills by uncovering secrets hidden in the event's electronic badge.

Compatibility: BSidesTLV 2026 Electronic Badge

Source

badge challenge

Exploration, modification, and embedded-challenge trail

The post-event account says attendees were encouraged to explore, modify, and hack the badge, interact with embedded challenges, and discover hidden functionality without publishing challenge implementation details.

Compatibility: BSides Kristiansand 2026 Shield Badge

Source
AvengerCon IX Electronic Badge officially documented

badge challenge

Four-challenge badge CTF

The official badge page says AvengerCon IX's badge carried a small four-challenge CTF contest.

Compatibility: AvengerCon IX Electronic Badge

Source
Ruxcon 2017 HHV Badge source-backed

badge challenge

HardFlag AES challenge

The hard flag path involved firmware inspection, Lua crypto module behavior, AES routines, and badge-specific challenge material.

Compatibility: Ruxcon 2017 HHV Badge

Source

badge challenge

Hidden hardware and firmware challenge

The official source describes a hidden hardware/firmware challenge using reverse-engineering skills, with prizes for successful solvers. It does not independently identify the exact Roulette board, its eight-stage maker CTF, or a shared challenge implementation.

Compatibility: Seasides 2026 Roulette Badge

Source

badge challenge

Khong Guan building CTF firmware

The badge CTF uses serial interaction, OSINT, crypto, and stegano story challenges, six floor unlocks, elevator navigation, remembered flags, and a final trophy/leaderboard prompt.

Compatibility: SINCON 2023 Khong Guan Building CTF Badge

Source

badge challenge

LED key transposition challenge

The repository documents a challenge where the badge emits the encrypted text OIMXEXEXDXLXANYLOXMX and transmits the key MALUMABEBE through LED timing before validating SOLVE:YOAMOMEDELLIN.

Compatibility: DragonJARCON 2025 NFC Hardware Badge

Source

badge challenge

MicroPython badge challenge

The writeup documents USB file access, Python files, and six challenge flags across web, BLE, roulette, file, and inter-controller puzzle surfaces.

Compatibility: Off-By-One 2024 Hardware Badge

Source
REcon 2026 Badge officially documented

badge challenge

NFC flag-hunt

The PN7150 NFC daughterboard supports tag and reader detection, Mifare Classic read and write, and a flag-hunt where tapping a tag unlocks a flag and broadcasts it to every nearby badge.

Compatibility: REcon 2026 Badge

Source
Robotic Hacking Community DEF CON 34 AI-Connected Badge official released firmware documentation

badge challenge

On-badge CTF challenges

The released documentation identifies a Konami-code challenge, a snake-style game, registration QR behavior, and serial-only challenges. The event CTF's final operation and individual results remain unrecovered.

Compatibility: Robotic Hacking Community DEF CON 34 AI-Connected Badge

Source
THcon 2026 Badge officially documented

badge challenge

One-time-password challenge

The official badge page documents a one-time-password flow as the second badge challenge.

Compatibility: THcon 2026 Badge

Source
CHCon 2025 Badge source-backed

badge challenge

Progressive LED challenge modes

The challenge path unlocked rainbow LEDs, login/password interaction, named LED patterns, and custom pattern definition.

Compatibility: CHCon 2025 Badge

Source
LayerOne 2023 PIC HID Badge partial archive

badge challenge

RubberDucky 2.0 competition hook

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.

Compatibility: LayerOne 2023 PIC HID Badge

Source

badge challenge

Scavenger-hunt LED code path

The badge doubled as a scavenger hunt where attendees collected codes to light the LEDs.

Compatibility: AvengerCon VIII 8-8-8 Badge

Source

badge challenge

Seven official challenge LEDs

The Wombat-2 CTF presented seven official puzzles; each successful binary flag lit the matching progress LED on the badge.

Compatibility: BSides Adelaide 2025 Wombat-2 CTF Badge

Source

badge challenge

Seven-LED CTF challenge surface

Noroff reports that the duck-shaped electronic badge used seven LED lights, each representing a unique challenge, and quotes SolaSec saying there were seven different ways to hack it.

Compatibility: BSides Kristiansand 2025 Sykt Badge

Source
BSides Des Moines 2026 Badge officially documented

badge challenge

Static flags and hash unlock

The firmware encodes two static flags (a plaintext constant and a Ghidra-disassembleable byte-assembled string) plus a hash-based unlock that celebrates a specific UID-derived LED combination.

Compatibility: BSides Des Moines 2026 Badge

Source

badge challenge

USB CTF flag unlocks

The 2024 badge used micro-USB CTF interaction, correct flags, persistent progress, and LED animations to show unlocked challenge state.

Compatibility: BSides Adelaide 2024 Wombat Badge

Source

badge challenge

Underground mining CTF narrative

The badge challenge centers on encrypted logs, hidden communications, coordinates, and a rogue underground bitcoin-mining operation stealing power from local businesses.

Compatibility: BSides Ballarat 2026 Underground Badge

Source
REcon 2026 Badge officially documented

badge challenge and game

Magspoof and Simon

The badge emulates magnetic stripe cards over USB serial and includes a solo Simon Says memory game triggered by holding button 4.

Compatibility: REcon 2026 Badge

Source
BadgeLife Village Badge (DEF CON 34) official instructions published; completion outcome unverified

badge challenge and user-installed component surface

Power Boost and Distress Beacon challenge parts

The guide says Badgey Bodgerton uses a supplied bodge wire plus a user-installed 3 mm LED, 1 kΩ resistor, and polarized buzzer in challenge work. It describes the parts and their badge-local challenge context without revealing answers or proving every badge shipped with identical parts, that a participant completed the work, or that any assembly is safe or successful.

Compatibility: Documented BadgeLife Village Badge challenge context; do not treat as a universal assembly or repair recommendation

Source

badge challenge archive

Main-badge CTF paths

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.

Compatibility: Car Hacking Village DC32 Main Badge

Source
BSides Roanoke 2026 Participant Badge Challenge self-identified challenge source

badge challenge companion

ShenLabs clearance web puzzle

The ShenLabs footer states that the fictional site was created for the BSides Roanoke 2026 badge challenge, using clearance and decryption framing; it does not establish that the web experience ran on, or was physically encoded into, the attendee badge.

Compatibility: BSides Roanoke 2026 Participant Badge Challenge

Source

badge challenge set

Secure Impact nine-challenge badge

The official CyberThreat page says CyberThreat 2024 used brand-new hackable badges from Secure Impact with nine challenges.

Compatibility: CyberThreat 2024 Hackable Badge

Source
X-CTF 2016 Badge released

badge challenge software

CTF firmware apps

The firmware repository preserves applet, challenge, Wi-Fi scanner, LCD, and game source modules for the event badge firmware.

Compatibility: X-CTF 2016 Badge

Source

badge challenge software

GreyCTF finals challenge set

The filesystem README names the Grey finals challenges as Hornet Revenge, Leaky Pin, Bricked Up, Shooting Flags, Secure Memory, and CatCore.

Compatibility: GreyCTF Summit 2025 GreyBadge

Source

badge challenge surface

Badge Village reprogramming and challenges

HITB invited attendees to learn how to hack the badge, expand its functionality, get started reprogramming, and unlock secret features, challenges, and more.

Compatibility: HITBSecConf2019 Amsterdam Badge

Source
RVAsec 2018 Badge source-backed

badge challenge surface

Badge games and puzzles

HackRVA's recap documents games and puzzles as part of the 2018 hardware badge experience.

Compatibility: RVAsec 2018 Badge

Source

badge challenge surface

Mini-games, hidden challenges, and reprogramming

The Badge Village promised secret feature unlocks, mini-games, hidden challenges, and help getting started with reprogramming the badge.

Compatibility: HITBSecConf2018 Amsterdam Badge

Source

badge challenge surface

Mini-games, hidden challenges, and reprogramming

The Badge Village promised secret feature unlocks, mini-games, hidden challenges, and help getting started with reprogramming the HITB2018PEK badge.

Compatibility: JD-HITBSecConf2018 Beijing Badge

Source

badge challenge surface

Score programmer and hidden touch target

Hackaday documents a score programmer, a 0-to-9 digit collection challenge, a secret capacitive touch sensor, and pad fields intended for attendee hacking.

Compatibility: TROOPERS11 Nixie Badge

Source

badge challenge surface

Secret features and mini-games

HITB described badge hacking as a path to unlock secret features, mini-games, and expanded functionality during the Dubai event.

Compatibility: HITBSecConf2018 Dubai Badge

Source

badge component

Red CC1111 RFCat RF badge

The red RF badge carried a CC1111 RFCat-compatible chip, USB port, button, and exposed rear contacts, becoming the radio surface for the 2017 challenge.

Compatibility: BSides Cape Town 2017 RFCat Badge

Source

badge display platform

8x16 LED matrix display

The red 128-LED matrix was the main visual surface for animations, gravity simulation, messages, Tetris, challenge feedback, and blinky badge hacks.

Compatibility: Hackaday Supercon 2016 LED Matrix Badge

Source
NorthSec 2026 Badge official event-page backed

badge distribution

New social electronic badge entitlement

The registration page lists a new social electronic badge as an included item for multiple NorthSec 2026 ticket classes while supplies lasted.

Compatibility: NorthSec 2026 conference, CTF, combo, and training attendance

Source
RootedCON 2026 Pacman Badge community-reversed

badge firmware

Pacman-themed original firmware

The original PACMAN-themed badge firmware's native quiz-server CTF protocol was reversed by the community. The community repository is not an official RootedCON release.

Compatibility: RootedCON 2026 Pacman Badge

Source

badge game

Achievements and CTF flag unlocks

The official about page documents eight achievement levels that unlocked LED patterns and CTF flags.

Compatibility: Kernelcon 2025 Race Condition Badge

Source

badge game

Are You Human Or Are You Hacker

HITB lists 'Are You Human Or Are You Hacker' under What's On the Badge for the special-edition Beijing badge.

Compatibility: JD-HITBSecConf2018 Beijing Badge

Source
AND!XOR DC26 Badge source-backed

badge game

B.E.N.D.E.R. console challenge

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.

Compatibility: AND!XOR DC26 Badge

Source
AND!XOR DC27 Badge source-backed

badge game

B.E.N.D.E.R. v2.0

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.

Compatibility: AND!XOR DC27 Badge

Source

badge game

BadUSB badge game

The official PCB Badge guide documents a BadUSB activity path as part of the 2024 badge game surface.

Compatibility: HITCON CMT 2024 PCB Badge

Source
HITCON 2025 PCB Badge source-backed

badge game

BadUSB script execution

The badge guide documents BadUSB behavior and script execution as part of the 2025 badge activity surface.

Compatibility: HITCON 2025 PCB Badge

Source
THOTCON 0xC Badge source-backed

badge game

Contra laser-tag badge game

Rehrig describes the 0xC badge theme as Contra and the core functionality as a conference-wide laser-tag game.

Compatibility: THOTCON 0xC Badge

Source

badge game

Daily score and threshold prize loop

The badge mini-games awarded special prizes to the top three daily scores and participation-prize eligibility when attendees crossed stated thresholds.

Compatibility: HITCON CMT 2023 NFC Badge

Source
DEF CON 32 Badge archived

badge game

GB Studio badge game

The public DEFCON 32 Badge Game repository contains GB Studio project files and graphical assets for the badge's LVCC-themed game.

Compatibility: DEF CON 32 Badge

Source
HITCON 2025 PCB Badge source-backed

badge game

Hacker Pet badge mode

The 2025 PCB Badge guide documents a Hacker Pet mode alongside score display and other badge activities.

Compatibility: HITCON 2025 PCB Badge

Source

badge game

Hackermon badge challenge

One official Badge Challenges path asked attendees to catch all Hackermon and become Hackermon master, with a HITCON CMT 2018 ticket as the award.

Compatibility: HITCON CMT 2017 MediaTek Badge

Source
DC503 5ohBEE Pager source-backed

badge game

HugQuest HUG-token game

HugQuest v1.5 stores HUG tokens, supports mining and sending HUGs, tracks names, and displays token state through the SMART Response XE interface.

Compatibility: DC503 5ohBEE Pager

Source
DC503 Wagon Party Badge source-backed

badge game

Hunter and Bender minigame

The hunt loop moves a hunter sprite, tracks laser direction from input pins, draws a Bender sprite, and increments score on hits.

Compatibility: DC503 Wagon Party Badge

Source

badge game

IR and 433 MHz packet-decoding game

HITB lists an IR and 433 MHz packet-decoding game as a badge activity, tying the RF/IR hardware to explicit on-site play.

Compatibility: HITBSecConf2018 Amsterdam Badge

Source
RVAsec 2019 Badge source-backed

badge game

Laser Tag and base stations

The 2019 badge post documents base-station laser-tag behavior and point collection plans.

Compatibility: RVAsec 2019 Badge

Source
BSides Newcastle 2025 Space Badge maker-documented event interaction

badge game

Morse-code venue game

The repository says signs with player codes were placed around the venue and preserves the signs plus Morse-code guide material. It establishes the source-described game context, not an event-wide participation result, challenge completion record, prize outcome, or current playable service.

Compatibility: BSides Newcastle 2025 Space Badge event context only; no current game, network, or support claim

Source
NorthSec 2021 Badge documented

badge game

North Sectoria flag game

The official badge page documents ten badge flags hidden across trivia, reverse engineering, and badge interfaces, submitted through FLAGBOT.

Compatibility: NorthSec 2021 Badge

Source

badge game

Snake badge challenge

The second official Badge Challenges path was Master of Snake, also tied to a HITCON CMT 2018 ticket prize.

Compatibility: HITCON CMT 2017 MediaTek Badge

Source

badge game

Stroop-effect color game

The README describes a Stroop-effect color game where positive or negative shock reinforcement can be configured before play.

Compatibility: Tipsy Badge game firmware

Source
DC503 Wagon Party Badge source-backed

badge game

Wagon animation and mileage mode

The wagon loop draws wagon and mountain sprites, prints the current banner, and increments a displayed score in miles.

Compatibility: DC503 Wagon Party Badge

Source

badge game

Wi-Fi beacon exploration game

The conference badge game used Wi-Fi beacons scattered around Plexpod Westport for attendee discovery and exploration.

Compatibility: BSidesKC 2019 Conference Badge

Source
THOTCON 0x8 Badge historical

badge game

tesserHack 8x8x8 maze firmware

Stock firmware challenged attendees to navigate an 8x8x8 maze using the three potentiometers for Z, X, and Y movement.

Compatibility: THOTCON 0x8 Badge

Source

badge game and server

Snake and tetris online scoreboard

The firmware and server trees preserve snake and tetris apps, score-token generation, online scoreboard tables, and bPodUpdater/server packaging.

Compatibility: BSides Canberra 2023 bPod

Source

badge game and story

Thirteen-chapter Ritual and unlockable modes

The listing describes a 13-chapter Ritual with story, screen, and LED animations; six side-quest challenges; and Bling, The Corrupt Ritual, R'lyeh Arena, Another Adventure, Exploit, and Rick Roll unlockable modes. No firmware archive or full game-rule source is published.

Compatibility: Cult of Cthulhu Indie DEF CON 34 Badge

Source
RVAs3c 2014 Badge source-backed

badge game platform

IR and LCD game surface

Official preview material documents IR, LCD, LED, audio, and input surfaces intended for badge applications and games.

Compatibility: RVAs3c 2014 Badge

Source
BornHack 2026 Badge post-event source-backed

badge game software

BornPets and mini-games

Badge.Team now describes a BornPets virtual pet inspired by Tamagotchi and mini-games as the active badge software path, with top-level screens available in public usage docs.

Compatibility: BornHack 2026 Badge

Source
RVAsec 2019 Badge source-backed

badge games

Badge Monsters and Maze

HackRVA documented Badge Monsters and Maze as 2019 badge activities.

Compatibility: RVAsec 2019 Badge

Source

badge hacking contest

Best badge hack prize

Pre-event coverage told attendees there would be a prize for the best badge hack, framing the badge as a hackable participant artifact.

Compatibility: BSides Perth 2018 NodeMCU Badge

Source

badge hacking surface

Arduino-compatible protoboard expansion

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.

Compatibility: CarolinaCon 12 Electronic Kit Badge

Source
RV4sec 2015 Badge source-backed

badge hacking surface

Reset-header development option

The 2015 build post documents unpopulated surface-mount pads and a reset-header option for connecting into the board.

Compatibility: RV4sec 2015 Badge

Source
RVA5sec 2016 Badge source-backed

badge hacking workflow

Standard USB reflashing

HackRVA described standard USB as a way to make post-event reflashing easier.

Compatibility: RVA5sec 2016 Badge

Source
RVAs3c 2014 Badge planned/source-backed

badge hacking workflow

USB bootloader goal

The preview describes a bootloader and micro-USB programming path as a goal for post-event hacking.

Compatibility: RVAs3c 2014 Badge

Source
h-c0n 2026 CTF BADge source-backed

badge hardware platform

Functional electronic development board

The official h-c0n badge post says the CTF BADge is a fully functional development board that can be used for personal projects, not only an ornament.

Compatibility: h-c0n 2026 CTF BADge

Source
BSides Lisbon 2025 Electronic Badge source-backed but underspecified

badge hardware programme

Official electronic badge programme

The official about page says BSidesLisbon 2025 would have an electronic badge alongside talks, networking, and a CTF.

Compatibility: BSides Lisbon 2025 Electronic Badge

Source
HackConRD 2026 eBadge source-backed

badge identity settings

NVS profile and role persistence

The README documents a seven-character nick, BadgeRole profile, LED brightness, RF profile, fox frequency, friends history, challenge state, and high-score keys in NVS.

Compatibility: HackConRD 2026 eBadge

Source
RVAsec 2013 Badge source-backed

badge interaction

Infrared badge play

Official sources document IR communication and badge-to-badge game behavior in the 2013 badge lineage.

Compatibility: RVAsec 2013 Badge

Source

badge interaction surface

Four-button LED challenge interface

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.

Compatibility: Bug Bounty Village DC33 BBV Badge

Source

badge interface

8x32 LED matrix menu

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.

Compatibility: SAINTCON 2018 ESP32 Badge

Source
Hackbat DEF CON 32 Badge source-backed

badge interface

OLED and six-button handheld layout

The documentation describes a Game Boy-like badge layout with OLED display and six push buttons for attendee interaction.

Compatibility: Hackbat DEF CON 32 Badge

Source
DEF CON 30 Badge historical

badge interface

Playable synthesizer keyboard

The badge operated as a playable musical keyboard and synthesizer with instrument behavior, display, speaker, and challenge mode tied to note entry.

Compatibility: DEF CON 30 Badge

Source

badge interface

SAO, SPI, USB, and switch pins

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.

Compatibility: BSidesPDX 2018 ATTiny861 Badge

Source

badge interface

Standalone binary CTF controls

The 2025 badge replaced USB-dependent input with onboard CTF, 1, and 0 tactile buttons for entering ten-bit challenge flags directly on the badge.

Compatibility: BSides Adelaide 2025 Wombat-2 CTF Badge

Source

badge provisioning

Controller genfiles and flash workflow

The Trick-or-Treat README points to controller code for generating game files and flashing badge-specific storage contents.

Compatibility: BSidesPDX 2024 OpenTaxus Badge

Source

badge puzzle mode

Packet Hack CTF binary-input mode

The Hackster writeup says holding S1 launches Insert Code mode, where right-side keys enter a Packet Hack CTF binary value and S2 clears input.

Compatibility: HITB+CyberWeek 2021 Packet Hack Badge

Source

badge puzzle surface

8-bit art and hidden code surface

The log says the badge carried 8-bit art plus many codes in many places while withholding the exact meanings and Gerber artwork.

Compatibility: ToorCon 20 Official Badge

Source
AND!XOR DC25 Badge source-backed

badge scripting environment

TCLish scripting and GPIO

The scripting log documents TCLish language support plus badge-specific graphics, LED, button, timing, file, and GPIO commands for day-one badge hacking.

Compatibility: AND!XOR DC25 Badge

Source
RVAsec 2022 Badge source-backed

badge software

Badge apps and games

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.

Compatibility: RVAsec 2022 Badge

Source
LayerOne 2017 CAN Bus Badge partial archive

badge software

CAN logger and emulator experiments

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.

Compatibility: LayerOne 2017 CAN Bus Badge

Source
RVAsec 2024 Badge source-backed

badge software

Expanded 2024 app tree

The app tree includes AA Gunner, Badgey, Battlezone, Clue, Moon Patrol, Rover Adventure, Tank vs Tank, and other badge apps/games.

Compatibility: RVAsec 2024 Badge

Source
RVAsec 2023 Badge source-backed

badge software

Expanded badge games

The repository includes Asteroids, Battlezone, Clue, Pong, Tank vs Tank, Magic 8 Ball, Badge Monsters, Maze, and other apps/games.

Compatibility: RVAsec 2023 Badge

Source

badge software

Games, challenges, and schedule apps

The repository tag preserves firmware apps, games, challenge material, schedule code, BLE control, and LED control utilities.

Compatibility: NorthSec 2019 Badge

Source

badge software environment

Vintage time-sharing emulator

After the relay-computer game path, the badge became an emulator for a vintage time-sharing operating system where attendees could write code.

Compatibility: CypherCon 2017 Cube Badge

Source
AND!XOR DC26 Badge source-backed

badge software interface

CP2102N USB serial console

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.

Compatibility: AND!XOR DC26 Badge

Source
The Shattered Shard (DEF CON 34) public pre-event player-guide description

badge-hosted CTF progression

Ten-chapter Aegis Sigil quest

The public guide frames The Shattered Shard as a ten-chapter rune-restoration quest with sequentially unlocked progress and per-badge state. It establishes a planned game surface, not a full challenge archive, final scoring system, prize, winner record, completion ledger, event deployment, or permission to reproduce solutions or probe anything beyond an assigned badge and its advertised services.

Compatibility: The Shattered Shard challenge badge assigned to a participant; final availability and event deployment unverified

Source

badge-to-badge challenge

Twenty-six-badge Enigma ring

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.

Compatibility: SAINTCON 2019 Enigma Badge

Source

badge-to-badge communication

Infrared UART badge protocol

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.

Compatibility: Hackaday Supercon 2016 LED Matrix Badge

Source

badge-to-badge game

802.15.4 mesh Battleships

Hackaday describes a Battleships game played with another badge over the ESP32-C6's 802.15.4 mesh networking.

Compatibility: HackerHotel 2024 Telegraph Badge

Source
AND!XOR DC25 Badge source-backed

badge-to-badge game

BOTNET badge-to-badge game

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.

Compatibility: AND!XOR DC25 Badge

Source

badge-to-badge game

IR social quest and special-badge unlocks

Each badge periodically transmitted a unique IR code and listened for other badges; seeing twelve special speaker/organizer badges unlocked parts of a hidden image.

Compatibility: DORS/CLUC 2024 Badge

Source

badge-to-badge game

Robot-fighting badge game

The product and forum sources describe a main badge that uses onboard controls and supports robot fights against other badges.

Compatibility: NilbinSec DC33 Hack 'Em Crack 'Em Robots

Source
Tildagon ongoing

badge-to-badge game app

EMFight

JonTheNiceGuy's EMFight lets EMF Camp badge holders challenge each other, keeping inter-attendee play in the app-store layer rather than only in built-in firmware.

Compatibility: Tildagon OS

Source

badge-to-badge game system

Badge roles and Séance interaction

The maker names Acolyte, Glyph, Elder God, and redacted Cthulhu badge types. Its Séance description says four badges complete a circuit and beacon to nearby badges, without identifying radio hardware, a wireless protocol, role counts, or on-site distribution confirmation.

Compatibility: Cult of Cthulhu Indie DEF CON 34 Badge

Source
DEF CON 26 Badge historical

badge-to-badge interaction

Badge-to-badge unlock connector

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.

Compatibility: DEF CON 26 Badge

Source
DEF CON 20 Badge historical

badge-to-badge interaction

Infrared encounter graph

Badges communicated over infrared and could report encountered badge identities through a serial terminal, turning attendee movement and mingling into puzzle state.

Compatibility: DEF CON 20 Badge

Source
DEF CON 17 Badge source-backed

badge-to-badge interaction

Wired badge-to-badge communication

The badge included multi-badge communication through a wired interface, and the role shapes also formed a seven-piece physical puzzle.

Compatibility: DEF CON 17 Badge

Source
AND!XOR DC27 Badge source-backed

badge-to-badge network

BOTNET Bluetooth mesh

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.

Compatibility: AND!XOR DC27 Badge

Source
DEF CON 21 Badge historical

black-badge artifact

Mechanical Uber badge watch

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.

Compatibility: DEF CON 21 Uber Badge

Source

camp identity workflow

Shady Tag handle

The Euphoria CTF page directs players to register a Shady Tag at the Shadytel Experience Center before starting the badge challenge.

Compatibility: ToorCamp 2024 Shadybucks Wristband

Source
SiNE historical

camp-game extension

Treasure-hunt LED alphabet

The wiki describes hidden beacons around EMWave/Stubnitz: reaching a clue location and holding the badge near the matching letter lit the corresponding location LED, with progress preserved in EEPROM.

Compatibility: SiNE / EMW2013

Source

challenge archive

Collaborative CTF write-up archive

The public CTF repository preserves write-up entry points for Rooting, Mr Bean Walker, BruteSearcher, NoNameCon SpyNet, Ployka PWNer, Binary Hero, and Side Blennel.

Compatibility: NoNameCon 2019 NoNameBadge

Source

challenge artifact

2022 challenge media archive

The public hardware tree preserves a badge challenge directory with bitmap, JPEG, PNG, and PSD assets tied to the 2022 badge archive.

Compatibility: NorthSec 2022 Badge

Source

challenge artifact

Hackers Challenge CTF badge context

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.

Compatibility: SAINTCON 2020 Hackers Challenge

Source

challenge behavior

Pre-installed clue and badge-to-badge exchange

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.

Compatibility: BSidesSF 2024 Hardware Challenge Village Badge

Source

challenge bypass

Hack-the-badge bypass path

The same public source says participants could hack the badge and bypass the contest altogether.

Compatibility: AvengerCon VIII 8-8-8 Badge

Source

challenge companion

Virtual companion and challenge context

The project README documents a virtual companion and online-challenge context. The catalogue records that high-level relationship without reproducing service details, credentials, operational endpoints, or challenge solutions.

Compatibility: BSides Perth 2025 ESP32 TFT Badge

Source

challenge device

BLE mesh controller-screen challenge

The official controller-screen repository documents an ESP32 screen interface that controlled 2023 badge LEDs over BLE mesh, exposed debug/admin menu behavior, sent messages/popups, and used secure boot on competition boards.

Compatibility: NorthSec 2023 Badge and controller-screen challenge

Source
DEF CON Singapore 2026 TISC ESP32 Trinket first-hand finalist-backed

challenge hardware

ESP32 finalist trinket

The finalist writeup says each TISC@DEF CON SG finals participant was handed an ESP32 hardware trinket for one of the on-site challenges.

Compatibility: DEF CON Singapore 2026 TISC ESP32 Trinket

Source

challenge interaction

DIP-switch clue paths

The writeup documents multiple clue texts triggered by toggling DIP switches and pressing a badge button, turning a small hardware input surface into the puzzle selector.

Compatibility: Security Fest 2018 Challenge Badge

Source

challenge mechanic

Commander badge progression

The write-up documents special Commander badges used by SAINTCON Committee members to help Agent rings progress through later challenge stages.

Compatibility: SAINTCON 2019 Badge Challenge

Source

challenge mechanic

Hidden Hacker Challenge code secret

Datko says Matt Lorimer found one of the SAINTCON secrets by examining the badge source code, tying the badge to the Hacker Challenge trail.

Compatibility: SAINTCON 2014 Hacker Challenge

Source
BSides Athens 2024 Electronic Circuit Badge source-backed but underspecified

challenge or puzzle surface

Hidden secrets

The recovered wrap-up states that the badge contained secrets, but no public challenge archive or firmware source was recovered in this pass.

Compatibility: BSides Athens 2024 Electronic Circuit Badge

Source

challenge platform link

Vulnmachines solve path

SecOps directs badge participants to Vulnmachines to solve the badge hacking challenge and receive the binary codes needed to unlock the badge.

Compatibility: BSides Goa 2024 SecOps Hackable Badge

Source
SAINTCON 2021 MiniBadge Collection officially documented

challenge rewards

Hackers Challenge and contest MiniBadges

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.

Compatibility: SAINTCON 2021 contests

Source
SAINTCON 2022 MiniBadge Collection officially documented

challenge rewards

Hackers Challenge and game MiniBadges

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.

Compatibility: SAINTCON 2022 Hackers Challenge

Source

challenge software

Airship storyline CTF

The badge CTF is framed as an airship journey with touch-key and serial navigation, games, riddles, and harder crypto, reverse-engineering, and memory-corruption challenges.

Compatibility: Security Fest 2024 Feskekôrka Piano Badge

Source

challenge software

Cryptography serial CTF

The badge CTF uses a serial monitor at 9600 baud; sending three stars enters CTF mode and solving eight cryptography puzzles unlocks eight building lights.

Compatibility: Security Fest 2023 Gothenburg Skyline Badge

Source

challenge software

HID and serial puzzle flow

The badge presents itself as both HID and serial; HID button output gives onboarding and clues, while listening on the serial interface reveals the path into the PGP/key-recovery challenge.

Compatibility: Security Fest 2018 Challenge Badge

Source

challenge software

Serial CTF console

The guide documents a serial CTF menu with visual hardware debugging, reverse engineering, RF hacking, and crypto protection categories.

Compatibility: Hacktivity 2018 Badge

Source

challenge surface

BLE game and UART/SAO CTF context

The README describes the BLE game and high-level Wargames-themed challenge access through UART with SAO context. The catalogue deliberately does not reproduce challenge procedures, values, answers, credentials, or operational details.

Compatibility: BSides San Diego 2024 ESP32-C3 Badge

Source
NorthSec 2015 Team Hardware Badge officially documented

challenge surface

Network, RF, and smartcard challenge context

The same official note connects the badge context to network challenges, simulated IPv6 workstations, an RF monitoring station, and a provided smartcard.

Compatibility: NorthSec 2015 Team Hardware Badge

Source

challenge surface

Serial-terminal embedded CTF

The Basic Edition firmware was documented with CTF tasks started through serial terminal utilities, and the public CTF repository preserves eight post-event challenge write-up areas.

Compatibility: NoNameCon 2020 Air Quality Badge

Source

challenge tooling

Python console helper

The Virtualabs repository preserves Python console tooling and serial interaction material for working with the badge challenge.

Compatibility: Nuit du Hack 2014 Collector Badge

Source
DEF CON 23 Badge historical

cipher material

Nyctograph and Gold Bug lanyards

The badge challenge used six lanyards carrying Lewis Carroll Nyctograph symbols and Poe Gold Bug cipher material that translated into early-stage secret messages.

Compatibility: DEF CON 23 Badge

Source

communications challenge

BLE and serial puzzle surfaces

The teardown documents 115200-baud serial output, BLE-readable messages, hash clues, and firmware strings analyzed with Ghidra.

Compatibility: Wild West Hackin' Fest Deadwood 2025 E-Badge

Source

community archive

Badge-hacking project gallery

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.

Compatibility: Hackaday Supercon 2018 Retrocomputer Badge

Source

community badge app

Video player and AM radio transmitter

Konrad Beckmann's README-listed project used the RP2040 game badge as a video player and AM radio transmitter.

Compatibility: BornHack 2022 Game On

Source

community badge game

Adventure hack-and-slash game

Jens 'JWolf' Larsen's README-listed adventure game preserved the Game On badge as a homebrew handheld target.

Compatibility: BornHack 2022 Game On

Source

community badge game

Flappybirds

Pieter Vander Vennet's README-listed Flappybirds project appears in the BornHack 2022 badge project list.

Compatibility: BornHack 2022 Game On

Source

community badge game

Pacman

Glymphie's README-listed Pacman project is one of the preserved homebrew examples for the Game On badge.

Compatibility: BornHack 2022 Game On

Source

community badge game

Survivator

Daniel Lundsgaard Skovenborg's README-listed Survivator arcade game used a micro:bit for controls.

Compatibility: BornHack 2022 Game On plus micro:bit controller

Source
DEF CON 32 Badge historical

community firmware

Custom Game Boy ROM experiments

Community ROM work showed the badge running custom Game Boy ROM code and controlling all nine LEDs beyond the default controls.

Compatibility: DEF CON 32 Badge

Source
SAINTCON 2022 MiniBadge Collection officially documented

community participation

Community booth MiniBadges

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.

Compatibility: SAINTCON 2022 community areas

Source
Fri3d 2022 Badge post-event

community software port

nofrendo NES emulator port

A community Arduino nofrendo port ran NES games on the Fri3D 2022 badge with display output, buzzer audio, ROM loading from SPIFFS, and a documented START-button workaround.

Compatibility: Fri3d 2022 Badge

Source
Hak4Kidz Chicago 2026 Fun Badge official 2026 event page

completed conference programme context

Time Travel: Capture the Flag event context

The official home identifies Time Travel: Capture the Flag as the June 6 event's hands-on CTF context. It does not say the fun badge runs, unlocks, contains, or is required for the CTF.

Compatibility: Hak4Kidz Chicago 2026 event context only; badge-to-CTF linkage unverified

Source

contest add-on

Challenge Accepted contest SAO

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.

Compatibility: BSidesKC 2019 badge challenges

Source

contest artifact

2023 contest and challenge MiniBadges

The 2023 data export lists contest-category entries including Lockpick Village, Tamper Evidence, and Hackers Challenge records, preserving acquisition routes tied to challenge activity.

Compatibility: SAINTCON 2023 contests

Source
X-CTF 2016 Badge source-backed

controls

Six-button input surface

The badge used multiple buttons for menu and challenge interaction, with GPIO support preserved in the public firmware.

Compatibility: X-CTF 2016 Badge

Source

ctf entry point

Euphoria CTF badge challenge

The Euphoria CTF page says the first challenge is on the badge after Shady Tag registration at the Shadytel Experience Center.

Compatibility: ToorCamp 2024 Shadybucks Wristband

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) published pre-event schedule; completion and revision unconfirmed

current event-association record

DEF CON 34 BadgeLife Masonic33 planned recurrence

Badge.Life's live DC34 Village Schedule lists Masonic33 Badge — heal at 10:30 AM Friday August 7 and 11:00 AM Saturday August 8, 2026. It supports a planned current recurrence of the named artifact, not a new board or revision, price, allocation, stock, official DEF CON issue, admission, completed handoff, or reusable-image term.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source

debug and expansion interface

SWD, UART, I2C, and header breakout

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.

Compatibility: BSidesPDX 2017 BMD-300 Badge

Source

debug and expansion interface

Six-pin programming and signal header

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.

Compatibility: BSidesPDX 2016 ATTiny85 Badge

Source

demoscene software platform

Hackaday BASIC, CP/M, and Z80 emulation

The 2018 badge software turned the device into a BASIC and CP/M/Z80 playground for demoscene entries, games, music, serial experiments, keyboard apps, color-display work, and flash-storage hacks.

Compatibility: Hackaday Belgrade 2018 Badge

Source
CHCon 2025 Badge source-backed

display and challenge feedback

Dual 12-pixel RGB LED strips

The badge included two addressable RGB LED strips with 12 LEDs each, used for animated eyes and unlocked challenge feedback.

Compatibility: CHCon 2025 Badge

Source

display and input hardware

8×16 RGB matrix and five-button surface

The public event guide describes an 8×16 RGB LED matrix and five physical buttons on the wearable game-console badge, while the event source targets a CH32V003 board.

Compatibility: C1B3RTR4CKS 2026 CH32V003 Badge

Source

display subsystem

GC9A01 round SPI display

The main schematic includes a GC9A01 IPS SPI display, while the firmware README describes user-customizable 240x240 JPG/GIF badge images.

Compatibility: GreyCTF Summit 2025 GreyBadge

Source
X-CTF 2016 Badge source-backed

display subsystem

Nokia 5110 / PCD8544 LCD

The firmware and hardware trail document a Nokia 5110-style PCD8544 LCD as the badge display surface.

Compatibility: X-CTF 2016 Badge

Source

distribution and game

400-distributed badge and BLE game

Somerset Recon's README says 400 badges were distributed at BSides San Diego 2024 and describes a wireless Bluetooth LE rock-paper-scissors game. The count is a source-archive claim, not a recipient ledger or proof that every attendee had an identical unit.

Compatibility: BSides San Diego 2024 ESP32-C3 Badge

Source
H2HC 2023 Game Boy Badge source-backed

distribution artifact

Flashed Game Boy cartridges

The source describes flashing about 120 cartridges for the H2HC 2023 Game Boy badge/game artifact.

Compatibility: H2HC 2023 Game Boy Badge

Source
AND!XOR DC34 5N4CK3Y Badge announced pre-event

distribution model

Philanthropy-supported badge distribution

AND!XOR says its limited philanthropy sale reserves a badge for supporters while helping manufacture additional badges to give away; it says more than 84 percent are planned for free distribution through convention challenges, contests, and events.

Compatibility: AND!XOR DC34 5N4CK3Y Badge

Source

distribution scope

Top-50 on-site finals context

CSIT documents TISC@DEF CON SG as an online qualifier followed by on-site finals, while the finalist writeup says the top 50 finalists qualified and had six hours for five challenges.

Compatibility: DEF CON Singapore 2026 TISC ESP32 Trinket

Source
Portal Badge (DEF CON 34) public firmware source

documented audio and progression system

SD-card DAC audio and flash-persisted unlock state

Source initializes SD-card SPI and DAC/DMA sound playback at 22,050 Hz, with a no-SD state, amp-enable pin, and on-chip fallback settings. Separate flash-state code records diode, SAO, badge-to-badge, game, and sphere unlock flags. The sources do not establish installed media, speaker/amplifier hardware, volume, content rights, storage-card provisioning, power/runtime behavior, or final event software configuration.

Compatibility: Portal Badge (DEF CON 34)

Source

documented badge interaction

RFID slide and image-sharing interaction

The README says included slides or other RFID tags can be scanned to change what appears on the round display and mentions additional images intended for sharing or trading. It does not identify RFID frequency/protocol, tag type, reader configuration, stored content, data collection, authentication, access control, privacy practices, security properties, final gameplay rules, or a confirmed live event deployment.

Compatibility: Project interaction described in the public README; reader/tag protocol and final event behavior unverified

Source
Portal Badge (DEF CON 34) public source and design documentation

documented extension and challenge surface

Portal Gun SAO, serial badge-to-badge signal, and diode unlock

The design document says a connected Portal Gun SAO, a two-badge USB connection, and a back-side soldered diode can unlock features. Current source implements 9,600-baud serial status handling, portal-SAO and badge-to-badge counters, a retained I²C pin setup, and a directional diode check. It does not publish a final compatible accessory, connector pinout, USB electrical design, I²C behavior, voltage/current budget, or test matrix.

Compatibility: Portal Badge (DEF CON 34)

Source
BSides Vancouver 2025 Electronic Badge public refactored-source documentation

documented firmware capability

NFC and activity-progress source surface

The later source archive documents NFC tag interactions, LED progress indicators, sensors, optional Wi-Fi control-panel behavior, and a mini-CTF. The catalogue preserves that high-level feature surface while refusing to call it the exact factory image or reproduce programming and challenge instructions.

Compatibility: Documented 2025 board and later public source archive

Source
Portal Badge (DEF CON 34) public design documentation and firmware modules

documented game and interaction design

Standby, Nyan, and four-level Portal puzzle game

The design document describes Standby, Game, and Nyan modes plus a four-level puzzle in which spheres move through portals while users avoid or extinguish fire. The committed source contains standby, nyan, game, Simon, fire, display, random, and unlock modules. Design notes include TBD/possibly-change language, so this is a documented pre-event design and implementation trail rather than proof of final gameplay or attendee instructions.

Compatibility: Portal Badge (DEF CON 34)

Source
Cyb3rBytes404 Cyber-Cat Badge (DEF CON 34) public unversioned source; no GitHub releases listed

educational source archive

Public MicroPython teaching-source trail

The repository publishes starter scripts, a helper library, and code-challenge material for the named Cyber-Cat project. The release page reports no releases. This provides a public educational source trail, not a final installed event image, a configuration or operating guide, a supported update path, a source-to-device mapping, or a code/media reuse authorization.

Compatibility: Cyb3rBytes404 Cyber-Cat project documentation only

Source
Queercon 16 Q Badge historical

event ARG infrastructure

Handler missions and base station

Handler staff badges distributed missions and a chill-room base station reported aggregate progress, turning the badge game into a venue-wide social challenge.

Compatibility: Queercon 16 ARG

Source
RootedCON 2026 Pacman Badge direct project-builder account

event CTF and badge networking

Ed25519-signed ESP-NOW CTF interaction

The builder describes ESP-NOW question distribution, Ed25519 verification before display, and individual badge-signed replies to the game server. This preserves the source-described event architecture without publishing packet construction, key-recovery steps, backend endpoints, final protocol source, cryptographic review, or a general security guarantee.

Compatibility: RootedCON 2026 PACMAN/Ghost attendee CTF badge

Source

event backend

SpyNet backend interaction

The badge CTF story used a SpyNet server that logged badge activity and exposed web/application-security challenge material.

Compatibility: NoNameCon 2019 NoNameBadge

Source
RootedCON 2026 Pacman Badge direct project-builder account

event badge design and allocation

PACMAN Ghost board choices and organization-only PACMAN variant

The TechFrontiers builder account says attendees could choose red, purple, green, or blue Ghost boards, while PACMAN boards were reserved for the organization. It does not establish quantities, exact recipient ledger, final color inventory, or every physical-board variant.

Compatibility: RootedCON 2026 PACMAN/Ghost attendee CTF badge

Source
BSides Exeter 2025 Pirate Ship Badge maker-documented event interaction

event badge game

Venue treasure-chest interaction

The maker archive says attendees could use venue treasure chests to unlock additional LED modes and preserves companion source/model material. It establishes the source-described event interaction, not a chest count, deployment record, device configuration, challenge value, participant result, prize outcome, or current playable service.

Compatibility: BSides Exeter 2025 Pirate Ship Badge event context only; no current interaction, hardware, or support claim

Source
DEF CON 33 Badge historical

event challenge

Arts & Entertainment booth badge challenge

The creator announcement directed attendees to spot clues around the convention and visit the Arts & Entertainment booth to participate in the badge challenge.

Compatibility: DEF CON 33 Badge

Source

event challenge

Badge CTF contest

The 2024 Hardware Challenge Village description ties the badge to a competitive badge CTF contest and hands-on electronics tinkering.

Compatibility: BSidesSF 2024 Hardware Challenge Village Badge

Source

event challenge

Badge Hacking Ceremony

The official Hackaday schedule placed the Badge Hacking Ceremony on Saturday night from 22:00 to 24:00.

Compatibility: Hackaday Europe 2025 SAO Badge

Source

event challenge

Badge Hacking Ceremony

The official schedule data lists a Saturday 22:00 Badge Hacking Ceremony before the Hackaday Europe party.

Compatibility: Hackaday Europe 2026 Communicator Badge

Source

event challenge

Badge challenge track

The official CHCon 2018 event page says CTF, badge, and locksport challenges would run throughout the main event.

Compatibility: CHCon 2018 Identity Badge and Badge Challenge

Source

event challenge

Badge-hacking and crypto challenge

Supercon ran badge-hacking awards for blinky, deadbug, over-the-top, and crypto-solving work, with public presentations and prize recognition after the event.

Compatibility: Hackaday Supercon 2016 LED Matrix Badge

Source

event challenge

Badge-hacking ceremony

Hackaday announced a Saturday-night badge-hacking ceremony for attendees to show what they made with the Berlin Voja4 badge.

Compatibility: Hackaday Berlin 2023 Voja4 Badge

Source

event challenge

Badge-hacking ceremony

The official event schedule included a Saturday-night badge-hacking ceremony, and the heise report describes participants presenting judged badge hacks.

Compatibility: Hackaday Europe 2024 Vectorscope Badge

Source

event challenge

Badge-hacking ceremony projects

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.

Compatibility: Hackaday Supercon 2019 FPGA Badge

Source

event challenge

Badge-hacking contest projects

Post-event coverage documented camera, printer, charging, VR, thermal, time-lapse, and 3D-printer projects built around the official badge.

Compatibility: Hackaday Supercon 2017 Camera Badge

Source
DEF CON 17 Badge historical

event challenge

DEF CON 17 badge hacking contest

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.

Compatibility: DEF CON 17 Badge

Source
DEF CON 15 Badge historical

event challenge

DEFCON 15 badge hacking contest

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.

Compatibility: DEF CON 15 Badge

Source
DEF CON 14 Badge historical

event challenge

DEFCON Badge Hacking Contest

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.

Compatibility: DEF CON 14 Badge

Source

event challenge

Electronic CTF challenge context

The official CHCon 2019 about page says the CTF included cyber, physical, and electronic challenges across both main-event days.

Compatibility: CHCon 2019 Identity Tags and Badges

Source

event challenge

Electronic tinkering and programming village

The 2025 Hardware Challenge Village description frames the badge activity around electronic tinkering, programming, and competitive CTF play.

Compatibility: BSidesSF 2025 Hardware Challenge Village Badge

Source

event challenge

Functional SAO contest

The Supercon 8 Add On Contest pushed entrants toward functional SAOs using I2C, GPIO, sensors, displays, radios, and other active peripherals.

Compatibility: Hackaday Supercon 2024 SAO Badge

Source

event challenge

Grand Challenge and Konami unlock

Hackaday reports a Konami-code sequence, hidden behavior, and a Grand Challenge for hacked badges during the event.

Compatibility: NodeConf EU 2017 Badge

Source
DEF CON 30 Badge historical

event challenge

Nine-variant music challenge

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.

Compatibility: DEF CON 30 Badge

Source
DEF CON 19 Badge historical

event challenge

Non-electronic puzzle reality game

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.

Compatibility: DEF CON 19 Badge

Source
DEF CON 21 Badge historical

event challenge

Playing-card crypto matrix

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.

Compatibility: DEF CON 21 Badge

Source
DEF CON 22 Badge historical

event challenge

Propeller 1 badge puzzle platform

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.

Compatibility: DEF CON 22 Badge

Source

event challenge

Sponsor challenge flag entry

Zoom, Intigriti, HackerOne, and CTF.ae challenge legs each produced binary flags that could be entered into the badge.

Compatibility: Bug Bounty Village DC33 BBV Badge

Source

event challenge

Vectorscope badge-hacking ceremony

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.

Compatibility: Hackaday Supercon 2023 Vectorscope Badge

Source
Car Hacking Village DEF CON 34 CAN-FD CTF Badge announced; outcome unverified

event challenge access

On-premise CTF badge access

The pre-event CTF announcement says all challenges would be on-premise, purchase would not be necessary to compete, and five CHV badges would be available specifically to CTF participants. The scheduled event dates have elapsed, but final allocation and CTF operation remain unreported.

Compatibility: Car Hacking Village DEF CON 34 CAN-FD CTF Badge

Source
RVAsec 2018 Badge source-backed

event challenge context

Badge-hacking CTF room

RVAsec layout and CTF sources place badge hacking and badge-challenge material in the 2018 CTF conference flow.

Compatibility: RVAsec 2018 Badge

Source
RVAsec 2024 Badge source-backed

event challenge context

Badge-hacking event context

The official RVAsec 13 layout places badge hacking in the event context.

Compatibility: RVAsec 2024 Badge

Source

event challenge context

CTF-adjacent conference context

The same official sources place the badge experience alongside a Capture The Flag competition, technical talks, hands-on workshops, and networking, but do not yet expose badge-specific challenge mechanics.

Compatibility: BSides Porto 2026 Electronic Badge Experience

Source
GPN17 Badge historical

event challenge ecosystem

Hack-the-Badge challenges

The GPN17 challenge page collected badge-hacking tasks, scoring, and prize context for attendees during the event.

Compatibility: GPN17 Badge

Source
Disobey 2026 Badge source-backed

event challenge firmware

CTF challenge firmware station

The official page documents a second CTF firmware path and a flashing station near the CTF area, with source release promised after the event.

Compatibility: Disobey 2026 Badge

Source

event challenge integration

Hacker Challenge registration

The official badge page and registration manual tie the badge to Hacker Challenge participation and document pairing the badge with the challenge server.

Compatibility: SAINTCON 2017 Hacker Challenge

Source

event challenge integration

Hackers Challenge badge registration

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.

Compatibility: SAINTCON 2016 Hackers Challenge

Source

event challenge station

Hut 6 teleprinter challenge station

Attendees visited a Hut 6 station with a teleprinter-style receipt printer to receive intercepted messages for Enigma decoding.

Compatibility: SAINTCON 2019 Badge Challenge

Source

event challenge track

Hardware Hacking Village challenges

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.

Compatibility: LayerOne 2025 HHV

Source
h-c0n 2026 CTF BADge source-backed

event challenge window

Registration pickup and timed CTF

The official post says participants could start the CTF when registration opened on February 6, 2026 at 16:45, with the competition ending on February 13 at 17:00 or when three participants solved every flag.

Compatibility: h-c0n 2026 CTF BADge

Source
Disobey 2026 Badge source-backed

event competition

Hardware mod and miniapp competitions

The competition rules solicit hardware mods, 3D models, apps, games, and standalone firmware for the badge, and list public hardware-mod submissions.

Compatibility: Disobey 2026 Badge

Source
BSidesPDX 2018 ATTiny861 Badge official schedule

event context

BSidesPDX 101 badges context

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.

Compatibility: BSidesPDX 2018 ATTiny861 Badge

Source
BSidesPDX 2019 Multnomah Badge official schedule

event context

BSidesPDX 101 badges context

The official schedule says BSidesPDX 101 covered CTF, contests and events, badges, and more on Friday morning.

Compatibility: BSidesPDX 2019 Multnomah Badge

Source

event context

Community BSides CTF context

The official post-event page reports the April 2, 2026 IUT de Saint-Pierre conference, about 80 participants, more than 10 CTF teams, keynotes, and conference sessions.

Compatibility: BSides Reunion 2026 Participant Badge

Source

event firmware

Public game-console firmware

SEIF-UAM publishes C and PlatformIO source for the event badge's menu and compact game collection. The catalogue links the source but does not reproduce build, flashing, game-control, or hidden-feature instructions.

Compatibility: C1B3RTR4CKS 2026 CH32V003 Badge

Source
AND!XOR DC28 Badge historical

event game

BENDERPISS standalone CTF

The badge hosted a BENDER CTF variant playable directly on the badge while mirroring interaction over an RS232 serial connection.

Compatibility: AND!XOR DC28 Badge

Source

event game

Challenge server and unlock flow

The challenge server used distinct RF settings, periodic hints, player-state persistence, 88-miles-an-hour and 1.21-gigawatts stages, and an XOR/base64 unlock payload for the final box.

Compatibility: BSides Cape Town 2017 RFCat Badge

Source

event game

HITCON Token and Hacker Cat activity

The official 2018 pages introduced digital currency into souvenirs, HITCON Token collection, and Hacker Cat upgrades alongside the Wallet badge context.

Compatibility: HITCON CMT 2018 HITCON Wallet Badge

Source

event game

IR faction game

Badges were assigned red, blue, or green factions and used IR interactions plus server-side logic to convert or level nearby badges during the conference.

Compatibility: BSides Cape Town 2016 Badge

Source
DEF CON 27 Badge historical

event game

NFMI badge pairing game

The DEF CON 27 badge game used near-field magnetic induction badge interactions and role-specific badge types to advance through DEFCON letter levels.

Compatibility: DEF CON 27 Badge

Source
HITCON 2025 PCB Badge source-backed

event game

Red-vs-Blue tower capture

The official guide describes Red-vs-Blue tower capture behavior as a team game played through the badge ecosystem.

Compatibility: HITCON 2025 PCB Badge

Source
DEF CON 20 Badge historical

event game

Secret-society badge challenge

The badge puzzle combined firmware, hieroglyphic shapes, binary codes, lanyards, venue clues, program material, and social interaction into a secret-society narrative.

Compatibility: DEF CON 20 Badge

Source
DEFCON China 1.0 Badge source-backed

event game

Tree-lighting conference task game

Attendees illuminated roots and branches of the badge's tree by completing conference tasks, with completion turning the badge into a sparkling tree display.

Compatibility: DEFCON China 1.0 Badge

Source

event game

Trick-or-Treat and Attribution game modes

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.

Compatibility: BSidesPDX 2024 OpenTaxus Badge

Source

event game content

Challenge content

The public team record credits challenge work, making puzzle content part of the badge's event role even though technical details remain sparse.

Compatibility: HackerHotel 2023 Badge

Source

event game content

Challenge workflow record

The talk and schedule context preserve the badge as a HackerHotel challenge surface, even though component-level firmware and app-store records remain open.

Compatibility: HackerHotel 2025 Badge

Source
Laser* Tag Badge DS (DEF CON 34) announced pre-event

event game context

DEF CON-week pickup and multi-day game

The public late-July update announces DEF CON-week pickup points and a wearable multi-day infrared tag game, while final assembly and flashing remain in progress.

Compatibility: Laser* Tag Badge DS (DEF CON 34)

Source

event information app

Schedule, score, and zone display

The badge could display the conference schedule, live Hacker Challenge score, and current location zone within the venue.

Compatibility: SAINTCON 2015 event services

Source

event infrastructure

Interactive panel integration

Interactive panels were used for CTF signup, answer submission, attendee Sched-profile display, nicknames, profile pictures, and XP points.

Compatibility: BSides Prague 2025 Electronic Badge

Source

event lifecycle

Third-edition event context

The CFP, current sponsor page, and Humanitix listing identify the July 27-28, 2026 Amora/Hilton Adelaide event as the third BSides Adelaide and anchor CTF, village, hardware, embedded, IoT, and RF topic context without making badge-implementation claims.

Compatibility: BSides Adelaide 2026 Identity Lanyard Badge

Source

event mechanic

Badge mini-games card-reader path

HITCON placed card readers and mini-games at booths and scattered around the venue, letting attendees activate interactions with their badge.

Compatibility: HITCON CMT 2023 NFC Badge

Source

event mechanic

Score-accruing PCB badge activities

The 2024 activity system used the PCB badge as an attendee score surface across HITCON activities and games.

Compatibility: HITCON CMT 2024 PCB Badge

Source
HITCON CMT 2019 Badge source-backed

event mechanic

Sponsor LED unlock path

Attendees could unlock badge LEDs by solving the board puzzle or completing sponsor booth challenges, with all LEDs unlocked leading to a HITCON lottery chance.

Compatibility: HITCON CMT 2019 Badge

Source

event puzzle

Badge-challenge clue surface

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.

Compatibility: BSides Tampa 2026 Badge Challenge

Source
DEF CON 24 Badge historical

event puzzle

Lanyard and conference-media trail

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.

Compatibility: DEF CON 24 Badge

Source
DEF CON 23 Badge historical

event puzzle

Noir key-card trail

Public writeups and attendee recaps describe DEF CON 23 key-card material as part of the noir-themed badge challenge trail.

Compatibility: DEF CON 23 Badge

Source
Disobey 2019 Badge historical

event puzzle content

Puzzle pointers

The Disobey 2019 badge firmware contained pointers used as part of the event's hacker puzzle competition.

Compatibility: Disobey 2019 Badge

Source
TiDAL in progress

event service app

Barstats

James Harrison's Barstats is an event-related Hatchery app, documenting that TiDAL apps included live camp-service integrations as well as graphics and games.

Compatibility: TiDAL and EMF 2022 event data/services

Source
CarolinaCon Online 2021 Badge Kit source-backed boundary

event software context

Public CTF source boundary

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.

Compatibility: CarolinaCon Online 2021 event context

Source

event venue

USF Marshall Student Center context

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.

Compatibility: BSides Tampa 2026

Source
HackNWA 2026 VIP Assembled Badge official pre-event announcement and event page

event-programme context

CTF and hardware-hacking activity context

HackNWA promoted a CTF, ASMb1337, Solder Village, and Badge/Hardware Hacking activities for the conference. The sources do not identify the VIP Assembled Badge as their subject, interface, prerequisite, prize, or device platform.

Compatibility: HackNWA 2026 event context only; no badge-to-activity technical link is documented.

Source

firmware and app archive

MicroPython, CTF, and app source archive

The repository provides MicroPython application source and firmware documentation that describes compiled C modules and CTF challenge support. No reviewed release, tag, post-event guide, or device record verifies the production image or an owner-support path for 2026 units.

Compatibility: BSidesFW2026Badge source archive

Source
Open Sauce 2026 Badge designer and independent attendee source-backed

firmware and community outcome

Original Bop It and four-game post-event hacking trail

The designer archive describes its Bop It firmware and says at least two people hacked badges Saturday night and showed four new games Sunday. The independent attendee README calls the original a Bop It-style game and documents a replacement project. The record preserves the outcome at a high level without reproducing game, programming, or modification instructions.

Compatibility: Open Sauce 2026 Badge

Source
rad1o historical with 2022 update

firmware and l0dable bundle

binary-cccamp2015 firmware package

The binary repository preserved flashable camp firmware, HackRF images, games, animations, fonts, images, l0dables, and a REV 05 release aligned with HackRF v2022.09.1.

Compatibility: rad1o firmware update workflow

Source
Shitty Kitty V2 (DEF CON 34) storefront-documented and announced

firmware and user interface

SkittyOS features and announced firmware refresh

The listing describes SkittyOS graphics demos, scrolling text, font/character settings, independent screen modes, and flash-persisted settings, and announces future firmware with new graphics and puzzles. No firmware release, source, binary, flashing guide, or license is linked.

Compatibility: Shitty Kitty V2 (DEF CON 34)

Source
RVAsec 2026 Badge repository-backed

firmware archive

Badge app source tree

The source tree preserves app/game modules, CLI code, display buffers, platform HAL files, and generated image assets for the RVAsec 2026 badge software.

Compatibility: RVAsec 2026 Badge

Source
DEF CON 24 Badge historical

firmware behavior

Konami Code serial unlock

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.

Compatibility: DEF CON 24 Badge

Source

firmware behavior

Mode-button jigawatts animation

The firmware watches a pull-up mode button and triggers a named animation routine that ramps the center LED before stepping the grouped LEDs.

Compatibility: SEC Youth Challenge 2023 Flux Decoder Badge

Source

firmware behavior

PwnPet Pwn Llama runtime

The badge repository identifies the PwnPet BLE virtual-pet framework, persistent state, peer or friend interaction, integrated CTF challenges, and this Pwn Llama variant at a high level.

Compatibility: Unknown Security Conference 2026 Pwn Llama Badge

Source

firmware challenge

CRC16/XMODEM firmware integrity repair

The A Nice Edit walkthrough describes firmware validation, red-screen failure after an edited flash, CRC16/XMODEM analysis, corrective bytes, and restoring a valid challenge-completion firmware image.

Compatibility: CyberThreat 2024 Hackable Badge

Source
h-c0n 2026 CTF BADge repository-backed

firmware challenge

RP2350 RISC-V CTF firmware

The public hcon2026hwctf repository provides ctf.uf2 and describes RP2350/RISC-V Hazard3 exploitation challenges for the HC0N 2026 hardware CTF.

Compatibility: h-c0n 2026 CTF BADge

Source

firmware challenge

Signed OTA firmware challenge

TechMaker describes OTA firmware updates with digital-signature verification, key recovery from badge information, and participant-signed firmware as a CTF path.

Compatibility: NoNameCon 2019 NoNameBadge

Source
THOTCON 0xD Badge public demo archive

firmware examples

Arduino/ESP32 demo firmware archive

The `thotcon-examples` repository preserves cleaned-up Arduino/ESP32 examples for touch input, LEDs, audio modes, display output, menus, mini-game placeholders, and credits.

Compatibility: THOTCON 0xD Badge

Source
BugCON 2023 Badge archived source

firmware examples

DinoGame and Spoof firmware examples

Separate firmware directories preserve an SSD1306 OLED DinoGame sketch and a BLE advertising Spoof sketch modified for ESP32-S3.

Compatibility: BugCON 2023 Badge

Source

firmware feature

Public welcome, animation, and game firmware

The repository's public Arduino/C++ source describes display states, animations, games, and personalization for the badge without establishing a final production firmware image for every unit.

Compatibility: Security Fest 2026 RP2040 Badge

Source

firmware image

Custom MicroPython firmware

The firmware README documents a custom MicroPython 1.26.0 image with compiled badge-challenge modules and a Russ Hughes GC9A01 C display driver.

Compatibility: BSides Fort Wayne 2025 Badge

Source

firmware interface

USB CDC NDEF command interface

The badge exposes USB CDC commands for URI, TEXT, VCARD, HELP, ABOUT, STATUS, CHALLENGE, LEDS, and SOLVE, with serial operation documented at 115200 baud.

Compatibility: DragonJARCON 2025 NFC Hardware Badge

Source

firmware interface

USB-serial badge interface

The badge is played by turning off battery power, connecting micro-USB, opening a terminal or Arduino IDE serial monitor at 9600 baud with Both NL & CR, and sending three stars to enter CTF mode.

Compatibility: SINCON 2023 Khong Guan Building CTF Badge

Source

firmware lifecycle

Conference and CTF PlatformIO firmware

The repository documents separate PlatformIO build/upload environments for conference and CTF firmware on top of Espressif IDF.

Compatibility: NorthSec 2025 Badge

Source

firmware lifecycle

Conference, CTF, and add-on firmware targets

The repository documents PlatformIO/ESP-IDF environments for conference, CTF, and addon firmware plus USB serial monitoring and DTR reset behavior.

Compatibility: NorthSec 2024 Badge

Source
OzSec 2025 CRASHANDBURN Badge source-backed work in progress

firmware prototype

MicroPython selectable game set

The current main script selects HiLo, DTMF, Kode, and Rock-Paper-Scissors games, updates associated LEDs, registers buttons, and restores a random idle blink mode.

Compatibility: OzSec 2025 CRASHANDBURN firmware source snapshot

Source

firmware release

v2026.2 and CTF firmware binaries

GitHub Releases publishes the v2026.2 UF2 binary plus a v2026.2-ctf prerelease binary for the 2026 badge.

Compatibility: RVAsec 2026 Badge

Source

firmware source

Arduino badge program

The official badge page links an Arduino sketch with TimerOne LED scanning, two interrupt-driven buttons, menu modes, POV output, and a not-binary game path.

Compatibility: AVTOKYO 2015 Electrical Badge

Source

firmware source

GPL-3.0 firmware archive

The public repository preserves the badge firmware, ESP32 binary, assets, Arduino build settings, TFT_eSPI configuration, SDL local-debug path, games, demos, OTA code, WiFi scanner, and Bluetooth material.

Compatibility: BSides Cape Town 2019 Badge

Source
Hackers Teaching Hackers 2026 Eagle 5 Badge public post-event initial release

firmware source archive

Public firmware, CLI, animation, and CTF source

The July source archive includes firmware code for a badge CLI, LED animations, BLE-related components, and CTF state material. The catalogue records the published source context without giving operational, radio, flashing, or challenge-completion instructions or claiming a deployed production image.

Compatibility: Eagle 5 2026 HTH source archive

Source

firmware training

Arduino IDE programming workflow

Participants learned IC programming and used the Arduino IDE, then shared code and developed new badge features with others at the conference.

Compatibility: Kiwicon 2038 Intro to Badge Hacking Training Badge

Source
DEF CON 32 Badge archived

firmware workflow

Official firmware and hardware archive

The DEF CON media-server badge directory published hardware, firmware, game, music, asset, and later FREEWiLi firmware files for post-event hacking.

Compatibility: DEF CON 32 Badge

Source

firmware workflow

Optiboot and avrdude firmware workflow

The final-challenge walkthroughs document Optiboot at 115200 baud and avrdude commands for dumping and writing flash through an Arduino-compatible bootloader.

Compatibility: CyberThreat 2024 Hackable Badge

Source
DEF CON 20 Badge archived

firmware workflow

Propeller firmware release path

Parallax and DEF CON published firmware, schematic, top-level objects, LED examples, VGA/PS2 examples, and conference-DVD materials for post-event badge hacking.

Compatibility: DEF CON 20 Badge

Source

firmware workflow

Stock firmware restore and workshop archive

The repository preserves esptool.py commands for restoring stock firmware plus a workshop PDF used for THOTCON 0xA badge hacking.

Compatibility: THOTCON 0xA / Infinity Badge

Source
DEF CON 29 Badge archived

firmware workflow

UF2 firmware update workflow

Forum and field-report sources document firmware updates through USB storage/UF2-style workflows and role-specific challenge firmware behavior.

Compatibility: DEF CON 29 Badge

Source
leHACK 2026 Badge Hackropole public source guide

firmware workflow

WLED v0.15.5 flash and Wi-Fi setup

The source guide aligns the distributed firmware with WLED v0.15.5, documents ESP32-S3 bootloader flashing with esptool, a WLED Wi-Fi access-point onboarding flow, a web interface, and touch controls for lighting and effects.

Compatibility: Hackropole source-tree workflow; it is not evidence of an event-specific application, CTF, backend, account, final firmware state, or support/update service for every workshop artifact.

Source

firmware workflow

megaTinyCore programming note

The PCB silkscreen records ATtiny1614 Arduino instructions pointing builders toward the megaTinyCore workflow for the microcontroller family.

Compatibility: SEC Youth Challenge 2023 Flux Decoder Badge

Source
Aerospace Village DC34 SR-71 CTF Badge no public repository linked yet

future technical-source statement

After-con code or firmware availability statement

The public roster says code or firmware will be available after the con, but provides no URL, release date, source license, binary, build instructions, hardware target, flashing method, support channel, or evidence of a completed release.

Compatibility: SR-71 planned DEF CON 34 record; future release is not modeled as current software

Source

game

Snake game

The fifth firmware screen provided a playable snake game, giving the badge an explicit entertainment surface beyond schedule and discovery functions.

Compatibility: RomHack Camp 2022 Badge

Source
Fri3d 2024 Badge current/historical

game add-on

Blaster

Fri3d 2024 documentation includes a blaster add-on for camp play and badge interaction.

Compatibility: Fri3d 2024 Badge

Source
Fri3d 2022 Badge historical

game add-on

GameOn

Fri3d 2022's add-on ecosystem includes GameOn-style game hardware tied to badge play.

Compatibility: Fri3d 2022 Badge

Source
TiDAL post-event

game app

Doom!

Phlash's Doom port reached revision 8 in 2024; the Hatchery notes basic play, menus and demo levels, while warning that it overwrites the unused OTA partition and cannot ship the WAD through Hatchery because of upload size.

Compatibility: TiDAL with Doom binary and WAD assets

Source

game behavior

CTF flag endpoint

The README and firmware document `/flag` and `/flag?newflag=...` behavior, with source code initializing the default flag as BADGERMASTER.

Compatibility: BSidesPDX 2015 Badger Badge

Source
H2HC 2023 Game Boy Badge source-backed

game content

Custom music and hidden interactions

The game includes custom assets, music, maps, and hidden interactions rather than firmware for a microcontroller badge.

Compatibility: H2HC 2023 Game Boy Badge

Source

game firmware app

CB Pong

CB Pong can run as a simple two-player Pong game or, when connected, as a game against a BCD-0o27 cyberdeck through the external interface.

Compatibility: BalCCon Mini Cyberdeck 0o00 plus optional BCD-0o27

Source

game firmware app

Space Invaders

The MC-0o00 documentation links a Space Invaders game by Jovan, published with source code and released under the MIT license.

Compatibility: BalCCon Mini Cyberdeck 0o00

Source

game interface

3.3 V serial terminal game interface

The challenge used a 3.3 V USB-serial adapter on the SAO connector at 115200 8n1, with OS-specific Badge.Team guides for Linux, macOS, and Windows.

Compatibility: HackerHotel 2020 Badge

Source

game-to-hardware lifecycle

Challenge-unlocked parts progression

Rabbit Radio reports that challenge progress unlocked more parts for the PCB, turning puzzle progress into a physical badge build-up mechanic.

Compatibility: Easterhegg 2024 RCA Badge

Source
Fri3d 2022 Badge historical

game/puzzle add-on

Time Blaster

The Time Blaster add-on path captures the badge as a game and camp-activity peripheral.

Compatibility: Fri3d 2022 Badge

Source

hardware CTF challenge

Black Badge challenge

The official challenge asked participants to assemble the collector badge, analyze its embedded secure system, and solve first for a Nuit du Hack Black Badge life pass.

Compatibility: Nuit du Hack 2014 Collector Badge

Source

hardware add-on

CYBER SCARAB

Tilde Industries produced a CYBER SCARAB add-on for the HackerHotel 2020 challenge badge.

Compatibility: HackerHotel 2020 Badge

Source

hardware add-on

RCA badge add-ons

Participant reporting says CTF success yielded cool add-ons for the Easterhegg badge and that the badge could later be soldered in the hackerspace.

Compatibility: Easterhegg 2024 RCA Badge

Source

hardware architecture

Colour IPS ESP32 game badge core

The first-hand making-of post documents an ESP32 badge with 1.3-inch 240x240 IPS colour display, custom PCB, touch buttons, 18650 battery, and 3D-printed case.

Compatibility: BSides Cape Town 2019 Badge

Source
NorthSec 2021 Badge source-backed

hardware architecture

ESP32 LCD game board

The 2021 badge combined ESP32, 240x240 LCD, Wi-Fi, NeoPixels, six buttons, buzzer, and USB or external battery power.

Compatibility: NorthSec 2021 Badge

Source

hardware architecture

MS51FB9AE CTF badge core

The 2024 Wombat badge combined a custom PCB, MS51FB9AE Nuvoton microcontroller, CH340G USB serial, micro-USB, RGB LED, six challenge LEDs, CR2032 holder, and slide switch.

Compatibility: BSides Adelaide 2024 Wombat Badge

Source

hardware architecture

MediaTek wireless badge platform

HITCON's official events page says the 2017 electronic badge was powered by a MediaTek chipset and included Wi-Fi, Bluetooth LE, joystick/game-controller input, infrared, and an LED display.

Compatibility: HITCON CMT 2017 MediaTek Badge

Source

hardware challenge

Secret hardware challenge

Creator and attendee writeups document a hidden challenge beneath the published CTF path, with PCB inspection and extra LED behavior rewarding hardware probing.

Compatibility: BSides Adelaide 2025 Wombat-2 CTF Badge

Source

hardware challenge mod

Airship LED unlock path

Hackerware documents replacing C1 and C2 with 22 pF capacitors, then adding SMD LEDs and resistors at D9-D13 and R8-R12 to play the CTF and unlock airship lights.

Compatibility: Security Fest 2024 Feskekôrka Piano Badge

Source
DEF CON 29 Badge historical

hardware expansion

Dual SAO connector host

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.

Compatibility: DEF CON 29 Badge

Source
CactusCon 14 Badge source-backed

hardware expansion

MicroSD, buzzer, and SAO v1.69 expansion

The public design archive preserves MicroSD, buzzer, and Badgelife SAO v1.69 expansion evidence for badge hacking and add-on use.

Compatibility: CactusCon 14 Badge

Source

hardware expansion

SAO and Qwiic/STEMMA QT expansion

The BornHack 2022 badge exposed accessory connectors and a prototyping area for hardware add-ons.

Compatibility: BornHack 2022 Game On

Source
Ruxcon 2017 HHV Badge source-backed

hardware interface

3.3V UART badge access

The official HHV page required attendees to bring a 3.3V USB-UART adapter, and the EasyFlag writeup shows UART boot output used to interact with the badge challenge.

Compatibility: Ruxcon 2017 HHV Badge

Source

hardware interface

Four-line screen and joystick interface

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.

Compatibility: BSidesSF 2024 Hardware Challenge Village Badge

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) published schedule; outcome unconfirmed

historical event-association record

DEF CON 33 BadgeLife Masonic33 scheduled drop

The recovered DEF CON 33 schedule lists a 10:30-10:59 PDT BadgeLife Community Masonic33 Badge drop credited to Heal-Hak4Kidz. This establishes published 2025 creator activity, not organizer issuance, attendance entitlement, confirmed stock, completed handoff, recipient allocation, or admission function.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source

host CAN tooling

CHV Badge Tools

`chv_badgetools` provides `chv-candump`, `chv-cansend`, automatic USB-port discovery, and a `python-can` interface plugin for the DEF CON 34 CTF badge.

Compatibility: Car Hacking Village DEF CON 34 CAN-FD CTF Badge

Source

identity artifact

Badge and lanyard admission package

The current official FAQ says every participant gets access to all tracks plus a BSides Tampa shirt, badge, lanyard, and happy-hour access.

Compatibility: BSides Tampa 2026 Badge Challenge

Source
CPEC DC34 MechBattle Badge public source; event behavior unconfirmed

in-progress code surface

Source-level display, BLE, QR, and sound modules

The game repository references ST77xx display libraries, NimBLE, QR-code support, and a buzzer-oriented sound module. It does not publish a stable radio protocol, user-consent model, player-data practice, safe electrical design, final UI, host compatibility matrix, or proof that these modules ship together in a DEF CON artifact.

Compatibility: CPEC DC34 MechBattle Badge

Source

included SAO set

Red and blue fighter SAOs

The NilbinSec announcement and product page describe two included SAOs, red and blue fighters, with game data and hidden interactions carried through EEPROM.

Compatibility: NilbinSec DC33 Hack 'Em Crack 'Em Robots

Source

infrared game

Laser* Tag multiplayer game

Every powered-on official badge played an infrared Laser* Tag game with five color teams, valid-hit cooldowns, and individual contributions to aggregate team scores.

Compatibility: DEF CON Singapore 2026 DC-SG-1 Official Badge

Source
Disobey 2020 Badge historical

interaction layer

Touch-button launcher and keyboard

The Disobey 2020 docs describe Gameboy-inspired touch buttons, a launcher opened with START, a nickname app, and an on-badge keyboard with input, cursor, and confirmation modes.

Compatibility: Disobey 2020 Badge

Source
BSides Dublin 2026 Harp Badge post-event source-backed

interaction tooling

Serial CLI and badge CTF

The repository documents a serial CLI and four CTF flags hidden in the badge.

Compatibility: BSides Dublin 2026 Harp Badge

Source

kids badge

Jr Hacker IR laser-tag badge

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.

Compatibility: BSidesKC 2019 Jr Hacker badge

Source
Laser* Tag Badge DS (DEF CON 34) planned with stated fallback

leaderboard synchronization

LoRa and QR score sync

The maker page describes online leaderboard score syncing over LoRa if RF conditions permit, with QR-code encoding of game data as the documented fallback.

Compatibility: Laser* Tag Badge DS (DEF CON 34)

Source
RVAsec 2021 Badge source-backed

lineage context

Annual HackRVA badge lineage

HackRVA describes the RVAsec electronic badge programme as a recurring badge-team effort with schedules, games, and surprises.

Compatibility: RVAsec 2021 Badge

Source
Hackfest 2019 Electronic Badge official history backed

lineage milestone

CTF electronic-badge introduction

Hackfest's official history says the 2019 CTF introduced an electronic badge and that participants immediately appreciated it.

Compatibility: Hackfest 2019 CTF

Source
2026 eChallengeCoin (DEF CON 34) conflicting source claims retained

linked-primary-source hardware description

USB, touch, NeoPixel, speaker, and no-battery source surface

AoSC describes Micro-USB, one large touch pad, three NeoPixel groups, a small speaker, and no battery. The linked Coin M0 profile instead describes native USB-C, three capacitive touch pads, three RGB-NeoPixel groups, and a speaker. The shared lighting/audio concepts are source-backed, but the exact connector, touch count, board revision, LED count/current, speaker part, power path, and final 2026 configuration remain unresolved.

Compatibility: 2026 eChallengeCoin (DEF CON 34)

Source
NilbinSec DC34 Main Badge Fuzzer SAO maker-documented firmware behavior

main-badge interface probe

Mode 2 open-drain CPU-wake assertion

The README describes Mode 2 as triggering the open-drain CPU wake-up interrupt on GPIO4 of the right SAO port. The source holds its configured GPIO line low while the Attack/Trigger switch is pressed, then releases it to high impedance. This documents the public implementation, not a safe/authorized use, final badge compatibility, or successful challenge result.

Compatibility: NilbinSec DC34 Main Badge Fuzzer SAO; right-side target-port interpretation

Source

maker and vendor-described game surface

CTF, bling modes, Drinking Roulette, and programmable claim

The vendor list says CTF challenges unlock extra features and bling modes, names Drinking Roulette, and calls the product fully programmable. No source publishes game rules, age/access policy, challenge/solution path, reset path, player scope, score service, firmware, configuration, content rights, data handling, or security review.

Compatibility: Gunslinger-B-Gone Badge and Sheriff SAO Combo (DEF CON 33)

Source
2026 eChallengeCoin (DEF CON 34) donation/pickup process announced; outcome unconfirmed

maker-described acquisition and manufacturing context

Choose Your Own Charity gift and student-brass statements

AoSC says a confirmed $100-or-greater donation to a youth-STEM-supporting charity may receive a 2026 eChallengeCoin by U.S. mail or DEF CON pickup, and says the first 20 recipients are intended to have brass blanks created by students from a local high-school engineering program. These statements do not establish charity status, tax treatment, donation validation, privacy/retention practice, quantity awarded, recipient eligibility, shipping, pickup, school identity, manufacturing quality, payment, or final delivery.

Compatibility: 2026 eChallengeCoin (DEF CON 34)

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) high-level gameplay claims

maker-described badge challenge

Analog-input hidden LED-sequence puzzle

The listing says two analog inputs are tuned precisely to unlock a hidden LED pattern, and solving four puzzles unlocks the badge's full potential. It does not publish the inputs, sequence logic, calibration range, solutions, reset behavior, accessibility path, scoring, or outcome evidence.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source
2026 eChallengeCoin (DEF CON 34) maker-described planned software behavior

maker-described badge game

Sara and the Missing Artifacts serial text adventure

The maker says the 2026 coin presents as a serial device when connected to a computer and hosts the Sara and the Missing Artifacts terminal text adventure. It also says new firmware can support other adventures. No public game source, binary, command reference, release/version mapping, host test matrix, reset/save guide, accessibility documentation, or support policy was recovered.

Compatibility: 2026 eChallengeCoin (DEF CON 34)

Source
Wordweaving Badge (DEF CON 34) official maker pages disagree on count

maker-described badge game

Top-down adventure and broad CTF challenge claim

The project page describes a Game Boy-inspired top-down adventure with 30-plus CTF puzzles, while the live listing describes 35-plus CTF and puzzle challenges. Both frame the badge as a playable adventure with unlockable bling; no public challenge archive, final count, solution policy, ruleset, scoring system, accessibility review, or completed game behavior is published.

Compatibility: Wordweaving Badge (DEF CON 34)

Source
DC-34 Countdown to Singularity Badge public pre-event README documentation

maker-described badge purpose

Eight-display singularity-estimate interaction

The README says the badge lets users display an estimate for when the AI singularity will occur, with front buttons that shift that estimate, eight seven-segment displays, and a real-time clock. It documents a source-project interaction concept, not an assembled unit, final screen/readout behavior, calibrated clock, usability result, event challenge, prize, or completed distribution.

Compatibility: DC-34 Countdown to Singularity project as described by its public README; final physical unit unverified

Source
FrogStar Badge (DEF CON 33) game and CTF behavior claimed

maker-described challenge and interaction surface

Frog CTF, secret content, and built-in game framing

The maker says a frog-themed CTF unlocks GIFs, bling, and secret surprises, and that a frogger-like game is built into the badge. No source provides challenge rules, release dates, solution path, scoring/leaderboard, content source or license, offline/online behavior, telemetry, personal-data handling, security model, or preservation archive.

Compatibility: FrogStar Badge (DEF CON 33)

Source
Submarine Badge & Pirate SAO (DEF CON 33) high-level game and CTF claims

maker-described challenge and narrative

DEF-SEA CTF and undersea story surface

The seller describes an underwater world where CTF challenges deliver packages to DEF-SEA inhabitants, potentially with other players, plus pirate battles, underwater cults, and a hidden Atlantis. No source provides rules, release timing, solution path, challenge inventory, player count, score validation, server/network behavior, content provenance, archive, or accessibility information.

Compatibility: Submarine Badge & Pirate SAO (DEF CON 33)

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) component-level product description

maker-described electronic hardware surface

ATtiny1616, potentiometer, LED, and UPDI surface

The maker names an ATtiny1616, two 10 kΩ potentiometers, eleven independently controlled LEDs, and a UPDI-compatible one-wire programming interface. It does not publish circuit or pinout documentation, LED electrical characteristics, controller configuration, programmer settings, firmware, or electrical-safety validation.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) high-level physical description

maker-described form factor and power

AAA-powered 4.25-inch custom PCB claim

The listing says the custom PCB is 4.25 inches tall with black solder mask and white silkscreen and runs from included AAA batteries through a 4.5 V input. It does not identify the battery holder, power path, regulator, current draw, runtime, protection, board thickness, materials, mechanical test, or compliance evidence.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source
H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34) team-announced pre-event experience

maker-described game software

Firmware CTF and gated-backend claim

The team says the CTF lives in firmware, is multi-stage and not solo-completable, uses real protocols, and unlocks backend pages through progress. No code, binary, challenge archive, protocol specification, endpoint, scoring system, access policy, data policy, or final running service is published in the reviewed sources.

Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)

Source
Wordweaving Badge (DEF CON 34) official maker product description

maker-described hardware challenge

Additional-component soldering challenge claim

The live listing says that soldering additional components unlocks CTF challenges. It does not identify the components, modification points, tools, difficulty, required safety precautions, challenge behavior, allocation, assembly instructions, or support scope.

Compatibility: Wordweaving Badge (DEF CON 34)

Source
FightDystopia 2025 Badge (DEF CON 33) high-level game and display claims

maker-described interaction and lighting surface

CTF, puzzle, GIF/bling, and twelve-RGB-LED claim

The seller says a CTF with Windows Vista-era throwbacks and hardware/software puzzles unlocks bling and GIFs, and names twelve RGB LEDs with custom light patterns. It does not publish the challenge rules, source/licensing of content, LED part/current, score/service path, solution/reset method, privacy/data handling, or final behavior.

Compatibility: FightDystopia 2025 Badge (DEF CON 33)

Source
Station 562 Badge (DEF CON 34) first-hand pre-event announcement

maker-described interaction surface

BLE number-station, proximity-game, and MIDI feature set

The maker describes a BLE number-station puzzle, red-versus-blue proximity game, autonomous social/dance mode, expressive BLE MIDI instrument, tamper-evident mode, Setup menu, and optional hardware CTF. The source does not describe BLE services, radio range, pairing, player/account data, game protocol, MIDI mapping, tamper condition, CTF rules, security controls, or final behavior.

Compatibility: Station 562 Badge (DEF CON 34)

Source

maker-described interaction surface

Customizable LEDs, theremin, and collectible-system claims

The Standard product description advertises customizable LEDs, a theremin, and more than 90 collectibles; the shop's social metadata also names a 3D-code scanner. No reviewed source explains the underlying components, collectible encoding, scanner modality, data storage, interoperability, game rules, accessibility, privacy, service availability, or post-event preservation. These are maker-described features, not a verified technical specification.

Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) listing contents claimed; delivery unconfirmed

maker-described package

VHS-style package and bonus merchandise

The maker describes a custom VHS-style lore box plus embroidered patches, themed lanyard, and three exclusive vinyl stickers. It does not establish the exact contents of every unit, package revision, artwork rights, recipient allocation, completed shipment, pickup, or resale state.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source
2026 eChallengeCoin (DEF CON 34) planned limited edition; final production and allocation unconfirmed

maker-described production and physical form

Planned 40-brass-coin limited run

AoSC says the 2026 edition is a limited release with a plan for 40 brass eChallengeCoins, each weighing 46 grams. It does not establish a finished quantity, serialized allocation, component parity, production date, inventory, recipients, shipping/pickup outcomes, replacements, resale, or post-event availability.

Compatibility: 2026 eChallengeCoin (DEF CON 34)

Source

maker-described puzzle surface

Hardware/software and soldering puzzle claim

The product page says Submarine includes hardware and software puzzles plus a few soldering challenges. It does not list a component kit, soldering steps, temperature/safety guidance, challenge prerequisites, tooling, board revisions, troubleshooting, reset path, solution policy, or completed event-support record.

Compatibility: Submarine Badge & Pirate SAO (DEF CON 33)

Source
Ouroboros Badge (DEF CON 34) source claims; independent validation not found

maker-described software and protocol surface

Bare-metal UART puzzle and performance/security claims

The product and maker post describe bare-metal/pure RISC-V assembly on CH32V003 and a custom UART puzzle at 115200 baud; the product describes fourteen stages, Davies-Meyer, SPECK-128/256, a constant-time MAC, and an 8 MHz low-power mode. These claims do not substitute for matching released firmware, binaries, build or flash instructions, test vectors, benchmark method, security review, recovery process, or proof that any shipped unit matches the description.

Compatibility: Ouroboros Badge (DEF CON 34)

Source
MalO SAO (DEF CON 34) project work ongoing before the event

maker-described software experience

Games, puzzles, screensavers, messages, and editable-firmware claim

The sources describe games, puzzles, screensavers, messages, user modification through USB-C, a compiled C library, and an evolving Python/C++ two-core arrangement. No reviewed material supplies a tagged final firmware, end-user build/flash guide, challenge archive, stable UI specification, release hashes, update policy, test report, or final behavior guarantee.

Compatibility: MalO SAO (DEF CON 34)

Source
Seasides 2026 Roulette Badge source-backed maker documentation

maker-documented firmware behavior

Eight-stage CTF and UART progression

The README describes an eight-stage embedded CTF, 1,200-baud software UART, EEPROM-backed progression, encoding challenges, and animation unlocks. It does not prove current availability, rules, solution handling, participant scope, service operation, safety review, or firmware parity across all physical event units.

Compatibility: Seasides 2026 Roulette Badge

Source
The Shattered Shard (DEF CON 34) public player guide; operational details intentionally not reproduced

maker-documented local challenge interface

Badge-local Wi-Fi and browser quest surface

The guide says the badge exposes a local Wi-Fi/browser quest interface and includes an explicit assigned-badge-and-advertised-services boundary. The catalogue preserves that narrow interaction fact without publishing connection identifiers, credentials, local addresses, hidden resources, browser instructions, or exploitation details, and without treating a CTF surface as general conference infrastructure or a production security model.

Compatibility: The Shattered Shard challenge badge only; network configuration and authorization beyond the guide's assigned-badge context unverified

Source
The Shattered Shard (DEF CON 34) public player guide; hardware details incomplete

maker-documented physical interaction surface

Serial, LED-panel, and labelled-SAO challenge context

The Player Guide names a CP2102 programming connector, a serial-terminal chapter, an LED-panel observation, and one physical task using only labelled SAO GPIO1/GPIO2 contacts. It does not establish connector wiring, pinout, voltage/current limits, toolchain, serial-command set, safe procedure, firmware image, general compatibility, or permission to attach hardware outside the assigned-badge context.

Compatibility: The Shattered Shard challenge badge as described in its Player Guide; physical/unit parity and safe interaction outcome unverified

Source
INSPECTRON 34 SAO (DEF CON 34) post-conference source and V5 update published

maker-documented software surface

CRT-TV GIF player and puzzle firmware

The public README and handoff describe GIF channels, a device puzzle, settings, USB-drive loading, and the V4-to-V5 firmware history. This preserves the published software surface without making a safe flashing, recovery, support, security, or source-to-unit version claim.

Compatibility: INSPECTRON 34 only; final installed firmware and every-host behavior are unverified

Source
BSides Peoria 2025 HackTheBadge Challenge Badge event-period README; final device unverified

maker-published hardware outline

Maker-stated ESP32 and ILI9341 TFT parts surface

The pre-event README names an off-the-shelf ESP32, a 240×320 ILI9341 TFT panel, wiring, and two batteries. This establishes a maker-stated parts surface only; it does not prove a PCB, enclosure, wearable form, final board/module, battery chemistry/capacity/protection, power budget, or an event-unit configuration.

Compatibility: Technet8394's self-described BSides Peoria Badge Challenge 2025 project only; physical form and event-unit parity unverified

Source

manufacturing and firmware lifecycle

Prototype and summit release assets

The releases page preserves Prototype 3 BOM/CPL/Gerber/schematic assets plus summit_v1 and summit_v2 firmware and filesystem release files.

Compatibility: GreyCTF Summit 2025 GreyBadge

Source

media challenge

Printed liner and audio puzzle

Folded liner notes and the cassette audio carried track-list, color, character, tone, and number-station-style clues for remote badge solving.

Compatibility: DEF CON 28 Safe Mode Badge

Source
X-CTF 2016 Badge source-backed

microcontroller and Wi-Fi

ESP8266 badge core

The hardware writeup and repository document the badge around an ESP8266 module with USB serial programming and Wi-Fi features.

Compatibility: X-CTF 2016 Badge

Source
Tildagon ongoing

multiplayer game app

TILDENSTEIN 3D

webboggles' TILDENSTEIN 3D is a 2026 Tildagon App Directory release: a Wolfenstein-style raycasting FPS with ESP-NOW multiplayer set around the EMF Camp grounds.

Compatibility: Tildagon OS with ESP-NOW peer play

Source

network challenge interface

DUCK Wi-Fi AP and embedded web CTF

The badge created a DUCK-prefixed Wi-Fi access point, exposed an embedded web server at 192.168.4.1, and hosted CTF pages for flag capture.

Compatibility: BSides Kristiansand 2025 Sykt Badge

Source
NorthSec 2026 Badge official 2026 competition page backed

official CTF challenge surface

CTF-integrated badge challenges

The official competition page's retained 2026 Solarpunk section says the hackable electronic badge was fully integrated into the CTF and that solving badge challenges earned points; it separately names badge-firmware tampering among on-site physical tracks.

Compatibility: NorthSec 2026 CTF and electronic badge

Source
2026 eChallengeCoin (DEF CON 34) CircuitPython profile published; final 2026 mapping unresolved

official board-platform documentation

Coin M0 CircuitPython and Arduino development surface

AoSC links CircuitPython's Bradán Lane STUDIO Coin M0 build specifically for the eChallengeCoin. CircuitPython says Coin M0 has an ATSAMD21G1A with 4 MB flash and supports CircuitPython or Arduino plus USB serial, MIDI, HID, and disk uses; AoSC suggests a one-button macropad after the game. The sources do not prove final 2026 firmware, every-unit compatibility, user-safe reflashing, or a detailed implementation/license trail for the eChallengeCoin game.

Compatibility: 2026 eChallengeCoin (DEF CON 34)

Source
NorthSec 2026 Badge public source; no tagged binary release

official firmware source

Official conference/CTF firmware source

NorthSec's C++/Arduino PlatformIO tree includes shared NFC, e-paper, LED, and button modules alongside conference/CTF partition material. The public snapshot does not identify a tagged release, factory binary, or event-unit deployment revision.

Compatibility: NorthSec 2026 badge source tree; exact deployed firmware unconfirmed

Source
WomenCon 2026 Digital Morpher Badge official organizer ticket posts

official organizer-described intended use

Interactive Electronic Cats hardware-hacking statement

WomenCon calls the Digital Morpher an interactive electronic and collectible badge designed or developed by Electronic Cats, explicitly intended to be connected for hardware hacking. The sources do not identify the connection type, interfaces, hardware-hacking activities, safety rules, firmware behavior, challenge, access-control role, or supported workflow.

Compatibility: WomenCon 2026 Digital Morpher Badge

Source
BSides Maine 2026 Electronic Lighthouse Badge official pre-event announcement; completed-event agenda retained

official puzzle framing

Badge puzzle and collaborative-hacking prompt

Official BSides Maine posts frame the badge as a puzzle for exploration, collaboration, experimentation, and hacking; the agenda later asks whether anyone solved it.

Compatibility: BSides Maine 2026 badge context; no source identifies a puzzle mechanism, flags, software, scoring, reward, or solution.

Source
RTV D20 Badge (DEF CON 34) official event page published

official village event association

Red Team Village DEF CON 34 event context

Red Team Village's official page places the Village at DEF CON 34 on August 6-9 in the Las Vegas Convention Center Red Team Village area and announces workshops, activities, swag, and more. It does not state that RTV D20 is included with registration, used in a workshop/CTF, issued to all attendees, or grants access to any Village or conference space.

Compatibility: RTV D20 Badge (DEF CON 34)

Source

open protocol

OpenLASIR protocol interoperability

The official badge supported the public OpenLASIR infrared protocol, allowing compatible third-party devices to join the game while tracking official and third-party interactions separately.

Compatibility: DEF CON Singapore 2026 DC-SG-1 Official Badge

Source
44CON 2025 RF Detector Badge source published

operating mode

Shield-only OLED mini-game mode

The README says the badge can operate with the shield installed, where it drives the OLED display and runs the built-in mini-game without the ESP32 path.

Compatibility: 44CON 2025 RF Detector Badge

Source
THOTCON 0xC Badge source-backed

optical and mechanical design

TIR lens design

Rehrig documents total-internal-reflection lens work intended to focus emitter output and shape the optical behavior needed for the laser-tag game.

Compatibility: THOTCON 0xC Badge

Source
DOJOConf Panamá 2026 Electronic Badge intended role plus public source context

organizer- and source-described event context

Announced CTF role and high-level PwnPet framework

ComunidadDOJO says the 2026 DOJOConf badge will be useful in the CTF, while the archive identifies PwnPet as its firmware framework and describes virtual-pet and CTF context only at a high level. The catalogue does not reproduce setup, connection, configuration, challenge, scoring, or interaction procedures, and the sources do not establish a completed event outcome or a unit-matched firmware release.

Compatibility: DOJOConf Panamá 2026 Electronic Badge

Source
RVAsec 2025 Badge source-backed

package companion artifact

Challenge coin pairing

The registration page pairs the electronic badge with a custom RVAsec challenge coin in the guaranteed package.

Compatibility: RVAsec 2025 Badge

Source

parallel challenge artifact

Non-electronic crypto challenge path

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.

Compatibility: BSidesKC 2019 badge ecosystem

Source
DC503 5ohBEE Pager source-backed

persistent state

EEPROM-backed identity state

The sketches use EEPROM for stored names and HugQuest token/infection state, keeping the pager identity and game state across restarts.

Compatibility: DC503 5ohBEE Pager

Source
DEF CON 19 Badge source-backed

physical badge artifact

Waterjet-cut titanium credential

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.

Compatibility: DEF CON 19 Badge

Source
DEF CON 21 Badge historical

physical challenge

Continuity-probed PCB puzzle

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.

Compatibility: DEF CON 21 Badge

Source
DEF CON 24 Badge historical

physical challenge

Hidden trace and silkscreen puzzle

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.

Compatibility: DEF CON 24 Badge

Source

physical challenge

Lanyard cipher surface

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.

Compatibility: DEF CON 28 Safe Mode Badge

Source
DEF CON 33 Badge historical

physical challenge

Layered-lens optical challenge

Mar Williams described the DC33 badge as interacting with 3D images and layered art around the con through different lenses and lens combinations.

Compatibility: DEF CON 33 Badge

Source

physical game media

Booklet, postcard, sticker, and lanyard media set

The closing talk lists the wider RCA kit around the badge, including lanyard, business card, two sticker variants, postcard, and booklet.

Compatibility: Easterhegg 2024 RCA Badge

Source
BSides Nashville 2026 Challenge Coin official 2026 event information

physical identity companion artifact

Attendee badge-package challenge coin

The official event page says every attendee will receive the BSides Nashville 2026 challenge coin and repeats that each attendee badge includes it.

Compatibility: BSides Nashville 2026 attendee badge package; no material, physical dimensions, mounting method, or separate access function is documented.

Source

pinout documentation

Official pinout table

The pinout page lists button GPIOs, OLED I2C pins, I2S/audio labels, and userport GPIOs for badge hacking, with the exact table kept as documentation rather than a schematic or PCB archive.

Compatibility: CONFidence 2026 ConfiBadge

Source
Aerospace Village DC34 SR-71 CTF Badge public team self-submission

planned CTF acquisition route

Winnable Aerospace Village booth and Discord CTF claim

The roster says SR-71 is only winnable and that the ACR team will host a CTF at its Aerospace Village booth and on its Discord. It does not publish the CTF rules, eligibility, schedule, task set, venue authorization, winner count, badge quantity, pickup process, or completed award outcome.

Compatibility: SR-71 DEF CON 34 badge listing; no confirmed participant entitlement or delivery

Source
CyberThreat 2026 Planned Hackable Badge Challenge official 2026 programme statement

planned badge challenge

2026 interactive hackable badge challenge

CyberThreat's official site says delegates can attempt an interactive hackable badge challenge. That supports a planned badge-related activity but does not state the number or form of badges, who receives one, challenge rules, entry requirements, timing, scoring, prize terms, technical surface, safety boundary, or completion outcome.

Compatibility: CyberThreat 2026 Planned Hackable Badge Challenge

Source

planned badge interaction

Planned specialty stations

The public plan sketches badge stations for hardware hacking, puzzles, games, a photo booth, or similar event-specific interactions.

Compatibility: PhreakNIC 27 Planned MK.II ESL Badge

Source
Aerospace Village DC34 SR-71 CTF Badge public team self-submission

planned badge-game lifecycle

NFC TCG card-collection and raffle claim

The team says the badge contains a TCG-type game using NFC peer-to-peer and NFC reader modes, and that a full card collection enters an attendee into a raffle for Lockheed Martin and ACR swag. The listing does not identify whether NFC lives in the badge, cards, phone, or booth hardware; it also omits game rules, card count, persistence, scoring, raffle terms, odds, prizes, or security controls.

Compatibility: SR-71 planned game as publicly described; final implementation and operating rules unreleased

Source
BSides Lisbon 2026 Electronic Badge officially advertised

planned conference activity

Concurrent CTF programme

The current 2026 About page also lists a CTF. It does not say the CTF is a physical challenge, uses the electronic badge, or has a badge-specific implementation.

Compatibility: BSides Lisbon 2026 conference context only; not evidence of a badge-linked CTF or software feature.

Source
BSides Lisbon 2026 Electronic Badge officially advertised

planned event badge programme

Planned electronic-badge programme

The current official 2026 About page says BSides Lisbon will have an electronic badge alongside talks, networking, and a CTF.

Compatibility: BSides Lisbon 2026 programme context; no hardware, firmware, recipient, or final delivery specification is public.

Source
H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34) team-announced pre-event scenario

planned in-person interaction

Live transmission zones, Cure Stations, and medkit-prop game claim

The team describes crew members as roaming live transmission zones, fixed but unmapped Cure Stations, and hidden 3D-printed medkit props. This is a planned game surface, not proof of venue approval, final locations, staff participation, accessibility, safety review, implementation, participant effect, prize, or event outcome.

Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)

Source

post-build challenge

Hackster HIDIOT project competition

The brochure promoted a HIDIOT Hackster project-submission path with a prize for the best attendee project.

Compatibility: 44CON 2017 HIDIOT 1.0 Badge

Source
SHA2017 Badge historical

post-camp app hack

Gameboy emulator on e-ink

Sprite_tm documented adapting a Gameboy emulator to the SHA2017 badge's e-paper display, preserving a concrete example of post-camp app hacking under unusual display constraints.

Compatibility: SHA2017 badge

Source
BSides Peoria 2025 HackTheBadge Challenge Badge source visible; event deployment unverified

post-event Arduino source context

Source-level Wi-Fi and display challenge surface

The post-event Arduino-style source contains Wi-Fi, local web-server, SPI, preferences, and ILI9341 display code. The catalogue records this high-level source context without publishing connection details, credentials, URLs, endpoints, challenge answers, access steps, or a claim that the visible code was deployed at the event.

Compatibility: Public HackTheBadge source archive; network configuration, device state, challenge parity, and operating conditions unverified

Source
h-c0n 2026 CTF BADge post-event documented

post-event CTF archive

Winner write-up archive

The Hackplayers recap links the first three winner write-ups and summarizes their approaches: firmware extraction, RISC-V reversing, logical-flaw exploitation, static and dynamic analysis, validation weaknesses, and state manipulation.

Compatibility: h-c0n 2026 CTF BADge

Source
AvengerCon IX Electronic Badge officially documented

post-event CTF support

Post-event unlock-code publication

After AC9, the official badge page published four booth/village unlock codes for people who missed them during the event.

Compatibility: AvengerCon IX Electronic Badge

Source
BSides Nashville 2026 Challenge Coin official organizer feed re-share

post-event attendee report

Post-event attendee coin corroboration

The organizer's public feed re-shares an attendee thanking BSides Nashville and SkillBit for coins after the event. This corroborates attendee-side coin receipt but does not establish all-recipient delivery, a coin count, maker role, material, or variant inventory.

Compatibility: Post-event BSides Nashville 2026 attendee context; not a technical or manufacturing specification.

Source

post-event badge challenge

20 badge puzzles and stated source release

A March 24 post-event update by Dr Paul Black says the conference badge had 20 puzzles to solve and that full source code was released. The post directs readers through a short link whose final archive target was not independently recovered in this pass.

Compatibility: BSides Ballarat 2026 Underground Badge

Source

post-event challenge support

Post-event mixed-reality workaround guide

Badge.Team published a post-event guide for completing the mixed-reality challenge without the original hotel props, magnetic maze, and badge-to-badge team formation.

Compatibility: HackerHotel 2020 Badge

Source
NorthSec 2026 Badge official commit-pinned publication

post-event official source release

Official 2026 Apache-2.0 source release

NorthSec publicly released the separate nsec/badge-2026 source tree after the event, including hardware, firmware, animations, CTF content, dock material, and source artwork. Its historical commit timestamps are retained project chronology, not proof of public availability before the event.

Compatibility: NorthSec 2026 badge project; no physical-unit or deployed-firmware revision mapping published

Source
h-c0n 2026 CTF BADge repository-backed

post-event technical archive

Public winner write-ups and tooling notes

The repository preserves first, second, and third winner write-ups plus serial, picotool, BOOTSEL, and debugging guidance for people replaying the hardware CTF.

Compatibility: h-c0n 2026 CTF BADge

Source

post-event tooling

Post-event challenge hash unlocks

After the conference, a badge-number form could output correct hashes to unlock all challenges and add-ons such as Pong, WiFi scanner, and animations.

Compatibility: BSides Cape Town 2016 Badge

Source
RootedCON 2026 Pacman Badge direct project-builder account

power and debug architecture

LiPo/UVLO, USB serial, and screen-power design surface

The builder describes LiPo 1S, integrated charging, under-voltage lockout, automatic USB-serial RESET/EN control, exposed UART0, and an extra screen-ground MOSFET on some boards. The account does not establish cell capacity, charge settings, board-revision coverage, electrical testing, safe modification, or a production-service procedure.

Compatibility: RootedCON 2026 PACMAN/Ghost attendee CTF badge

Source

power interface

Interactive 12 V power-management surface

The official badge announcement lists interactive power management and a 12 V 1.5 A power supply, without documenting the underlying design, safety limits, or supported external equipment.

Compatibility: Car Hacking Village DEF CON 34 CAN-FD CTF Badge

Source
X-CTF 2016 Badge source-backed

power subsystem

LiPo charging and portable power

The hardware trail documents lithium-polymer battery power and MCP73831-based charging for portable badge use.

Compatibility: X-CTF 2016 Badge

Source
Puzzled Hackers LED Badge (DEF CON 34) official checkout currently marks online allocation sold out

pre-event availability and acquisition record

$20 limited online allocation and sold-out state

The official checkout lists $20 including tax and says all online stock allocations are exhausted. The Puzzled Hackers Team says paid sales were capped at a break-even point. Neither source publishes a unit count, payment ledger, production total, in-person stock, completed sale, delivery, refund, replacement, or post-event availability result.

Compatibility: Puzzled Hackers LED Badge (DEF CON 34)

Source
Station 562 Badge (DEF CON 34) first-hand maker comment; completion unconfirmed

pre-event availability and configuration statement

Maker-stated build, giveaway, sale, and blank-board snapshot

The maker says about 55 badges had been made with roughly ten boards left, a few may be given to the first roughly five signal-intel puzzle solvers, most or all RGB units are accounted for, a few non-RGB units may be sold at cost, and some RGB blank boards may be given away. These comments do not establish a production ledger, final build count, exact price, payment, eligibility, pickup site/time, receipt, donation, assembly, delivery, support, or post-event outcome.

Compatibility: Station 562 Badge (DEF CON 34)

Source
MF Doom SAO v2 (DEF CON 34) maker thread and roster published; outcome unconfirmed

pre-event availability and revision statement

MF Doom SAO v2 $20 maker preorder and handoff statement

The roster gives MF Doom SAO v2 a $20 Coming soon entry, while the maker's Reddit thread says preorders will be handled by direct message and describes local handoff near the Las Vegas Convention Center. The public statements do not prove final stock, price, manufacture, payment, venue authorization, exact meeting point, pickup, shipment, refund, replacement, support, recipient allocation, or completed delivery.

Compatibility: MF Doom SAO v2 (DEF CON 34)

Source

pre-event challenge surface

Collectible badge challenge

RomHack Camp 2026 is currently advertised with a unique hardware badge and collectible challenge; final challenge mechanics are not yet public in the source set.

Compatibility: RomHack Camp 2026 Badge

Source

printed puzzle surface

Sticker backing-paper entry point

The 2021 walkthrough says the badge challenge started from text printed on the back of the Kākācon sticker.

Compatibility: Kākācon 2021 Sticker Badge Challenge

Source

printed puzzle surface

Sticker backing-paper entry point

The 2022 walkthrough says the second Kākācon badge challenge again started from text printed on the back of the sticker.

Compatibility: Kākācon 2022 Sticker Badge Challenge

Source

production and delivery

Programmed, flashed, and delivered production trail

The post-event account describes programming, flashing, testing, cross-continent transport, and on-time delivery after tight deadlines and logistical challenges.

Compatibility: BSides Kristiansand 2026 Shield Badge

Source

production lifecycle

Badge-team lessons-learned talk

The public HackerHotel Badge talk captures the badge-team process, challenge integration, and lessons learned as part of the badge's post-event record.

Compatibility: HackerHotel 2025 Badge

Source

project lifecycle

Budget and prototyping phases

The project is publicly shown in staged progress from idea collection through prototyping, electronic design, firmware, and delivery, with budget fit called out as the next challenge.

Compatibility: HackerHotel 2027 Badge

Source
CyberThreat 2026 Planned Hackable Badge Challenge official 2026 registration listing

registration-package activity

In-person Hackable Badge Competition listing

SANS lists a Hackable Badge Competition among the in-person CyberThreat 2026 inclusions. The page does not say whether that listing grants a physical badge, which registrants may participate, whether there are badge variants, or how the competition operates.

Compatibility: CyberThreat 2026 Planned Hackable Badge Challenge

Source

related planned conference access

DragonJARCON conference entry and CTF context

The diploma package includes DragonJARCON 2026 entry. The official event home separately advertises a standard 2026 kit and official CTF for the September 10-11 conference, but does not state that the standard kit is electronic or identical to the diploma package's badge.

Compatibility: Related September 10-11 DragonJAR Security Conference context only; not a cross-ticket badge-equivalence claim.

Source

research badge interface

SaikoCTF hardware badge interfaces

The official SaikoCTF page says the hardware badge exposes physio, cyber challenge, and programmable hardware component interfaces for the HITB Bangkok challenge.

Compatibility: HITBSecConf2024 Bangkok SaikoCTF Badge

Source

research participant badge

Electronic SaikoCTF participation badge

The recruitment statement says participants received an electronic SaikoCTF badge as a participation token together with a brief soft-skills assessment summary.

Compatibility: HITBSecConf2024 Bangkok SaikoCTF Badge

Source

research protocol

VR and physiological-sensor CTF study workflow

The study workflow put participants in VR goggles and physiological sensors for a roughly one-hour simulated-network CTF using a Kali Linux VM, questionnaires, and researcher check-ins.

Compatibility: HITBSecConf2024 Bangkok SaikoCTF Badge

Source
DEF CON 17 Badge historical

role-set puzzle

Seven-badge puzzle and Uber hack

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.

Compatibility: DEF CON 17 Badge set

Source
DEF CON 25 Badge documented

scope marker

No official badge challenge

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.

Compatibility: DEF CON 25 Badge

Source
HITCON CMT 2019 Badge source-backed

security challenge

ARM TrustZone badge challenge

The badge challenge used ARM TrustZone separation with non-secure and secure stages, command-line interaction, snake warm-up behavior, and unlock states.

Compatibility: HITCON CMT 2019 Badge

Source
Masonic33 Indie Puzzle Badge (DEF CON 33) price and mission statement published

seller availability and funding context

$125 seller state and Hak4Kidz mission wording

The product and Hacker Couture list show $125, while the Hak4Kidz Lab profile says all proceeds support its mission and ethos. These statements do not establish inventory, payment, quantity, fulfillment, the amount or destination of any particular proceeds, tax treatment, charitable accounting, or completed donation outcome.

Compatibility: Masonic33 Indie Puzzle Badge (DEF CON 33)

Source
Spectre Sniffer Badge (DEF CON 34) maker-published claim

seller-described interaction

Spirit Box, EMF-rate behavior, and arcade games

NilbinSec describes a Spirit Box with a randomized word bank whose output rate is driven by its stated EMF signal, plus one- and two-player arcade games. The source supplies neither the implementation nor game, signal, audio, or firmware documentation.

Compatibility: Spectre Sniffer Badge (DEF CON 34)

Source

social badge interaction

Badge docking and game battle

The 2024 badge guide describes docking badges with other attendees and game battle behavior, making the physical badge a social interaction device.

Compatibility: HITCON CMT 2024 PCB Badge

Source
HITCON 2025 PCB Badge source-backed

social badge interaction

Cross-board game battle

The 2025 guide documents cross-board interaction and game-battle behavior, pairing badge-to-badge play with Tetris, Dino, and Snake activities.

Compatibility: HITCON 2025 PCB Badge

Source
DEF CON 19 Badge documented

social interaction mechanic

Badge-as-participation design

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.

Compatibility: DEF CON 19 Badge

Source
TiDAL historical

software add-on ecosystem

TiDAL apps and custom ports

Developer docs and community writeups show TiDAL apps and experiments such as a custom Doom port while preserving MicroPython functionality.

Compatibility: TiDAL / EMF 2022

Source
H2HC 2023 Game Boy Badge source-backed

software artifact

GB Studio conference game

The badge artifact was implemented as a custom GB Studio game that guides players through a virtual Sao Paulo, hotel, conference, and Brazil-themed environment.

Compatibility: H2HC 2023 Game Boy Badge

Source
CONFidence 2026 ConfiBadge source-backed but incomplete

software challenge surface

Firmware and hidden challenges

The badge home page invites attendees to explore firmware, write code, use onboard peripherals, and discover hidden features and challenges.

Compatibility: CONFidence 2026 ConfiBadge

Source
NodeConf EU 2017 Badge source-backed

software examples

On-badge games and code examples

The repository includes apps and examples such as menu, REPL, Asteroids, Flappy Bird, Snake, Mario, T-Rex, sketch, and image-display code.

Compatibility: NodeConf EU 2017 Badge

Source

software examples

User app examples

The repository preserves user-app directories for games, screensavers, spectrum analysis, text adventure, air-quality, hardware-monitor, app-manager, and other MicroPython examples.

Compatibility: Hackaday Supercon 2025 Communicator Badge

Source
TiLDA historical

software/hardware add-on ecosystem

Wireless games and contributed code

The original TiLDA wiki grouped wireless experiments, game mechanics, contributed code, hardware plans, and bug fixes as a shared camp hacking surface.

Compatibility: TiLDA 2012

Source

software/hardware expansion

Demoscene and accelerometer hacks

The badge records preserve Tetris, moving messages, accelerometer readouts, and a planned demoscene contest as first-class badge activity.

Compatibility: Hackaday Belgrade 2016 Badge

Source

soldering challenge

Eight-LED SMD Challenge

The builder log says the ToorCon badge incorporated an SMD Challenge with eight LEDs, including one smaller 0201 LED.

Compatibility: ToorCon 20 Official Badge

Source

soldering challenge

MakersBox SMD challenge circuit

The badge incorporated an SMD soldering challenge circuit credited to MakersBox, turning part of the board into a small assembly exercise.

Compatibility: Hackaday Remoticon 2020 Unofficial Badge

Source
NorthSec 2025 Badge first-hand writeup

soldering challenge

Soldering village eight-LED challenge add-on

The 2025 soldering-village writeup documents an add-on challenge with eight LEDs, polarity/defect debugging, VCC and pin behavior, SAO table context, scrambled code recovery, and final flag submission.

Compatibility: NorthSec 2025 Badge and soldering village

Source
BSides Peoria 2025 HackTheBadge Challenge Badge repository existed before the event; code published after it

source chronology

Post-event public source-release trail

The repository's visible history has an event-period README before the October 25 conference, while the main Arduino source appears in a November 21 post-event commit. The chronology preserves public evidence without equating the later checkout with a dated event binary or documented final artifact.

Compatibility: HackTheBadge public repository only; no tagged event release or source-to-device mapping

Source

source release

Apache-2.0 post-CTF source archive

The public repository preserves firmware, Gerbers, SPI tooling, troubleshooting notes, a flash-image archive, and Apache-2.0 license metadata after the CTF window.

Compatibility: AND!XOR DC28 Badge

Source
PWNEDCR 0x08 Electronic Badge named post-event account

source-described badge interaction

Hackable CTF and hidden-challenge surface

The report says the electronic badge was hackable, had already been hacked by at least three people during the CTF, and contained hidden Easter eggs and challenges integral to that competition. It does not describe the challenge design, interfaces, exploitation path, firmware, scoring, data handling, or any completed participant outcome.

Compatibility: PWNEDCR 0x08 Electronic Badge

Source
Puzzled Hackers LED Badge (DEF CON 34) official checkout terminology only

source-named electronic artifact

Narrow LED badge classification

The official checkout calls the physical item a limited-edition LED badge. It does not identify a PCB, programmable controller, LED count/color, power system, firmware, radio, connector, or any other engineering surface, so the record preserves the narrow source classification rather than reconstructing electronics.

Compatibility: Puzzled Hackers LED Badge (DEF CON 34)

Source
CPEC DC34 MechBattle Badge in-progress; explicitly not final

source-published interaction surface

Draft MechBattle menu and game code

The CPEC repositories publish menu, pilot-record, game-state, display, sound, and game modules, and the earlier repository calls its code a non-final second iteration. Those sources establish an in-progress planned interaction surface, not final gameplay, player outcomes, a completed CTF, physical controls, accessibility behavior, or a deployed event experience.

Compatibility: CPEC DC34 MechBattle Badge

Source
CPEC DC34 MechBattle Badge in-progress configuration; physical parity unconfirmed

source-targeted development platform

ESP32-S3 PlatformIO source target

The game repository's PlatformIO configuration targets an Adafruit Feather ESP32-S3 no-PSRAM board with Arduino and a LittleFS configuration. This records an intended development target only; it does not identify a final badge PCB, assembly, controller population, storage, boot flow, power design, or a manufactured event unit.

Compatibility: CPEC DC34 MechBattle Badge

Source

technical preservation source

MIT Arduino, KiCad, Gerber, CAD, and fabrication archive

The DC32 repository publishes Arduino sketches, setup/compile/upload scripts, KiCad project files, Gerbers, CAD/fabrication material, a parts list, and assembly instructions under an MIT repository license. Its documentation also notes a then-precompiled CTF library, and no reviewed source establishes that every current fundraiser unit ships a specific repository commit or complete CTF source.

Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)

Source
Disobey 2026 Badge work in progress

third-party badge game

CyberSlayer MicroPython game

Piia Alavesa's public CyberSlayer app targets the Disobey 2025/2026 board with a ten-zone cybersecurity combat game, NeoPixel progress and combat feedback, and documented installation via mpremote or the official development-firmware loader.

Compatibility: Disobey 2025/2026 Badge (third-party app)

Source
Disobey 2026 Badge source-backed

third-party firmware examples

Rust games and demos

The Rust repository documents badge examples including Breakout, Skyroads, Snake, Space Shooter, demoscene, shader, vector demo, display tests, LED bars, microphone, name-tag, scrolling, vibration, and async task-switch examples.

Compatibility: Disobey 2026 Badge

Source
BSides Cheltenham 2026 Challenge Coin pre-event Early Bird package; sold out

ticket-tier conference token

Early Bird limited-edition challenge coin

The organizer says the limited Early Bird release included an exclusive Limited Edition BSides Cheltenham 2026 Challenge Coin alongside conference and afterparty access, a t-shirt, and a swag bag. The source does not establish a completed unit, final specification, coin count, recipient list, or delivery outcome.

Compatibility: BSides Cheltenham 2026 Challenge Coin

Source

training artifact

Supplied electrical badge kit

The official training page says all components and tools required to create a standard conference badge were supplied during the one-day workshop.

Compatibility: Kiwicon 2038 Intro to Badge Hacking Training Badge

Source

unofficial variant and contest

Pirate badge and counterfeit contest

Badge Pirates documents an unofficial Pirate badge variant plus a counterfeit-badge challenge triggered after badge imagery leaked before the event.

Compatibility: BSidesKC 2019 badge variants

Source

vehicle-network interface

DB9 CAN 2.0 / CAN FD interface

Car Hacking Village's official badge announcement lists DB9 CAN 2.0/CAN FD support for the DEF CON 34 badge.

Compatibility: Car Hacking Village DEF CON 34 CAN-FD CTF Badge

Source

village activity

Public Safety Village challenge and swag context

The HTX Public Safety Village page ties the village to AI and IoT public-safety challenges and says top HTX CTF finalists unlocked limited-edition DEF CON Singapore Public Safety Village swag.

Compatibility: DEF CON Singapore 2026 Public Safety Village Badge

Source

village badge

Hardware Challenge Village badge

The official 2025 schedule says the village hosted a competitive CTF using a badge designed specifically for the Hardware Challenge Village.

Compatibility: BSidesSF 2025 Hardware Challenge Village Badge

Source

village badge

Specially designed HCV badge

The official 2024 schedule says the Hardware Challenge Village used a specially designed village badge for HCV.

Compatibility: BSidesSF 2024 Hardware Challenge Village Badge

Source

village programme

Hardware Hacking Village track

The hardware village combined soldering, hardware talks, a hardware CTF, networking, and badge activity across the Seasides 2026 conference.

Compatibility: Seasides 2026 Roulette Badge

Source

visual challenge

Binary and Morse LED challenges

The teardown documents four upper and four lower LEDs used for binary output, followed by a Morse-code light sequence.

Compatibility: Wild West Hackin' Fest Deadwood 2025 E-Badge

Source

visual hardware

Flux-capacitor LED groups

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.

Compatibility: SEC Youth Challenge 2023 Flux Decoder Badge

Source
WOPR Summit 0x00 Badge source-backed

visual interface

Dozen colored LEDs and eight RGB LEDs

Hackaday describes the WarGames-inspired display surface as a dozen colored LEDs plus eight RGB LEDs.

Compatibility: WOPR Summit 0x00 Badge

Source

web puzzle path

Bird-image cipher trail

The 2022 challenge used URL reconstruction, repeated bird-image clues, and substitution solving after the sticker entry point.

Compatibility: Kākācon 2022 Sticker Badge Challenge

Source

web puzzle path

Bird-media puzzle trail

The 2021 challenge used web pages, source comments, dawn-chorus audio, image EXIF data, and substitution solving after the sticker entry point.

Compatibility: Kākācon 2021 Sticker Badge Challenge

Source
DEF CON Singapore 2026 TISC ESP32 Trinket first-hand finalist-backed

wireless challenge

BLE mesh chat protocol

The trinket ran a customized mesh chat protocol over BLE, with the challenge requiring reverse engineering to gain access to an administrative system broadcasting over the protocol.

Compatibility: DEF CON Singapore 2026 TISC ESP32 Trinket

Source
DC503 5ohBEE Pager source-backed

wireless game mechanic

WANNAHUG infection mechanic

HugQuest includes WANNAHUG transmission, infected-state persistence, a displayed ransom-style HUG-token prompt, and an unlock command requiring HUG tokens.

Compatibility: DC503 5ohBEE Pager

Source
DEFCON China 1.0 Badge source-backed

workshop

Badge hacking workshop path

The official workshop slides documented guided hacking paths for attendees working with the flexible-PCB badge and related hardware.

Compatibility: DEFCON China 1.0 Badge

Source
LCA2018 LoliBot source-backed

workshop challenge surface

Robot soccer and sensor exercise surface

The tutorial documents neopixels, motor H-bridges, reflection sensor input, exposed headers, and a kicker servo, with exercises for lights, wheels, servo motion, sensor detection, and touch inputs.

Compatibility: LCA2018 LoliBot

Source

workshop village

Hardware-village LED soldering

Attendees personalized the badge at the conference by soldering their own 1206 SMD challenge LEDs with hardware-village support.

Compatibility: BSides Adelaide 2024 Wombat Badge

Source

workshop village

Hardware-village SMD soldering activity

The SINCON hardware village used the badge for a soldering activity with tiny SMD LEDs mounted upside down, pairing hardware work with the software CTF.

Compatibility: SINCON 2023 Khong Guan Building CTF Badge

Source

Impact

Challenge-related caveats

camp impact · public feedback · historical

Feedback says there was little badge hacking during camp compared with SHA2017 and MCH2022, partly due to late arrival, limited distribution, missing app-store workflow, LoRa limitations, and sparse documentation.

The badge's technical potential was hard to realize while the camp was happening.

WHY2025 Feedback page.

ctf impact · first-hand participant report, partially corroborated · reported

A CTF participant reported receiving their badge only on the final day of camp, making it difficult to work on an embedded-device challenge during the event.

Badge-dependent embedded work became timing-constrained for at least one participant; this aligns with public feedback about late handout.

First-hand report from badge.gallery project owner; corroborated by public late-distribution feedback.

CTF/RCA communication · public event feedback · historical

Public feedback says some attendees did not understand that RCA was the CTF, that badge-related rewards existed, or how to start early enough.

The badge-linked challenge was praised by some participants but also created discoverability and inclusion friction for others.

Easterhegg 2024 feedback page.

TiDAL moderate

firmware/storage caveat · live Hatchery app metadata · documented caveat

The Doom! Hatchery entry warns that running the app overwrites the unused OTA partition and that Hatchery could not host the compressed DOOM1.WAD because it was too large.

Some TiDAL apps changed device storage/update assumptions and required manual asset handling, so app-store links need per-app risk notes.

EMF 2022 Hatchery Doom! metadata.

2024 lineage non-transfer boundary · separate year-specific source records · 2024 archive retained separately; 2026 design unannounced

CyberThreat's site still hosts rich 2024 Secure Impact badge and walkthrough material, including hardware and firmware challenge evidence, while its 2026 pages give only high-level hackable-badge activity wording. No reviewed source says that Secure Impact, the ATmega1284P/FTDI design, the nine challenges, or any 2024 mechanics will return in 2026.

The catalogue preserves the 2024 technical dossier without silently carrying its components, creator, challenge count, software, or delivery model into the planned 2026 record.

CyberThreat 2024 archive on the current official site and CyberThreat/SANS 2026 event pages.

2024/2025 PCB Badge Quest separation · official 2026 programme wording · older PCB-board activity explicitly separated

The official 2026 Badge Quest wording applies to 2024 or 2025 PCB badges that must be flashed with event firmware. It does not state that the 2026 NTAG215 attendee badge is a PCB, programmable, flashable, powered, display-equipped, or compatible with that firmware.

No historic HITCON PCB hardware, controller, firmware, game, connector, display, or BadUSB claim is carried forward into the narrower 2026 NFC attendee-badge record.

HITCON 2026 events page, Badge Quest and NFC Battle descriptions.

BLE, proximity, MIDI, puzzle, CTF, and privacy gap · maker-described feature list · interaction claims without public behavior or data documentation

The feature list names BLE proximity, a number-station puzzle, red-versus-blue play, a social/dance mode, MIDI, tamper evidence, and an optional hardware CTF, but does not publish radio settings, range, identifiers, pairing/consent behavior, data collection/retention, player safety, puzzle rules, score handling, CTF target/rules, accessibility, abuse controls, or privacy/security testing.

The record does not claim wireless interoperability, participant tracking behavior, a safe game design, data practices, live puzzle availability, or an authorized security-testing target.

Station 562 maker announcement.

BOTNET game caveat · primary project source · documented

The project page describes unauthenticated remote command execution within the badge's Bluetooth mesh as an event game mechanic and explicitly ties it to the badge ecosystem.

The catalogue records the game behavior without implying broader real-world botnet capability beyond the AND!XOR badge network described by the project owners.

AND!XOR DC27 project page.

CTF and sponsor boundary · official source wording · documented

The official CTF page says there were no physical challenges in 2025, and the sponsors page proves the BitSight Badge Sponsor slot but not the badge design, sponsor-logo placement details, or production vendor.

The record avoids turning the electronic badge into a proven badge-CTF platform or adding unsupported physical-design claims.

BSidesLisbon 2025 CTF and sponsors pages.

CTF boundary · official source separation · documented

The official page also announces public CTF challenge source, but does not connect those CTF files to badge hardware or badge firmware.

The catalogue avoids merging the online CTF archive into the badge record without source-backed badge integration evidence.

CarolinaCon Online 2021 official page.

CTF firmware release caveat · official badge page · source still pending

The official badge page still says the CTF challenge firmware source code will be released after the event, but the public sources checked in this pass did not expose that release.

The catalogue keeps the CTF flashing-station workflow as source-backed event behavior while avoiding a false claim that the CTF firmware source has already been published.

Disobey 2026 badge page and public repository refresh.

CTF role, challenge, and software scope gap · organizer-controlled intended-use statement and public README · high-level framework context; mechanics not represented

The organizer says the badge will be useful in the CTF, and the public README names PwnPet with virtual-pet and CTF context at a high level. The recovered sources do not establish an event-specific challenge archive, target authorization, final firmware image, unit configuration, participant data practice, results, or a verified attendee experience. The catalogue deliberately does not reproduce setup, connection, configuration, or challenge procedures.

The record does not present source-described context as a shipped challenge, a defined security-testing target, a privacy practice, or a verified participant outcome.

ComunidadDOJO 2026 CTF update, Electronic Cats public post, and badge-dojocon-2026 README.

CTF, distribution, and credential scope gap · named post-event account · event interaction documented; issuance terms unknown

The report links the badge to CTF hacking and describes hidden challenges, but does not document participant eligibility, badge count, price, registration tier, badge distribution, pickup, delivery, access-control role, challenge rules, scoring, data handling, completion, support, or whether every attendee received one.

The badge is not presented as an admission credential, universal attendee entitlement, complete CTF platform, or verified distribution record.

Best of PWNEDCR 0x08 by Simón Correa.

CTF, free-redemption, giveaway, and account-data boundary · first-hand Team announcement · acquisition statements only

The Team identifies a top-50 CTF redemption route and a possible random giveaway after the paid cap, but does not publish final puzzles, rules, score verification, account/QR-data retention, eligibility disputes, identity checks, selection method, inventory split, recipient outcomes, or a claim that CTF software is installed on the LED badge.

The catalogue retains the public community-acquisition context without supplying private account details, challenge content, player data, unsupported redemption mechanics, or badge-software claims.

Puzzled Hackers Team Meetup Post #4.

CTF, game, GIF, and secret-content rules gap · maker feature description · high-level interaction claims only

The maker describes a frog-themed CTF, unlockable GIFs/bling/secrets, and a frogger-like built-in game but does not publish challenge rules, intended player scope, solution or reset path, scoring, service availability, networking, telemetry, content provenance, data handling, archival plan, accessibility, or security testing.

The catalogue treats these as source-described interactive features rather than asserting a verified challenge system, live service, privacy posture, or preserved gameplay archive.

BigTaro FrogStar 2025 project and seller listings.

CTF, game, and authorship boundary · official schedule and named first-hand announcements · activity relationship source-backed; artifact roles unresolved

The official registration pairs a badge and CTF access, the founder says the badge could be used in Pieces of Eight / Pirate Scavenger Hunt play, the official schedule credits DEAD MEAT SOCIETY and SHIPSTONE for a CTF and Badge Intro, and Matt Aragon announces two NFC games. The reviewed sources do not publish the exact badge-to-game mapping, operation, scoring, rewards, results, participant privacy/data flow, or a reliable badge designer/manufacturer attribution.

Schedule and announcement context remains discoverable without attributing badge design to the game host or scheduled organizations, or inventing a finished challenge system.

NaClCON registration and schedule, Luke McOmie announcement, and Matt Aragon announcement.

CTF/backend archive boundary · public firmware and write-up sources · partial archive

The public firmware and write-up repositories document major badge CTF surfaces, but this pass does not prove that every private backend, provisioning script, factory image, key, leaderboard implementation, or organizer service has been published.

Software claims stay limited to the recovered TechMaker post, public firmware tree, public CTF writeups, and talk material.

NoNameBadge public firmware project and Coders in UA CTF write-up repository.

CTF/backend archive boundary · public article, firmware tree, and write-up sources · partial archive

The public firmware archive omits the private CTF portion by TechMaker's own framing, and the CTF write-up repository reconstructs public challenge paths rather than proving that every backend, provisioning, leaderboard, key, or organizer service was released.

Software claims stay limited to the recovered TechMaker article, public firmware tree, schematic, and CTF write-up repository.

NoNameBadge 2020 public firmware project and Coders in UA CTF write-up repository.

EEPROM corruption recovery · primary docs · documented recovery path

The troubleshooting section documented an unresponsive three-red-light state as EEPROM corruption and directed attendees to Badge.Team members for quick reprogramming.

The record captures both a failure mode and the on-site support workflow that kept the challenge playable.

HackerHotel 2020 troubleshooting docs.

IR, NFC/RFID, microphone, privacy, and interaction-safety boundary · maker-described communication and sensing claims · no final policy or protocol release identified

The sources describe IR message exchange, NFC/RFID, a microphone, motion/light/environmental sensors, games, and social interactions, but do not publish a final communications protocol, authentication/security model, user consent flow, microphone activation/data behavior, local storage/retention policy, pairing/discovery rules, radio/IR performance limits, accessibility policy, moderation plan, or incident guidance.

The record does not turn a feature list into a privacy guarantee, secure messaging claim, surveillance assurance, or universally suitable interaction model.

MalO SAO product page, MalO_SAO repository, and MalO SAO developer diary.

Masonic theme, terminology, and affiliation boundary · maker theme wording only · Freemasonry-inspired presentation; affiliation unsubstantiated

The maker describes square-and-compass imagery, 33rd-degree mystique, and secret-society/Freemasonry-inspired modern puzzle elements. No reviewed source establishes sponsorship, endorsement, membership, authority, or affiliation with any Masonic or fraternal organization, nor provides a license for theme/artwork elements.

The catalogue documents the source's creative framing without inferring religious, fraternal, organizational, legal, or licensing relationships beyond that stated theme.

Masonic33 Tindie listing and Hacker Couture DEFCON 33 Product List.

Micro-USB, USB-C, touch-count, and Coin M0 mapping conflict · conflicting linked primary sources · unresolved source discrepancy

AoSC's eChallengeCoin page says Micro-USB and one large touch pad, while the CircuitPython Coin M0 profile that AoSC links as the eChallengeCoin-specific build says native USB-C and three capacitive touch pads. Both sources mention three NeoPixel groups and a speaker. This pass did not recover a revision note, schematic, product BOM, photo with cleared technical annotation, or maker clarification resolving whether the pages describe the same final 2026 unit, a transitional revision, or differing interface vocabulary.

Readers should not select cables, infer a connector, design touch software, rely on a touch count, or assume final board parity from either page alone.

AoSC 2026 eChallengeCoin page and CircuitPython Bradán Lane STUDIO Coin M0 profile.

Morse-game participation and outcome boundary · maker repository description · venue-sign game documented; participant outcome unrecovered

The maker archive says player-code signs were placed around the venue and preserves guide/sign material for the Morse-code game. It does not publish a player count, score or completion data, participant identities, prize policy, final game-state report, official event result, or ongoing service status.

The catalogue records the documented badge interaction without claiming a completed CTF, universal player participation, or any individual outcome.

bsides-newcastle-2025-badge README and signs directory.

OLED variant and distribution gap · repository but incomplete · needs final-population confirmation

The repository carries two SSD1306 OLED footprint variants (128x32 and 128x64) and does not confirm which is populated on the final badge, nor whether the badge was distributed to all attendees or a limited quantity.

The catalogue records the full hardware and challenge surface without asserting the exact populated OLED variant or the physical distribution scope.

ElectronicCats/badge-recon-2026 repository footprints and release notes.

UPDI programming and modification boundary · maker interface label only · UPDI-compatible interface named; use conditions undocumented

The product labels a UPDI-compatible one-wire programming interface, but does not disclose the connector/pad pinout, voltage, wiring, programmer compatibility, fuse/lock-bit state, erase behavior, backup, recovery, user-data effects, board warranty, or safe modification procedure.

The catalogue records an explicit programming surface without presenting it as a risk-free, universally compatible, authorized, or supported reflashing path.

Masonic33 Tindie listing.

Uber Badge caveat · official registry · documented; no 2026 awardee claimed

The current Uber Badge page documents the lifetime-admission award model and public registry, but the public registry does not list a 2026 badge-challenge winner as of the current recheck.

The catalogue treats Uber Badges as an award lineage attached to the challenge and avoids naming unverified 2026 winners.

BSides Tampa Uber Badge registry page, rechecked 2026-05-21.

activity material, participant, and outcome boundary · maker repository description · on-day printed-material statement documented; content and outcome unrecovered

The maker archive says a companion activity flyer was given out on the day, but it does not establish an organizer-approved activity, flyer contents, activity values, participant count, participation record, completion data, participant identities, prize policy, final result, current service status, or a safe/reproducible operating procedure. No codes, activity content, connection, or configuration directions are reproduced here.

The catalogue records the historical printed-material statement without exposing activity instructions or inferring universal participation, a completed challenge, individual outcomes, or current availability.

bsides-cheltenham-2024-badge README and public archive.

allocation and CTF-access boundary · official CTF announcement · needs post-event fulfillment report

The official pre-event CTF announcement says a badge could be purchased from the Village and five CHV badges would be available specifically for CTF participants, while also saying purchase was not necessary to compete. It does not publish a final sales quantity, recipient population, allocation process, physical variant list, CTF result, or final rules.

The catalogue does not infer universal distribution, a guaranteed participant badge, a completed CTF, or a final allocation count from the announced CTF access route.

Car Hacking Village DEF CON 34 CTF announcement.

analog scope · source-backed · documented

DEF CON 23's official badge is documented as a fully analog playable record rather than an electronic board.

The compendium avoids MCU, firmware, LED, battery, and circuit claims and records the audio, physical, lanyard, and printed clue surfaces instead.

Hackaday, The Register, and DEF CON 23 challenge writeups.

archive split · current source trail · documented

Badge facts are split across the NearForm repository, hardware directory, NodeBadge app page, Espruino event note, and Hackaday report.

The dossier separates hardware, software, event, and challenge claims by source instead of treating one page as a complete archive.

NearForm GitHub repository, nodebadge.org, Espruino, and Hackaday.

archive-depth caveat · source-backed but incomplete · needs deeper artifact inventory

The public repository preserves firmware, Gerbers, SPI tools, troubleshooting, and a flash image, while this pass does not audit every firmware commit, CTF flag, Slack hint, scoreboard state, patch, land-mine flag, or physical drop artifact.

The record captures the verified hardware/software surfaces without claiming complete CTF reconstruction or complete production logistics.

AND!XOR DC28 RTFM, CTF walkthrough logs, and GitHub repository.

artifact classification · official wiki sources · modeled conservatively

The public sources prove a Shadybucks wristband, Shady Tag identity workflow, and badge CTF entry path, but not a recovered universal electronic PCB badge archive.

The record is classified as an identity/payment and CTF artifact instead of inventing electronics, components, firmware, or distribution details beyond the official wiki.

Shadybucks and Euphoria CTF wiki pages.

artifact classification · primary official media attachments · documented narrowly

The recovered sources prove official 2021 badge-art variants, but not a physical badge, lanyard credential, electronic badge, PCB, firmware, badge challenge, or production/distribution quantity.

The entry is modeled as official role and competition badge artwork instead of being upgraded into an unsupported hardware badge.

Ekoparty attachment titles for attendee, speaker, workshop, ACFT, ICFT player, and Lado B variants.

artifact classification · primary writeup · documented

The source proves a custom Game Boy game artifact for H2HC, but not a conference PCB badge, firmware repository, or electronic badge board.

The entry is classified as a playable event artifact rather than upgraded into unsupported electronic-badge claims.

Security-Bits H2HC 2023 Game Boy writeup.

artifact detail boundary · official sponsorship source but narrow · classified as badge-sponsor inventory

The recovered public source trail proves a Badge Sponsor slot for the 2025 event, but does not prove an electronic badge, final printed credential design, lanyard artwork, sponsor imprint, attendee distribution count, schematic, PCB, firmware, challenge behavior, or production files.

The dossier preserves the real public badge-sponsor evidence while avoiding unsupported hardware or final-artifact claims.

BSides Cape Town 2025 sponsor page and Quicket event page.

artifact specification gap · organizer ticketing source · needs artifact-level documentation

Public sources establish that General Admission included a badge, but do not identify its material, artwork, dimensions, lanyard, QR/RFID/NFC behavior, electronic status, components, or production/distribution detail.

The record is modeled as a participant admission/identity artifact and does not infer a paper badge, electronic badge, or technical design.

Roanoke InfoSec Exchange Inc / Zeffy General Admission w/Badge listing and BSides Roanoke official site.

artifact-depth caveat · source-limited · needs official badge archive recovery

The recovered notes prove a paid badge option, but they do not say whether the badge was printed, electronic, PCB-based, lanyard-only, challenge-enabled, or produced in a specific quantity.

The catalogue keeps the 2018 record as a paid-badge entitlement and avoids unsupported physical or electronic details.

Arizona LoCo Team September 2018 notes.

artifact-depth caveat · source-backed but incomplete · needs deeper archive recovery

This pass relies on contemporary Hackaday technical coverage and DEF CON host-event context but does not recover an official Queercon 16 badge repository, firmware archive, full ARG ruleset, or production photo set.

The catalogue records verified hardware and social-game behavior while leaving firmware, challenge, and complete variant archaeology for a later pass.

Hackaday Queercon 16 article and DEF CON 27 host archive.

attendee reverse-engineering shortcut · attendee writeup · documented

Cryptax documents extracting and decrypting the flag database through the MicroPython filesystem rather than solving every challenge through the intended path.

The record keeps this as a CTF-solving and archive detail rather than treating it as a badge defect or official intended workflow.

Cryptax BSides Kristiansand Badge CTF 2025 write-up.

audio-artifact caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document the cassette, liner, lanyard, and media-server availability, but this pass does not mirror or audit every audio file, transcript, tape variant, or final puzzle solution branch.

The catalogue records the verified analog badge surfaces and leaves complete audio forensics for a later artifact-level pass.

DEF CON forum challenge post, Hackaday hands-on article, and CIRCUITS TO KERNEL writeup.

badge and CTF relationship boundary · official current About page · both programme items announced; linkage unproven

The About page lists an electronic badge and a CTF in the same programme sentence, but does not say the CTF is physical, badge-based, or implemented by the badge. No challenge mechanics, source, scores, data flow, prizes, or results are public.

The catalogue records both official programme elements without incorrectly presenting the badge as a CTF device or asserting a physical challenge path.

BSidesLisbon 2026 About page.

badge firmware and design archive gap · official maker page and public protocol repository · needs final badge archive

OpenLASIR is a public MIT-licensed compatibility protocol with examples, but reviewed sources do not publish complete final DS firmware, a badge-specific flashing workflow, schematic, PCB files, Gerbers, BOM, electrical design details, or a complete badge firmware license.

The catalogue can distinguish documented interoperability and game intentions from unverified full-badge implementation or reproducible-build claims.

OpenLASIR repository and Dani Weidman official maker page.

badge technology, access-control, and data boundary · official FAQ review · no technical or badge-linked data behavior published

The official FAQ says a valid QR code is scanned on entry and separately says a handle or name may be written on a badge. It does not connect those statements or publish a badge barcode/QR, RFID/NFC, chip, firmware, app, protocol, identity system, data collection, privacy notice, retention, account linkage, CTF behavior, repository, or security review.

The entry does not turn the event's admission procedure into a technical feature, access-control claim, or data-handling claim about the attendee name badge.

Hack Glasgow official 2026 FAQ and event page.

boot timing caveat · public badge guide · historical

The guide says the badge sends its interesting serial output during boot and users may see nothing if they connect too late; it estimates about 90 seconds before the OS and CTF app finish booting.

This captures a practical beginner trap: the badge worked, but the serial workflow depended on reconnect timing and terminal setup.

Jump ESP, jump! badge guide and migrated mirror.

budget scope · current project page · documented caveat

Badge.Team explicitly calls out fitting the LoRa, keyboard, big-screen, ESP32-P4 ambition into budget as the next challenge.

The final badge may differ from the early public ambition, so hardware claims should be revisited when production docs are published.

Badge.Team homepage HackerHotel 2027 section.

builder-completion caveat · primary project and Hackaday article · documented

Public sources describe the badge as a PCB canvas with space for builders to add their own electronics, including a MicroMod variant, rather than a complete stock electronics-and-firmware package.

The record avoids inventing a fixed MCU, app set, puzzle, or firmware behavior for the base Remoticon.2 template.

Hackaday article, Hackaday.io project description, file list, and project logs.

challenge integration gap · self-identified challenge source · needs challenge walkthrough

ShenLabs explicitly identifies itself as a BSides Roanoke 2026 badge challenge, but no reviewed source explains how the participant badge connected to the web puzzle, its clues, a QR/URL/credential mechanism, a solution, or any reward path.

The catalogue can document the declared challenge companion without claiming that it was firmware, a badge-hosted application, or a particular physical interaction.

ShenLabs footer and reviewed BSides Roanoke / organizer ticketing sources.

challenge, multiplayer, privacy, and behavior boundary · official maker pages · marketing-level behavior only

The project page and listing differ between 30-plus and 35-plus CTF/puzzle wording and make high-level multiplayer/link-up/word-building claims. They do not publish final challenge inventory, spoilers policy, rules, score validation, pairing/transport protocol, range, player-data handling, threat model, privacy/security review, accessibility details, event support, or a stable behavior contract.

The catalogue preserves the game and collaboration claims without inventing a final challenge count, protocol, network/privacy guarantee, completed event experience, or solution material.

BigTaro Wordweaving project page and Uberflux product page/payload.

challenge-archive caveat · organizer walkthrough · partial public reconstruction

The walkthrough documents the solved path, but this pass does not preserve all original challenge pages, audio, images, or server state.

The catalogue summarizes the puzzle structure while avoiding claims that the live challenge infrastructure remains complete.

2021 Kākācon badge challenge walkthrough.

challenge-archive caveat · organizer walkthrough · partial public reconstruction

The walkthrough documents the solved path, but this pass does not preserve all original challenge pages, images, or server state.

The catalogue summarizes the puzzle structure while avoiding claims that the live challenge infrastructure remains complete.

2022 Kākācon badge challenge walkthrough.

challenge-artifact caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document hardware, firmware updates, SAO/IR hints, serial/Morse material, and solving paths, but this pass does not mirror or audit every firmware image, forum attachment, add-on, or final badge state.

The catalogue records the verified hardware and challenge surfaces while leaving full artifact preservation for a later pass.

DEF CON forum badge-hacking thread, Hackaday hands-on article, and Science Viking Labs writeup.

challenge-artifact classification · official C517 source plus first-hand finalist writeup · documented

The ESP32 trinket is documented as a TISC finals challenge device handed to finalists, not as an all-attendee DEF CON Singapore badge or universal conference credential.

The catalogue includes it as a source-backed C517 Village challenge artifact while avoiding an official admission-badge claim.

CSIT C517 Village page, U-Zyn Chua finalist writeup, and DEF CON Singapore event page.

challenge-author caveat · first-hand writeup · documented

The challenge author states that he did not have a badge before the conference and used Yardstick One hardware to mimic the badge RF environment during development.

The dossier distinguishes the badge hardware from the off-badge development and challenge-server test setup.

SensePost BSidesCPT17 RFCat challenge writeup.

challenge-completion caveat · primary retrospective · documented

The retrospective says more than four dozen people actively worked on the B.E.N.D.E.R. challenges, but that no individual player beat the full game during the event because progress was spread across different challenge areas and social collaboration did not converge in time.

The software record describes the intended and observed challenge surface without implying a completed public solve path for every attendee.

AND!XOR DC26 retrospective.

challenge-detail caveat · official source but intentionally narrow · needs post-event walkthrough

The badge-challenge page deliberately withholds hints and says it is possible there may not be a winner this year; this pass did not recover an official puzzle solution, final badge artwork, clue inventory, or challenge source archive.

The entry keeps the challenge description narrow until an official or first-hand walkthrough appears.

BSides Tampa 2026 badge-challenge page.

challenge-details, participant-data, software-release, support, and license boundary · public Player Guide only · high-level player guide published; complete archive and terms unrecovered

The guide describes a badge-local quest, configurable participant handle, local network settings, saved progress, serial interaction, and reset/recovery concepts, but the reviewed repository exposes no implementation source, firmware/binary, board files, release/tag, license, build/deployment record, challenge-state/data-retention policy, privacy/security review, event terms, vulnerability policy, recovery package, support channel, warranty, or image-reuse grant. The guide itself directs use only of the assigned badge and advertised services.

The catalogue intentionally does not reproduce connection credentials, network or local-service details, flags, hidden resources, challenge hints, serial commands, reset steps, or exploit material; it also does not imply a privacy/security review, safe operational configuration, reproducible build, legal reuse, or ongoing support.

The Shattered Shard Player Guide and repository root, reviewed 2026-08-05.

challenge-spoiler source caveat · source-backed · documented caveat

The strongest surviving public technical sources are post-event challenge writeups that contain flag-recovery detail rather than neutral hardware documentation.

The catalogue uses them to prove badge behavior and firmware surfaces while avoiding full solution reproduction in the main badge summary.

Darkglade Ruxcon 2017 HHV Badge Flag Part 1 and Part 2 writeups.

challenge-spoiler source caveat · source-backed · documented caveat

One source is a post-event challenge walkthrough that contains puzzle solutions and hidden-challenge details, not just neutral hardware documentation.

The catalogue uses it to prove badge behavior and puzzle surfaces while avoiding full challenge-solution reproduction in the main badge summary.

semaja2 BSides Adelaide 2025 Hardware Badge Writeup.

challenge-spoiler source caveat · attendee writeup · documented

The strongest technical source is a post-event writeup containing all six flag strings and solution details.

The catalogue uses the writeup to prove challenge behavior while avoiding full challenge-solution reproduction in the badge summary.

elmo Off-By-One 2024 Hardware Badge writeup.

community-port input caveat · community repository · documented

The nofrendo port documented working display, buzzer audio, SPIFFS ROM loading, and a START-button workaround, but also noted that more button configuration was still TODO because the badge did not have buttons.

The page separates an impressive post-event software port from a complete game-console experience.

arduino-nofrendo Fri3D Camp Badge repository.

component-source gap · source-limited · unrecovered

The public trail proves electronic hardware badges and badge software/challenge behavior, but no complete 2018 schematic, BOM, PCB source, final firmware tree, or manufacturing archive was recovered in this pass.

The record avoids unverified controller, pinout, schematic, or production-detail claims.

2018 HackRVA recap, HackRVA wiki, official layout, CTF archive, and InfoconDB.

component-source mix · primary repo plus secondary article · documented

Exact module and LCD identifiers come from the hardware archive, while user-facing behavior such as CR2032, NFC, challenge, and unlock details are drawn from Hackaday's technical report.

The page avoids extrapolating a complete BOM, shipped firmware history, or production quantity beyond the recovered sources.

NearForm hardware README and Hackaday article.

conference-token classification and physical-specification gap · official Early Bird package wording · challenge coin named; final object details unrecovered

The official package calls the item a Limited Edition Challenge Coin but does not identify its material, dimensions, weight, artwork, finish, edge, serialisation, manufacturer, manufacturing method, final quantity, physical configuration, or electronic capabilities.

The record is modeled as a planned conference token rather than as an electronic badge, a generic admission credential, or a specific finished coin unsupported by the organizer's page.

BSides Cheltenham 2026 official event and Early Bird package page.

controller-mode caveat · repository README · source published

The README says at least one of the two control paths must be soldered: shield-only operation gives OLED mini-game behavior, while the recommended fuller experience uses the ESP32 Wemos D1 module and related support parts.

The record separates the minimal shield/display experience from the ESP32 and RF-detector build path instead of treating every configuration as identical.

ElectronicCats/badge-44con-2025 README.

delivery logistics caveat · post-event account · documented narrowly

The published post-event account reports tight deadlines, logistical challenges, and cross-continent transport before saying the programmed, flashed, and tested badges arrived in time. It does not specify a late shipment, defect, attendee impact, or a production failure.

The entry preserves a real delivery constraint without overstating it as a failed distribution or hardware-quality incident.

The Story Behind the BSides Kristiansand 2026 Shield Badge post-event account.

destructive reflash caveat · repository README · documented

The README warns that reprogramming erases badge memory, including challenge progress and custom messages.

Surviving-badge owners should preserve state before using the documented post-event firmware path or DFU flashing workflow.

Saintcon 2019 Enigma Badge README.

disappeared project-page caveat · live page audit · needs archive recovery

The repository README links the historical `secyc23badge` page, but that URL currently returns a WordPress 404.

Future work should recover an archived copy before adding additional lore, instructions, or imagery from the original project page.

FluxDecoder README and live 404 at https://www.se.community/secyc23badge/.

distribution and variant boundary · official promise and organizer-feed corroboration · attendee receipt corroborated; full ledger unavailable

The official page promises a coin for every attendee, and the official organization feed re-shares an attendee report of coins. The reviewed sources do not publish attendance count, production count, handout ledger, no-show handling, replacements, lost-item support, individual receipt evidence, or any coin variants.

The record can distinguish a documented conference-wide promise and a corroborated attendee report from a complete fulfillment or variant inventory claim.

What's New for BSides Nashville 2026 and BSides Nashville organizer updates.

distribution scope caveat · official event page · documented source limitation

The official page proves hackable badges at CyberThreat 2024 and describes in-person delegate hands-on opportunities, but does not publish exact badge quantity, ticket-tier eligibility, or whether every on-site attendee received one.

The catalogue records the badge as a CyberThreat 2024 challenge artifact without inventing a universal distribution count.

CyberThreat official event page.

distribution scope caveat · badge-maker writeup · documented

Badge Pirates says only 250 preregistration attendees received electronic badges, organizer/speaker/volunteer/Jr Hacker batches totaled 128 hand-assembled boards, and non-electronic participant PCBs carried crypto-challenge clues.

The catalogue avoids implying every BSidesKC attendee had a fully electronic badge while still recording the verified electronic badge ecosystem.

Badge Pirates BSidesKC 2019 badge writeup.

distribution scope caveat · official source wording · documented

The source describes CTF participants grouped into teams of eight and does not say that every conference attendee received this badge.

The badge is classified as a CTF team hardware artifact rather than a confirmed all-attendee admission badge.

NorthSec past-editions page.

distribution, ticket, and attendee-handoff gap · official event and post-event archive sources · event complete; allocation outcome unrecovered

Official HTH sources establish that the June 3-5 conference occurred, and a public attendee account says a light-up badge was part of the CTF. No reviewed source establishes ticket eligibility, badge price, production quantity, inventory, role variants, recipient count, registration pickup, shipment, replacement, refund, attendee-wide allocation, or individual physical receipt of the Eagle 5 hardware.

The entry does not turn a public source archive or one attendee account into a distribution record or a claim that every conference participant received the same badge.

HTH official site and LinkedIn updates; Paul Danis public account; Eagle 5 source repository.

SiNE note

documentation/lore · primary wiki · historical

The clue list and badge behavior are preserved, but the wiki notes some details were only filled in after EMWave had passed and still left some answers to be added.

The hidden-beacon mechanic is source-backed, while exact participant gameplay reconstruction remains partial.

EMF Badge Wiki SiNE page.

donation proof, privacy, tax, and charity-verification scope · public form fields and organizer wording · collection flow published; policies not recovered

The form asks for contact information and an uploaded donation receipt/confirmation that can show amount, charity name/address, and identifying information, but reviewed sources do not publish a privacy notice, controller/contact policy, retention/deletion period, storage/security safeguards, data-sharing terms, age/minor policy, tax-deductibility statement, nonprofit-status standard, charitable solicitation registration, verification method, receipt policy, or dispute process.

Readers can distinguish the organizer's philanthropic request from financial, tax, legal, privacy, or data-security advice and should not assume a particular validation, deduction, confidentiality, retention, or delivery outcome.

Choose Your Own Charity eChallengeCoin Submission form and AoSC eChallengeCoin page.

draft code and physical-artifact boundary · primary CPEC repositories · planned project and companion design sources; physical artifacts unverified

CPEC's first repository explicitly says its code is not final, while the second is an active in-progress game repository. The third, scoped companion repository provides KiCad, BOM, and placement source assets, but no reviewed source supplies a provenance-backed photograph of a completed MechBattle or companion unit, a physical prototype account, manufacturing/order evidence, serial/revision log, assembly/test record, final hardware population, or completed event-unit confirmation.

The catalogue records a real named planned badge project and a source-published companion design trail, but does not turn source files into proof of physical, safe, completed, or distributed hardware artifacts.

CPEC DC34 MechBattle, DC34 Mech Badge Game, and DC-34-Mech-SAO repositories.

draft game-design and media-rights boundary · source-linked draft document and local image-policy review · creative context only; no reusable media basis

The source-linked game document is a draft creative reference and the badge, game, and companion repositories contain code and media assets, but none pairs a selected factual physical-badge or companion image with a reusable license or explicit permission basis, named attribution, source URL, and processing notes. The sources also do not establish final game content or third-party rights.

The record remains image-free and does not reproduce draft lore, repository previews, screenshots, logos, board renders, or any generated/approximate badge image.

CPEC DC34 MechBattle, DC34 Mech Badge Game, and DC-34-Mech-SAO repositories, linked game-design document, and badge.gallery image policy.

e-paper app constraints · app writeup · historical

The Gameboy emulator writeup highlights the challenge of adapting fast interactive graphics to an e-paper badge display.

This is useful lore for app-store records: the badge could run surprising software, but display technology shaped what was practical.

SpritesMods e-ink Gameboy writeup.

electronic badge not proven · official guide but intentionally narrow · classified as identity artifact

The official guide proves a paid-attendee Survival Kit with conference badge, lanyard, and sticker set, but does not prove an electronic badge, PCB, firmware, components, production run, shipped count, or challenge behavior.

The dossier preserves the pandemic-era badge/lanyard artifact without upgrading it into unsupported electronics.

RC14 Quick Guide.

electronic badge not proven · source-backed but incomplete · classified as physical identity artifact

The recovered public sources prove a Human/Human+ badge-and-lanyard inclusion and lanyard artwork, but do not prove an electronic badge, firmware, PCB, component stack, challenge behavior, or badge variant taxonomy.

The dossier preserves ROOTCON 17 as an attendee identity artifact and avoids upgrading the record into unsupported electronics.

RC17 Conference Overview, RC17 Pocket Guide, and ROOTCON 17 Art directory.

electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact

The recovered public sources prove limited Entry badge availability and closed-conference registration context, but do not prove an electronic badge, PCB, firmware, component stack, challenge behavior, physical badge design, or lanyard artwork.

The dossier preserves Zer0Con 2024 as an admission-badge availability record without inventing electronics or a physical credential design.

Zer0Con 2024 archive and POC Security official update trail.

electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact

The recovered public sources prove limited Entry badge availability and closed-conference context, but do not prove an electronic badge, PCB, firmware, component stack, challenge behavior, physical badge design, or lanyard artwork.

The dossier preserves Zer0Con 2025 as an admission-badge availability record without inventing electronics or a physical credential design.

Zer0Con 2025 archive and POC Security official update trail.

electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact

The recovered public sources prove limited registration availability and closed-conference context, but do not prove an electronic badge, PCB, firmware, component stack, challenge behavior, physical badge design, or lanyard artwork.

The dossier preserves Zer0Con 2026 as an admission-badge availability record without inventing electronics or a physical credential design.

Zer0Con 2026 official page and POC Security official update trail.

electronic-badge evidence boundary · official prospectus and event-page comparison · no 2026 electronic attendee artifact established

The official sponsorship prospectus lists an Electronic Badge Sponsor option, while the completed-event information explicitly documents the attendee challenge coin. Neither source identifies an issued 2026 electronic badge, a PCB, electronics, firmware, recipient allocation, or a technical archive.

The commercial sponsorship label is preserved as context but does not turn this non-electronic coin record into an unsupported electronic-badge claim.

BSides Nashville 2026 Sponsorship Prospectus and What's New for BSides Nashville 2026.

electronic-badge evidence gap · source-backed limitation · documented; monitor future updates

The recovered official sources prove badges as sponsorship/logo-placement artifacts, but they do not describe a PCB, firmware, soldering project, hardware challenge, QR workflow, lanyard design, production quantity, or exact physical badge design.

The catalogue classifies this as a conservative conference identity artifact instead of an electronic badge or badgelife project.

BSides Reykjavik sponsorship packages and 2026 event pages.

event allocation and physical-production boundary · official event sources and maker archive · event completed; badge allocation unverified

Hack Club's official pages establish a completed Singapore game jam, while Kai Pereira's maker archive explicitly identifies Overglade hackathon badges. Neither reviewed official page publishes a ticket-to-badge entitlement, recipient list, allocation rule, quantity, pickup/delivery record, organizer-issued credential role, manufacturing record, or final physical-production ledger.

The catalogue records a real event-specific maker artifact without treating it as a universal attendee benefit, official access credential, organizer-issued device, or complete production account.

Overglade official page, Hack Club Horizons Arcana retrospective, and Kai Pereira's Overglade-Badges archive.

event scope caveat · official summit page plus badge repository · documented

The official page frames GreyCTF Summit 2025 as a cybersecurity summit with talks, workshops, booths, and GreyCTF context, while the repository frames the artifact as the GreyCTF 2025 badge. This record treats it as a source-backed Singapore hacker-culture/security badge without overclaiming universal public distribution.

The event and badge are included, but distribution and admission-credential claims remain conservative.

GreyCTF Summit 2025 page and NUSGreyhats/greybadge25 README/release trail.

event-software caveat · project-owner writeup · documented

HackRVA noted time pressure around the scoreboard and base-station/game content, so the record treats some game/networking elements as planned or constrained rather than fully proven completed behavior.

The entry separates source-backed plans, public interpreter code, and final-event uncertainty.

HackRVA RVAsec 8 layout post.

field-accessory availability · primary docs · historical

The getting-started notes say USB-serial adapters and headphones were available only as needed, not in every badge bag.

The badge game depended on accessories that some attendees needed to borrow from the badge hacking area.

HackerHotel 2020 getting-started docs.

field-kit dependency · primary docs · documented

Badge hacking depended on attendee-supplied USB and battery power.

The official page recommended a micro USB data cable plus replacement AA batteries or a power bank, so a prepared kit mattered for camp hacking.

RomHack badge page and RHC22 README.

field-report scope caveat · official docs plus secondary field report · needs schematic-level review

The Hackaday report is useful for attendee-facing behavior and lore, but detailed component claims should still be checked against the official Badge.Team hardware repositories and schematics.

The dossier can use the report for mesh gameplay and relay-interface lore while keeping low-level hardware claims anchored to primary sources.

Hackaday field report and Badge.Team HackerHotel 2024 docs.

field-writeup scope caveat · first-hand writeup · documented

The 2025 Conference badge and Soldering village writeups document practical reverse engineering and challenge solving from an attendee perspective, but they are not a complete official challenge archive or manufacturing release.

The catalogue uses them to enrich firmware and challenge behavior while keeping authoritative hardware-source claims tied to the official NorthSec repository.

NorthSec competition write-up index and Jean Privat's 2025 badge writeups.

final-hardware archive gap · source-backed but incomplete · needs post-event technical source

Ticketing proves a cool badge and the prospectus proves electronic badge design/build was available as a supporter item, but this pass did not recover final schematics, board files, firmware, BOM, or component-level documentation.

The record does not claim processor, display, radio, CTF, battery, or shipped electronic features beyond the public sources.

BSides Brisbane 2025 Humanitix page and 2025 sponsorship prospectus.

finicky Arduino-clone caveat · badge text quoted in field writeup · historical

The quoted badge text says the board is loaded with an Arduino Leonardo bootloader and can be treated as an Arduino clone, but warns that getting everything to work and fit can be finicky.

The compendium records this as a practical attendee caveat rather than an unresolved defect: the badge was intentionally open and modifiable, but not frictionless.

Zeta-Two field writeup quoting the challenge badge text.

firmware absence caveat · source-backed but intentionally narrow · documented

The recovered sources describe a soldered RGB blinky badge, transparent PCB design, and coin-cell power, but do not document a programmable MCU, firmware, serial shell, repository, or CTF behavior for the AVTOKYO 2019 badge.

The dossier keeps the artifact as a beginner soldering-village blinky badge instead of inventing software behavior.

Hackster.io blinky-badge writeup and AVTOKYO 2019 event page.

firmware absence caveat · source-backed but intentionally narrow · documented

The recovered sources describe a soldered blinky badge, LED mounting choices, and coin-cell power, but do not document a programmable MCU, firmware, serial shell, repository, or CTF behavior for the CODE BLUE 2019 badge.

The dossier keeps the artifact as a beginner soldering-village blinky badge instead of inventing software behavior.

Hackster.io blinky-badge writeup.

firmware and app release boundary · official documentation and MIT firmware repository · partly documented / post-event source pass

The public firmware and App Store paths establish a programmable platform, but they do not prove the final attendee firmware image, final pre-installed app set, App Store inventory or availability during camp, final game payloads, or post-event support. The firmware README also documents a manual headset-output configuration choice.

The catalogue records the released software architecture and recovery workflow without converting a public repository into claims about final attendee experience.

Fri3d Camp 2026 badge documentation and badge_firmware_MicroPythonOS README.

firmware and challenge-safety boundary · commit-pinned README and firmware source · firmware variants documented; production mapping and safe challenge instructions withheld

The README distinguishes older and newer firmware behavior, while the source includes serial-menu, LED/OLED, and challenge modules. The public archive does not supply a tagged production release, signed binary provenance, source-to-unit mapping, complete intended challenge deployment, support policy, or confirmation that each physical artifact used the same firmware. The catalogue deliberately does not republish flashing, serial-access, flag, or challenge-solving procedures from the archive.

The entry retains a useful public firmware trail without turning it into operating instructions, a security challenge walkthrough, a guarantee of USB behavior, or proof of a final event configuration.

Div0 Tingkak eBadge commit-pinned README and firmware source.

firmware and schematic gap · official badge guide with limited hardware depth · needs deeper archive recovery

The official badge page documents CTF behavior, CP2102 serial access, BAT CON battery handling, 9600-baud workflow, unlock codes, and safety instructions, but this pass did not recover firmware source, schematic files, BOM, Gerbers, challenge binaries, or a complete hardware archive.

The catalogue keeps the strong official badge-guide evidence while avoiding unsupported claims about the unrecovered design files or shipped firmware internals.

AvengerCon IX Electronic Badge guide and linked hints page.

firmware binary, compatibility, and update-scope boundary · public source and commit history · no tagged release identified

The latest public firmware commit is titled “final code checks,” but the reviewed project provides no tagged release, signed/final binary, flash procedure, source revision declaration for event units, test/CI result, media-image provisioning method, rollback/recovery plan, hardware-variant compatibility matrix, or support lifecycle.

Source-level game and interface behavior remains discoverable without labeling the branch as a final, universally flashable, supported event firmware package.

`ch32fun-portal-badge` PlatformIO configuration, source tree, and commit history.

firmware deployment and release gap · public repository and GitHub metadata · source visible; final deployed image unrecovered

The current repository exposes MicroPython source, apps, custom-firmware documentation, and June revisions, but has no GitHub tag or release. No reviewed source maps a versioned binary or source commit to a physically delivered 2026 e-badge, provides post-event recovery/support scope, or records CTF deployment and results.

The record treats the code as a valuable public archive without asserting a final official firmware release, production flash state, challenge outcome, or supported owner-update path.

BSidesFW2026Badge repository tree, firmware README, source commit history, and empty tag/release endpoints.

firmware release and challenge boundary · public source-tree review · source available but release parity unknown

The organizer-linked repository exposes source and user documentation, but no tagged event release, signed image, installation ledger, or complete post-event challenge archive was recovered. The catalogue intentionally withholds operational use instructions and any claim about exact source-to-unit parity.

Public code remains an important preservation resource without being presented as a verified reproduction image or complete challenge solution set.

SEIF-UAM C1B3RTR4CKS 2026 badge repository and commit metadata.

firmware release and deployed-image gap · GitHub repository state · post-event initial source release visible; final device state unrecovered

The public repository has a single July 15 initial-release commit and no GitHub tag or release. It exposes firmware source and documentation, but reviewed sources do not map a versioned build to actual event units, establish a final signed/validated production image, state CTF deployment/results, or define an owner recovery/support lifecycle.

The dossier treats it as valuable code evidence without claiming the current checkout is the final deployed badge firmware or a supported update/recovery path.

Eagle 5 repository metadata, commit history, README, and tag/release endpoints.

firmware release and licensing gap · primary maker storefront and profile sources · awaiting announced firmware release

The product says new firmware with graphics and puzzles will be released and describes SkittyOS features, but it links no source repository, binary, versioned release, flashing workflow, build instructions, puzzle material, protocol documentation, or software/hardware/documentation license.

The record can describe the maker's announced feature surface without claiming a released, reproducible, inspectable, or reusable firmware archive.

Uberflux Shitty Kitty V2 product listing and lipo maker profile.

firmware release and validation gap · primary source repository · prototype source visible; production release unrecovered

The repository includes current MicroPython source and ESP32-S3/Pico 2 target files, but the README describes breadboard development and work in progress. No tagged final firmware, reproducible production build, test result, challenge outcome, or evidence that this source ran on conference units was recovered.

The game and flashing material remains valuable development evidence, but not a claim about production behavior or a supported owner-update path.

OzSecICT badge-crashandburn README, firmware directory, and main source.

firmware release, toolchain, dependencies, and software-license gap · repository and diary describe evolving work · implementation materials exist; final user release not identified

The sources discuss a compiled C library, Arduino IDE material, an evolving Python/C++ split, graphics/file-system/sensor work, games, puzzles, and USB-C modification, but do not provide a tagged final firmware release, stable installation guide, complete build environment, dependency inventory, update/recovery path, release integrity, formal test result, final game content, or a separate software license. The repository's CC BY-SA statement is not treated as a resolved license for every code dependency.

The dossier links the public work without presenting it as a finished end-user firmware or support package.

MalO_SAO repository and MalO SAO developer diary.

firmware, CTF, game, and source-license gap · programmable/CTF/game wording · features named; implementation and release context unpublished

The sources call the combo fully programmable and name CTF, bling modes, laser tag, TV control, and Drinking Roulette, but no reviewed source provides firmware, binary, code, repository, license, build/flash instructions, configuration, game rules, solution/reset path, scoring, data handling, update policy, or security testing.

Readers can understand the advertised feature set without assuming it is open source, reproducible, supported, safe, or available in every unit/configuration.

Gunslinger-B-Gone Tindie listing and Hacker Couture DEFCON 33 Product List.

firmware, CTF, gameplay, source, and licensing gap · no artifact-level technical source recovered · no implementation or interaction documentation located

No reviewed source says RTV D20 has firmware, software, a repository, binary, website, CTF challenge, game mechanic, D20 interaction, workshop use, update/recovery path, source code, license, security review, user-data behavior, or accessibility information. The Village's broader CTF/program descriptions are not attributed to this badge.

Readers are not led to assume that the D20 name denotes an electronic game, an access pass, a CTF device, or any documented implementation.

Red Team Village event page and DEFCON 34 Badgelife Form response.

firmware, CTF, party-support, and source-license gap · high-level maker feature and party wording · features and purpose named; implementation and accounting context unpublished

The listing says the ESP32-S3 badge is fully programmable, has a CTF/puzzles, unlocks GIFs/bling, and helps support the FD party, but no reviewed source provides firmware, binary, code, repository, license, build/flash instructions, game rules, solution/reset path, score service, content rights, data handling, party recipient, donation amount, accounting, affiliation, update policy, or security testing.

The catalogue records the advertised activity and party-support framing without assuming open source, an ongoing service, rights-cleared content, a particular beneficiary, or a verified fulfillment of support.

FightDystopia 2025 Badge product listing.

firmware, CTF, protocol, backend, and licensing gap · team-announced software claim · no public technical release identified

The source says the CTF lives in firmware and invokes real protocols plus a gated backend, but no reviewed material publishes firmware, source code, binary, challenge inventory, protocol description, backend service, build/flash path, update/recovery path, account-data policy, score validation, software license, or terms for player content.

The record does not convert a game announcement into a reproducible software release, operational service, security claim, data-handling guarantee, or solution guide.

Zombie Badge Info Dump.

firmware, cryptography, performance, and source-license boundary · maker-described product claims and adjacent repository review · claims are not independently validated; matching release and clear license absent

The source describes RISC-V assembly, UART puzzles, named cryptographic primitives, constant-time behavior, and low-power/performance characteristics, while the linked GitHub repository describes a separate AVR/ATmega328P framework with an Other license field. No matching CH32V003 source, binary, build/flash path, test vector, benchmark method, hardware package, recovery process, security review, or clear applicable license was reviewed.

The catalogue does not characterize the badge as secure, audited, reproducible, open source, performant, or suitable for a security-sensitive purpose solely from maker marketing or an adjacent framework.

Ouroboros Badge #BadgeLife product page, How It Works PDF, and mytechnotalent/ouroboros repository.

firmware, documentation, and licensing gap · primary maker product statement · maker promises post-con material; no current release identified

The listing promises post-con hardware documentation and a stub firmware but no reviewed source currently provides a repository, binary, source tree, game data, build/flash instructions, update/recovery path, release version, firmware hash, hardware license, software license, or documentation/media license.

The dossier records the promise as a future source lead without asserting software availability, reproducible builds, final feature behavior, or reuse rights.

Wordweaving Badge Uberflux listing and BigTaro project page.

firmware, feature-readiness, and security-behavior boundary · author's explicit day-one qualifier · only source-starred features described as available day 1

The author expressly says most listed capability categories are not ready out of the box and marks only LED adjustment, a hidden CTF/scavenger hunt, and NFC read/write as day-one functions. No firmware, binary, source tree, build/flash guide, challenge rules, feature matrix, configuration, protocol, update/recovery path, security review, test result, privacy policy, or software license is public.

The record does not represent deferred or merely hardware-capable categories as shipped functions, supported workflows, secure behavior, or final user experience.

Sneakreaper limited edition defcon badge!

firmware, interaction-protocol, and licensing gap · primary maker storefront source · needs public archive or terms

The product copy narrates game modes and badge-to-badge beacon behavior but does not link firmware source or binary, a flashing/update path, a wireless protocol, message format, source/build instructions, or a software/documentation/hardware license.

The catalogue does not infer radio technology, cryptographic behavior, exploit mechanics, interoperable networking, source availability, or redistribution rights from promotional game language.

Pfarrside Creations badge-only product listing.

firmware, puzzle, CTF, and source-license gap · high-level programmable and challenge wording · features named; implementation and release context unpublished

The source names fully-programmable behavior, hardware/software puzzles, soldering challenges, CTF deliveries, and narrative/game elements but does not publish firmware, a binary, code, repository, license, build/flash instructions, rules, reset path, solutions, scoring, networking, data handling, update policy, or security testing.

Readers can understand the advertised interaction surface without assuming open source, completed service availability, reproducible behavior, or a verified security model.

Submarine Badge & Pirate SAO product listing.

firmware, puzzle, and source-license gap · high-level maker puzzle wording · gameplay behavior named; implementation and source context unpublished

The listing says analog tuning and four puzzles unlock LED patterns, but no reviewed source provides firmware, binary, code, repository, license, build toolchain, fuse map, calibration values, puzzle solutions, score/reset path, update policy, accessibility information, security review, or test results.

The catalogue preserves the advertised interactive surface without assuming it is open source, reproducible, stable, fully documented, supported, or uniformly present in every unit.

Masonic33 Tindie listing and Hacker Couture DEFCON 33 Product List.

firmware, radio, privacy, and license boundary · public repository review · in-progress source and Arduino file with no reviewed final release or root license

The game source contains BLE-related code, QR support, display/sound modules, and game data, and the companion tree contains an Arduino source file, but no reviewed repository supplies a tagged release, final binary, reproducible build statement, hardware-matched configuration, stable radio or add-on protocol, player-data/privacy statement, consent model, security review, update/recovery policy, or explicit root license. The sources cannot establish final wireless behavior, data handling, or a working host/add-on firmware result.

The record does not offer configuration or operating instructions, claim secure or private interaction, assert a released firmware, or treat public code as a license grant.

CPEC DC34 Mech Badge Game and DC-34-Mech-SAO repositories and metadata review.

firmware, release, and license gap · public repository tree and GitHub metadata · no firmware/release/tag or declared repository license identified

The public root contains KiCad and backup files but no README, firmware, binary, programming/recovery guide, CTF, app, release, tag, LICENSE file, or detected GitHub repository license. The reviewed schematic also does not instantiate a microcontroller.

The dossier does not infer programmable behavior, a user-update path, a released build, support obligation, open-source or open-hardware terms, or permission to redistribute repository files or visual material merely from public visibility.

2026-badge repository tree, GitHub metadata, tag/release endpoints, and reviewed schematic.

firmware, software, source, and license gap · no implementation source recovered · no software or source documentation located

No reviewed source identifies a controller, firmware, binary, source repository, license, game, animation, operating behavior, update/recovery path, security model, user-data handling, accessibility guidance, or support policy. The MF Doom name does not establish that v2 runs the Doom video game or any software.

Readers are not led to assume electronic behavior, firmware availability, open-source status, video-game functionality, or a supported modification path from the artifact name alone.

u/Truth-Miserable MF Doom SAO v2 Reddit post and DEFCON 34 Badgelife Form response.

firmware, source, and licensing gap · public repository and release inspection · binary update path published; readable software and hardware source absent

The public repository says it will contain information and software updates, and its release/README document a UF2 update path, but the reviewed tree does not provide readable firmware source, build tooling, hardware design, a license file, source history, change log, game/application documentation, security analysis, or an image-use license.

Readers can follow the documented update surface without assuming the badge is open source, reproducible, auditable, redistributable, or supported beyond the published high-level instructions.

im-redactd/dantes_inferno repository and Initial Release - v1.1.

firmware, source-code, challenge, and recovery boundary · official BadgeLife guide · high-level recovery documentation published; firmware release and support unrecovered

The guide names USB CDC, DFU/BOOTSEL, and firmware.uf2 recovery, and labels firmware source as after-con material while intentionally withholding challenge answers. The reviewed source does not publish a firmware file, source repository, versioned release, build/dependency record, source-to-device mapping, signature/integrity mechanism, challenge solution, complete recovery image, security review, privacy/data policy, support channel, warranty, or proof of successful field updates.

The record makes the public documentation discoverable without turning it into an invitation to bypass challenges, a verified update path, a final firmware archive, or a supported modification procedure.

Badge.Life DC34 Village Badge guide.

firmware, vendor-command, secret-content, and licensing gap · official product-level behavior description · no public technical release identified

The source mentions lighting modes, generic LED control, vendor commands, reprogramming, and an undisclosed possible secret, but no reviewed material publishes firmware, source tree, binary, command definitions, IDs, secret content, build/flash instructions, update/recovery path, software license, dependency inventory, or terms for user content.

The catalogue records public behavior claims without exposing or inventing challenge content, protocol messages, source availability, update steps, or reuse rights.

Firefly Jar SAO product page and Lepi Labs DC34 announcement.

firmware-and-controversy caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document the save issue, firmware archives, GB Studio game source, and DEF CON's response to contractor-credit and firmware claims, but this pass does not adjudicate every dispute, audit every firmware build, or mirror every hardware/game asset.

The catalogue records the verified public badge surfaces and flags that the production and firmware story needs a deeper artifact-level chronology.

DEF CON news and response post, media-server badge archive, badge-game repository, Raspberry Pi RP2350 sources, and community ROM writeup.

firmware-and-final-state caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document firmware dumping/modification, key combos, badge variants, and challenge flow, but this pass does not mirror every firmware image, media artifact, phone recording, badge variant, or post-win state.

The catalogue records verified hardware and challenge structure while leaving full artifact preservation and firmware archaeology for a later pass.

DEF CON forum thread, FaultPoint firmware extraction, Red Balloon Security OFRAK writeup, and Kybr challenge writeup.

firmware-detail caveat · source-backed but incomplete · needs deeper artifact inventory

Public writeups expose serial strings and interaction behavior but this pass does not unpack the full badge firmware or media-server archive.

The compendium records observed behavior and published challenge paths while avoiding unsupported claims about the badge's internal firmware architecture.

Degenerate Metric writeup, Inverse report, and DEF CON 24 media links.

firmware-scope caveat · source-backed but intentionally narrow · documented

Recovered sources prove an analog 555-timer badge kit and optional Arduino-compatible expansion path, but no CarolinaCon 12 badge firmware repository, microcontroller stock firmware, CTF code, or final attendee modifications were recovered.

The entry records the verified soldering badge and hacking surface without inventing software behavior.

CarolinaCon 12 badge section and instruction manual.

firmware-source caveat · source-backed but incomplete · needs deeper archive recovery

Hackaday.io links stock firmware source and an Arduino RGB demo, but this pass records the public project evidence rather than auditing, mirroring, or validating every firmware artifact and challenge branch.

The catalogue records verified hardware, game behavior, and recovery workflow while leaving full firmware preservation and challenge reconstruction for a later pass.

Hackaday.io THOTCON 0x8 project links and project logs.

firmware-source caveat · source-backed but incomplete · documented; monitor newly surfaced 2022 badge archives

The recovered public tree proves hardware, BOM, production, challenge-media, and SAO assets, and the official competition write-up index preserves 2022 CTF writeups, but this pass did not recover a dedicated 2022 badge firmware README, final event guide, badge-specific writeup, or complete challenge source.

The record documents verified hardware and archive surfaces while avoiding unsupported badge-game or firmware-behavior claims.

NorthSec 2022 badge hardware tree, challenge directory, and competition write-ups index.

firmware-source caveat · repository tree and decoded sketches · needs deeper firmware inventory

The firmware tree preserves Blink_Bug, AudioWAV, Chona.wav, and an EdgeImpulse note, but this pass did not audit every sketch dependency, runtime command implementation, challenge binary, audio asset provenance, or final shipped firmware image.

Software claims stay tied to the README instructions, visible firmware tree, and decoded example sketches rather than treating the repository as a complete final production firmware archive.

ElectronicCats/Badge-BugCON-2022 firmware tree, Blink_Bug sketch, AudioWAV sketch, and Edge_impulse.txt.

firmware-source gap · project logs but incomplete source recovery · needs artifact-level archive

The project logs describe firmware tracks, CAN tooling, HID/CDC behavior, and emulator experiments, but this pass did not recover a complete public final firmware repository, board-production release, or challenge/utility software archive.

Software and protocol claims are kept to the public project statements rather than treating development notes as a complete release package.

Hackaday.io LayerOne 2017 details and logs.

firmware-source gap · source-backed but incomplete · needs archive recovery

The public record proves staff firmware flashing after attendee assembly, but this pass did not recover a public firmware repository, binary release, pin map, bootloader workflow, or badge-challenge source archive.

The software section records the verified staff-flashing workflow without inventing firmware behavior or challenge internals.

Hackaday WOPR Summit field report and Russell Handorf WOPR 0x00 build guide.

firmware-version caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document firmware update paths and version checks, but this pass does not mirror or audit every media-server artifact, hex file, writeup, or internal game branch.

The catalogue records the verified hardware and update workflow while leaving complete firmware archaeology for a later artifact-level pass.

DEF CON 26 archive firmware notice, Hackaday.io solving project, and DEF CON forum curated content.

firmware/backend boundary · public firmware archive · documented

The public firmware repository preserves participant-side badge code and CTF apps, but this pass did not recover every private organizer backend, provisioning script, or final competition infrastructure artifact.

The software section describes the recovered badge firmware without overclaiming complete event infrastructure publication.

irq5.io firmware writeup and geekman/badger repository.

format and technical detail gap · official schedule and organizer post-event update · no public design or technical archive recovered

The official Summit 2026 page uses the word badge at registration, and the post-event update confirms the summit concluded, but neither source identifies an identity-card format, material, lanyard, QR/barcode, RFID/NFC, electronic hardware, firmware, credential system, maker, final design, or challenge behavior.

The entry is classified only as a generic identity artifact and must not be upgraded into a physical-card or electronic-badge record without more public evidence.

AfricaHackOn Cybersecurity Summit 2026 official schedule and organizer post-event update.

game firmware, update, source, and license gap · maker game claims and public board binary context · CircuitPython build available; eChallengeCoin game/release trail incomplete

The maker says the coin supports a terminal game and new firmware, and CircuitPython offers a board-specific UF2 build, but no reviewed source provides the 2026 text-adventure game source/binary, a release tag, checksum, flash/update instructions, serial protocol, game documentation, final firmware-to-unit mapping, recovery process, package license, hardware license, artwork license, security review, vulnerability process, support policy, or warranty.

The catalogue points to a public board platform without representing the shipped game or final coin as open source, reproducibly buildable, safe to reflash, supported, security-reviewed, or licensed for redistribution.

AoSC eChallengeCoin page and CircuitPython Coin M0 download profile.

hardware and firmware archive gap · official organizer and credited maker posts · maker identified; technical archive still absent

The organizer identifies Technische Fachschule Bern as designer and assembler, and the school says it developed and manufactured the hardware. Those sources still disclose no named MCU, schematic, PCB, pinout, power specification, firmware, challenge documentation, or technical release.

The dossier can credit the institutional hardware contribution without implying a particular ESP family, SAO wiring standard, or technical behavior beyond the public wording.

Area41 2026 organizer recap and Technische Fachschule Bern hardware update.

hardware and firmware archive gap · source-backed but incomplete · needs artifact-level archive

No public schematic, PCB, BOM, firmware repository, flashing workflow, challenge binary, radio/display/power details, or badge-team writeup was recovered in this pass.

Component and software claims remain intentionally withheld until artifact-level sources appear.

BSides Porto official site, about page, agenda page, and ticketing page.

hardware and firmware archive gap · named post-event account · electronic and hackable classification only

The recovered account establishes an electronic, hackable CTF badge but names no MCU, board, display, LEDs, radio, power system, connector, schematic, BOM, fabrication files, firmware, source, binary, app, protocol, toolchain, license, update path, or maker.

The catalogue deliberately stops at source-described electronic and interactive behavior rather than inventing a technical architecture or user workflow.

Best of PWNEDCR 0x08 by Simón Correa.

hardware and firmware archive gap · source-backed but incomplete · needs public DCSG1 archive

The recovered sources identify the ESP32-C6 platform, flash capacity, IR game hardware, software frameworks, and development workflow, but do not publish a DCSG1-specific schematic, PCB files, BOM, final firmware source, binary release, exact display model, power design, or production quantity.

The dossier describes only the substantiated hardware and software surface instead of inferring a complete board design or claiming that the separate OpenLASIR repository is DCSG1 firmware.

Cryptocurrency Village 2026 workbook, DEF CON Singapore Official Badge Laser* Tag archive, and OpenLASIR repository.

hardware and firmware archive gap · first-hand finalist source but incomplete technical archive · needs public challenge archive

The public source trail identifies ESP32 hardware and BLE mesh behavior but does not publish schematic, PCB files, BOM, firmware, binaries, protocol documentation, exact module variant, or production files.

Hardware and software claims stay limited to the finalist writeup's challenge description.

U-Zyn Chua TISC@DEFCON Singapore 2026 Finals writeup.

hardware and firmware archive gap · current public source pass · no technical archive recovered

The reviewed public event and ticket sources announce an electronic badge but do not publish hardware specifications, PCB or schematic files, firmware, source code, flashing instructions, challenge details, or a final physical design.

The record remains limited to the advertised electronic-badge inclusion until Ekoparty or a credited badge team publishes technical or post-event documentation.

Ekoparty Buenos Aires 2026 event page and organizer-linked Champion ticket page.

hardware and firmware documentation gap · official announcement and public tooling · needs final technical archive

Public sources establish high-level RP2040, CAN/CAN FD, power, USB, and host-tool behavior but do not provide a complete badge board design, schematic, BOM, Gerbers, transceiver details, power source, manufacturing files, main firmware, flashing workflow, or final badge-specific license.

The record retains documented engineering surfaces while withholding a complete implementation claim until Car Hacking Village publishes a final technical archive.

Car Hacking Village badge announcement and `chv_badgetools` README.

hardware and firmware source gap · source-backed but incomplete · needs artifact-level archive

The recovered public sources prove an electronic badge and Badge Sponsor category, but do not describe a PCB, firmware, soldering project, badge app, QR workflow, lanyard design, production quantity, challenge integration, or exact physical badge design.

The catalogue records the electronic-badge programme while withholding unsupported component, software, distribution, and interaction claims.

BSidesLisbon 2025 about page, sponsors page, CTF page, and Eventbrite listing.

hardware and firmware source gap · source-backed but incomplete · needs public technical archive

The public sources document high-level Pico/OLED/button/SAO/EEPROM/game behavior, but this pass did not recover schematics, PCB files, BOM, firmware source, protocol documentation, production files, or a public repository.

Component and firmware claims remain limited to the public product and announcement text, with no invented electronics or implementation details.

DEF CON forum announcement, RENXCHANGE product page, and DC33 schedule mirror.

hardware and firmware source gap · source-conservative public record · needs primary technical archive

Public sources prove a speaker-colored electronic badge and post-event badge-team activity, but no board photo with reuse rights, physical form, PCB, MCU, display, radio, power, connector, schematic, Gerber, BOM, firmware, challenge, programming guide, protocol, or repository was recovered.

The dossier records the real electronic artifact without treating the term electronic, a ticket-page slogan, or social confirmation as a component-level technical description.

cackalackycon 2026 CFP, Eventzilla listing, organizer updates, and Jeff Shouse report.

hardware and software archive gap · official current page · electronic-badge term published; implementation unreleased

The official 2026 package uses the term electronic badge but publishes no physical form, component list, PCB, schematic, Gerber, BOM, firmware, app, source repository, flashing guide, radio/credential protocol, license, or security/privacy documentation.

The catalogue does not turn the word electronic into assumed powered hardware, NFC, a specific controller, a challenge, or a reproducible software stack.

DragonJARCON 2026 conference and diploma page.

hardware and software specification gap · primary and first-hand source trail · needs badge-team documentation

Public sources establish a custom PCB/circuit-board badge but do not identify any electronic components, active behavior, power source, board dimensions, schematic, BOM, Gerbers, firmware, programming method, or challenge implementation.

The record preserves the verified physical PCB form while withholding an electronic-device, firmware, component, or challenge claim until Fox Pick, BSidesNOLA, or another primary archive provides it.

BSides Global event listing, NOLABSides site, BSidesNOLA organizer updates, and Liz Gore attendee account.

hardware and software specification gap · ticket wording and event activity context only · no artifact-level technical release recovered

The phrase VIP Assembled Badge and the event's hardware-hacking activity do not identify an electronic badge, PCB, kit, material, artwork, QR/RFID/NFC function, controller, battery, display, connector, schematic, BOM, firmware, app, challenge linkage, binary, source release, licence, flashing path, or physical credential behavior.

The record remains an explicitly ticket-listed identity artifact rather than inventing electronics, software, CTF integration, or a finished construction from a tier name.

HackNWA official event page, organizer announcement, registration page, and contemporaneous ticket listing.

hardware archive gap · official walkthroughs · needs deeper archive recovery

The walkthroughs document ATmega1284P, FTDI serial, Optiboot, flash dumping and flashing, but do not publish schematic, PCB files, BOM, component placement, enclosure files, source firmware, or manufacturing records.

Hardware and software fields stay limited to the official challenge walkthrough evidence.

CyberThreat Echo Service and A Nice Edit walkthrough PDFs.

hardware archive gap · post-event report and attendee observation · needs badge-team archive

The recovered public trail proves the electronic duck badge, CTF LEDs, and observed RP2040/MicroPython behavior, but does not expose schematics, PCB files, BOM, official firmware source, case files, or production files.

The catalogue records observed hardware and software behavior while avoiding unrecovered component, board-source, and manufacturing claims.

Noroff post-event report, BSides Kristiansand recordings page, and Cryptax technical write-up.

hardware archive gap · source-backed but incomplete · needs schematic or BOM recovery

The recovered sources document the wearable badge, OLED, controls, headers, pinouts, AVR/ISP flashing, firmware behavior, and CTF mode, but this pass did not recover a schematic, BOM, board files, exact MCU package, or production quantity.

The record stays at source-backed hardware surfaces and avoids unsupported component-level claims.

Hackster Packet Hack Badge project and GitHub firmware repository.

hardware archive gap · source-backed but incomplete · needs schematic or PCB archive

The recovered source trail proves an assembled Ruxcon 2017 HHV badge, UART adapter requirement, ESP8266/NodeMCU firmware, and challenge behavior, but this pass did not recover schematic, PCB files, BOM, manufacturing count, or exact board revision.

The record keeps component claims to ESP8266/NodeMCU evidence and avoids unsupported board-layout or production-run detail.

Ruxcon 2017 HHV page, Darkglade writeups, source-release post, and ruxconhhv2017 repository.

hardware archive gap · source-backed but incomplete · needs primary badge archive

The recovered sources document a home-made Arduino badge and running-order display, but not a schematic, BOM, firmware, exact Arduino board, display part, artwork, or production archive.

The catalogue records the verified electronic-badge behavior while avoiding unsupported claims about circuit design, parts, firmware, or challenge features.

BSides Canberra 2016 event page and The Register event report.

hardware archive gap · source-backed but incomplete · needs public badge-team archive

The public source trail documents components, visible board behavior, and challenge surfaces, but this pass did not recover a public schematic, KiCad tree, BOM, firmware repository, Gerbers, production quantity, or official badge-team release.

Hardware and software fields stay limited to the attendee writeup, licensed photos, and public event context.

elmo writeup, AiSP event listing, and current Off-By-One site.

hardware configuration and delivery scope gap · primary maker documentation · configuration and allocation not publicly mapped

The maker documentation targets ESP8266 / ESP32 hardware and shows a cased device, but does not map a final board, parts population, power system, radio configuration, firmware build, production run, recipient list, handoff, or attendance eligibility to WICC units.

The catalogue records the documented electronic CTF platform without inventing a universal configuration, quantity, delivery outcome, or attendee credential role.

Commit-pinned OzmoOzmo SecurityConferenceCTFBadge README and repository contents.

hardware detail caveat · official source with limited technical detail · documented

The official past-editions page proves a hardware badge but does not publish component names, board files, firmware, schematics, or a repository for the 2015 artifact.

The catalogue records the badge's existence and challenge context without inventing electronics.

NorthSec past-editions page.

hardware detail caveat · official article but narrow technical detail · needs public technical archive

HTX's launch article proves a Public Safety Village badge artifact and visible illuminated emergency-vehicle icons, but no reviewed public source publishes a MCU, schematic, firmware, BOM, battery, distribution count, or challenge protocol for this badge.

The record documents the verified village badge artifact without inventing electronics, firmware, production, or distribution details.

HTX launch article, HTX Public Safety Village page, and HTX preview article.

hardware license caveat · GitHub API and repository tree recheck · no visible hardware license

The public hardware repository preserves Eagle design files and badge imagery but GitHub reported no detected license, and no top-level reusable hardware or image license was recovered in this pass.

Hardware files are cited as evidence, but repository images are not copied locally and reuse claims stay limited.

jellyjellyrobot/neander GitHub API and repository tree recheck.

hardware power caveat · source-backed · documented

The production story records that the badge's power path could not reliably support flash writes at full 80 MHz operation, requiring firmware and clocking attention.

Surviving-badge hacking and firmware flashing should respect the documented power and flash-write constraints.

Hackaday production article.

hardware privilege boundary · public badge guide · historical

Moving jumpers from UART1 to UART0 exposed a 115200 baud root-shell path after reconnecting the Omega shield.

For a learning badge this is useful lore rather than a production vulnerability: it shows how physical access and debug interfaces were deliberately part of the challenge surface.

Jump ESP, jump! badge guide.

hardware, firmware, and challenge-implementation gap · official high-level challenge wording · no technical release recovered

The sources use hackable-badge and competition language but publish no physical form, PCB, controller, components, display, power system, connector, radio, sensor, schematic, BOM, Gerber, firmware, source, binary, app, protocol, toolchain, flashing path, challenge rules, scoring model, test plan, safety guidance, or licence.

The record does not turn a planned interactive challenge into an electronic specification, a reproducible workflow, or a safe operating instruction.

CyberThreat official event page and SANS CyberThreat 2026 registration page.

hardware, firmware, and interaction-specification gap · official ticket-tier wording plus source-limited attendee community record · no public technical archive recovered

Official wording confirms an interactive circuit-board PCB badge. A commit-pinned attendee-community README identifies a repository for SecretCon 26 attendees, but it supplies no component identities, circuit or board files, power design, physical details, firmware, application, protocol, challenge rules, source/binary release, license, or accessibility documentation. The higher Extreme-tier wording and community owl-badge name are not specifications.

The catalogue records the organizer ticket description and narrow community terminology without presenting either as a documented electronic architecture, programmed feature set, safety statement, or reusable hardware design.

SecretCon 2026 registration listing and FAQ plus the commit-pinned SecretCon 26 attendee community README.

hardware, firmware, and interaction-specification gap · official ticket-tier wording and limited social corroboration · interactive PCB claim retained; technical archive unrecovered

The official listing calls the Digital / Circuit Badge an interactive circuit-board PCB badge, and an organizer-account repost says unspecified CypherCon badges were programmed, tested, and packaged. No recovered source provides component identities, schematic, BOM, PCB files, power design, physical dimensions, firmware, application, protocol, challenge, source/binary release, license, test criteria, or accessibility documentation, and the repost is not mapped to this tier.

The catalogue preserves the exact ticket and timeline language without presenting the record as a documented electronic architecture, released software project, safety statement, or reproducible hardware build.

CypherCon 2026 registration and FAQ plus the public CypherCon-account timeline mirror.

hardware, power, LED, and UPDI documentation gap · maker component claims · needs engineering documentation and safety testing

The maker names ATtiny1616, potentiometers, LEDs, UPDI, AAA input, and board dimensions, but does not provide LED part/current, controller configuration, input circuit, power path, battery holder/protection, voltage/current limits, pinout, circuit, schematic, BOM, PCB/Gerbers, assembly, test matrix, safety guidance, or compliance evidence.

The record provides a traceable hardware surface without representing it as an electrically complete design, runtime guarantee, programming guarantee, or safety validation.

Masonic33 Tindie listing.

hardware, power, USB, and electrical-safety documentation gap · high-level source descriptions only · feature-level hardware claims published; engineering documentation absent

Sources name brass, no battery, ATSAMD21G1A/4 MB on the linked Coin M0 profile, USB, NeoPixels, touch, and speaker, but do not publish a final schematic, BOM, PCB/Gerbers, final dimensions, brass/PCB construction, MCU package/clock/bootloader, LED count/model/current, resistor values, touch circuitry, audio circuit, USB protection, cable/current requirements, power rails, ESD/short-circuit guidance, test results, user manual, or compliance evidence.

The record retains a traceable hardware surface without presenting the coin as electrically characterized, safe for every cable/host, reproducible, compliance-tested, or suitable for unsupervised modification.

AoSC eChallengeCoin page and CircuitPython Coin M0 profile.

hardware, power, firmware, and electronic-specification gap · official checkout terminology only · LED badge with no technical archive identified

The only reviewed artifact-level technical claim is the official label LED badge. No source identifies its PCB, controller, LEDs, display, power/battery/charging path, USB, radio, connectors, sensors, dimensions, materials, schematic, BOM, firmware, software license, source release, assembly process, safety guidance, final revision, or test evidence.

The entry does not turn an LED-badge product label into a claimed circuit, operating behavior, repair path, certification, or safety assurance.

Puzzled Hackers CTF badge checkout and Team meetup announcement.

hardware, power, host-interface, and safety boundary · commit-pinned README and public KiCad tree · high-level design surface published; final electrical and physical validation unrecovered

The README names an ATtiny1604-SS, LEDs, a button, soldering-challenge positions, a 3.3 V operating statement, and KiCad source files. It does not establish a final production BOM, substitutions, power source, battery or charging design, current budget, protection, thermal or optical performance, SAO header version/pinout, host-voltage/current compatibility, assembly quality, mechanical durability, test result, certification, safety review, or safe outcome for every configuration. The catalogue does not republish programming or soldering procedures.

The entry keeps its useful electronic-design trail visible while avoiding an electrical guarantee, universal SAO compatibility claim, safety endorsement, or do-it-yourself operating instruction.

Commit-pinned 2026 iFixit SAO README and public repository tree.

hardware, software, and challenge-disclosure boundary · official organizer announcements · badge-and-lanyard form and high-level challenge wording public; implementation unreleased

The official sources establish a new badge, lanyard, a named Badge Sponsor, and high-level new-design/new-challenges language, but do not publish a PCB, electronic components, power system, physical dimensions, schematic, BOM, manufacturing archive, firmware, source repository, application, protocol, programming guide, challenge implementation, security review, or support documentation.

The record does not upgrade a reveal or sponsor label into a technical specification, software claim, challenge mechanism, safety assessment, or reproducible badge design.

Telecom Village official site and official organizer-account updates.

hardware, software, and operational-detail gap · historical programme description · named large physical educational artifact; implementation unrecovered

The recovered programme establishes a named large physical ATM attack-surface simulation, but does not publish a board, electronics, readers, card interfaces, controller, display, lights, power system, enclosure, dimensions, weight, internal mechanism, final unit, firmware, application, challenge environment, source archive, operating procedure, safety guidance, or test result. The current 2026 introductory talk does not close those gaps.

The catalogue records the real high-level artifact without publishing operational payment-security instructions or turning programme language into a technical teardown, safety assessment, or reproducible design.

Preserved DEF CON 33 programme copy and Payment Village's official DEF CON 34 programme.

hardware, surface-mount, and connector documentation gap · maker SAO label and high-level surface-mount statement · artifact class and one fabrication change named; engineering details undisclosed

Public sources call the item an SAO and say v2 parts will be surface mounted, but do not identify the specific parts, controller, connector model/pinout, SAO version, power requirements, circuit, schematic, BOM, PCB/Gerbers, mechanical design, assembly/test process, safety guidance, host compatibility, or compliance evidence.

The record preserves the verified artifact classification and v2 fabrication statement without inventing electronics, connector behavior, or electrical safety properties.

u/Truth-Miserable MF Doom SAO v2 Reddit post and DEFCON 34 Badgelife Form response.

hardware-detail caveat · source-backed but incomplete · needs schematic or firmware recovery

The official page proves four buttons, four LEDs, challenge flags, and hardware-hacking acknowledgement, but it does not publish component identifiers, schematic, firmware, PCB files, battery details, or production notes.

The catalogue records only the verified badge behavior and avoids inventing electronics beyond the public BBV Badge 2025 source.

Bug Bounty Village BBV Badge 2025 page.

hardware-detail caveat · source-backed but intentionally narrow · needs schematic or BOM recovery

The public project record proves a simple discrete marquee attendee kit, but this pass did not recover public schematics, BOM, assembly guide, firmware, battery, controller, LED count, or event-game documentation.

The catalogue keeps the record as a source-backed kit badge and avoids inventing electronics beyond the published discrete marquee description.

Hackaday.io BSides Orlando 2018 Badge project.

hardware-detail caveat · official registration source · needs hardware archive recovery

The recovered official sources prove that CactusCon 8 offered an electronic badge option and issued printed or electronic badges by ticket type, but they do not describe electronics, manufacturer, firmware, challenge behavior, production count, final appearance, or distribution beyond ticket entitlement.

The catalogue records the badge as a real registration-tier artifact without upgrading it into a specific PCB platform or game badge.

CactusCon registration update and Friday/Saturday registration pages.

hardware-detail caveat · source-backed but intentionally narrow · needs public technical archive

The recovered official sources document the electronic badge, MediaTek chipset, Wi-Fi, Bluetooth LE, joystick/game-controller input, infrared, LED display, Hackermon, Snake, and premium-ticket distribution, but do not recover a schematic, BOM, firmware repository, production count, or exact part numbers.

The dossier records the verified platform and challenge claims while avoiding unsupported component-level or firmware claims.

HITCON CMT 2017 events and ticketing pages.

hardware-detail caveat · source-backed but intentionally narrow · needs public technical archive

The recovered sources document badge mini-game behavior, card readers, NFC-reader inspection, and welcome-kit inclusion, but do not identify an exact chip, NFC tag type, memory layout, schematic, or firmware repository.

The dossier records the verified interaction model while avoiding unsupported component-level or security-primitive claims.

HITCON CMT 2023 event, location, and ticketing pages.

hardware-detail caveat · source-backed but incomplete · needs artifact documentation

The public source shows a green PCB-form speaker credential but does not disclose whether it had powered circuitry, firmware, components, schematic, NFC, RF, display, or challenge behavior.

The catalogue records only the proved speaker-badge artifact and visible PCB-form context until direct technical documentation appears.

MOS & BOO OzSecCon 2018 conference wrap-up.

hardware-detail caveat · primary source-backed but incomplete · needs badge-team release or post-event writeup

The public ticketing source proves electronic badge inclusion, but this pass did not recover a 2026 schematic, BOM, PCB file, firmware repository, final component list, production note, or shipped-badge teardown.

The catalogue does not infer microcontrollers, displays, batteries, radios, add-on connectors, games, or firmware behavior until those details are published.

BSides Canberra 2026 Humanitix ticketing page and official CFP.

hardware-detail caveat · official source but no technical badge archive · needs primary badge archive

The recovered official source does not identify the badge material, electronics, firmware, serial behavior, puzzle files, or whether the badge challenge used the attendee tag itself.

The catalogue keeps the record to identity-badge and challenge evidence until a direct technical source appears.

CHCon 2018 event page.

hardware-detail caveat · official source but no technical badge archive · needs primary badge archive

The recovered official sources do not document badge electronics, firmware, microcontroller, serial interface, display, radio, NFC, QR behavior, or a badge-specific challenge repository.

The catalogue keeps component-level fields empty until direct badge documentation is recovered.

CHCon 2019 about and sponsorship pages.

hardware-detail caveat · source-backed but incomplete · needs public schematic or participant notes

The official source documents supplied electrical components, tools, soldering, IC programming, and Arduino IDE use, but not the exact PCB, chip, battery, display, schematic, or firmware.

The record avoids inventing component-level details until a workshop handout, schematic, or first-hand writeup is recovered.

Kiwicon 2038 Intro to Badge Hacking page.

hardware-detail caveat · source-backed but incomplete · needs original badge-team archive

The current public source describes visible badge components and challenge behavior, but does not recover schematics, board files, bill of materials, firmware for the ESP badge, or a full original badge-team build writeup.

The record preserves the source-backed two-part badge without inventing component-level details that are not public in the recovered sources.

SensePost writeup and released RFCat challenge gist.

hardware-detail gap · source-backed but intentionally narrow · needs public schematic or firmware archive

The official source proves an electronic Infinity Glove badge and hardware CTF framing, but this pass did not recover component lists, schematics, board files, firmware, or challenge-source archives.

The record preserves badge existence, distribution, and CTF framing while avoiding unsupported component-level claims.

BSidesTLV 2025 electronic badge page.

hardware-detail gap · source-backed but intentionally narrow · needs public schematic or firmware archive

The official source proves a planned electronic badge and hardware CTF framing, but this pass did not recover component lists, schematics, board files, firmware, production notes, or challenge-source archives.

The record preserves badge existence and planned CTF framing while avoiding unsupported component-level claims.

BSidesTLV 2026 Hardware Village page.

hardware-form-factor gap · firmware-only repository · needs hardware archive recovery

The repository documents the CH585, NFC, SK6812 LEDs, buttons, and audio in firmware but contains no PCB gerbers, KiCad or schematic files, board layout, power source, or physical form factor.

The catalogue records the verified firmware and challenge surface without inventing physical-form-factor, power, or hardware-design details.

iot-pwn/bsidesdsm26 repository file tree.

hardware-source boundary · official challenge page plus attendee teardown · needs deeper archive recovery

The official WWHF page proves an electronic badge and badge CTF but does not publish a component list, schematic, BOM, firmware release, PCB files, or challenge-source archive; component-level details currently come from a post-event attendee teardown.

The catalogue records ESP32-S3, OLED, charger, LED, BLE, serial, and firmware-analysis details as teardown-backed rather than official board documentation.

WWHF e-badge page and AlrikRr NetRunSecurity badge-hacking writeup.

hardware-source caveat · source-backed but incomplete · needs badge-team archive

Public sources prove BSides Tampa 2018 event context, electronic badge assembly activity, and a visible badge/lanyard artifact, but this pass did not recover schematic, BOM, firmware, assembly instructions, controller part, battery details, or challenge-source material.

The record captures the source-backed artifact without inventing electronics or software behavior beyond the public evidence.

St. Petersburg College attendee report, Wikimedia Commons photo metadata, and badge.gallery inclusion policy.

hardware-source caveat · official source plus matching public archive · technical archive recovered; needs authoritative release mapping

The official page documents the custom ESP32-S3-WROOM / LoRa badge and its visible features. A commit-pinned archive titled 2025 Utahtastic BSides Badge mirrors that description and includes KiCad PCB/schematic files plus a Meshtastic-derived source tree, but BSidesSLC does not directly link it or name its author.

The catalogue can now record the public technical archive while withholding an audited final BOM, manufacturing package, event firmware image/configuration, app settings, challenge archive, production count, and proof that every delivered unit matched the public tree.

BSidesSLC official site and distinctm1nd/2025_utahtastic_bsides_badge at b0eb50f42125df564aef9f3beee962fa5024decf.

hardware-source caveat · official post-event source plus first-hand observation · official design source documented; event-unit deployment scope remains open

NorthSec's separate Apache-2.0 nsec/badge-2026 repository now publishes KiCad, BOM/CPL/Gerbers, a pin map, and C++/PlatformIO source for the ESP32-S3/NFC/e-paper/NeoPixel design. It does not identify a source commit, binary, display state, component revision, or assembly/flash configuration for each distributed badge. Marx314's write-up remains useful first-hand context, including its observed 16 MB module report, but it is not an official production ledger.

The catalogue can document the official technical surface and CTF integration without presenting the published design snapshot or any third-party observation as a universal recipient-unit configuration.

nsec/badge-2026 commit 4dab9e6c4c0b8efc9a643ee646a49550453ea22c hardware tree, board_pins.h, platformio.ini, and LICENSE; NorthSec 2026 registration/competition/villages/schedule pages; NSEC26 Badge Shenanigans.

hardware-source caveat · official source but technically shallow · needs primary badge archive

The official sources prove an electronic badge was introduced for the 2019 CTF, but this pass did not recover a schematic, BOM, PCB repository, firmware, controller details, display, radio, battery, badge-team writeup, or production count.

The record preserves the electronic-badge milestone while avoiding invented component or firmware claims.

Hackfest history, Hackfest 2019 schedule, and Hackfest CTF 2019 page.

hardware-source depth caveat · firmware/readme source but no CAD archive · needs hardware archive recovery

The recovered 2026 trail documents controller, display, radio, LEDs, buzzer, buttons, firmware, games, RF behavior, and ticket inclusion, but this pass did not recover schematic, PCB files, BOM, enclosure files, exact shipped quantity, or hardware errata.

The record keeps hardware claims to the official site and firmware repository without inventing a final circuit, board revision, manufacturing run, or image provenance.

HackConRD 2026 site, eBadge page, and Badge_HackConRD_2026 README.

hardware-source scope caveat · source-backed but incomplete · needs deeper post-event artifact inventory

The public repository preserves README, KiCad, BOM, schematic, and firmware material, but this pass does not mirror every CTF challenge artifact, post-event solve, manufactured-board photograph, or field report.

The catalogue records verified hardware and firmware surfaces while leaving deeper NorthSec 2025 artifact archaeology for later work.

NorthSec 2025 badge repository, README, hardware tree, and schematic PDF.

historical electronic-badge reference boundary · official organizer wording · prior-year promotion retained separately from 2026 artifact evidence

The sponsor call says people were still talking about the previous year's electronic badges before describing what is new in 2026. It does not explicitly say that the planned 2026 badge is electronic or reuses a previous design, and no technical 2026 badge archive was recovered.

The entry does not turn a historical promotional sentence into a 2026 electronics, firmware, challenge, compatibility, or delivery claim.

Call For Sponsors: BSides Peoria 2026 official organizer post.

identity-artifact boundary · official source · documented

The terms prove visible badge access control for the conference floor, but do not document electronics, hardware specifications, firmware, challenges, or badge design details.

The catalogue records x33fcon 2026 as an identity-artifact badge and avoids any electronic-badge claim.

x33fcon Terms & Conditions Conference Badges section.

identity-artifact boundary · primary source · post-event verification complete

The 2026 Adelaide record is now treated as an identity/lanyard surface trail from CFP, sponsorship-page, Humanitix, and sponsor-brief sources, not a confirmed distributed badge implementation.

The catalogue tracks the attendee badge/lanyard surface while keeping hardware, firmware, artwork, challenge behavior, and distribution claims open until post-event technical recovery appears.

BSides Adelaide 2026 CFP, sponsorship page, Humanitix ticketing, and sponsor brief.

identity-artifact boundary · official source but limited · documented

The official source proves badge distribution at check-in but does not prove an electronic badge, hardware challenge, badge firmware, schematic, PCB, lanyard design, or badge variants.

The catalogue records the real identity artifact while avoiding unsupported electronic-badge claims.

BSides Reunion volunteer missions and official event page.

identity-artifact classification · official source · documented

The official WAHCKon ticket page proves a ticket-included badge but does not document an electronic or programmable badge.

The record is modeled as an identity artifact and avoids unsupported PCB, firmware, RF, display, NFC, or challenge claims.

WAHCKon 2013 ticket page.

identity-artifact classification · official source · documented

The recovered BSides Melbourne 2020 sources prove conference registration and lanyards, but do not prove an electronic badge or a separate printed badge artifact.

The entry is intentionally modeled as a lanyard and registration identity artifact so the Melbourne lineage expands without inventing PCB, firmware, RF, display, CTF, or programmable behavior.

BSides Melbourne 2020 schedule and sponsor page.

identity-artifact classification · official source · documented

The recovered BSides Melbourne source trail proves a badge and lanyard credential with consent and interaction-protocol signalling, but does not prove an electronic badge.

The entry is intentionally modeled as a conference identity artifact so the Melbourne lineage expands without inventing PCB, firmware, RF, display, CTF, or programmable behavior.

BSides Melbourne 2023 attendee communications and official archive.

identity-artifact classification · official source · documented

The recovered 2024 prospectus proves a badge/lanyard identity artifact with pronoun, photo-permission, and interaction-preference signalling, but does not prove an electronic badge.

The entry is intentionally modeled as a social-signal identity artifact so the Melbourne lineage expands without inventing PCB, firmware, RF, display, CTF, or programmable behavior.

BSides Melbourne 2024 sponsorship prospectus and sponsors page.

identity-artifact classification · official source · documented

The recovered CrikeyCon 2017 sources prove attendee badge pickup and special speaker badges but do not prove an electronic conference badge.

The entry is intentionally modeled as a conference identity and speaker credential so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

CrikeyCon 2017 archive and CFP pages.

identity-artifact classification · official source · documented

The recovered CrikeyCon V source proves attendee badge pickup and special speaker badges but does not prove an electronic conference badge.

The entry is intentionally modeled as a conference identity and speaker credential so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

CrikeyCon V official archive page.

identity-artifact classification · official source · documented

The recovered CrikeyCon VI source proves attendee badge pickup, staff badges, Friendly Bear name badges, and special speaker badges but does not prove an electronic conference badge.

The entry is intentionally modeled as conference identity, support, and speaker credentials so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

CrikeyCon VI official archive page.

identity-artifact classification · official source · documented

The recovered CrikeyCon VII sources prove badge pickup and a CrikeyCon Connect badge marker but do not prove an electronic conference badge.

The entry is intentionally modeled as a conference identity and support-signal artifact so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

CrikeyCon VII archive, schedule, and events pages.

identity-artifact classification · official source · documented

The recovered CrikeyCon IX sources prove badge pickup and custom accessibility badge/pin artifacts but do not prove an electronic conference badge.

The entry is intentionally modeled as a conference identity and accessibility artifact so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

CrikeyCon IX schedule, archive page, and Humanitix ticketing.

identity-artifact classification · official source · documented

The recovered CrikeyCon X sources prove a badge pickup workflow and conference credential but do not prove an electronic badge.

The entry is intentionally modeled as a conference identity artifact so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, or display claims.

CrikeyCon X schedule, archive page, and Humanitix ticketing.

identity-artifact classification · official source · documented

The official CHCon 2018 source proves identification tags/badges and badge challenges but does not prove that the attendee credential was an electronic PCB badge.

The record is modeled as an identity and challenge artifact so the CHCon lineage expands without unsupported microcontroller, firmware, display, radio, NFC, or CTF-on-badge claims.

CHCon 2018 event and sponsorship page.

identity-artifact classification · official source · documented

The CHCon 2019 sources prove identification tags/badges and nearby electronic CTF challenges, but not an electronic attendee badge.

The entry separates identity-badge materials from CTF electronics so the record does not invent a PCB credential.

CHCon 2019 about and sponsorship pages.

identity-artifact classification · official source · documented

The official Kiwicon 7 source proves event badge assembly and pickup context, but not an electronic attendee badge.

The entry is modeled as a Kiwicon identity artifact so New Zealand coverage expands without inventing PCB, firmware, display, radio, NFC, or CTF behavior.

Kiwicon 7 home/news and about pages.

identity-artifact classification · official source · documented

The official Kiwicon 9 source proves a visible venue badge credential, but not an electronic attendee badge.

The entry is modeled as a Kiwicon identity artifact so New Zealand coverage expands without inventing PCB, firmware, display, radio, NFC, or CTF behavior.

Kiwicon 9 home/news and HQ pages.

identity-artifact classification · official source · documented

The official Kiwicon 2038 source trail proves a badge and lanyard credential but not a public electronic attendee badge.

The entry is intentionally modeled as a conference identity artifact so New Zealand coverage expands without inventing hardware, firmware, RF, CTF, or PCB claims.

Kiwicon 2038AD home/news page and FAQ.

identity-artifact classification · official source · documented

The official Kawaiicon badge page proves a physical conference badge made from seed paper but does not support electronic hardware, firmware, display, RF, or CTF claims for the credential.

The record keeps the Kawaiicon badge as a material identity artifact rather than upgrading it into a PCB badge without evidence.

Kawaiicon badges page, FAQ, and about page.

identity-artifact classification · official source · documented

The official Purplecon diary proves a lanyard badge, but not an electronic attendee badge.

The entry is modeled as a glow-in-the-dark identity artifact and avoids unsupported PCB, firmware, display, radio, NFC, or CTF claims.

Purplecon 2018 diary and home page.

identity-artifact classification · official source but no technical archive · documented

The recovered public trail proves a conference badge and lanyard sponsor context plus visible volunteer-badge requirement, but it does not prove an electronic badge, PCB, firmware, badge challenge, component list, schematic, production count, or final artwork.

The catalogue models the 2018 item as a conference identity/admission artifact and avoids upgrading sponsor and volunteer evidence into unsupported electronics claims.

Nullcon Goa 2018 sponsors page, volunteer page, schedule, venue page, and archive.

identity-artifact classification · source-backed but narrow · documented

The CFP proves a speaker VIP badge benefit, but it does not prove a public attendee badge, electronic badge, PCB, firmware, challenge behavior, badge design, or production quantity.

The catalogue models the item as a narrow speaker identity artifact and avoids unsupported hardware claims.

NotPinkCon PaperCall CFP.

identity-artifact classification · primary writeups · documented

The sources prove a custom CR80 Hacker ID Card / reusable name-tag artifact and on-site card-printing workflow, but not a PCB, firmware project, badge challenge, or electronic conference badge.

The entry is modeled as an identity-card badge artifact and avoids unsupported electronics claims.

Security-Bits Hacker ID Card page, H2HC custom-card production post, and Need a New ID? follow-up.

identity-artifact classification · source-backed but incomplete · documented

The recovered sources prove a VIP special badge but do not prove electronic hardware, components, firmware, badge challenges, or attendee-wide issue.

The badge is classified conservatively as a VIP identity/swag artifact, not as an electronic conference badge.

8.8 Reloaded announcement coverage.

image-rights boundary · local project policy · needs licensed original replacement

No local Hackfest 2019 badge image is published because this pass did not pair any specific badge photo or official raster with reusable image rights, attribution, source URL, and processing notes.

The entry remains image-free rather than copying event media, Flickr photos, screenshots, social images, or generated placeholder art.

badge.gallery image policy, Hackfest history photo links, Hackfest 2019 schedule, and Hackfest CTF source trail.

in-person game, wireless, player-data, and safety boundary · team-announced proximity and event-interaction claims · planned behavior only

The announcement describes transmission, IR/NFC/BLE, crew zones, fixed Cure Stations, hidden props, and an SAO effect in range, but does not publish interaction rules, consent model, accessibility plan, physical-safety precautions, radio/privacy/security design, data collection/retention, venue coordination, staff identification, moderation, incident response, participant eligibility, or post-event result.

Readers can see the intended collaborative game context without assuming that proximity effects, wireless behavior, data use, safety, or onsite logistics were implemented, authorized, or suitable for every participant.

Zombie Badge Info Dump.

incomplete software, IR, data, and safety boundary · commit-pinned source header and repository review · handshake, infrared, and logging explicitly not wired up; release and review state unrecovered

The source header says handshake, infrared, and logging logic is not wired up yet, and the hardware-test commit says over-air infrared needs physical LED/receiver wiring. The public repository does not establish final behavior, protocols, stored or transmitted data, privacy practice, authorization model, security review, safe electrical or infrared use, tagged binary, reproducible build, recovery package, integrity process, vulnerability handling, support, or warranty. This record does not reproduce controls, pins, protocols, or modification steps.

The listed source remains useful as a development snapshot while users are warned not to infer functional infrared/game behavior, safe operation, data handling, or a supported release.

Agency SAO Badge V2 commit-pinned source snapshot and 2026-07-21 hardware-test commit.

independent DEF CON association and MF DOOM affiliation boundary · public maker self-submission and fan-themed product name · independent planned BadgeLife artifact; credential and rights status undocumented

The roster and maker thread associate the planned item with DEF CON 34, but neither says DEF CON issued it, included it with registration, grants entry, replaces a Human badge, or has organizer endorsement. Neither source establishes authorization, affiliation, endorsement, or artwork rights from MF DOOM's estate, label, collaborators, or other rights holders.

The catalogue records a real independent maker-announced SAO while avoiding an official credential claim or an inference of artistic/trademark authorization.

DEFCON 34 Badgelife Form response and u/Truth-Miserable MF Doom SAO v2 Reddit post.

independent DEF CON association and credential boundary · maker listing, schedule, and vendor-list sources · independent electronic puzzle badge with scheduled creator activity

The maker calls the badge for DEF CON attendees, the public schedule lists its BadgeLife drop, and a vendor list places it in a DEF CON 33 product context, but no source says DEF CON issued it, included it with registration, made it a Human-badge replacement, granted access, or endorsed it as an official credential.

The catalogue classifies Masonic33 as an independent BadgeLife artifact associated with DEF CON 33, not as an organizer-issued conference credential, admission item, or universal attendee handout.

Masonic33 product listing, recovered DEF CON 33 schedule, and Hacker Couture product list.

independent DEF CON association and credential boundary · maker pickup wording and current-event index · independent planned eChallengeCoin associated with DEF CON 34

AoSC offers in-person pickup at DEF CON and DEF CON.outel.org lists the eChallengeCoin in a current planning roundup, but no reviewed source says DEF CON issued it, includes it with registration, grants admission, replaces a Human badge, has organizer endorsement, is required for a village, or has verified venue authorization.

The catalogue connects this independent maker artifact to its cited DEF CON 34 discovery/pickup context without presenting it as official conference hardware, an access item, a universal attendee benefit, or a completed organizer distribution.

AoSC eChallengeCoin page, AoSC form, and DEF CON 34 Planning Highlights.

independent DEF CON association and credential boundary · maker repository wording · independent pre-event challenge-tool association documented

NilbinSec calls this an SAO for the DC34 conference badge and specifically targets the DEF CON 34 main badge, but no reviewed source says DEF CON issued, sold, endorsed, requested, or officially authorized the tool; includes it with registration; grants admission; replaces a Human badge; or guarantees a sanctioned challenge path.

The catalogue keeps the target relationship searchable while classifying this as independent BadgeLife hardware rather than official conference hardware, an access credential, a universal attendee item, or evidence of organizer endorsement.

NilbinSec repository and README.

independent DEF CON association, RM-Cyber relationship, allocation, and credential boundary · public repository description and Player Guide · pre-event source project documented; organization relationship and handoff unverified

The repository description calls The Shattered Shard a DEF CON 34 RM-Cyber challenge badge, while its Player Guide addresses an assigned badge. No reviewed DEF CON, RM-Cyber, venue, or organizer source confirms the publisher's relationship; organizer authorization; price; sale/giveaway; physical run; recipient criteria; assigned-badge allocation; pickup; shipping; completed handoff; admission or access role; support; or post-event result.

The catalogue preserves the source's current event association and distinct project name without presenting it as an official DEF CON badge, an RM-Cyber-issued artifact, a guaranteed attendee benefit, an access credential, a completed release, or proof that any participant received one.

BigDawgDave/The-Shattered-Shard repository description and Player Guide, reviewed 2026-08-05.

independent meetup and DEF CON credential boundary · first-hand Team announcement and official checkout · independent community meetup artifact

The Team says its meetup is free, badges are optional, and an actual DEF CON badge is not needed for the first Wednesday gathering. The checkout labels the item for DEF CON 34 and offers a possible arranged DEF CON handoff, but neither source makes Puzzled Hackers a DEF CON organizer, says the LED badge is included with registration, grants conference access, replaces a Human badge, or proves conference/venue authorization.

The catalogue models a real Puzzled Hackers community badge associated with DEF CON 34 while keeping it distinct from official admission, organizer issuance, and verified event access.

Puzzled Hackers CTF badge checkout and Team meetup announcement.

large archive scope caveat · source-backed but compact · documented

The public 2019 repository includes a broad hardware, firmware, games, challenge, and utility tree; this catalogue entry summarizes the main surfaces rather than indexing every file.

The record is accurate at the badge level and leaves per-game or per-challenge archaeology for later expansion.

NorthSec 2019 badge repository tag.

license gap · repository inspection · no license file

The punk-security repository carries no LICENSE file, no license header in firmware.ino, and no license badge in the GitHub sidebar, so the firmware is treated as all-rights-reserved rather than redistributable.

The catalogue records the verified hardware and challenge surface without claiming redistribution rights over the firmware or any derivative.

punk-security/bsides-leeds-2026-badge repository file tree and firmware.ino.

limited availability · archived official challenge page · historical

The official challenge described a limited collector badge given out after solving an easy challenge, then used as the entry point to the harder Black Badge challenge.

This was not necessarily a universal attendee badge; the page models it as a collector/challenge object rather than a default registration badge.

Archived NDH 2014 badge challenge page.

lineage-behavior caveat · retrospective source only · documented as lineage context

Later sponsor-pack material says past BSides Perth electronic badges displayed sponsor messages, schedules, and CTF challenges, but the recovered source does not identify which exact year carried each feature.

The 2018 entry cites this only as broader Perth lineage context and does not treat it as direct 2018 behavior proof.

BSides Perth 2021 sponsor-pack transcript.

live challenge, scoreboard, and data-handling scope · official storefront statement · public concept only

The storefront announces a live hacking challenge, stages, and a scoreboard but provides no public rules, technical guide, challenge catalog, scoring integrity model, accessibility accommodations, account/privacy notice, retention policy, service availability, moderation, prize terms, or post-event result/archive.

The record keeps the organizer-published challenge framing discoverable without assuring a particular technical experience, safe data practice, fair scoring, accessibility, availability, or a final public result.

FloridaMan 2026 official storefront.

main-badge evidence boundary · source-limited audit · not promoted

The main official DEF CON 12 badge remains source-limited in this pass; reviewed official event and media-archive sources support event context but do not yet provide enough artifact-level evidence for a separate official-badge record.

The catalogue avoids inventing material, role, visual, puzzle, or electronic claims for the official DEF CON 12 badge until stronger public sources are recovered.

DEF CON 12 official event page, media archive, InfoconDB event metadata, and forum-badge thread.

maker-to-event association boundary · maker archive plus independent official event sources · maker-declared association; organizer linkage unverified

OzmoOzmo's public README explicitly titles the project Women's International Cybersecurity Challenge Badge 2026 and links WICC, while WICC's official site and Cyber Ireland's recap confirm the event. Neither organizer source names this exact repository, maker, or device as an official WICC artifact.

The record is an event-linked maker badge and must not be read as a WICC organizer-issued credential, sponsor deliverable, official hardware programme, or attendee-wide handout.

WICC official event page, Cyber Ireland post-event recap, and commit-pinned OzmoOzmo SecurityConferenceCTFBadge README.

maker-to-event provenance, final configuration, and source-license boundary · official generic village evidence plus maker documentation · individual artifact documented; official identity and reuse license absent

Official pages establish a generic soldering badge and hidden challenge at the Hardware Hacking Village. Rahul Thareja's archive calls its design the Seasides 2026 Roulette Badge and provides technical source material, but the official event publishers do not independently name that board, authorize the claim, identify its final revision, or confirm it was the only or universal village badge. The repository's root exposes no license, so source code, design files, art, and photos are not treated as reusable.

The catalogue can identify a real maker-documented hardware artifact without representing it as an organizer-issued credential, a fully verified all-attendee unit, a specific final manufacturing configuration, or an open/reusable media release.

HW101 Hardware Hacking Village page and Rahul Thareja's commit-pinned Roulette Badge README/source archive.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSidesLisbon 2025 badge image is published because the recovered official pages, sponsor logos, ticketing graphics, and event media do not provide a specific badge photo or official raster with reusable license or explicit permission, attribution, source URL, and processing provenance.

The Portugal record remains source-backed and image-free rather than copying sponsor logos, event-page media, ticketing screenshots, or generated badge art.

badge.gallery image policy, BSidesLisbon 2025 about page, sponsors page, CTF page, and Eventbrite listing.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Roanoke 2026 badge image is published because the official event site, organizer-operated ticketing page, and ShenLabs challenge page do not pair a specific badge image with source URL, reusable license or explicit permission basis, attribution, and processing notes.

The United States record remains source-backed and image-free rather than copying event media, ticket graphics, screenshots, social-media photos, placeholders, or generated approximations.

badge.gallery image policy and reviewed BSides Roanoke, Zeffy, and ShenLabs sources.

missing rights-cleared image · local project policy · needs licensed original replacement

No Car Hacking Village DEF CON 34 badge image is published because the official event site, official announcements, and public repository do not pair a specific badge image with source URL, reusable license or explicit permission basis, attribution, and processing notes.

The United States record remains source-backed and image-free rather than copying event-site artwork, LinkedIn images, repository previews, screenshots, placeholders, or generated approximations.

badge.gallery image policy and reviewed Car Hacking Village sources.

missing rights-cleared image · public-roster and official-event media review · needs selected, attributable, cleared original

The reviewed public roster and Aerospace Village event page establish the planned SR-71 listing and event context but do not pair a selected factual badge image with a reusable license or explicit permission basis, attribution, source URL, and processing provenance.

SR-71 remains image-free rather than copying roster media, event graphics, social posts, screenshots, stock imagery, or generated approximations.

Public DEF CON 34 BadgeLife roster, Aerospace Village DEF CON 34 event page, and badge.gallery image policy.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No Wordweaving Badge image is published because BigTaro's project page, Uberflux listing, maker directory, screenshots, and product imagery do not pair one selected factual badge image with a reusable license or explicit permission basis, attribution, source URL, and processing notes.

The record remains source-backed and image-free rather than copying maker renders/photos, game screenshots, marketplace images, social-media media, placeholders, or generated approximations.

badge.gallery image policy and reviewed BigTaro / Uberflux sources.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No Puzzled Hackers LED Badge image is published because the official checkout page and Team announcement do not pair a selected factual badge image with a reusable license or explicit permission basis, attribution, source URL, and processing notes.

The record remains source-backed and image-free rather than copying the checkout photo, Reddit media, screenshots, social posts, thumbnails, placeholders, or generated approximations.

badge.gallery image policy and reviewed Puzzled Hackers sources.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No Masonic33 Indie Puzzle Badge image is published because the reviewed maker listing, maker profile, schedule, and vendor-list sources do not pair a selected factual artifact image with a reusable license or explicit permission basis, attribution, source URL, and processing notes.

The entry remains source-backed and image-free rather than copying storefront, schedule, vendor-PDF, social-media, screenshot, placeholder, or generated imagery.

badge.gallery image policy and reviewed Hak4Kidz and Hacker Couture sources.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No MF Doom SAO v2 image is published because the reviewed Reddit post, preview image, comments, and public Badgelife roster do not pair a selected factual artifact image with a reusable license or explicit permission basis, attribution, source URL, and processing notes.

The planned record remains source-backed and image-free rather than copying Reddit previews, roster-linked media, screenshots, placeholders, or generated imagery.

badge.gallery image policy and reviewed Reddit and public Badgelife sources.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No 2026 eChallengeCoin image is published because the AoSC project/form pages and CircuitPython profile do not pair a selected factual artifact image with a reusable license or explicit permission basis, attribution, source URL, and processing notes.

The record remains source-backed and image-free rather than copying project photos, CircuitPython board artwork, embedded video, form images, screenshots, social media, placeholders, or generated approximations.

badge.gallery image policy and reviewed AoSC and CircuitPython sources.

missing rights-cleared image · local project policy · needs licensed original replacement

No h-c0n 2026 CTF BADge image is published because the official blog media, Hackplayers recap media, and repository photos have not been paired with complete reusable image rights, attribution, source URL, and processing provenance for catalogue publication.

The Spanish h-c0n record remains source-backed and image-free rather than copying blog images, repository photos, prize photos, screenshots, logos, or generated badge art.

badge.gallery image policy, h-c0n CTF BADge post, Hackplayers post-event write-up, and therealdreg/hcon2026hwctf repository.

missing rights-cleared image · local project policy · needs licensed original replacement

The hardware repository and writeups include real badge imagery, but no image is promoted because this pass did not recover a complete reusable image license, attribution basis, and processing provenance for catalogue publication.

The Singapore record remains source-backed and image-free rather than copying repository photos, sponsor artwork, or blog images without complete image rights.

badge.gallery image policy, irq5.io writeups, and jellyjellyrobot/neander repository.

missing rights-cleared image · local project policy plus repository license check · needs licensed original replacement

No GreyBadge image is published because the repository artwork, README/media, and schematic-embedded images have not been paired with an explicit reusable image license, attribution basis, and processing provenance for badge.gallery publication.

The Singapore record remains source-backed and image-free rather than copying repository artwork, social media, slides, screenshots, or generated badge art.

badge.gallery image policy, NUSGreyhats/greybadge25 repository, and 2026-05-21 GitHub API license recheck.

missing rights-cleared image · local project policy · needs licensed original replacement

No local DEF CON 28 cassette-badge photo has been added because article and writeup images have not been paired with a complete reuse basis, attribution string, and processing record for this catalogue.

The entry remains image-free rather than copying Hackaday or personal writeup photography without provenance.

badge.gallery image policy, Hackaday article images, and independent challenge-writeup images.

missing rights-cleared image · local project policy · needs licensed original replacement

No local DEF CON 30 musical-badge photo has been added because article, forum, GitHub, and writeup images have not been paired with a complete reuse basis, attribution string, and processing record for this catalogue.

The entry remains image-free rather than copying attendee, press, forum, or GitHub-hosted challenge photography without provenance.

badge.gallery image policy, DEF CON forum images, FaultPoint images, Red Balloon Security images, and challenge-writeup assets.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Tampa 2026 badge, lanyard, or Uber Badge image is published because official site images and event media have not been paired with explicit reusable image rights, attribution, source URL, and processing provenance.

The entry remains image-free rather than using event-page graphics, screenshots, social-media photos, generated imagery, or placeholders.

badge.gallery image policy and reviewed BSides Tampa 2026 official pages.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSidesSF 2024 Hardware Challenge Village badge image is published because no source paired the badge media with reusable image rights, attribution, and processing provenance.

The record remains source-backed and image-free rather than copying event-page graphics, sponsor avatars, social photos, or screenshots.

badge.gallery image policy and BSidesSF 2024 Sched archive.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSidesSF 2025 Hardware Challenge Village badge image is published because no public source recovered in this pass provided complete reusable image rights, attribution, source URL, and processing notes.

The record remains image-free rather than publishing uncleared or synthetic visuals.

badge.gallery image policy and BSidesSF 2025 Sched archive.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Nashville 2026 challenge-coin image is published because the official event page, organizer updates, and sponsorship material do not pair a specific artifact image with a reusable license or explicit permission basis, attribution, source URL, and processing record.

The Tennessee record remains source-backed and image-free rather than copying event graphics, organizer-feed media, attendee photos, screenshots, storefront imagery, or generated approximations.

badge.gallery image policy and BSides Nashville 2026 official sources.

missing rights-cleared image · local project policy · needs licensed original replacement

No NaClCON 2026 badge image is published because the official event pages, ticketing, organizer announcement, game-host post, and attendee report do not pair a specific factual badge image with a reusable licence or explicit permission basis, attribution, source URL, and processing record.

The North Carolina dossier remains source-backed and image-free rather than copying official page graphics, social-media images, attendee photos, screenshots, event branding, or generated approximations.

badge.gallery image policy and the NaClCON 2026 source set.

missing rights-cleared image · local project policy · open

No Flux Decoder image is published because the repository has no top-level license and the live SEC site is all-rights-reserved; board-cache images and page artwork are not copied without complete reuse provenance.

The record remains source-backed and image-free rather than publishing generated, placeholder, screenshot, repository-cache, or uncleared page imagery.

badge.gallery image policy, Social Engineering Community site footer, and FluxDecoder repository license probe.

missing rights-cleared image · local project policy · needs licensed original replacement

No local HITBSecConf2024 Bangkok SaikoCTF badge image has been added because the official sources have not been paired with reusable image rights, attribution, and processing notes for publication.

The entry remains source-backed and image-free rather than copying PDF imagery, event imagery, screenshots, social-media photos, or generated placeholder art.

badge.gallery image policy, HITB Bangkok SaikoCTF page, and HITB recruitment statement.

missing rights-cleared image · local project policy · needs licensed original replacement

No local BSides Adelaide 2025 badge image is published because public project photos and attendee-writeup images have not been cleared with exact reuse rights, attribution, and processing notes.

The entry remains text-and-source only until a licensed original photo or upstream raster render is selected and documented.

badge.gallery image policy, Hackerware Wombat-2 page, Hackster writeup, and semaja2 attendee writeup.

missing rights-cleared image · local project policy · needs licensed original replacement

No CHCon 2018 badge or challenge image is published because no reusable original photo with source URL, license, attribution, and processing notes has been recovered.

The record remains source-backed and image-free rather than copying event imagery, sponsor logos, social photos, or generated badge art.

badge.gallery image policy and CHCon 2018 source trail.

missing rights-cleared image · local project policy · needs licensed original replacement

No Kiwicon 2038 training badge image is published because no reusable original photo with complete source URL, license, attribution, and processing notes has been recovered.

The training-badge record remains source-backed and image-free rather than copying event imagery or using generated art.

badge.gallery image policy and Kiwicon training page.

missing rights-cleared image · local project policy · needs licensed original replacement

No Kākācon 2021 sticker image is published because the recovered page images have not been paired with explicit reuse rights, attribution, and processing notes.

The record remains source-backed and image-free rather than copying blog or art-page images without complete provenance.

badge.gallery image policy, Kākācon art page, and 2021 walkthrough.

missing rights-cleared image · local project policy · needs licensed original replacement

No Kākācon 2022 sticker image is published because the recovered page images have not been paired with explicit reuse rights, attribution, and processing notes.

The record remains source-backed and image-free rather than copying blog or art-page images without complete provenance.

badge.gallery image policy, Kākācon art page, and 2022 walkthrough.

missing rights-cleared image · local project policy · needs licensed original replacement

No local SINCON 2023 badge photo has been added because the recovered Hackster article images have not been paired with explicit image reuse rights, attribution, and processing notes for catalogue publication.

The Singapore entry remains source-backed and image-free rather than copying project photos without a complete image provenance record.

badge.gallery image policy and Hackster.io badge writeup.

missing rights-cleared image · local project policy · needs licensed original replacement

No local H2HC 2023 Game Boy badge image has been added because the public writeup images are not paired with explicit reusable image rights, attribution, and processing provenance.

The record stays source-backed and image-free rather than copying blog photos or using generated cartridge art.

badge.gallery image policy and Security-Bits H2HC 2023 Game Boy source page.

missing rights-cleared image · local project policy · needs licensed original replacement

No local BSides Cape Town 2017 badge image has been added because the public writeup photos have not been paired with an explicit reuse license, attribution, and processing notes for catalogue publication.

The record stays image-free rather than copying SensePost or blog imagery without complete provenance.

badge.gallery image policy and BSidesCPT17 RFCat challenge writeup.

missing rights-cleared image · local project policy · needs licensed original replacement

No Security Fest 2018 Challenge Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The Sweden record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and Security Fest 2018 badge source trail.

missing rights-cleared image · local project policy · needs licensed original replacement

No CPEC DC34 MechBattle Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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.

badge.gallery image policy and CPEC DC34 MechBattle and game repositories plus the official DEF CON 34 registration source trail.

missing rights-cleared image · local project policy · needs licensed original replacement

No CyberThreat 2026 Planned Hackable Badge Challenge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The United Kingdom record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and CyberThreat and SANS official 2026 event and registration source trail.

missing rights-cleared image · local project policy · needs licensed original replacement

No NoNameCon 2019 NoNameBadge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The Ukraine record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and NoNameCon 2019 ticketing, TechMaker making-of, firmware, and CTF source trail.

missing rights-cleared image · local project policy · needs licensed original replacement

No NoNameCon 2020 Air Quality Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The Ukraine record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and NoNameCon 2020 DOU event listing, TechMaker badge writeup, firmware, and CTF source trail.

missing rights-cleared image · local project policy · needs licensed original replacement

No Car Hacking Village DC32 Main Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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.

badge.gallery image policy and Car Hacking Village DEF CON 32 official page, public CHV repositories, CTF challenge archive, SAO specification, and IOActive key-fob badge build series.

missing rights-cleared image · local project policy · needs licensed original replacement

No Wild West Hackin' Fest Deadwood 2025 E-Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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.

badge.gallery image policy and Wild West Hackin' Fest Deadwood 2025 official event page, official e-badge page, Meta CTF badge challenge link, and AlrikRr post-event badge-hacking writeup.

missing rights-cleared image · local project policy · needs licensed original replacement

No Hackfest 2019 Electronic Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The Canada record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and Hackfest official history, Hackfest 2019 schedule, and Hackfest CTF 2019 page.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Chennai 2026 Event Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The India record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and BSides Chennai 2026 official event, ticket, schedule, and CTF pages.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Cheltenham 2026 Challenge Coin image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The United Kingdom record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

badge.gallery image policy and BSides Cheltenham 2026 official event and Early Bird ticket-package page.

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Peoria 2025 HackTheBadge Challenge Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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.

badge.gallery image policy and BSides Peoria's 2025 event announcement and 2026 electronic-badge retrospective plus Technet8394's event-linked HackTheBadge source archive.

missing rights-cleared image · local project policy · needs licensed original replacement

No ToorCamp 2024 Shadybucks Wristband image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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.

badge.gallery image policy and ToorCamp 2024 Shadybucks, Shady Tag, and Euphoria CTF wiki source trail.

mixed-source classification · primary plus first-hand secondary · documented

Hardware-source context comes from the official nsec-badge repository, firmware/build details come from the official badge-conf-2023 repository, controller-screen challenge behavior comes from the official nsec-badge-controller-screen repository, and detailed EEPROM/badge-chain protocol behavior comes from a first-hand attendee technical writeup.

Claims are kept specific to what each source proves, and the record does not overstate official documentation beyond the public repositories and first-hand writeup.

NorthSec 2023 README, badge-conf-2023 README, nsec-badge-controller-screen README, and idk.bz conference-badge writeup.

no-firmware classification · official badge page · documented

The official about page says the badge kept things old school with no microcontrollers, using a 555 timer and 4017 counter instead.

The catalogue models the badge as analog electronic hardware and does not infer firmware or software challenges.

Kernelcon 2024 badge about page.

non-electronic artifact specification gap · official event information · physical coin established; physical details unreleased

The official page calls the item a challenge coin in each attendee badge package, but no source identified material, dimensions, weight, finish, artwork, serialisation, maker, production quantity, packaging, credential function, or electronics.

The catalogue records the real event-specific coin without inventing its construction, appearance, value, access function, or technical behavior.

What's New for BSides Nashville 2026 official event page.

non-electronic scope · official registration, ticketing, and CFP sources · documented

The reviewed official pages prove a required participant/admission badge and registration workflow, but do not prove a PCB, electronics, firmware, batteries, QR/RFID/NFC, lanyard specification, badge challenge, schematic, bill of materials, or hardware repository.

The catalogue records the current participant credential as an identity/access artifact without inventing technical behavior or construction.

BSides Las Vegas 2026 official registration, ticketing, volunteer-guide, and CFP pages.

non-electronic scope · source-backed classification · documented

DEF CON 13 is modeled as a non-electronic human identity badge because the public source trail proves a physical badge but places DEF CON's first electronic badge at DEF CON 14 in 2006.

The compendium preserves the pre-electronic artifact without inventing LEDs, firmware, microcontrollers, or a badge challenge for 2005.

Wikimedia Commons DC13 Badge photo, DEF CON 13 forum announcement, VICE/Motherboard badgelife history, and Grand Idea Studio DEF CON 14 materials.

non-electronic scope · primary program and forum sources · documented

DEF CON 19's standard badge is modeled as a non-electronic titanium identity and puzzle artifact because official sources explicitly say the year moved away from electronic badges.

The catalogue avoids MCU, firmware, LED, battery, and circuit claims for 2011 while still preserving the badge's physical fabrication and puzzle significance.

DEF CON 19 program and LosT's DEF CON forum repost.

non-electronic scope · source-backed · documented

DEF CON 21's standard badges were intentionally described as non-electronic-electronic rather than powered electronic gadgets.

The compendium models the badge as a PCB identity and puzzle artifact and avoids firmware, MCU, LED, or battery claims for the standard badge.

Hackaday DEF CON 21 report and WIRED badge reveal.

non-electronic scope · official registration sources · documented

The public source trail proves a badge-required admission model and badge pickup workflow, but does not prove an electronic PCB badge, firmware, schematic, challenge circuit, or hardware badge repository.

The catalogue preserves the major BSides Las Vegas badge lineage as an identity/access artifact without inventing electronics.

BSides Las Vegas 2019 Join Us and Registration FAQ pages.

non-electronic scope · source-backed but incomplete · documented

The recovered official sources prove an attendee badge/lanyard and a badge challenge, but do not prove electronics, firmware, batteries, PCB traces, displays, radios, NFC, or a public hardware repository.

The catalogue records the badge challenge and physical identity artifact without inventing hardware.

BSides Tampa attendee FAQ and badge-challenge page.

official-source caveat · builder-log backed · needs deeper archive recovery

The badge record relies on a public builder log that frames the work as an official-badge request, but this pass did not recover an official ToorCon badge guide, repository, schematic set, or firmware archive.

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.

Hackaday.io Official Toorcon Badge? log and InfoconDB event metadata.

official-source publication and deployment boundary · commit-pinned official GitHub publication · documented; public source release is post-event

The official nsec/badge-2026 repository appeared publicly after NorthSec 2026. Its March-to-May authored commit history documents development chronology but does not establish public availability during the May event. The reviewed repository has no tag, GitHub release, or published binary, and no source maps a specific commit to a physical attendee unit or deployed CTF state.

Readers can inspect a real official source release while the catalogue avoids backdating its publication, claiming a particular factory image, or treating one source revision as proof for every badge handed out.

nsec/badge-2026 commit 4dab9e6c4c0b8efc9a643ee646a49550453ea22c repository tree, commit history, and releases/tags surfaces reviewed 2026-08-04.

online-cap, pickup, QR-claim, and fulfillment boundary · official checkout and Team announcement · online allocation exhausted; handoff still pre-event

The official checkout says online stock is exhausted and no shipping is offered; the Team describes a capped paid allocation, meetup/arranged handoff, and offline QR claims. The future pickup dates and community terms do not prove paid orders, production completion, QR receipt, collector identity, pickup, alternate handoff, delivery, refund, or support outcome.

The catalogue records a real sold-out online offer without converting it into a complete production or fulfillment report.

Puzzled Hackers CTF badge checkout and Team meetup announcement.

online-edition distribution caveat · event listing and badge-team source · documented with limits

The event listing presents NoNameCon 2020 as online and the TechMaker article says some CTF tasks were reworked because of COVID social distancing and the absence of the offline part of the conference.

The record documents a real badge platform but avoids claiming ordinary on-site pickup, universal in-person attendee distribution, or full offline village behavior.

DOU NoNameCon 2020 listing and TechMaker NoNameBadge 2020 article.

organizer-to-maker association, issuance, and allocation boundary · official organizer pages plus maker-published repository · event and electronic-badge context verified; direct project link unrecovered

BSides Peoria's official sources establish the completed October 2025 event and later state that its electronic badges were memorable, while Technet8394's repository self-identifies as a BSides Peoria Badge Challenge 2025 project. No reviewed organizer source links the repository, names this device, identifies its author, calls it an official main badge, or records a ticket tier, distribution count, recipient group, pickup, sale, giveaway, or completed handoff.

The catalogue models a real maker-declared event-associated challenge artifact rather than presenting it as organizer-issued, attendee-wide, admission-bearing, or independently confirmed electronic hardware.

BSides Peoria 2025 ticket announcement; BSides Peoria 2026 sponsor retrospective; Technet8394/HackTheBadge.

package allocation boundary · official conference and diploma pages · diploma scope explicit; standard-ticket equivalence unproven

The official diploma benefits list calls the item an exclusive electronic badge, while the official conference page separately advertises a 2026 kit and CTF for standard admission. The reviewed sources do not identify a general-attendee electronic badge, compare the kit to the diploma artifact, or establish who ultimately receives either item.

The entry remains limited to the named diploma package and does not convert general conference-kit, CTF, or entry language into an electronic-badge allocation.

DragonJARCON 2026 conference and diploma page and official event home.

partial-competition archive · repository README and source · partial archive

The badge competition is documented as a partial RubberDucky 2.0 interpreter in the code, not as a complete public challenge archive with rules, released solve, or prize outcome.

The record preserves the competition hook without overstating the completeness of the recovered challenge material.

LayerOne2023 README badge competition note and `keyboard.c` partial parser.

parts/reward expectation friction · closing talk reaction and field report · historical

The closing talk includes attendee reaction about buying a ticket yet not receiving parts, while Rabbit Radio describes challenge progress unlocking more parts for the badge.

The RCA build-up mechanic was part of the fun, but also created expectations around badge parts and prize/reward availability.

Rabbit Chaos Adventure closing talk and Rabbit Radio report.

party-pager classification · repository description and firmware evidence · documented

The public source trail describes SMART Response XE-based pagers for the 503 Party 2019, not an official DEF CON admission badge or a BSidesPDX conference credential.

The catalogue models 5ohBEE as a DC503 party pager and game artifact while keeping official conference badge lineages separate.

pdxbadgers/5ohBEE-2019 repository metadata, README, and firmware sketches.

physical artifact and electronics documentation gap · primary product and storefront pages · identity/access artifact only

The official sources call the item a badge but provide no physical design or technical description. They do not document whether it is printed, wearable, token-like, electronic, programmable, connected, rechargeable, or capable of running the announced challenge.

The record does not invent a PCB, microcontroller, firmware, lanyard, RFID/NFC, app, radio, or other device properties from the word badge alone.

FloridaMan 2026 Badge product page and official storefront.

physical form, component parity, power, and safety boundary · maker README and source-tree review · high-level parts list visible; physical artifact details unrecovered

The maker identifies an ESP32, a TFT panel, wiring, and two batteries, and the later source configures an ILI9341 display. The public archive does not provide a schematic, PCB, Gerbers, enclosure/CAD, exact ESP32 module, wiring diagram, final component substitutions, battery chemistry/capacity, charge/protection design, power budget, electrical limits, assembly/test record, production count, physical photo provenance, or safety validation.

The entry records a narrow source-backed electronic challenge-device outline without treating it as a reproducible build, a safe assembly guide, a uniform physical badge, or a completed production run.

HackTheBadge event-period README, post-event main.ino source, and repository tree.

physical-artifact caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document the non-electronic lens/layer concept, clue trail, badge-making talk, and black-badge collaborator note, but this pass does not inventory every physical lens, badge type, printed layer, clue, or final challenge solution.

The catalogue records verified badge lineage and interaction surfaces while leaving full artifact photography and challenge reconstruction for a later pass.

Mar Williams Art announcement, DEF CON creator-talk page, and DEF CON media-server badge directory.

physical-form, hardware, and NFC-role boundary · public team self-submission · NFC game modes named; artifact construction unreleased

The roster calls SR-71 a badge and says its game uses NFC peer-to-peer and reader modes, but does not identify physical form, PCB, card, wearable, chip, antenna, controller, reader, power source, display, storage, connector, material, dimensions, artwork, production revision, or which device actually supplies NFC functionality.

The record does not infer an electronic PCB, active reader, passive tag, NFC chip model, radio placement, power budget, safety profile, or interoperability from high-level game wording.

Public DEF CON 34 BadgeLife roster SR-71 self-submission.

planned badge and fulfilment boundary · official 2026 event and registration pages · planned event; post-event evidence pending

CyberThreat and SANS advertise a 2026 hackable-badge activity before the event. Neither source confirms a final badge design, manufacture, shipment, quantity, ticket-tier entitlement, participant allocation, collection process, delivery, replacement policy, completed competition, or individual handoff.

The catalogue treats this as a source-backed planned badge challenge rather than a confirmed distributed 2026 conference artifact.

CyberThreat official event page and SANS CyberThreat 2026 registration page.

planned run, donation, allocation, and fulfillment boundary · maker and organizer source wording · 40-unit plan and may-receive process published; outcomes unconfirmed

AoSC plans 40 brass coins and says a $100-or-greater qualifying donation may receive one; the event had not yet occurred in this source pass. Sources do not establish completed production, exact inventory, donation validation, number approved, recipient allocation, item serials, pickup location/time, mail fulfillment, shipping cost, loss/replacement, refund, support, student-blank allocation, or post-event availability.

The catalogue records the announced limited-run and philanthropic path without treating it as a completed sale, charitable outcome, manufactured quantity, or delivery report.

2026 eChallengeCoin page and Choose Your Own Charity submission form.

planned v2, price, preorder, and fulfillment boundary · public maker roster and first-hand maker thread · Coming soon and $20 wording published; outcome unconfirmed

The roster calls the item an update to an existing SAO, says Coming soon, and gives $20; the maker thread says v2 will use surface-mounted parts and later mentions direct-message preorders plus local handoff. Sources do not establish final design, inventory, final price, manufacture, payment, event authorization, sale location/time, pickup, shipping, refunds, replacement, support, or completed distribution.

The catalogue records a concrete pre-event maker announcement without presenting it as a completed DEF CON sale, a guaranteed preorder, or an attendee entitlement.

DEFCON 34 Badgelife Form response and u/Truth-Miserable MF Doom SAO v2 Reddit post.

planned/pre-event identity-artifact classification · primary source · awaiting post-event evidence

The 2026 Perth record is based on official pre-event participant-ticket copy proving a planned conference-swag badge, not a delivered or technically documented badge.

The catalogue can track the upcoming Perth badge without claiming final manufacturing, distribution, electronics, or challenge behavior.

BSides Perth 2026 event page.

post-assembly challenge soldering · badge guide · historical

The CTF LED path required desoldering capacitors C1 and C2, replacing them with 22 pF capacitors, and soldering SMD LEDs and resistors at specific locations.

The badge intentionally blurs software play with hands-on hardware rework; the compendium tracks that as a lifecycle/challenge caveat.

Hackerware Security Fest Piano CTF Badge guide.

post-event archive boundary · official badge and event pages · needs deeper source recovery

CONFidence 2026 has happened and the official badge site now exposes a Badge Hub and media page, but no public schematic, PCB files, BOM, manufacturing archive, or full firmware repository has been recovered.

Hardware claims stay limited to the official component list and pinout table, and software claims stay limited to the official Badge Hub, package-hub, and stated firmware/challenge goals.

ConfiBadge 2026 page, hardware page, pinout page, Badge Hub, media page, CONFidence FAQ, PROIDEA event page, and official rules PDF.

post-event fulfillment boundary · primary official sources · scheduled dates elapsed; final outcome unreported

Car Hacking Village announced an August 2026 DEF CON 34 badge and CTF. Its official event listing remains public after the August 6-9 scheduled window, but reviewed primary sources do not report final badge manufacture, allocation, handoff, completed CTF operation, production, or an attendee-wide issue.

The catalogue preserves a documented hardware project and host tooling without converting a lapsed schedule into a fulfilled-badge, completed-CTF, or delivery claim.

Car Hacking Village official event listing, sponsorship agreement, badge announcement, and CTF announcement.

post-event source gap · official and post-event source wording · documented; monitor deeper archive

The official post intentionally withheld rear-side component details before attendees received the badge, and the later public trail improves the creator, firmware, tooling, and winner-write-up record without exposing board files, schematics, BOM, production files, final quantity, or full component identity.

The catalogue records only the official development-board, Hackplayers recap, and repository-backed RP2350/RISC-V challenge claims while withholding exact board-design and manufacturing claims.

h-c0n CTF BADge announcement, Hackplayers post-event write-up, and hcon2026hwctf repository.

pre-event activation and delivery boundary · official product page · awaiting DEF CON 34 outcome

The official page schedules BENDER challenge availability and activation instructions for August 7, 2026, and says philanthropist badges will ship by early August. DEF CON 34 has not yet occurred, and no completed activation, delivery, challenge, or post-event badge report is public.

The catalogue records announced game and logistics context, not a completed physical run, completed server activation, delivered firmware, or observed attendee experience.

AND!XOR DC34 official product page.

pre-event artifact fulfillment gap · official inclusion pages and founder announcement · event completed; exact artifact fulfilment unpublished

Official pages promised a NaClCON Badge and CTF access, and the founder announced a 3D-printed/NFC conference badge before the event. A named attendee confirms the first convention happened, but the reviewed post-event sources do not directly confirm final fabrication, how many badges existed, attendee handoff, reuse, losses, replacements, variants, or whether the announced 3D-print/NFC form was delivered.

The record can preserve a concrete pre-event artifact claim without presenting planning language or an event-completion report as proof of universal delivery or a final production configuration.

NaClCON registration, schedule, founder announcement, and named attendee report.

pre-event artifact, host association, and credential boundary · public team self-submission plus official Aerospace Village event page · planned independent CTF badge in public roster

A publicly named ACR team submits SR-71 to the BadgeLife roster and states an Aerospace Village booth/Discord CTF plan, while Aerospace Village independently establishes the DEF CON 34 event. Neither source says that Aerospace Village designed, issued, endorsed, or will distribute SR-71; nor do they say it is a DEF CON Human badge, a registration entitlement, an admission credential, or a completed event artifact. The roster team name alone is not treated as proof of corporate authorization.

The catalogue preserves a concrete event-associated BadgeLife listing without converting public self-description into organizer issuance, corporate endorsement, credential authority, or a completed distribution claim.

Aerospace Village DEF CON 34 event page and the public DEF CON 34 BadgeLife roster SR-71 self-submission.

pre-event assembly and fulfillment boundary · maker page and public assembly update · awaiting DEF CON 34 outcome

The maker page calls the project a 2026 DEF CON 34 version and warns that production might not finish in time. A public late-July update says boards are in hand and final assembly/flashing is more than halfway complete, but no completed run, attendee delivery, quantity, or final fulfillment report is public.

The catalogue records a currently evidenced independent project and announced pickup path, not a confirmed delivered run, attendance-wide issue, final recipient count, or post-event game outcome.

Dani Weidman official maker page and public late-July assembly update.

pre-event badge caveat · official ticket source · needs post-event confirmation

The current public evidence is pre-event ticket text, so this record does not claim final shipped hardware, final firmware, attendee delivery, or post-event challenge behavior.

The catalogue can preserve the limited PCB badge announcement while keeping final distribution and field behavior open for a post-event source pass.

SECCON official ticket page and event pages, checked 2026-05-21.

pre-event badge caveat · official page but future event · planned

Current official BSidesTLV pages place the 2026 conference on November 11, 2026, so the event has not happened yet as of this refresh; the Hardware Village page documents a Badge CTF Challenge but not shipped hardware.

The record should not claim shipped hardware, final challenge behavior, attendee distribution scope, or post-event outcomes until the event happens and artifact-level sources appear.

BSidesTLV 2026 home and Hardware Village pages.

pre-event coverage · current public event page · incomplete current record

Final hardware, firmware, photos, author credits, delivery status, and CTF/badge integration details are not public in the current source set; the official participant FAQ says badge details are expected closer to the camp.

The compendium can track the announced badge and challenge without inventing components, delivery outcomes, controversy, or authorship before the event ships.

RomHack 2026 event page, RomHack Camp participant FAQ, and RomHack Camp CTF page.

pre-event production and visual-rights boundary · official event-page review · future token announced; factual coin image and reuse basis unavailable

The conference remains future-dated and the reviewed organizer page does not publish a factual final-coin record with complete production, allocation, image-specific attribution, reusable license or explicit permission, source URL, and local processing provenance.

No image, final manufacturing, delivery, or visual-design claim is published; the record remains a source-backed, image-free planned token entry.

BSides Cheltenham 2026 official event page and badge.gallery image policy.

pre-event sale, stock, fulfillment, and party-outcome boundary · primary current listing · out of stock; outcome undocumented

The official listing currently shows a $90 product as out of stock and says it is no longer shipping, while the party has not yet occurred in this source pass. The reviewed pages do not establish previous order count, buyer communication, delivery, pickup, replacements, transfer/refund handling, final guest list, door implementation, venue capacity, schedule changes, or actual attendance.

A live/pre-event commerce snapshot is not presented as proof that badges were delivered, an access promise was honored, or the party/challenge happened as announced.

FloridaMan 2026 Badge official product page and FloridaMan Party 2026 official page.

pre-event specification boundary · official 2026 sources · planned

Official evidence confirms a 2.54 mm MiniBadge-socket interface and electronic sponsor-ticket category, but no final 2026 MCU, PCB, schematic, connector count, electrical pinout, display, battery, firmware, programming workflow, challenge specification, or manufacturing archive was recovered.

The dossier exposes the real planned badge surface while preventing teaser language and generic MiniBadge-standard documentation from becoming unsupported 2026 hardware or software claims.

SAINTCON 2026 MiniBadges page and Sponsor Prospectus.

price, stock, proceeds, and fulfillment boundary · seller, maker profile, and vendor-list wording · published $125 and mission context; inventory and delivery unconfirmed

The product and vendor list show $125, and the profile says all proceeds support Hak4Kidz's mission and ethos. Sources do not establish inventory, units sold, buyers, payments, proceeds amount/destination, charitable accounting, pickup, shipment, refunds, replacements, support, resale, or completed fulfillment.

The catalogue keeps the published marketplace and mission wording without treating it as proof of sales, donation outcome, official fundraising, or final recipient delivery.

Masonic33 Tindie listing, Hak4Kidz Lab profile, and Hacker Couture DEFCON 33 Product List.

primary technical archive gap · credible secondary source but incomplete primary archive · needs official schematic or firmware recovery

The recovered source trail documents a NodeMCU ESP8266 handmade badge and badge-hack contest, but this pass did not recover an official 2018 schematic, PCB, BOM, firmware repository, or direct organizer badge writeup.

The record keeps component claims to the published NodeMCU ESP8266 detail and avoids assigning unverified display, battery, schedule, or CTF features.

Australian Cyber Security Magazine 2018 report and BSides Perth 2021 sponsor-pack retrospective.

print form, data, consent, and access-function gap · official app page · networking purpose named; artifact and data model unreleased

The source says the Networking Badge facilitates attendee connections and is printable with the digital badge, but does not identify medium, dimensions, design, personal-data fields, QR/barcode/RFID/NFC behavior, app-to-print data flow, consent/opt-in controls, visibility settings, contact sharing, retention, security, accessibility, credential authentication, venue-access role, challenge role, or privacy terms specific to the printable artifact.

The dossier does not turn a networking purpose into a claim about badge technology, identity verification, data handling, contact exchange, physical construction, or permission to access the venue.

Barcelona Cybersecurity Congress app and networking badge page.

prior-year technology non-transferability · official 2026 page and 2025 retrospective · 2025 technical trail retained as historical context only

A credible 2025 retrospective describes a workshop-only Electronic Cats NFC/OLED badge with a 100-unit run. The official 2026 diploma page does not name Electronic Cats, reuse that hardware description, state a recipient count, or say the badge is a revision of the 2025 artifact.

Known 2025 NFC/OLED details cannot be presented as the 2026 diploma badge's components, maker, challenge, quantity, or eligibility conditions.

DragonJARCON 2026 official pages and Fluid Attacks' DragonJARCON 2025 retrospective.

privacy and sensor caveat · official research statement · documented

The study context involved VR goggles, physiological sensors, questionnaires, challenge activity, and researcher check-ins, with the recruitment statement explaining data collection and participant procedures.

The badge dossier preserves the research-study context while avoiding unrelated claims about public badge behavior, firmware, or attendee monitoring outside SaikoCTF participation.

HITB Recruitment statement.

project-builder confirmation and official-archive gap · direct project-builder post plus community sources · direct build/CTF confirmation; official archive unrecovered

The TechFrontiers write-up directly attributes the PACMAN Ghost badge build and CTF design to David Melendez Cano and Gabriela G., while community reversals independently document several component and firmware details. Neither source set supplies an official RootedCON design repository, complete schematic/PCB/BOM/Gerber archive, production ledger, final revision map, battery/charger documentation, backend/protocol source, release, or license.

The catalogue now records direct builder attribution and event architecture without portraying a personal project post or community reverse-engineering tree as an official RootedCON source release, complete production specification, firmware security audit, or reusable-image permission.

David Melendez Cano / TechFrontiers RootedCON badge write-up; RootedCON 2026 community reversing, custom-firmware, and repurpose repositories.

public-demo firmware boundary · source-backed but scoped · documented

The public repository is a cleaned-up demo firmware collection with examples and removed event-specific/proprietary material, while the Hackaday.io project describes a richer original badge firmware with menus, audio games, visual effects, timers, hidden screens, and challenge hooks.

The software description separates the recovered demo archive from the full shipped event firmware so the record does not overstate public source completeness.

Hackaday.io THOTCON 0xD project and `thotcon-examples` README.

public-source scope caveat · source-backed but compact · documented

The repository documents hardware and firmware targets, but this pass does not enumerate every CTF firmware behavior, add-on program, or produced attendee-board variant.

The catalogue records verified badge surfaces and leaves deeper event-specific artifact inventory for future work.

NorthSec 2024 badge README and repository tree.

radio scope, lawful-use, and field-operation boundary · source-backed capability but incomplete operational record · technical context documented; field use unverified

The source identifies an SX1262 and RNode/Reticulum-oriented firmware context but does not establish radio band/region configuration, antenna characteristics, authorization, venue coordination, permitted use conditions, actual over-the-air deployment, range, interference testing, privacy handling, or safety outcome at HTH 2026.

The catalogue records high-level communications capability only and deliberately omits operating instructions, frequency/configuration guidance, challenge tactics, and claims about lawful or safe field operation.

Eagle 5 README, CHANGES.md, and HTH 2026 source-review boundary.

recipient allocation and fulfillment boundary · primary official sources · post-event source release; recipient outcome unrecovered

RHC scheduled on-site physical-badge pickup for DEF CON 34 and later published firmware, but reviewed sources do not establish recipient eligibility, a distribution count, unit serial allocation, individual pickup, final firmware parity for every issued badge, or CTF participation/results.

The dossier records a released badge platform without converting event and source-release evidence into a completed attendee-delivery ledger.

Robotic Hacking Community home, CTF, badge documentation, and firmware repository.

remaining hardware caveat · source-backed but intentionally narrow · BOM and production notes recovered; still needs shipped-count and image provenance

Recovered official sources now include the PCB Badge guide, public technical repository, production BOM, production notes, firmware, PCB files, base-station/backend/game/web/software trees, hardware revision notes, timer/DMA details, menu-flow notes, and BadUSB protocol notes, but this pass still does not assert a shipped count or rights-cleared badge image.

The dossier records the verified interaction, production, and technical-archive surface while avoiding unsupported production-scale and image-provenance claims.

HITCON 2025 PCB Badge guide, HITCON agenda page, john0312/hitcon-pcb-badge repository, JLCPCB BOM, and production notes.

remote-edition context · official source · documented

NorthSec's official past-editions page describes 2021 as a lockdown/remote edition, so the catalogue avoids claiming ordinary in-person badge distribution logistics.

The record focuses on the public electronic badge, game flags, and development-board behavior rather than unsupported hallway-distribution details.

NorthSec past editions and 2021 badge page.

replay hardware boundary · repository documentation · documented

The repository says people replaying the CTF at home can flash a Raspberry Pi Pico 2, but boards different from the CTF PCB need an LED on GPIO 25 and one challenge may require a debug probe and cable.

The record distinguishes the conference CTF BADge from compatible at-home replay boards and preserves the hardware-debugging requirement without overstating universal compatibility.

therealdreg/hcon2026hwctf README.

repository license caveat · GitHub API recheck · no detected license

GitHub reported `license: null` for NUSGreyhats/greybadge25 during this pass, and no visible top-level LICENSE file was used as a reuse basis.

Repository files are cited as public evidence, but local reuse is limited: no repository images, artwork, hardware files, firmware, or slides are copied into the catalogue as licensed assets.

NUSGreyhats/greybadge25 GitHub API metadata and repository tree recheck.

repository license caveat · repository README · needs component-level review

The repository README says the project uses submodules with various licenses and instructs readers to check individual component licenses.

Firmware and hardware facts can be sourced from the repository, but code-reuse and asset-reuse claims should not be collapsed into one blanket license statement.

disobey-badge-2025-game-firmware README.

repository recovery gap · official source but unrecovered archive · needs deeper archive recovery

HITB stated that the badge hardware, software, and firmware were fully open sourced, but this pass did not recover a stable repository or downloadable source archive URL.

The dossier records the public hardware-spec and challenge surface while avoiding unsupported firmware, schematic, or implementation claims beyond the official page.

HITBSecConf2018 Amsterdam CommSec Village page.

repository recovery gap · official source but unrecovered archive · needs deeper archive recovery

HITB stated that the badge hardware, software, and firmware would be fully open sourced, but this pass did not recover a stable repository or downloadable source archive URL.

The dossier records the public hardware notes and challenge surface while avoiding unsupported firmware, schematic, exact-chip, or implementation claims beyond the official page.

JD-HITBSecConf2018 Beijing CommSec Village page.

repository scope caveat · primary repository plus official event sources · public hardware and firmware repository recovered

The Electronic Cats repository now proves badge components, firmware, commands, KiCad files, and the challenge flow, but this pass still does not verify final shipped-unit variations, attendee-specific provisioning, or rights-cleared documentary photos.

The dossier can use component-level and firmware claims from the repository while still keeping image and distribution details conservative.

ElectronicCats badge-dragonJar-2025 repository, DragonJARCON 2025 event page, and DragonJAR badge raffle page.

repository-license caveat · repository audit · documented

The public repository documents hardware and challenge behavior, but this pass did not recover a top-level license suitable for local image or code reuse assumptions.

The catalogue cites the repository as evidence while leaving images empty and avoiding license claims beyond the source text.

ZonkSec kernelcon-2019-badge repository.

repository-license caveat · repository audit · documented

The GitHub API reports no repository license for `secommunity/FluxDecoder` in this pass.

The catalogue cites the repository as evidence but does not assume reusable image, code, schematic, or PCB rendering rights beyond ordinary source citation.

GitHub repository metadata for secommunity/FluxDecoder.

repository-license caveat · GitHub metadata · documented for source only

GitHub reported no detected license for the DC32 main badge board, main badge firmware, CTF challenge, and CHV SAO specification repositories in this pass, while the separate Speedometer SAO firmware repository reports MIT.

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.

GitHub repository metadata for car-hacking-village/DC32_CHV_Badge_Board, DC32_CHV_Badge_Firmware, DC32_CTF_CHALLENGES, CHV_SAO_Specification, and DC32_CHV_Speedometer_Firmware.

research participant scope · official source but intentionally narrow · documented source limitation

The source trail proves an electronic SaikoCTF badge for research-study participants, not a universal HITBSecConf2024 admission credential or public attendee badge.

The record is modeled as a SaikoCTF participation badge so the catalogue does not overstate its distribution scope.

HITB SaikoCTF page and HITB Recruitment statement.

retrospective hardware caveat · official badge-team interview · documented

The 2014 preview discusses the 2013 badge retrospectively and notes that some 2013 badges lacked accelerometer hardware, so this record keeps input and game claims conservative.

The badge is modeled as a proven electronic badge while exact final per-attendee hardware capability remains caveated.

RVAs3c badge preview retrospective comments.

scheduled-drop, current recurrence, and completed-distribution gap · published schedules, seller listing, and vendor list · 2025 activity and planned 2026 recurrence documented; outcomes and revision unconfirmed

A public 2025 schedule records a Masonic33 Badge drop and seller/vendor pages show a $125 item. Badge.Life's current 2026 Village Schedule lists Masonic33 Badge — heal twice, but does not identify a new board or revision. This pass did not recover an after-action announcement, production count, booth location, receipt, recipient list, attendee report, final schedule confirmation, pickup/shipping record, completed donation accounting, or evidence that every listed package reached a recipient for either appearance.

The catalogue preserves a 2025 origin and planned 2026 recurrence without turning either schedule entry into a universal attendee distribution, completed event outcome, sale, allocation claim, or distinct DEF CON 34 badge.

Recovered DEF CON 33 schedule, Badge.Life DC34 Village Schedule, Masonic33 Tindie listing, Hak4Kidz profile, and Hacker Couture product list.

separate TOG hardware-flags boundary · first-hand TOG post-event account · distinct projects not equated

TOG reports building fifteen ESP8266 hardware flags in custom cases for the WICC CTF, but its account does not name OzmoOzmo, SecurityConferenceCTFBadge, or the repository's badge photo. Conversely, the maker README thanks TOG hackers and makers for beta testing without identifying TOG's fifteen flags as its own build.

The record preserves related physical-hardware context without merging separate maker provenance, hardware counts, designs, allocations, or authorship into one unsupported badge claim.

TOG Building Hardware Flags for WICC 2026 post and commit-pinned OzmoOzmo SecurityConferenceCTFBadge README.

soft-brick safety caveat · official walkthrough · documented

The A Nice Edit walkthrough warns that the challenge carries a high risk of soft-bricking the badge and explains that erasing flash without preserving the bootloader can make USB programming unrecoverable without ISP.

The badge page preserves the original risk context for firmware modification instead of presenting the challenge as routine or risk-free.

CyberThreat A Nice Edit walkthrough PDF.

software and puzzle archive gap · official event posts and agenda · puzzle role documented; implementation unreleased

Official wording confirms puzzle and solve context but does not disclose firmware, application, source repository, flashing method, protocol, flag count, challenge sequence, answers, scoring, prizes, source licence, or security analysis.

The entry does not turn the verified puzzle framing into unsupported CTF, firmware, networking, or credential claims.

BSides Maine badge puzzle post and 2026 agenda.

software, NFC protocol, data, privacy, and security gap · public team self-submission · future code or firmware mentioned; no implementation material linked

The roster says code or firmware will be available after the con, but currently provides no repository or implementation documentation. It does not disclose NFC protocol or payload design, card identifiers, peer/reader behavior, phone or app requirements, backend, accounts, authentication, authorization, cloning resistance, encryption, telemetry, logs, personal-data handling, retention, deletion, privacy notice, threat model, security review, update path, or support policy.

The catalogue presents only the stated NFC game concept, not a defined communications protocol, software release, privacy practice, security guarantee, or safe operating guidance.

Public DEF CON 34 BadgeLife roster SR-71 self-submission.

software-source caveat · badge-maker writeup · needs software archive recovery

The badge-maker writeup says the CactusCon crew planned a software-side writeup and hints at event wireless infrastructure, but this pass did not recover a public firmware repository, complete challenge source, or software architecture note.

The catalogue records verified hardware and firmware-access surfaces while avoiding unsupported claims about the badge's full event game or OTA backend.

Badge Pirates CactusCon 11 Badge writeup.

software-source caveat · repository tree inspection · needs final firmware recovery

The repository includes BasicCodeForQA, but this pass did not recover final event firmware, badge-game source, OTA service code, or challenge material.

The record keeps software claims limited to QA-code context and hardware-programming surfaces.

BadgePiratesLLC/CactusCon-12 CODE tree.

software-source caveat · repository tree inspection · needs firmware archive recovery

The CactusCon13 repository exposes CAD, outer-board, documentation, reference, and 3D-print material, but this pass did not recover standalone final firmware, event-game source, OTA service code, or challenge archive.

The catalogue records verified hardware/manufacturing evidence while avoiding unsupported claims about badge software behavior.

BadgePiratesLLC/CactusCon13 repository tree.

software-source caveat · repository tree inspection · needs firmware archive recovery

The GitHub repository description mentions firmware, but the visible public tree inspected in this pass primarily exposes hardware design, manufacturing, enclosure, BOM, schematic, and art outputs rather than standalone event firmware or challenge source.

The catalogue records the verified hardware archive while avoiding unsupported claims about badge applications, games, OTA behavior, or event infrastructure.

BadgePiratesLLC/CactusCon14 README and repository tree.

soil-sensing feature, field behavior, and outcome boundary · maker repository description · high-level feature documented; use and field result unrecovered

The maker archive calls the artifact a working soil sensor, but it does not publish a deployed-use record, participant count, environmental conditions, calibration result, measurement comparison, challenge or game rules, data retention, participant outcome, prize policy, ongoing service status, or a safe/reproducible operating procedure. No sensing, connection, configuration, or interaction directions are reproduced here.

The catalogue makes the source-described badge feature discoverable without inferring tested performance, universal participation, a completed challenge, individual outcomes, or a safe operating workflow.

bsides-newcastle-2024-badge README and public archive.

source archive, binary, and software-release scope · MIT source archive · substantial earlier archive; current release scope undocumented

The repository supplies substantial DC32 Arduino, KiCad, Gerber, CAD, and documentation material under MIT, but has no identified final 2026 product release, signed binary, provisioning record, current-source compatibility statement, rollback/recovery guidance, or support lifecycle. Its quickstart says the CTF portion was a precompiled library whose source was to be released after DEF CON 32.

The catalogue links the preservation source without misrepresenting it as a complete, current, supported, reproducible 2026 field-update package or a full release of every historic CTF component.

`btv_dc32_badge` README and code quickstart.

source depth · source-backed but compact · documented caveat

The public sources are strong for kit intent, BOM, assembly, Arduino workflow, Gerbers, KiCad files, and photos, but they do not provide a full event field report or attendee writeup for how the badge was used during the day.

The record keeps its claims to documented kit distribution, assembly, and sample-code behavior rather than inventing on-site gameplay or contest lore.

BSides PR 2019 badge docs, repository README, and Security BSides wiki page.

source release, deployed-firmware, and interaction boundary · repository chronology and maker wording · post-event Arduino source visible; event deployment and support unrecovered

The archive's public main.ino source was added after the event, has no reviewed compiled binary, tag, GitHub release, explicit repository license, deployment record, support policy, or source-to-device mapping. Its maker describes the project as a one-off challenge. The code's Wi-Fi and web-server surfaces are therefore treated as source context rather than a live service, accessible challenge, secure workflow, or operating instruction.

The catalogue does not expose connection or challenge details, claim a current working service, offer configuration guidance, infer a released event firmware, or treat public source visibility as a broad license or support commitment.

HackTheBadge commit history, post-event source-release commit, README, and repository metadata review.

source-code and production gap · official event archive plus public badge docs · needs badge-team archive

The public documentation proves the kit contents, assembly path, flashing workflow, and Hackers Challenge registration behavior, but this pass did not recover a public schematic archive, PCB source, production count, complete Lua source tree, final firmware image mirror, or badge-team repository.

The record preserves verified public hardware and workflow facts without inventing unrecovered firmware internals, board-source details, or manufacturing data.

SAINTCON 2016 archive, venue map, badge assembly, upload-code, and registration documentation.

source-code archive gap · source-backed but incomplete · needs public firmware or schematic recovery

The recovered sources document hardware components, soldering, USB CTF interaction, and LED progress behavior, but this pass did not recover a public firmware, schematic, PCB, BOM, or gerber archive.

The dossier records the verified badge behavior while avoiding unsupported pinout, firmware, protocol, or source-release claims.

Hackster Wombat badge writeup, Hackerware badge page, and soldering tutorial PDF.

source-code archive gap · source-backed but incomplete · needs public firmware or schematic recovery

The recovered sources document components, onboard controls, CTF prompts, LED behavior, and a PCB-blueprint challenge, but this pass did not recover public firmware source, schematic, BOM, or final gerber archive suitable for component-level verification.

The record keeps the hardware and software claims to creator and attendee documentation instead of inferring a full implementation.

Hackerware Wombat-2 pages, Hackster project-owner writeup, and semaja2 attendee challenge writeup.

source-code archive gap · organizer-reported release but archive unrecovered · needs public canonical source-archive link

The official event page documents the Underground badge's ESP32, screen, controls, badge-to-badge communication, SAO support, and CTF framing, and a maker writeup documents a WS2812B SAO board. A March 24 organizer post says the 20-puzzle conference badge received a full source-code release, but it routes through an unresolved LinkedIn short link; this pass therefore did not independently recover or inspect firmware, schematic, PCB, BOM, radio protocol, or production files for the main badge.

The record captures the post-event challenge and stated-release evidence while avoiding unsupported chip pinout, firmware, radio, protocol, software-license, or shipped-behavior claims until the canonical archive is retrieved.

BSides Ballarat 2026 event page, Ballarat Hackerspace reference, Eurekative reference, dmoges SAO maker writeup, and Dr Paul Black's March 24, 2026 post-event update.

source-code archive gap · source-backed but incomplete · needs public repository or schematic recovery

The designer writeup documents source-file names, firmware architecture, and implementation details, but the current source trail did not recover a reliable public firmware repository, schematic, board-file archive, or license statement.

The dossier can now describe the implemented firmware architecture from a primary source while still avoiding unsupported repository, schematic, image, or reuse-rights claims.

Sinclair Studios CHCon 2025 badge challenge writeup and Jeremy Stott technical writeup.

source-code archive gap · source-backed but incomplete · needs public firmware or schematic recovery

The recovered project-owner writeup documents hardware components and CTF behavior, but this pass did not recover a public firmware, schematic, PCB, or BOM archive for the SINCON badge.

The dossier records the observable hardware and serial CTF flow while avoiding unsupported repository or source-code claims.

Hackster.io Khong Guan Building CTF badge writeup.

source-code gap · official docs but incomplete source recovery · needs image/repository recovery

Official pages and the public manual document badge assembly, flashing, registration, and post-event conversion, but this pass did not recover a public source repository for the badge image, custom PCB design files, challenge daemons, or final production files.

The catalogue records the verified deployed badge and public manual without inventing unrecovered firmware internals or PCB-source details.

SAINTCON 2017 badge page and GitLab Pages badge manual.

source-depth caveat · repository, talk, wiki, field report, and participant reports · repository reviewed; firmware still not asserted

The repository review confirms schematics, Gerbers, LCSC parts exports, media, 3D-print files, NE556-related challenge material, and multi-board RCA structure, but this pass still does not claim a complete firmware architecture or full electrical BOM extraction.

The dossier is now specific about the public artifact package while still avoiding unsupported firmware and chip-level claims beyond what the repository and reports expose.

x70b1/eh21badge repository, Rabbit Chaos Adventure closing talk, Rabbit Radio, Easterhegg wiki, and participant reports.

source-depth caveat · detailed guide, mirror, and event archive · needs repository or team-page recovery

The badge guide and migrated mirror are strong for hacking workflow and credits, but no public design-file repository has been seeded yet for a full bill of materials or firmware-history record.

The dossier intentionally avoids unsupported MCU/module claims beyond the public USB UART, Omega shield, jumpers, CTF, and RF wiring notes.

Jump ESP, jump! badge guide, migrated mirror, and Hacktivity event archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove DEF CON 1 name-tag and paper role-badge artifacts but do not identify the badge designer, production process, complete role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and official registration context.

DEF CON 1 official announcement, official archive page, official picture index, media-server badge image, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove visible DEF CON 2 rectangular printed chest credentials but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and event context.

DEF CON 2 official media-server event photos, official DEF CON archive page, official picture index, announcement, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove visible DEF CON 3 colored rectangular waist credentials but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and event context.

DEF CON 3 official media-server event photos, official DEF CON archive page, official picture index, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove visible DEF CON 4 rectangular chest credentials but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and event context.

DEF CON 4 official media-server event photos, official DEF CON archive page, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove a visible DEF CON 5 hanging credential but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and event context.

DEF CON 5 official media-server event photo, official DEF CON archive page, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove visible DEF CON 6 credentials but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and event context.

DEF CON 6 official media-server event photos, official DEF CON event page, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove attendees wore DEF CON 8 lanyard credentials but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-credential evidence and event context.

DEF CON 8 official media-server event photos, official DEF CON event page, and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove attendees wore DEF CON 9 lanyard badges but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-badge evidence and event context.

DEF CON 9 official media-server event photos and scanned program archive.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove the physical badge artifact and corner-hole lore but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-badge evidence and official program context.

DEF CON 10 official program and media-server image listing.

source-depth caveat · source-backed but limited · needs deeper archive review

The current public sources prove the badge artifact and event context but do not identify the badge designer, production process, material, full role taxonomy, or any official puzzle layer.

The record limits claims to visible physical-badge evidence and official event context.

DEF CON 11 official program and media-server image listing.

source-depth caveat · primary source only · monitor for later releases

This pass found official BBV page evidence for the badge and CTF leg but no public repository, bill of materials, final challenge writeup, or rights-cleared documentary badge photo.

The record is intentionally compact and should be revisited if Bug Bounty Village publishes post-event technical material.

Bug Bounty Village BBV Badge 2025 and CTF 2025 pages.

source-depth caveat · source-backed but incomplete · needs deeper artifact inventory

The public sources prove the ESP32 audio badge, repository trail, and add-on connector, but this pass did not recover a complete final schematic, BOM, production package, firmware release tag, or attendee challenge archive.

The record keeps hardware and software statements tied to public evidence while avoiding unsupported production-scale and final-firmware claims.

LayerOne HHV archive, Hackaday event report, CharlieX repository, and mmca add-on log.

source-depth caveat · source-backed but incomplete · needs deeper artifact inventory

The public sources prove the ATtiny2313 main badge, repository source trail, and ESP32CAM/servo add-on context, but this pass did not recover a complete final schematic, BOM, production package, firmware release tag, or challenge solve archive.

The record keeps hardware, software, and add-on statements tied to public evidence while avoiding unsupported production-scale and final-firmware claims.

LayerOne HHV archive, Hackaday event report, and CharlieX layerOne2019 repository.

source-depth caveat · source-backed but incomplete · needs deeper artifact inventory

The repository preserves firmware, board and schematic files, host tooling, enclosure assets, and an interactive BOM, but this pass does not claim a complete production package, final assembly guide, attendee count, or challenge solve archive.

The record keeps hardware, USB, LED, and firmware statements tied to the recovered public repository while avoiding unsupported production-scale claims.

charlie-x/LayerOne2023 README, firmware sources, PCB files, OKBB host tool, and repository tree.

source-depth caveat · first-hand write-up plus secondary coverage · needs badge-team archive

The recovered public trail proves an Arduino-compatible badge, FTDI programming path, HHV assembly context, hidden challenge behavior, and blinky expansion board, but this pass did not recover an official 2014 archive page, schematic, BOM, PCB source, MCU identification, final firmware repository, production count, or complete build manual.

The record preserves verified badge behavior and named-source context without inventing unrecovered electronics, firmware internals, component values, or manufacturing details.

Josh Datko write-up, SparkFun repost, Hackaday coverage, and Cisco retrospective context.

source-depth caveat · official event metadata plus first-hand badge package write-up · needs badge-team archive

The official archive and metadata sources prove the virtual event context, and the first-hand DC540 write-up proves a shipped badge package, included MiniBadge, custom-MiniBadge coupon, and HC CTF badge context; this pass did not recover an official 2020 schematic, BOM, firmware archive, production count, or complete badge-team build notes.

The record treats SAINTCON 2020 as a conservative package-level badge entry instead of inventing unrecovered electronics, firmware behavior, or challenge mechanics.

SAINTCON 2020 archive, InfoconDB event entry, DC540 first-hand write-up, and MiniBadge standard README.

source-depth caveat · public repository and official talk source · needs final production archive

The official talk page and repository document the badge design, gameplay, hardware archive, and CircuitPython workflows, but this pass did not recover a final production count, shipped firmware release tag, manufacturing order, or rights-cleared field photo.

The record preserves the real BSidesPDX badge without overstating production logistics or publishing unclear media.

BSidesPDX speaker page, hardware README, Attribution Game badge guide, Trick-or-Treat README, and repository metadata.

source-depth caveat · first-hand attendee writeup · needs official badge archive recovery

The recovered source proves a paid badge package and observed Wi-Fi/Bluetooth scanner behavior, but this pass did not recover official badge-team documentation, schematics, BOM, firmware, production count, challenge material, or a source repository.

The catalogue records the real scanner badge while keeping technical claims limited to the public attendee writeup.

Ratil.life Hacking and Skydiving writeup.

source-depth caveat · source-backed but incomplete · needs deeper archive recovery

Rob Rehrig's first-hand writeup documents the 0xC badge theme, laser-tag behavior, enclosure, optics, and production decisions, but this pass did not recover a public schematic, Gerber set, BOM, firmware repository, binary archive, or full badge manual.

The catalogue records verified event, game, mechanical, and optical facts without claiming that the complete design archive is public.

Rob Rehrig THOTCON 0xC writeup, official THOTCON 0xC schedule, Fourfold work page, and InfoconDB event metadata.

source-depth caveat · single project-owner planning source plus official site · needs post-event source recovery

The current public trail names a planned MK.II badge and desired improvements, while the live PhreakNIC site currently promotes preregistration and challenge coins rather than PN27 badge specifications. No dedicated PN27 repository, schematic, BOM, firmware tree, attendee guide, station code, production note, or final event schedule entry has been recovered.

The record avoids final component, firmware, interaction, and distribution claims until stronger PhreakNIC 27 sources appear.

Official PN26 Electronic Badge writeup and live PhreakNIC website rechecked on July 7, 2026.

source-depth caveat · official interview · documented

The public source documents behavior and production context through an interview rather than a full hardware repository or final attendee manual.

The record avoids claiming a recovered schematic, BOM, final firmware tree, or complete CTF source.

Hack.RVA: 2016 Badges interview.

source-depth caveat · source-backed but incomplete · needs source recovery

The Hackster project provides first-hand build notes, materials, and a firmware binary link, but this pass did not recover a dedicated public source repository with complete C source, schematic, Gerbers, PCB production outputs, or a formal hardware license.

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.

Hackster DerbyCon Legacy Black Badge project and linked files.

source-depth caveat · single official agenda source · needs badge-team archive

The public source trail proves an AfricaHackOn 2018 electronic conference badge and making-of session, but does not expose the badge's component list, firmware, repository, schematics, board files, distribution model, or challenge behavior.

The record is intentionally narrow and should be expanded only if a badge-team writeup, slide deck, code release, or surviving-board documentation is recovered.

OPCDE Kenya agenda.

source-photo limitation · public writeup and image policy · needs licensed original replacement

The current build has not cleared a reusable original badge photo from the field writeup or repository.

The record remains source-backed for facts, while the catalogue withholds imagery until a licensed original photo is curated.

Project image provenance and Zeta-Two challenge-badge photo reference.

source-release gap · project logs but incomplete source recovery · needs artifact-level archive

The all-at-once log says Eagle files and software would be uploaded to GitHub, but this pass did not recover a complete public final repository, release package, board-production archive, or challenge/software bundle for the 2016 badge.

Hardware and software claims remain tied to the public HHV page and Hackaday.io logs instead of treating planned source publication as recovered source.

LayerOne 2016 All at once log and current source search.

sticker-badge classification · organizer walkthrough · documented

The Kākācon 2021 source trail proves a sticker-backed badge challenge, not an electronic badge.

The entry preserves the printed challenge artifact without inventing PCB hardware, firmware, RF, display, or battery behavior.

Kākācon art page and 2021 badge challenge walkthrough.

sticker-badge classification · organizer walkthrough · documented

The Kākācon 2022 source trail proves a sticker-backed badge challenge, not an electronic badge.

The entry preserves the printed challenge artifact without inventing PCB hardware, firmware, RF, display, or battery behavior.

Kākācon art page and 2022 badge challenge walkthrough.

story, organization, authorship, and endorsement boundary · maker story and manufacturing wording only · creative and contributor context recorded; relationships unsubstantiated

AoSC's story references the British Museum and its own Sara Cladlow/T.E.C. characters, while its manufacturing section says Bradán Lane STUDIO engraved brass faces and unnamed local high-school students made brass blanks. No reviewed source establishes permission, affiliation, sponsorship, endorsement, authorship allocation, artwork rights, relationship with the British Museum, relationship with a charity/school/DEF CON/CircuitPython, or media-reuse authority.

The dossier preserves source-named narrative and manufacturing context without assigning ownership, cultural/institutional relationship, approval, sponsorship, final manufacturing responsibility, or image rights beyond the published statements.

AoSC 2026 eChallengeCoin page and CircuitPython Coin M0 profile.

student-competition scope caveat · official event page · documented

X-CTF was a student cybersecurity competition rather than a general public hacker conference, but the official event page and badge-maker sources document a real event-specific electronic badge and firmware challenge surface.

The record is included as a Singapore hacker-culture competition badge while keeping the event type explicit.

NUS Greyhats X-CTF page and irq5.io badge writeups.

summit/finals firmware boundary · public release trail and filesystem README · documented

The public repository has both finals and summit firmware assets. The badge record describes the shared GreyMecha/Army badge archive and challenge surfaces without claiming every final attendee image, provisioning step, or private competition backend was public.

Software claims stay limited to the recovered repository, filesystem README, and release assets.

greybadge25 README, RP2350 filesystem README, and GitHub releases page.

target revision, interface, compatibility, and authorization boundary · maker purpose statement and pre-event timing · built against initial public information; final compatibility unknown

The README says the SAO was designed from initial public information about the DEF CON 34 main badge and may be reflashed as challenge information develops. It does not establish that a final badge uses the same port wiring, pull states, wake signal, I²C behavior, firmware, protections, or challenge interface, or that an owner has permission to test it.

Readers should not treat the public source as a compatibility guarantee, a target-specific exploit claim, an endorsement to connect the SAO, or authorization to interact with another attendee's hardware.

NilbinSec DC34 Main Badge Fuzzer SAO README and firmware source.

technical and CTF-linkage gap · official event, schedule, ticket, and CTF-page review · separate CTF documented; badge technology unreported

The official site separately documents the concluded 2026 CTF and a ticket-included Event Badge, but no reviewed source connects them technically or publishes badge hardware, firmware, app, repository, protocol, challenge behavior, source release, maker credit, support path, or safety/privacy characteristics.

No electronic, software, CTF, radio, power, data-use, or operational claim is inferred from the shared conference context.

BSides Chennai 2026 official event, ticket, schedule, and CTF pages.

technical and CTF-linkage gap · official event and ticket-page review · CTF and pickup separately announced; badge technology unreported

The organizer announces a two-phase CTF and separately schedules badge pickup, but no reviewed source technically connects them or publishes badge firmware, application, repository, protocol, hardware, challenge behavior, source release, maker credit, support path, safety information, or privacy characteristics.

No electronic, software, CTF, radio, power, data-use, or operational claim is inferred from common event context.

BSides Mumbai 2026 official event and ticket page.

technical and distribution archive gap · official historical source · documented source limitation

The official history establishes that the Redmond 2025 summit had an electronic badge, but it does not publish the artifact's physical form, components, PCB, power system, firmware, app, challenge, creator, licence, production quantity, ticket or invitation eligibility, recipient allocation, collection, delivery, issue history, or final configuration.

The catalogue records the confirmed electronic-badge milestone without turning a one-sentence historical designation into an invented hardware, software, credential, distribution, or manufacturing dossier.

Red Team Summit official history.

technical source gap · official status page and post-event sources · awaiting public badge archive

Official sources prove the electronic keyboard badge, assembly model, blinkies, UV-resin art layer, and repair response, but do not identify its controller, LEDs, power, radio, display, connectors, PCB files, schematic, BOM, firmware, binary, build process, challenge, or software license. The official badge-status page still says the 2026 information is forthcoming.

The catalogue records the verified artifact and hands-on event context without upgrading a visual or assembly description into unsupported electrical or software claims.

LayerOne 2026 wrap-up, Hardware Hacking Village page, and official badge-status page checked 2026-08-03.

technical-source caveat · public repository archive · needs deeper production archive

The repository exposes Eagle CAD, firmware sketches, and 3D-print files, but this pass did not recover a final BOM, ordered assembly record, firmware release tag, complete user manual, or post-event challenge writeup.

Hardware and software claims remain limited to the public repository files and official talk description.

pdxbadgers/2018-banglet repository tree, sketches README, firmware, and 3D-print README.

technical-source caveat · official source but incomplete · needs artifact archive

The recovered official page proves an all-parts badge kit in the merch bundle, but no component list, schematic, PCB artwork, firmware, battery details, assembly guide, or challenge writeup was recovered.

The record stays narrow and does not invent electronics beyond the official badge-kit language.

CarolinaCon Online 2021 official page and schedule.

technical-source caveat · official source but incomplete · needs artifact archive

The recovered official pages prove a Conference PCB Badge and electronic-badge merch bundle, but do not publish component, firmware, schematic, BOM, battery, image-rights, or challenge-source detail.

The record preserves the artifact while avoiding unsupported claims about hardware design or firmware behavior.

CarolinaCon Online 2 home, about, and schedule pages.

technical-source caveat · official source plus attendee report but incomplete archive · needs badge-team archive

The official schedule proves a specially designed HCV badge and badge CTF contest, and a Veritas attendee report documents the screen, joystick, USB-C/battery power, and clue-exchange behavior, but no source recovered here publishes component identifiers, schematics, firmware, PCB files, production notes, or challenge source.

The catalogue can describe observed user-facing badge behavior while leaving schematic, firmware, and manufacturing details for a later badge-team archive.

BSidesSF 2024 Hardware Challenge Village schedule description and Veritas attendee report.

technical-source caveat · official source but incomplete · needs badge-team archive

The official schedule proves a badge designed specifically for the Hardware Challenge Village CTF, but does not publish component identifiers, schematics, firmware, PCB files, production notes, challenge source, or scoreboard archive.

The catalogue records the verified village badge and leaves hardware/software archaeology for a later source recovery pass.

BSidesSF 2025 Hardware Challenge Village schedule description.

technical-source caveat · public source archive · needs final production archive

The public PCB and firmware archives document the design files and ESP8266 badge behavior, but this pass did not recover BOM notes, assembly instructions, final flashed release tag, manufacturing order, workshop handout count, or post-event challenge results.

Hardware and firmware claims remain limited to the public repository files and official schedule wording.

pdxbadgers/pcb-2015, pdxbadgers/fw-2015 README, badger.ino, and BSidesPDX 2015 schedule.

technical-source caveat · public hardware and firmware archive · needs final production archive

The public repository exposes Eagle board, schematic, BOM, and an Arduino sketch, but this pass did not recover final Gerbers, assembly instructions, production photos, challenge docs, release tags, or a post-event firmware history.

Hardware and firmware claims remain limited to the public repository files plus event-context wording.

pdxbadgers/pcb-2016 BoM.csv, badge.sch, badge.brd, and badge.ino.

technical-source caveat · public hardware archive · needs firmware and production archive

The public repository exposes Eagle board, schematic, BOM, and library files, but this pass did not recover final firmware, challenge docs, production photos, Gerber release, or a talk transcript explaining intended badge behavior.

Hardware and software claims remain limited to the public repository files and official schedule/speaker wording.

pdxbadgers/pcb-2017, BSidesPDX 2017 schedule, and BSidesPDX 2017 speakers page.

technical-source caveat · public source archive · needs final production archive

The public repository exposes KiCad, BOM, LED mapping, and test firmware files, but this pass did not recover final firmware release notes, challenge docs, production photos, or a full talk transcript explaining intended gameplay.

Hardware and firmware claims remain limited to the public repository files and official schedule/speaker wording.

pdxbadgers/badge-2018, BSidesPDX 2018 schedule, and BSidesPDX 2018 speakers page.

technical-source caveat · public source archive · needs final production archive

The public repository exposes KiCad, BOM, and simple firmware files, but this pass did not recover assembly instructions, final firmware release notes, challenge docs, production photos, or talk notes explaining intended gameplay.

Hardware and firmware claims remain limited to the public repository files and official schedule wording.

pdxbadgers/badge-2019 and BSidesPDX 2019 schedule.

technical-source gap · source-backed but incomplete · needs artifact-level archive

The public trail recovered so far does not expose the badge schematic, PCB files, BOM, firmware, chip list, challenge binary, flashing workflow, or production quantity.

The catalogue limits the record to the electronic circuit badge, soldering light-up path, breadboard reuse, and hidden-secrets claims explicitly supported by recovered sources.

BSides Athens 2024 official site and recovered wrap-up PDF.

technical-source gap · source-backed but incomplete · needs artifact-level archive

The public source trail does not expose the badge schematic, PCB files, BOM, component list, firmware, power design, challenge code, or final assembly guide.

The catalogue describes only the participant badge, DIY soldering project, custom configuration, and named design credit supported by official sources.

BSides Tallinn 2022 official page and current BSides Tallinn archive.

technical-source gap · source-backed but incomplete · needs artifact-level archive

The recovered public trail proves an electronic PCB badge, multiple processors, two integrated systems, chip-based challenges, and nickname display, but does not expose schematics, PCB files, BOM, component identities, firmware, challenge binaries, protocol docs, or production files.

The catalogue keeps the record useful without inventing part numbers, exact processors, firmware behavior, or board-source availability.

BSides Prague official Sched page and Hung Ngo organizer retrospective.

technical-source gap · official and post-event source-backed limitation · needs public hardware and firmware archive

The public trail proves a custom hackable electronic shield badge, all-attendee distribution, design credit, and broad programming/flash/test activity, but it does not expose a controller identifier, component list, schematic, BOM, PCB files, power details, stock firmware, binary, source repository, challenge implementation, or reuse license.

The catalogue records the verified artifact and its supported narrative without treating an event description or post-event story as a complete technical release.

BSides Kristiansand 2026 event site and organizer article, Billetto event archive, and published Shield Badge post-event account.

technical-source gap · official source but incomplete · needs badge-team archive

The official badge page proves Patches, soldering tradition, customization, and Voodoo Heart continuity, but this pass did not recover a schematic, BOM, controller, firmware repository, badge guide, battery details, LED count, production count, or complete challenge archive.

The catalogue records the verified 2025 badge artifact and avoids inventing unsupported electronics or firmware behavior.

NolaCon badge page, talks archive, sponsor pack, and badge.gallery inclusion policy.

technical-source gap · official badge guide with limited hardware depth · needs deeper archive recovery

The official badge guide proves an ESP32-powered Cyberpunk Bunny portable CTF with accelerometer, crypto challenges, BLE co-op behavior, and hidden flag path, but no schematic, BOM, PCB files, firmware source, exact module revision, battery details, or production count were recovered.

The catalogue records verified badge behavior without inventing component-level electronics, source-release status, or shipped-hardware internals.

BSides San Diego Badge Challenge page.

technical-source gap · badge-maker production and binary-delivery sources with limited archive depth · binary delivery documented; needs schematic, BOM, source, and deployment recovery

The public sources prove an ESP32 touchscreen badge batch with Wi-Fi, SD card slots, PCBWay assembly, customs/tariff logistics, and a selectable ESP32-S3 binary manifest. They still do not recover a schematic, BOM, Gerbers, source code, changelog, signed release, challenge files, battery details, full component placement record, or source-to-event deployment mapping.

The catalogue records the verified chip-family flashing target and maker-announced continuation while avoiding unsupported board, firmware-source, challenge, and production claims.

Badge Pirates tariff/shipping updates, public 2026 Ad Astra update, and BSidesKC 25 flash manifest.

technical-source gap · official source but incomplete · needs badge-team archive

The official source documents ATTINY85, SAO ports, programming connector parts, reprogrammability, and contest framing, but this pass did not recover a schematic, BOM, Gerbers, firmware repository, flashing guide, badge challenge source, or final production file archive.

Hardware and software claims remain limited to the official badge-page text and avoid unsupported electronics or firmware behavior.

BSidesROC 2019 badge page and public website-source repository.

technical-source gap · official source but incomplete · needs schematic, firmware, and repository recovery

The official ticket page proves a PCB badge with CTFs and features, but this pass did not recover component identifiers, schematic, BOM, Gerbers, firmware, challenge source, badge guide, production photos, or repository evidence.

The catalogue records only the verified official badge scope and avoids unsupported hardware, software, and challenge claims.

SECCON ticket page and current public-source search.

technical-source gap · source-backed but incomplete · needs deeper archive recovery

The public Army source proves the first electronic AvengerCon badge, 8-8-8 naming, scavenger-hunt behavior, hack-bypass option, in-person distribution until supplies ran out, more-than-300 build, and Capt. Richard Shmel maker credit, but it does not publish schematics, BOM, firmware, controller identity, protocol docs, or manufacturing files.

The catalogue records the verified badge lineage without inventing component-level details or open-source status.

U.S. Army AvengerCon VIII public-affairs article.

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves the cyberpunk owl design, glowing pink LED eyes, detailed mechanical artwork, and metallic blue-gray finish, but no schematic, firmware, BOM, controller, battery, challenge protocol, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Recon Village Badge Life page.

technical-source gap · source-backed but incomplete · needs hardware archive

The public source lists badge components and challenge behavior, but no schematic, BOM, PCB files, firmware image, source repository, challenge binaries, or exact chip identity were recovered in this pass.

The hardware and software notes stay at the exact level supported by the public SecOps writeup until a badge-team archive appears.

SecOps Hack the Badge page.

technical-source gap · source-backed but incomplete · needs hardware archive

The recovered source trail proves Badge Sponsor, all-attendee collectible badge framing, and soldering-village context, but does not expose the final badge circuit, component list, schematic, board files, firmware, badge challenge, or shipped quantity.

The catalogue keeps the Agra badge record conservative and avoids converting sponsor/social evidence into unsupported component-level claims.

Archived BSides Agra site and official BSides Agra LinkedIn trail.

third-party game license caveat · repository metadata · license not granted

GitHub's public metadata reports `license: null` for the CyberSlayer repository, and its current repository-root listing has no LICENSE file.

The catalogue can describe the game's badge compatibility and installation workflow, but must not treat its code or README image as cleared for reuse or as a catalogue image asset.

alavesa/cyberslayer GitHub metadata and repository root, checked 2026-08-03.

ticket-tier scope and fulfilment boundary · official ticket-package wording · Early Bird inclusion documented; recipient outcome unrecovered

The named coin belongs to the Early Bird package, which the organizer currently marks sold out. The First and Second Release descriptions do not mention the coin. Reviewed material does not establish Early Bird quantity, eligibility details beyond that package, exact purchaser count, allocation, production inventory, registration pickup, recipient receipt, transfer outcome, loss/replacement policy, shipment, refund treatment, or completed delivery.

The catalogue does not turn a sold-out limited package into proof that every ticket holder, every Early Bird purchaser, or any individual attendee has received a coin.

BSides Cheltenham 2026 official event and ticket-package page.

training-artifact classification · official source · documented

The official page proves a badge created in a training workshop, not necessarily the main attendee credential or a public mass-distributed badge.

The compendium keeps the artifact in the Kiwicon lineage while distinguishing a classroom build from a con-wide badge issue.

Kiwicon 2038 Intro to Badge Hacking page.

treasure-chest interaction, participant, and outcome boundary · maker repository description · venue interaction documented; configuration and player outcome unrecovered

The maker archive says attendees used venue treasure chests to unlock additional LED modes and preserves related source/model material. It does not publish a chest count, placement/deployment record, final companion configuration, connection details, challenge values, player count, participation data, score or completion data, participant identities, prize policy, official result, or ongoing service status. No interaction procedure is reproduced here.

The catalogue records the documented badge game without claiming universal participation, a completed CTF, any individual outcome, or a safe/reproducible operating procedure.

bsides-exeter-2025-badge README and public archive.

vendor-booth classification · source-backed but scoped · documented

The SecOps page proves a Hackable BCPen/CPen badge challenge tied to the SecOps booth at BSides Goa 2024, but does not prove the artifact was the official all-attendee BSides Goa admission badge.

The catalogue classifies this as a vendor-booth challenge badge artifact and avoids overstating event-wide distribution.

SecOps Hack the Badge page and BSides Goa 2024 event site.

village badge classification · source-backed classification · documented

The artifact belongs to the Social Engineering Community Youth Challenge at DEF CON 31 and is not the official DEF CON 31 admission badge.

The compendium keeps the record under its own Social Engineering Community series while cross-linking the DEF CON context.

FluxDecoder repository description and DEF CON forum Youth Challenge listing.

virtual artifact classification · source-backed but incomplete · classified as virtual identity artifact

The recovered public sources prove virtual-only Human Badge sponsorship allocations and official badge/lanyard artwork, but do not prove physical badge distribution, electronic hardware, firmware, a challenge platform, or attendee-wide badge variants.

The dossier keeps ROOTCON 15 in the lineage as a pandemic-era virtual badge/artwork artifact instead of implying a shipped electronic badge.

ROOTCON 15 archive, RC15 Sponsorship Overview, and ROOTCON 15 artwork directories.

virtual-event behavior caveat · project-owner source · historical

The serial CTF mini game was removed when Kernelcon 2020 became virtual, so the record documents planned/offline capability without claiming that the mini game ran at the event.

The badge remains an electronic artifact, but its event-game behavior is kept narrower than the original hardware capability.

ZonkSec retrospective and kernelcon-2020-badge README.

winnable CTF, raffle, allocation, and fulfilment boundary · public team self-submission · acquisition and raffle concepts disclosed; operational terms unreleased

The team says SR-71 is only winnable through its CTF and that a full card collection enters a raffle, but does not publish eligibility, entry conditions, required card set, winner count, badge quantity, cost, allocation, prize terms, odds, schedule, handoff, shipping, receipt, refund, replacement, or final fulfilment evidence.

No contest, lottery, acquisition, ownership, prize, or delivery outcome is implied beyond the narrowly stated planned CTF and raffle concepts.

Public DEF CON 34 BadgeLife roster SR-71 self-submission.

wireless-game caveat · primary game log · documented

The BOTNET log frames wireless activity as badge-only gameplay with custom packet structures and payloads interpreted only by AND!XOR badges, with activation and airplane-mode opt-out behavior.

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.

AND!XOR BOTNET game log.

withheld puzzle files · source-backed · documented

The builder log explicitly says the author was sworn to secrecy and forced to burn Gerber files, so the public record intentionally withholds the art secrets and full board files.

Future archive work should seek official or creator permission before treating private Gerbers, puzzle art, or code meanings as publishable catalogue evidence.

Hackaday.io Official Toorcon Badge? log.

workshop-firmware caveat · repository documentation · documented

The public code is a badge workshop/demo firmware that lights dice LEDs from button input, so it is not treated as proof of every firmware image or challenge shipped during Hack&Roll 2026.

The software section separates the recoverable ESP-IDF workshop code from any unrecovered event firmware or private production tooling.

firmware README and firmware/main/main.c.

youth-attendee allocation, event-outcome, and CTF-linkage boundary · official 2026 event page and flyer · past-date inclusion statement retained; issuance and delivery unrecovered

The flyer says youth attendees receive a fun badge, but supplies no recipient ledger, age or registration rules, adult or chaperone allocation, quantity, pickup or handoff details, delivery outcome, replacement process, or post-event confirmation. The home page's Time Travel: Capture the Flag wording is event context only and does not establish any badge-linked CTF function.

The record preserves a real organizer-published inclusion statement without turning it into proof that a particular youth attendee received an artifact or that it participated in the CTF.

Hak4Kidz Chicago 2026 official event page and flyer, reviewed 2026-08-05.