Not just specs
Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.
The warning shaped distribution, battery handling, user confidence, and the badge's public reputation.
The badge's technical potential was hard to realize while the camp was happening.
Badge-dependent embedded work became timing-constrained for at least one participant; this aligns with public feedback about late handout.
Many attendees could not use the badge as a nametag or as a normal camp hacking object.
The badge is a useful early case study for badge infrastructure as both playful telemetry and a privacy-sensitive camp artifact.
SHA2017 is remembered as successful, but its production story still shows the logistics risk behind ambitious camp badges.
Users were told to remove batteries when storing the badge and to handle the exposed front carefully.
Volunteers spent substantial camp time applying epoxy; users had handling and curing concerns.
The dossier preserves the kind of practical hardware caveat that matters to badge hackers: assembly order and first-power-on state could damage the device.
The conflict forms part of the badge's production history and likely contributed to a hurried replacement effort, but individual claims should not be overstated beyond public evidence.
CampZone 2020 should be represented as a reusable Badge.Team firmware badge with a different input API surface, not as a drop-in match for every BadgePython app.
The badge-linked challenge was praised by some participants but also created discoverability and inclusion friction for others.
LoRa was not a simple out-of-box feature: users needed soldering, antenna choice or tuning, and caution with auto-transmitting firmware such as Meshtastic to avoid RF damage.
RF expansion was intentionally hackable but not risk-free; the compendium records it as a hardware-modification caveat rather than a plug-and-play feature.
Laptop power-management defaults could make a working badge look broken until autosuspend was disabled for the rad1o USB IDs.
Using rad1o as an SDR depended on choosing the correct firmware mode and sometimes adding udev rules or updated SDR packages.
Even non-electronic badges can affect camp operations when printing, laminating, and handout throughput becomes a bottleneck.
Not every app-store entry runs on a stock badge; some represent firmware forks and deeper platform modifications.
Users needed post-event reflashing and troubleshooting before the badge became a stable hacking platform.
MK4 needs lifecycle treatment because the shipped camp experience, app behavior, and post-event firmware state were not identical.
Hardware add-ons and examples may depend on firmware version, so the badge needs lifecycle tracking rather than one-time hardware notes.
Some TiDAL apps changed device storage/update assumptions and required manual asset handling, so app-store links need per-app risk notes.
The first-use path depended on event infrastructure, while post-event users needed to follow a separate reflashing workflow.
Attendees needed a hardware fix for proper audio behavior.
Users wanting add-ons or full LED intensity needed rework guidance and sometimes volunteer help.
This captures a real camp-experience issue: a major badge can be technically strong while still arriving late enough to affect who can hack on it during the event.
The badge's visual polish came with substantial volunteer assembly effort that belongs in the compendium's production history.
The badge shipped, but the record preserves a realistic production-risk story for small-run event hardware.
The physical artifact has a documented handling caveat that belongs with the hardware record.
The record preserves the RF and navigation limits without implying universal aircraft tracking or software-selectable ADS-B bands.
Hardware and firmware features are kept to repeatedly corroborated repository and guide statements instead of overstating uncertain generated prose.
Fri3d 2024 has multiple programming paths, but they are not equivalent: users need to understand whether they are using the managed MicroPython partition or replacing the default firmware.
The catalogue records the game behavior without implying broader real-world botnet capability beyond the AND!XOR badge network described by the project owners.
The record avoids turning the electronic badge into a proven badge-CTF platform or adding unsupported physical-design claims.
The catalogue avoids merging the online CTF archive into the badge record without source-backed badge integration evidence.
The catalogue keeps the CTF flashing-station workflow as source-backed event behavior while avoiding a false claim that the CTF firmware source has already been published.
Software claims stay limited to the recovered TechMaker post, public firmware tree, public CTF writeups, and talk material.
Software claims stay limited to the recovered TechMaker article, public firmware tree, schematic, and CTF write-up repository.
The catalogue preserves the badge-culture artifact while avoiding universal distribution, official handout, or finished-product claims.
The record captures both a failure mode and the on-site support workflow that kept the challenge playable.
The catalogue records the ESP32-WROVER migration as a deliberate capability upgrade while preserving the team's documented engineering tradeoffs.
MCH2022 was accessible as a Python app badge, but its FPGA surface required a higher hardware-tooling skill level.
The record preserves a real manufacturing and bring-up issue as part of the badge history rather than presenting the 0xB build as frictionless.
Users need the supplied external antenna and should avoid sticking it directly to the copper-heavy PCB because that can reduce RF performance.
The badge record keeps those statements source-specific and avoids claiming a single verified final controller until the project publishes a reconciled BOM or final schematic note.
The catalogue records the full hardware and challenge surface without asserting the exact populated OLED variant or the physical distribution scope.
The badge was a real SDR, but practical RF work still required antenna knowledge and sometimes soldered hardware changes.
The catalogue records the intended mesh-chat behavior without implying that every RF condition, channel plan, or conference-floor routing outcome was solved before the event.
The record should not imply identical RF operating conditions, channel plans, or range behavior between Pasadena and Lecco.
The catalogue records the existence of those code paths as evidence only and does not provide operating instructions or imply that transmitting, jamming, or replaying RF signals is lawful in any jurisdiction.