DEF CON 32 Badge
An official DEF CON 32 electronic badge built around Raspberry Pi RP2350 silicon, a handheld-game-style interface, LEDs, firmware archives, and a DEF CON 32 badge game whose GB Studio project files were published after the event.
DEF CON
The 2024 DEF CON edition whose official electronic badge used Raspberry Pi RP2350 silicon, a handheld-game form factor, firmware/game archives, GB Studio source material, and a public badge patch trail.
Las Vegas Convention Center, Las Vegas, Nevada · United States · 2024
An official DEF CON 32 electronic badge built around Raspberry Pi RP2350 silicon, a handheld-game-style interface, LEDs, firmware archives, and a DEF CON 32 badge game whose GB Studio project files were published after the event.
The Hackbat Badge is an unofficial DEF CON 32 badgelife board documented by the Hackbat project page and GPL-3.0 GitHub repository, with ESP32-C3 Wi-Fi/BLE, OLED display, WS2812 LEDs, six buttons, AA-cell case support, and production files.
redactd's Tindie listing introduces Dante's Inferno as an electronic badge just in time for DefCon 32, inspired by the Dante's Inferno Room. It describes three connected circuit boards, special two-color solder mask on the top two boards, sixty LEDs, an included CR123A battery, a populated SAO v1.69bis port, custom-printed box, laser-cut foam insert, and lanyard. The same maker's public repository documents a USB/UF2 firmware-update procedure and a July 2024 v1.1 release for pre-sale 1.0/1.01 units. A Hacker Couture DEFCON 33 product list later repeats the $100 product and core three-board, sixty-LED, CR123A, and SAO claims. Together, these sources establish one source-backed independent 2024 DEF CON 32 artifact with a later 2025 vendor-list recurrence, not an official DEF CON credential, a second DC33 badge, confirmed distribution at either event, a complete electrical design, a licensed source-code archive, or reusable-image rights.
Retia, LLC's public repository is currently named `DefconBadge2026`, but its immutable first source-release commit calls the project `DEF CON badge (2024)` and its README is titled `DEF CON Badge (2024) — ESP32-S3`. That source snapshot includes KiCad and fabrication material named `2024_def_con_badge_v1`, a badge photograph, and high-level hardware documentation. The official DEF CON archive identifies the 2024 event as DEF CON 32, so the record is attached to that existing edition as a retrospectively documented independent artifact; neither Retia nor DEF CON source reviewed here calls it an official Human badge, an attendee entitlement, or a confirmed event handoff.
Lifecycle
The public DEFCON 32 Badge Game repository contains GB Studio project files and graphical assets for the badge's LVCC-themed game.
The documentation describes a Game Boy-like badge layout with OLED display and six push buttons for attendee interaction.
Community ROM work showed the badge running custom Game Boy ROM code and controlling all nine LEDs beyond the default controls.
The DEF CON media-server badge directory published hardware, firmware, game, music, asset, and later FREEWiLi firmware files for post-event hacking.
The Hackbat README documents the ESP32-C3 WROOM module as the badge core, with 2.4 GHz Wi-Fi, BLE 5.0, and Arduino IDE or ESP-IDF programming paths.
DEF CON described the DC32 badge as the first RP2350 board, while Raspberry Pi sources document the badge as powered by RP2350.
redactd's listing introduces Dante's Inferno just in time for DefCon 32. This establishes a maker-stated independent 2024 event association, not DEF CON issuance, registration inclusion, a Human-badge replacement, admission, organizer endorsement, quantity, or completed handoff.
The Hacker Couture DEFCON 33 list repeats Dante's Inferno Badge at $100 with the core three-board, sixty-LED, CR123A, and one-SAO-port description. This is retained as a later vendor-list recurrence of the DEF CON 32 artifact, not a duplicate DC33 badge, scheduled drop, organizer-issued item, confirmed stock, completed purchase, handoff, or attendee allocation.
The Hackbat documentation lists four WS2812 smart LEDs on the badge board.
The v1.1 release says some pre-sale 1.0 or 1.01 badges should flash the update to fix an unspecified issue, and says `enable, sh ver` can check that the badge is on the 1.1 build. It does not identify the issue, affected count, unit identifiers, changelog, validation, rollback, installed population, or update outcome.
The maker listing and later Hacker Couture list describe three connected boards, special two-color solder mask on the top two boards, sixty LEDs, an included CR123A battery, and one populated SAO v1.69bis port. They do not identify the controller, LED or battery characteristics, power design, SAO pinout, electrical limits, circuit, schematic, BOM, Gerbers, or safety validation.
The listing says the badge comes in a full-color custom-printed box with a laser-cut foam insert and unique lanyard, and says it ships ground in the United States with the battery removed for air shipping. It does not confirm which purchaser or event recipients received every listed component, final packaging variant, shipping availability, completed shipment, or battery compliance outcome.
The maker repository says to power the badge, open a serial connection at 1200 baud to force boot-select mode, mount the resulting USB drive, and drag a released UF2 firmware image onto it. Pre-sale badges with acrylic require manual boot-button access while powering on. The source does not identify the controller, serial device behavior, bootloader implementation, erase/recovery model, verification, signed-image process, support path, or safety implications.
The repository README documents compressing the production files and using the centroid and BOM files to order boards through JLCPCB.
The immutable README describes an ESP32-S3, color touch display, LoRa radio, storage, buttons, LEDs, sound, expansion, and two-AA or USB-C power surface. It is a documented design summary, not a final-batch bill of materials, final hardware revision, safety claim, or configuration guide.
The first public source-release commit preserves KiCad 8, schematic, and fabrication files whose paths identify 2024_def_con_badge_v1. This demonstrates a source-published hardware archive without proving the date of manufacture, board quantity, assembled population, test results, physical distribution, or a right to manufacture derivatives.
The repository's public releases visible in the reviewed source pass are dated July 2026, after the 2024 event. They establish a later public software trail without identifying software installed on any 2024 unit or a current supported operating path.
Retia's current repository name says DefconBadge2026, but its metadata calls the project a Retia 2024 DEF CON badge and the immutable first source-release commit/README explicitly say 2024. This records the source conflict and 2024 provenance without treating the repository label as a 2026 event association.
Operational history
The catalogue records the published battery and shipment wording without treating it as a complete safety, transport, charging, or replacement-battery procedure.
The record preserves the maker-stated 2024 origin and the separate 2025 listing without creating a duplicate DC33 badge or treating either listing as confirmed event distribution.
Source-backed component and interface references remain a bounded design trail rather than a universal physical-badge specification, safety certification, performance claim, manufacturing record, or operating guidance.
Readers can follow the documented update surface without assuming the badge is open source, reproducible, auditable, redistributable, or supported beyond the published high-level instructions.
The catalogue records the verified public badge surfaces and flags that the production and firmware story needs a deeper artifact-level chronology.
The catalogue preserves the battery/USB safety erratum and does not treat all Hackbat boards as identical to the fixed public revision.
The catalogue retains a traceable physical surface without representing it as a complete electrical design, measured power profile, host-compatibility guarantee, or safety validation.
The record has a rights-cleared official upstream raster render with source URL, license, attribution, local source preservation, and optimized WebP delivery while avoiding generated or placeholder imagery.
The catalogue classifies Dante's Inferno as an independent badge tied to public DEF CON market contexts, not as an organizer-issued conference credential, admission item, or universal attendee handout.
The catalogue cites the source archive but does not copy its badge photo, board images, code, fabrication files, artwork, logos, trademarks, screenshots, or a generated approximation.
The entry remains source-backed and image-free rather than copying storefront, repository, release, vendor-PDF, social-media, screenshot, placeholder, or generated imagery.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry remains image-free rather than copying official, press, or community photography without provenance.
The catalogue treats this as an independently documented event-associated badge, not an official DEF CON 32 attendee badge, credential, universal handout, completed distribution, or organizer-endorsed artifact.
The catalogue preserves a documented corrective-update trail without claiming the issue's severity, universal applicability, successful remediation, or a risk-free flashing process.
The catalogue keeps distinct seller/vendor snapshots instead of turning a displayed price or sold-out state into proof of event sale, recipient allocation, or fulfilled ownership.
The record links historical source evidence without presenting a later archive as confirmed 2024 event software, a secure deployment, a supported modification workflow, or operational instruction.
The record preserves the source's 2024 identity and its catalogue placement without silently converting a later repository name into a 2026 badge, an official DEF CON classification, or a verified contemporaneous event artifact announcement.
The catalogue keeps Hackbat as an unofficial DEF CON 32 badgelife record separate from the official RP2350 DEF CON 32 Badge.