39C3 Hub Digital Badges
The 39C3 info pages documented a Hub badge system where participants could collect assembly-created digital badges via redeem tokens, profile assignment, QR codes, and challenge or visit workflows.
Chaos Communication Congress
The December 27-30, 2025 Hamburg Chaos Communication Congress whose official info pages documented a Hub badge system for assembly-created digital souvenirs, challenge rewards, and help/exploration badges, alongside independently scoped Cyberwatch and Critical Decentralization Cluster electronic assembly badges.
Hamburg · Germany · 2025
The 39C3 info pages documented a Hub badge system where participants could collect assembly-created digital badges via redeem tokens, profile assignment, QR codes, and challenge or visit workflows.
An electronic badge created for 39C3 as a modular, solderable watch-style device. The project was designed to be reconfigurable with interchangeable daughter boards (called shards) for different use cases.
The Critical Decentralization Cluster's CDC Badge was presented as an electronic conference badge and development board at the completed 39th Chaos Communication Congress. The source-backed open-hardware platform combines an ESP32-S3, TROPIC01 secure element, front-lit e-paper display, twelve-button keypad, LiPo power path, and expansion ports, while public sources do not establish a conference-wide or admission-badge allocation.
Lifecycle
Project documentation and README material link a LoRa expansion shard to an adapted Meshtastic path, indicating an explicit long-range radio capability target.
The public repository documents a Raspberry Pi GPIO header, a SAO port, and a Grove-compatible connector as three expansion paths. It does not establish that any particular add-on was distributed or supported at 39C3.
The official 39C3 CDC Badge presentation and RIAT hardware repository identify an ESP32-S3 development platform paired with a TROPIC01 secure element. The catalogue does not treat that hardware description as a claim about every physical event unit's exact revision or configuration.
The 39C3 Cyberwatch project is documented as a solderable watch-style base badge that is designed to accept interchangeable shard boards through a modular hardware concept.
The project documentation describes an SD-card form-factor interface used to carry modular add-on boards in place of fixed accessory ports.
Project sources indicate a base firmware expectation around congress time and a prebuilt firmware trail for shard use, but they do not confirm a complete public production release artifact set for all build variants.
The 39C3 documentation lists General, Explore, and Help categories for badges created by assemblies through the Hub backoffice.
The 39C3 page documents Hub profile display, pending badge acceptance, default visibility, per-badge visibility choices, and badge management controls.
The 39C3 page says assemblies could provide redeem tokens with URLs and QR codes so participants could collect badges through the Hub.
RIAT publishes KiCad hardware, printable cases, documentation, fabrication-generation material, and v1.0/v1.1 releases under CERN-OHL-P-2.0. This preserves a reproducibility trail without proving final event production parity or a recipient inventory.
krim404's public GPL-3.0 CDC Badge OS describes an ESP-IDF/PlatformIO application stack with hardware-key, identity, plugin, and BLE capabilities, but labels itself pre-1.0 beta and warns of data loss on flashing. It is not a verified 39C3 deployment image.
The official event page describes a front-lit e-paper display and twelve-button keypad; the public hardware repository associates the keypad with a TCA9535 I²C expander.
Operational history
The record preserves the concrete 39C3 assembly artifact while not conflating a cluster badge with CCC's main credential or assuming every attendee received one.
The record may describe the public software capability surface but does not endorse the firmware, vouch for its cryptography, privacy, data durability, or safety, or imply it was the software deployed at 39C3.
The record preserves the system-level artifact without inventing individual badge names, counts, icons, or assembly-specific rewards.
The catalogue models this as an official digital/community badge workflow and avoids hardware claims.
Later firmware transparency is useful evidence, but the catalogue does not backdate it into a confirmed Congress software image or user-support commitment.
The entry remains image-free rather than copying unknown-rights project media, generated previews, or social/press photos.
The Germany record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record stays image-free rather than copying Hub UI screenshots, logos, badge icons, event graphics, or generated approximations.
Open hardware remains a preservation and reproduction trail without becoming a claim that every 39C3 badge exactly matches a current repository release or bill of materials.
The dossier records what is sourced—badge architecture and shard concept—without over-claiming circulation or official distribution scope.
The catalogue surfaces the published operational caution without presenting the badge as electrically validated, safe to charge, or safe to flash under every firmware/configuration combination.
The software record stays tied to the published architecture and shard references instead of inventing an endpoint, app-store, or locked release stream model.