Chaos Communication Congress

39th 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

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.

39C3 Cyberwatch Badge

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.

39C3 Critical Decentralization Cluster Badge

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

Add-ons & Upgrades

39C3 Cyberwatch Badge source-backed

badge communication

LoRa shard path

Project documentation and README material link a LoRa expansion shard to an adapted Meshtastic path, indicating an explicit long-range radio capability target.

Compatibility: 39C3 Cyberwatch Badge

badge hardware

ESP32-S3 and TROPIC01 secure-element core

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.

Compatibility: 39C3 Critical Decentralization Cluster Badge

39C3 Cyberwatch Badge source-backed

badge hardware

Modular watch architecture

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.

Compatibility: 39C3 Cyberwatch Badge

39C3 Cyberwatch Badge source-backed

badge hardware

SD-card shard interface

The project documentation describes an SD-card form-factor interface used to carry modular add-on boards in place of fixed accessory ports.

Compatibility: 39C3 Cyberwatch Badge

39C3 Cyberwatch Badge needs completion

badge software

Firmware expectation context

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.

Compatibility: 39C3 Cyberwatch Badge

39C3 Hub Digital Badges source-backed

digital badge workflow

Redeem-token and QR workflow

The 39C3 page says assemblies could provide redeem tokens with URLs and QR codes so participants could collect badges through the Hub.

Compatibility: 39C3 Hub profile and assembly pages

post-event firmware

CDC Badge OS public firmware trail

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.

Compatibility: CDC Badge v1.0/v1.1 hardware

Operational history

Issues & Camp Impact

assembly scope, official-credential, and allocation boundary · official 39C3 assembly and talk pages · assembly artifact documented; allocation unrecovered

The official Congress sources call the CDC Badge an electronic conference badge and development board presented by the Critical Decentralization Cluster, but reviewed sources do not identify it as the official CCC Human badge, a general Congress admission credential, a ticket entitlement, a conference-wide handout, an event price, an allocation count, or a recipient ledger.

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.

beta firmware, sensitive-data, and security-critical-use boundary · public firmware README · public source explicitly pre-1.0 beta

The later public CDC Badge OS README states that flashing can wipe stored FIDO2/U2F credentials, TOTP seeds, password-vault entries, GPG keys, and PIN data; it calls the project a proof of concept/demonstrator and says not to use it as-is for production or security-critical deployments.

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.

firmware-release and event-deployment boundary · repository chronology and project statements · post-event public firmware trail; 39C3 deployment unknown

The public CDC Badge OS repository was created after the December 2025 event and describes v1.0/v1.1 hardware, while the RIAT hardware repository links multiple possible firmware projects. The reviewed sources do not provide a signed 39C3 image, installed-version inventory, setup/recovery policy for event recipients, event-specific feature configuration, or a historical deployment release mapping.

Later firmware transparency is useful evidence, but the catalogue does not backdate it into a confirmed Congress software image or user-support commitment.

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

No 39C3 Critical Decentralization Cluster 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 Germany record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

physical revision, production, and unit-configuration boundary · versioned public hardware sources · v1.0/v1.1 source releases public; event-unit mapping unrecovered

RIAT publishes versioned v1.0 and v1.1 hardware sources, KiCad fabrication material, cases, and documentation, but the reviewed public record does not map a specific release, component substitutions, test result, PCB lot, enclosure, battery, production quantity, factory/assembly path, or final configuration to each physical 39C3 unit.

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.

power, charging, and electrical-safety configuration boundary · primary firmware checklist · source-published configuration cautions; deployed settings unrecovered

RIAT's firmware checklist says the BQ25895 default fast-charge current would damage the documented 1200 mAh bundled LiPo and directs firmware developers to lower it; it also covers USB charging-port detection, system-voltage configuration, shipping-mode power-off, and TROPIC01 sleep. The public record does not establish that all 39C3 units had those settings, a matching battery, protection validation, current/thermal testing, compliance review, or safe user configuration.

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.

Resources

Sources