DEF CON

DEF CON 32

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

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.

Hackbat DEF CON 32 Badge badge image

Hackbat DEF CON 32 Badge

The Hackbat Badge is an unofficial DEF CON 32 badgelife board documented by the Hackbat project page and GPL-3.0 GitHub repository, with ESP32-C3 Wi-Fi/BLE, OLED display, WS2812 LEDs, six buttons, AA-cell case support, and production files.

Dante's Inferno Badge (DEF CON 32)

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 DEF CON 32 Badge

Retia, LLC's public repository is currently named `DefconBadge2026`, but its immutable first source-release commit calls the project `DEF CON badge (2024)` and its README is titled `DEF CON Badge (2024) — ESP32-S3`. That source snapshot includes KiCad and fabrication material named `2024_def_con_badge_v1`, a badge photograph, and high-level hardware documentation. The official DEF CON archive identifies the 2024 event as DEF CON 32, so the record is attached to that existing edition as a retrospectively documented independent artifact; neither Retia nor DEF CON source reviewed here calls it an official Human badge, an attendee entitlement, or a confirmed event handoff.

Lifecycle

Add-ons & Upgrades

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

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

Hackbat DEF CON 32 Badge source-backed

hardware platform

ESP32-C3 WROOM badge core

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.

Compatibility: Hackbat DEF CON 32 Badge

DEF CON 32 Badge source-backed

hardware platform

RP2350 badge platform

DEF CON described the DC32 badge as the first RP2350 board, while Raspberry Pi sources document the badge as powered by RP2350.

Compatibility: DEF CON 32 Badge

Dante's Inferno Badge (DEF CON 32) maker listing says introduced just in time for DefCon 32

historical event-association record

DEF CON 32 maker launch framing

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.

Compatibility: Dante's Inferno Badge (DEF CON 32)

Dante's Inferno Badge (DEF CON 32) published 2025 product list; sale and handoff unconfirmed

later historical vendor-list record

DEF CON 33 Hacker Couture vendor-list recurrence

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.

Compatibility: Dante's Inferno Badge (DEF CON 32)

Dante's Inferno Badge (DEF CON 32) published July 28, 2024; issue details unpublished

maker firmware release

v1.1 pre-sale corrective release

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.

Compatibility: Dante's Inferno Badge (DEF CON 32)

Dante's Inferno Badge (DEF CON 32) high-level listing and vendor-list claims

maker-described electronic hardware surface

Three-board 60-LED, CR123A, and SAO surface

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.

Compatibility: Dante's Inferno Badge (DEF CON 32)

Dante's Inferno Badge (DEF CON 32) listing wording published; fulfillment unconfirmed

maker-described package and delivery context

Custom box, foam insert, lanyard, and shipment statement

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.

Compatibility: Dante's Inferno Badge (DEF CON 32)

Dante's Inferno Badge (DEF CON 32) README instruction published

maker-documented update workflow

USB UF2 firmware-update procedure

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.

Compatibility: Dante's Inferno Badge (DEF CON 32)

Retia DEF CON 32 Badge source-published design summary

retrospective hardware documentation

ESP32-S3 badge design and interface source trail

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.

Compatibility: Retia DEF CON 32 Badge source-described hardware only; no assertion about every physical unit, accessory, radio setting, or supported operation.

Retia DEF CON 32 Badge public immutable source tree

retrospective native hardware archive

2024_def_con_badge_v1 KiCad and fabrication archive

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.

Compatibility: Retia DEF CON 32 Badge documentation context only; no fabrication, assembly, modification, service, or reuse authorization is implied.

Retia DEF CON 32 Badge July 2026 release surface

retrospective software provenance

Later public software-release timeline

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.

Compatibility: Retia DEF CON 32 Badge source history only; no release-to-unit mapping, connection, configuration, radio, update, recovery, or support procedure is established.

Retia DEF CON 32 Badge immutable source snapshot published after event

retrospective source-provenance record

2024 source identity in a later DefconBadge2026 repository

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.

Compatibility: Retia DEF CON 32 Badge only; DEF CON 32 is the calendar mapping for the source-labelled 2024 artifact, not an organizer-published exact DC32 artifact name.

Operational history

Issues & Camp Impact

CR123A battery, shipping, and safety boundary · maker product/shipping wording · battery included and air-removal wording published; engineering context incomplete

The listing says the badge runs on an included CR123A and says it ships ground with the battery in the United States while the seller will remove the battery for air shipping. It does not identify the cell chemistry/brand/protection, holder, polarity protection, current draw, charging behavior, thermal/short-circuit precautions, storage/transport conditions, replacement compatibility, legal shipping compliance, or test evidence.

The catalogue records the published battery and shipment wording without treating it as a complete safety, transport, charging, or replacement-battery procedure.

DEF CON 32 origin, DEF CON 33 vendor list, and completed-distribution gap · maker launch wording, later vendor list, and seller state · origin and later vendor recurrence documented; event handoffs unconfirmed

