Critical Decentralization Cluster
The cluster's own 39C3 page identifies the CDC Badge repository within its completed Congress assembly context. This does not allocate individual board-design, production, or distribution roles.
Source39th Chaos Communication Congress · Germany · 2025
Open-hardware ESP32-S3 / TROPIC01 assembly badge and devboard
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.
People
The cluster's own 39C3 page identifies the CDC Badge repository within its completed Congress assembly context. This does not allocate individual board-design, production, or distribution roles.
SourceThe public CDC Badge repository attributes project source material to RIAT Institute and publishes it under CERN-OHL-P-2.0. This is a source-project credit, not a claim to every event media or third-party component asset.
SourceThe public krim404 repository publishes CDC Badge OS for v1.0/v1.1 hardware. This credit is limited to the later public firmware source and does not claim it was deployed at 39C3.
SourceThe official 39C3 event page lists Pavel Polach among the CDC Badge presenters; it does not assign an individual hardware, firmware, production, or distribution role.
SourceThe official 39C3 event page lists bobotronic among the CDC Badge presenters; it does not assign an individual hardware, firmware, production, or distribution role.
SourceThe official 39C3 event page lists dllud among the CDC Badge presenters; it does not assign an individual hardware, firmware, production, or distribution role.
SourceIt adds a substantial 39C3 assembly-level badge alongside the Congress Hub's digital badges and the separate Cyberwatch project. The documented hardware, fabrication outputs, and later public firmware make it a durable hackable artifact, while the catalogue keeps its exact event role and distribution scope distinct from the official CCC credential.
The official 39C3 assembly event and the CDC Badge open-hardware repository identify an ESP32-S3 and TROPIC01 secure element, a front-lit e-paper display, a twelve-button keypad, a JST connector for a single-cell LiPo battery, BQ25895 charging/power control, and Raspberry Pi GPIO, SAO, and Grove expansion surfaces. The hardware repository publishes KiCad schematics/layout, printable cases, documentation, fabrication generation, and v1.0/v1.1 releases, but these sources do not prove the exact board revision, component population, battery, or configuration of every 39C3 unit.
The hardware repository links public CDC Badge OS work built with PlatformIO and ESP-IDF. Its later CDC Badge OS source supports a secure-element-oriented application surface including FIDO2/WebAuthn, GPG/SSH, TOTP, a password vault, plugins, and Bluetooth LE features, but its own README labels the firmware pre-1.0 beta and warns that flashing can erase stored data. The catalogue records this as a post-event public software trail, not proof that it was deployed on every 39C3 device or safe for security-critical use.
The Critical Decentralization Cluster took physical form as a 39C3 assembly around privacy, open hardware, and decentralized systems, and its official Congress schedule included a dedicated CDC Badge presentation. That puts the board in the Congress's assembly badgelife rather than making it a substitute for the event's Human or Hub credential systems.
Source-backed hardware metadata
Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.
The official 39C3 assembly event identifies the CDC Badge as an electronic conference badge and devboard.
Signal sourceRIAT's public CDC Badge hardware repository identifies an ESP32-S3 microcontroller.
Signal sourceThe CDC Badge repository documents a Grove-compatible expansion connector.
Signal sourceThe CDC Badge repository documents a SAO expansion port.
Signal sourceThe CDC Badge repository documents the front-lit e-paper display surface.
Signal sourceThe CDC Badge repository documents single-cell LiPo support, while its separate firmware checklist preserves configuration and safety caveats.
Signal sourceThe later public CDC Badge OS source identifies an ESP-IDF firmware stack for CDC Badge v1.0/v1.1 hardware; exact 39C3 deployment remains unverified.
Signal sourceRepair, preservation, and legal lab context
Parts, tools, and supplies that match this badge's documented hardware, protocols, or preservation needs. These are category-level recommendations, not compatibility guarantees.
Headers and connector supplies for SAO repair, add-on testing, and preservation.
This badge has a documented SAO connector. Matched technical signals: SAO.
Vendor link · selected for technical relevance
Display modules and related parts for repair and preservation planning.
This badge has a documented display signal. Matched technical signals: E-paper.
Vendor link · selected for technical relevance
I2C adapter supplies for badge add-ons, sensors, and lab documentation.
SAO workflows often use I2C-compatible add-on testing and bench documentation. Matched technical signals: SAO.
Vendor link · selected for technical relevance
Extension wiring and jumper supplies for testing or displaying SAO add-ons away from the main badge.
Extension wiring is useful for testing and displaying SAO add-ons. Matched technical signals: SAO.
Vendor link · selected for technical relevance
Headers, sockets, and connector supplies for display repair or replacement work.
Display headers and connectors are useful for repair and preservation planning. Matched technical signals: E-paper.
Vendor link · selected for technical relevance
Lifecycle
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.
SourceThe 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.
SourceRIAT 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.
Sourcekrim404'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.
SourceThe 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.
SourceOperational 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.
Later firmware transparency is useful evidence, but the catalogue does not backdate it into a confirmed Congress software image or user-support commitment.
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.
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 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.