Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
DragonJAR's badge page describes an exclusive DragonJARCON 2025 badge with NFC hacking functions and says only 100 exist.
SourceEkoparty sold a limited 500-unit electronic badge as a paid support option while preserving free entry for the 2023 Buenos Aires conference.
SourceBSidesTLV documents the Infinity Glove as a limited electronic badge sold by pre-order only and collected on-site at the event.
SourceThe KKTIX page tied the limited deluxe electronic badge to Premium Pass tickets, while the official events page said a few electric badges would be released for attendee purchase during the conference.
SourceHITCON described the Wallet badge as coming with Royal VIP and Premium Passes, with the KKTIX page documenting limited electronic-board inclusion for VIP and Premium tickets.
SourceROOTCON 19 attendees who did not receive a limited electronic badge at check-in received a simpler non-electronic Type-B badge.
SourceThe RC20 con-goers guide says electronic badges will be first-come at on-site check-in while supplies last and that a Type-B non-electronic badge will be provided as the fallback.
SourceCSIT 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.
SourceSource 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.
SourceThe README separately lists a companion SAO PCB, a six-pin male header, and four RGB LEDs, then says its LEDs light when connected to the main badge's six-pin female header. It does not establish an SAO version, pinout, voltage/current limits, LED model, electrical protection, hot-plug behavior, compatibility with any other host, assembly quality, or final distribution.
SourceThe 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.
SourceThe designer README calls the badge's T-piece Arduino Sopracciglio and Arduino MKR Zero-compatible, while the independent attendee archive also describes a custom board based on Arduino MKR Zero. The record does not infer a chip-level bill of materials, exact board revision, supply behavior, or final population beyond the published statements.
SourceThe README identifies a CH32V003 F4P6 RISC-V MCU and describes 3.3 V SAO-host input stepped to 5 V plus an automatic boost-disable path when USB-C 5 V is detected. It does not publish finalized USB-C hardware, board power budget, current/thermal measurements, fault behavior, host limitations, or safety/compliance results.
SourceThe board source contains a CR2032 holder footprint, a through-hole LED footprint, one 6 mm button, a through-hole SPDT slide switch, and a resistor. The source frames these as an experimentation surface, not a finalized populated circuit, power-budget guarantee, battery-included promise, or validated electrical configuration.
SourceThe Eventbrite listing says an appropriate mode can show deauthentication activity or nearby Flipper Zeros. The archived `camera_badge_rev01` source filters Wi-Fi management/data traffic, counts deauthentication frames while hopping channels, and performs BLE scans that increment a count for two source-labelled Flipper MAC prefixes. That is a source trail, not a validated 2026 alerting, identification, accuracy, privacy, or RF-compliance claim.
SourceThe current list names a screen, an `ESP23 Dev Board /w connector`, switch, PCBs, and headers. The archived DC32 parts/assembly documentation identifies a 1.28-inch 240×240 GC9A01 round TFT plus an ESP32 Lite V1.0.0 / ESP32 REV1 Type-C Wi-Fi/Bluetooth board with LiPo connection and charging circuit. The sources do not map that documented platform to a verified final 2026 production revision.
SourceThe public README lists one PCB, ESP32 Dev Module, round LCD, RFID reader, microSD reader/card, slide switch, Schottky diode, RGB LED, six-pin female SAO header, battery holder, four AAA batteries, foam tape, stand, slides, and RFID sticker tags. It documents a project inventory, not a verified finished unit, component variants, electrical design, safe assembly/operation result, quantity, allocation, or completed event handoff.
SourceThe public technical accounts identify an ESP32-C3, 42 WS2812B LEDs, an I2S microphone, and an accelerometer described as work in progress. They do not establish final component substitutions, feature enablement, calibration, electrical limits, all-unit parity, or a production BOM beyond the public archive's scope.
SourceThe 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.
SourceThe 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.
SourceThe project describes an infinity-mirror LED ring whose blue/cyan water effect follows gravity with damping, with selectable modes, dim/off behavior, motion wake, inactivity handling, watchdog recovery, and sensor-fault indication. This describes public intended software behavior, not final LED optics, battery runtime, motion accuracy, accessibility, production-firmware parity, or operation of a distributed badge.
SourceThe README says palette and effect indices persist in CH32V003 flash memory and identifies a PD3 effect button and PD2 palette button. It does not establish a final firmware build, power-loss behavior across all revisions, input accessibility, user guide, release process, or recipient experience.
SourceThe 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.
SourceSemiTO-V identifies an RP2350 microcontroller and GOWIN GW1N-9 FPGA for the badge. The record does not infer unlisted peripherals, power behavior, safety limits, complete bill of materials, or exact population of every physical unit.
SourceThe public hardware reference describes a 100 mm × 100 mm board, ESP32-C3FH4, ST25R3911B NFC reader, RGB and charlieplex LEDs, sensors, buttons, USB edge connector, and CR2032 holders, and calls the PCB REV 2 dated 2025-05-05. This is linked as a technical documentation trail rather than a production audit or safety certification.
SourceThe firmware defines 85 24-bit LED pixels and fourteen active-low input positions labelled for four personality spheres, four portals, radio, camera, Nyan, Aperture, turret, and cake. The design document calls these button/touch interactions. The sources do not confirm the final physical input technology, LED package, enclosure, brightness, current draw, or accessibility behavior.
SourceThe README consistently specifies eighteen side-emitting addressable LEDs, while using `WS2812-2020` in the overview and `SK6812D-EC3210R` in its feature list. The record retains the shared count and source labels without deciding which part number, brightness, color order, current draw, or final layout was manufactured.
SourceThe committed PlatformIO configuration targets `genericCH32V303CBT6` using the `ch32v` platform and `ch32v003fun` framework; firmware configuration enables the CH32V30x family and declares 128 KiB flash. No source identifies a final flashed event binary, board configuration, toolchain lockfile, test report, or recovery path.
SourceThe repository README and workshop guide describe a hands-on badge-workshop package with a starter template and source material. The record keeps this as source-published workshop context; no reviewed organizer source proves every session date, participant count, or completed workshop outcome.
SourceThe official current page lists a September 14-18, 2026 in-person diploma with 40 total hours, food and coffee-break benefits, conference entry, certificates, and an exclusive electronic badge.
SourceThe 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.
SourceThe June announcement and August event-week guide identify a programmable circuit-board badge with five LEDs, three buttons, a mini screen, Wi-Fi, and USB programming. The partner archive gives a public hardware/software reference, but neither source independently audits every final board or recipient handoff.
SourceWinglet OS 2.0 added ADS-B range and reliability work, Map Scope, GPS View, flight-board improvements, SD-card custom media, Wi-Fi scanning, USB-host reliability fixes, optional 3 A charging, and DC33 SAO support.
SourceHITB describes the device as suited for attacks on devices like Arduino, letting researchers and engineers study abnormal states in a controlled environment.
SourceThe Rust firmware exposes a Rhai scripting engine over USB serial, with bindings for system, inputs, SAO, display, LED, accelerometer, battery, Trx/Rx, and CAN behavior.
SourceThe case was printed in three PLA pieces, used integrated PCB slots and snap clips, and avoided screws or extra assembly hardware.
SourcePips801 publishes drawings, front/back PCB and test-jig directories plus firmware and UI trees; the Software README names an older PlatformIO build/erase/filesystem/upload path. The current public archive does not itself establish final production parity, a stable release, a complete build environment, a warranty-safe flashing path, an explicit license, or permission to republish source media.
SourceThe Ph0xx project describes an Air jewel that could interface with a dust particle sensor and GPS, extending the badge into environmental sensing.
SourceCreators Edition/supporter functionality includes the BME680 environmental sensor for temperature, humidity, pressure, IAQ, and VOC-based air-quality monitoring.
SourceHandler staff badges distributed missions and a chill-room base station reported aggregate progress, turning the badge game into a venue-wide social challenge.
SourceThe 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.
SourceThe official schedule says attendees needed a 0xC badge for entry to the THOTCON 0xC party at Ravenswood Event Center.
SourceThe official storefront says entry is badge-only and that every attendee needs a valid event badge for venue access. It does not explain credential validation, name transfer, whether the listed product alone is sufficient, age/guest/sponsor conditions, venue capacity, door policy, or whether this party badge has any relationship to a DEF CON registration credential.
SourceThe official conference page documents the on-site Gdynia and online split, plus the event registration path used to establish access before any physical floor-badge claim.
SourceThe Eagle 5 repository calls itself the HTH 2026 conference-badge firmware, and its publisher has a multi-year HTH badge archive. The official HTH organization previously forked the publisher's 2025 badge source. Together this supports a conservative badge-team association, not an assertion that HTH owned the 2026 repository or administered all distribution.
SourceBSides Orlando's official site links the GitHub organization, whose profile calls itself the official GitHub organization for Security BSides Orlando and describes its Badge repositories as electronic badge firmware and designs. That organization published the public 2026-badge project. This establishes an organizer-published planned badge-design trail, not attendee inclusion, production completion, a credential function, or delivery.
SourceOfficial Open Sauce pages establish the July San Mateo festival. Caleb Marting's archive names the 2026 badge, and an independent attendee archive calls itself replacement firmware for the 2026 Open Sauce badge. This supports a strong physical-event association without saying the organizer owned either repository or issued the board as a universal credential.
SourceThe badge CTF story used a SpyNet server that logged badge activity and exposed web/application-security challenge material.
Source