Sec
Listed by media.ccc.de as Stefan 'Sec' Zehl for the Camp 2011 r0ket talk and the 28C3 r0ket++ follow-up.
SourceChaos Communication Camp 2011 · Germany · 2011
CCCamp 2011 electronic badge
A shiny electronic nametag and full-featured microcontroller development board that established the long-lived CCC Camp badge tradition rad1o later built on.
People
Listed by media.ccc.de as Stefan 'Sec' Zehl for the Camp 2011 r0ket talk and the 28C3 r0ket++ follow-up.
SourceListed by media.ccc.de as a speaker for the Camp 2011 r0ket talk.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field.
SourceListed in the Camp 2011 r0ket wiki People field and as a speaker for the r0ket talk.
SourceListed by media.ccc.de as a speaker for the 28C3 r0ket++ talk.
Sourcer0ket turned a camp badge into a shared development target: attendees could write software, build plug-in m0duls, trade code, and keep hacking after camp.
r0ket uses an ARM Cortex-M3, LiPo charged over USB, LCD, 5-way input, RF transceiver, and add-on/shield ideas, as described in public sources.
r0ket's software surface includes manual, code, software, build notes, contributed code, and a simulator, per the public wiki. The r0ket talk on media.ccc.de documents the badge as the CCC-Badge.
The later rad1o announcement explicitly cites how r0ket badges were still being used years after Camp 2011.
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 r0ket documentation describes an electronic badge platform.
Signal sourceThe r0ket platform documentation describes 2.4 GHz radio functionality used by the badge.
Signal sourceThe r0ket public documentation describes a display-equipped badge.
Signal sourceThe r0ket documentation includes firmware and flashing workflow material.
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.
Display modules and related parts for repair and preservation planning.
This badge has a documented display signal. Matched technical signals: LCD.
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: LCD.
Vendor link · selected for technical relevance
Anti-static bags and storage supplies for preserving loose badge PCBs and sensitive components.
This is documented as an electronic or hardware artifact where anti-static storage can support preservation. Matched technical signals: Electronic badge.
Vendor link · selected for technical relevance
Lifecycle
The r0ket wiki tracked hardware hacks, shields, and add-on ideas, making expansion hardware part of the badge culture from the start.
Source28C3 included USB missile launchers for a competition to combine launcher hardware with r0ket; the first 100 published hacks could keep the launcher.
SourceTeam r0ket brought RGB flame m0dules to 28C3 as a purchasable hardware extension for the badge.
SourceThe 28C3 update promised an improved mesh network, l0dables for interactive installations, and support for the next flame generation.
SourceOperational history
The record stays source-backed and image-free rather than copying the archived wiki image, Hackaday images, screenshots, or generated approximations.