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.
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.
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 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.
Operational history
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.
The record stays image-free rather than copying Hub UI screenshots, logos, badge icons, event graphics, or generated approximations.
The entry remains image-free rather than copying unknown-rights project media, generated previews, or social/press photos.
The dossier records what is sourced—badge architecture and shard concept—without over-claiming circulation or official distribution scope.
The software record stays tied to the published architecture and shard references instead of inventing an endpoint, app-store, or locked release stream model.