Chaos Computer Club
The official info page identifies CCC and volunteers as Congress organizers; the Badges and you page documents the public Hub badge workflow.
Source39th Chaos Communication Congress · Germany · 2025
Assembly-created Hub achievement 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.
People
The official info page identifies CCC and volunteers as Congress organizers; the Badges and you page documents the public Hub badge workflow.
SourceThe official Badges and you page says assemblies could create badges for visitors, tasks, exploration, and help requests.
SourceIt continues the Congress Hub badge lineage while preserving the classification boundary: the source trail proves a digital souvenir and achievement system, not a physical or electronic admission badge.
No physical or electronic badge hardware is claimed. The artifact is a Hub-managed digital badge system tied to assemblies, participant profiles, QR/redeem-token flows, and community activities.
The official 'Badges and you' page documents registration with the Hub, profile display and badge management, redeem tokens, QR-code redemption, assembly backoffice badge creation, General/Explore/Help categories, and visibility controls.
The page suggests uses such as 'I visited' assembly souvenirs, Mixology exploration badges for the first 50 visitors, help-wanted badges, hackertour badges, and electronic souvenirs for tour participants.
Lifecycle
The 39C3 documentation lists General, Explore, and Help categories for badges created by assemblies through the Hub backoffice.
SourceThe 39C3 page documents Hub profile display, pending badge acceptance, default visibility, per-badge visibility choices, and badge management controls.
SourceThe 39C3 page says assemblies could provide redeem tokens with URLs and QR codes so participants could collect badges through the Hub.
SourceOperational 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.