The product was introduced for DefCon 32, later appears on a DEF CON 33 Hacker Couture list, and the Tindie page says it sold out in September 2024. This pass did not recover a production count, event schedule, booth location, receipt, purchaser/recipient list, attendee report, pickup/shipping record, vendor after-action, unit history, or proof that the 2025 vendor listing used an identical run or remaining 2024 inventory.

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.

final hardware, power, radio, and physical-unit boundary · Retia immutable README and KiCad source tree · high-level design and fabrication source public; final unit/manufacturing evidence unrecovered

The source documents a hardware design and preserves KiCad/fabrication files, but it does not establish a final board revision, component substitutions, display or radio population, antenna configuration, battery brand/capacity, power-path limits, runtime, charging behavior, power safety, radio compliance, electrical test results, manufacture, quality control, or a physical-unit inventory.

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.

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.

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.

hardware, power, LED, and SAO documentation gap · high-level maker and vendor descriptions · needs engineering documentation and testing

Sources name three boards, sixty LEDs, CR123A, and one SAO port, but do not identify controller, board interconnect, LED part/current, power path, regulator, battery holder/protection, voltage/current limits, USB behavior, SAO pinout/rating, circuit, schematic, BOM, PCB/Gerbers, dimensions, materials, assembly, test matrix, safety guidance, or compliance evidence.

The catalogue retains a traceable physical surface without representing it as a complete electrical design, measured power profile, host-compatibility guarantee, or safety validation.

independent DEF CON association and credential boundary · maker listing and later vendor product list · independent electronic badge associated with DEF CON market contexts

The maker says the badge was introduced just in time for DefCon 32 and a later vendor list places it in a DEF CON 33 product context, but neither 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 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.

license, image, artwork, and branding boundary · GitHub metadata and immutable repository-tree review · no detected repository license; selected image reuse rights unresolved

GitHub metadata reports no detected license and the immutable source tree has no root LICENSE or COPYING file. The README includes a badge photograph, but the source does not pair it with a selected-image reuse basis, named attribution, processing provenance, or permission covering artwork, marks, event naming, or media.

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.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No Dante's Inferno Badge image is published because the reviewed maker listing, repository, release, 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, repository, release, vendor-PDF, social-media, screenshot, placeholder, or generated imagery.

missing rights-cleared image · local project policy · needs licensed original replacement

No Retia DEF CON 32 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.

organizer affiliation, allocation, handoff, and credential boundary · Retia source archive and DEF CON official archive · independent design documentation public; organizer relationship and distribution unverified

Retia's archive documents a badge design and source tree, but reviewed sources do not say DEF CON commissioned, approved, sold, issued, or distributed it. They do not identify a price, quantity, sale, giveaway, ticket tier, pickup, booth, recipient, delivery, replacement, admission, access-control, Human-badge, or Black-badge role.

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.

pre-sale version and flashing boundary · maker README and v1.1 release · some pre-sale versions named; affected issue and upgrade outcome unspecified

The v1.1 release says pre-sale badges with firmware 1.0 or 1.01 should flash an update to fix an unspecified issue, while the README describes an acrylic-dependent manual boot-button path. It does not identify the issue, which serials were affected, firmware integrity, backed-up state, user-data effects, failure recovery, rollback, host compatibility, support, or the number of badges successfully upgraded.

The catalogue preserves a documented corrective-update trail without claiming the issue's severity, universal applicability, successful remediation, or a risk-free flashing process.

price, stock, and fulfillment boundary · maker listing and later vendor list · published $100 and 2024 sold-out state; inventory and delivery unconfirmed

The maker page shows $100 and says the badge has been sold out since September 7, 2024; the later Hacker Couture list also shows $100. Neither source establishes stock relationship, production quantity, buyers, payments, event pickup, shipment, refunds, replacements, resale, support, packaging completion, or completed delivery.

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.

software release, security, and operating-procedure boundary · Retia repository release history and immutable source snapshot · later public package trail; 2024 installed state and supported use unrecovered

The later archive contains examples and optional software packages, and the visible release surface is dated July 2026. No reviewed source identifies a 2024 installed image, source-to-unit mapping, signed release, default state, user-data handling, support policy, recovery policy, or safe current operating procedure. No code, flashing, configuration, connection, radio-use, or recovery directions are reproduced here.

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.

source-year, event-edition, and provenance boundary · immutable Retia source release and official DEF CON archive · 2024 source label retained; exact DC32 naming and contemporaneous publication unrecovered

Retia's public repository name says DefconBadge2026, while its current description, immutable first commit, README, and hardware filenames label the project 2024. DEF CON's official archive makes 2024 DEF CON 32, so the catalogue attaches the artifact to that edition as an explicit calendar mapping. No reviewed Retia or DEF CON page calls this artifact by the exact DC32 name or provides a contemporaneous 2024 publication date.

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.

Resources

Sources