Not just specs
Issues & Camp Impact
Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.
event-source split · mixed source trail · documented
The dossier keeps hardware claims tied to the project archive and event claims tied to Pixels Camp and Portuguese event coverage.
Source note: CADLAB, Pixels Camp FAQ, Shifter, and PCGuia.
experimental LED firmware caveat · official badge page · experimental
The record preserves the WLED-style extension idea while avoiding a claim that all badges shipped with that behavior or that it was part of the event firmware baseline.
Source note: Disobey 2026 badge page.
exposed electronics caution · primary repository · documented
The safety note belongs in the record because it affects handling of the physical artifact.
Source note: Ekoparty Badge 2025 repository README/use section.
extension pinout care · primary docs · documented caveat
The badge exposed rich expansion hardware, but safe use depended on reading the correct connector documentation.
Source note: Badge.Team extension-header documentation.
external antenna caveat · primary FAQ · documented
The catalogue records the optional antenna path while preserving the modification risk and RF-protection context.
Source note: AV Badge FAQ external antenna section.
external media caveat · source-backed but rights-limited · documented
The catalogue avoids importing media from social/gallery/press surfaces while preserving source links for future review.
Source note: Grand Idea Studio documentation links and DEF CON 17 official contest-results media list.
field operation caveat · primary user guide · documented
The record presents the badge as a serviceable field device with operational constraints rather than a frictionless consumer gadget.
Source note: PamirAI Distiller BHV Edition user guide.
field-accessory availability · primary docs · historical
The badge game depended on accessories that some attendees needed to borrow from the badge hacking area.
Source note: HackerHotel 2020 getting-started docs.
field-kit dependency · primary docs · documented
The official page recommended a micro USB data cable plus replacement AA batteries or a power bank, so a prepared kit mattered for camp hacking.
Source note: RomHack badge page and RHC22 README.
field-report scope caveat · official docs plus secondary field report · needs schematic-level review
The dossier can use the report for mesh gameplay and relay-interface lore while keeping low-level hardware claims anchored to primary sources.
Source note: Hackaday field report and Badge.Team HackerHotel 2024 docs.
field-use caveats · primary README · documented
The record preserves practical attendee-facing limitations instead of presenting the badge as frictionless hardware.
Source note: nearform/nceubadge2018 README Bugs section.
field-writeup scope caveat · first-hand writeup · documented
The catalogue uses them to enrich firmware and challenge behavior while keeping authoritative hardware-source claims tied to the official NorthSec repository.
Source note: NorthSec competition write-up index and Jean Privat's 2025 badge writeups.
final-hardware archive gap · source-backed but incomplete · needs post-event technical source
The record does not claim processor, display, radio, CTF, battery, or shipped electronic features beyond the public sources.
Source note: BSides Brisbane 2025 Humanitix page and 2025 sponsorship prospectus.
finicky Arduino-clone caveat · badge text quoted in field writeup · historical
The compendium records this as a practical attendee caveat rather than an unresolved defect: the badge was intentionally open and modifiable, but not frictionless.
Source note: Zeta-Two field writeup quoting the challenge badge text.
firmware TODO caveat · primary README · work in progress
The record documents intended and exposed firmware surfaces without implying that every listed protocol or feature was complete during DEF CON 33.
Source note: Differential Destroyer README firmware TODO section.
firmware absence caveat · source-backed but intentionally narrow · documented
The dossier keeps the artifact as a beginner soldering-village blinky badge instead of inventing software behavior.
Source note: Hackster.io blinky-badge writeup and AVTOKYO 2019 event page.
firmware absence caveat · source-backed but intentionally narrow · documented
The dossier keeps the artifact as a beginner soldering-village blinky badge instead of inventing software behavior.
Source note: Hackster.io blinky-badge writeup.
firmware and artifact archive gap · source-backed but incomplete · needs post-event archive
Hardware and software fields stay limited to the official SAO spec until DEF CON publishes final badge files or credible post-event technical documentation.
Source note: DC34 SAO spec PDF and DEF CON media-server badge directory path.
firmware and schematic gap · official badge guide with limited hardware depth · needs deeper archive recovery
The catalogue keeps the strong official badge-guide evidence while avoiding unsupported claims about the unrecovered design files or shipped firmware internals.
Source note: AvengerCon IX Electronic Badge guide and linked hints page.
firmware archive boundary · current public source trail · needs deeper archive recovery
Software and hardware claims stay limited to Hackaday's compatibility statement, the v0j4 architecture notes, and the original Supercon badge context.
Source note: Hackaday Berlin preview, v0j4 details, and 2022 Supercon badge article.
firmware archive boundary · current public source trail · needs deeper archive recovery
Software claims stay limited to the announced revamped firmware, MicroPython lineage, SAO-port flashing statement, and upstream public repository workflow.
Source note: Hackaday Europe 2025 ticket preview and Hack-a-Day/2024-Supercon-8-Add-On-Badge repository.
firmware archive gap · project README · needs deeper recovery
The catalogue describes the software surface conservatively as an intended web-connected scrolling-text target.
Source note: CADLAB README excerpt.
firmware configuration caveat · primary repository snapshot · documented
The record can document Badge Connect behavior and cross-event lineage while keeping firmware-configuration claims conservative.
Source note: badge-EKOParty-2024 firmware Badge Link and Badge Connect sources.
firmware detail gap · source-backed but incomplete · needs deeper archive recovery
The record intentionally avoids detailed firmware claims beyond USB-oriented hackability until stronger primary source is recovered.
Source note: Grand Idea Studio slides, test procedure, and PCWorld coverage.
firmware documentation caveat · primary project page · in progress in source
The record should be revisited if the repository or project page publishes final attendee firmware, recovery, or app documentation.
Source note: MuHack Badge official page.
firmware drift caveat · primary docs · documented caveat
The compendium should treat the preserved API examples as historical firmware behavior, not a guarantee for every reflashed device.
Source note: Disobey 2019 Badge.Team docs.
firmware flashing risk · primary docs · documented
The page should treat firmware updates as a powerful but risky owner workflow, not just a casual app install.
Source note: CH405 Labs BCD-0o27 firmware guides.
firmware lifecycle · primary wiki and field note · post-event maintained
rad1o belongs in the continuing-platform part of badge.gallery: its record should track firmware and HackRF compatibility well after the camp weekend.
Source note: rad1o firmware releases wiki and BitBastelei firmware-upgrade note.
firmware timing caveat · primary-source backed · documented
The record treats the repository and firmware documentation as living event artifacts rather than claiming a frozen pre-event production firmware state.
Source note: Hackaday Communicator Badge reveal and 2025 Communicator Badge firmware repository.
firmware variant caveat · current public source trail · needs deeper archive recovery
Software claims stay tied to the public Europe articles and upstream Communicator Badge firmware repository rather than a separate Europe firmware tag.
Source note: Hackaday Europe 2026 CFP article and 2025 Communicator Badge firmware README.
firmware-and-controversy caveat · source-backed but incomplete · needs deeper artifact inventory
The catalogue records the verified public badge surfaces and flags that the production and firmware story needs a deeper artifact-level chronology.
Source note: DEF CON news and response post, media-server badge archive, badge-game repository, Raspberry Pi RP2350 sources, and community ROM writeup.
firmware-and-final-state caveat · source-backed but incomplete · needs deeper artifact inventory
The catalogue records verified hardware and challenge structure while leaving full artifact preservation and firmware archaeology for a later pass.
Source note: DEF CON forum thread, FaultPoint firmware extraction, Red Balloon Security OFRAK writeup, and Kybr challenge writeup.
firmware-artifact caveat · source-backed but incomplete · needs deeper artifact inventory
The catalogue records verified hardware and hacking surfaces while leaving complete firmware and variant preservation for a later artifact-level pass.
Source note: HOPE XV Electronic Badge wiki, HOPE schedule, and linked open-hardware repository.
firmware-detail caveat · source-backed but incomplete · needs deeper artifact inventory
The compendium records observed behavior and published challenge paths while avoiding unsupported claims about the badge's internal firmware architecture.
Source note: Degenerate Metric writeup, Inverse report, and DEF CON 24 media links.
firmware-feature caveat · source-backed but intentionally narrow · documented
The badge page describes the published public-domain source and visible electronic invitation hardware without upgrading abandoned goals into production behavior.
Source note: DEF CON forum thread and unsynchronized.org source-code archive.
firmware-linkage caveat · primary source · documented
The record preserves an operational caveat that matters for surviving badges and avoids presenting reflashing as a risk-free generic CC1111 workflow.
Source note: Great Scott Gadgets ToorCon 14 badge page, RfCat repository, and CC Bootloader reference.
firmware-patching risk · project-owner writeup · documented
The project owner notes that interrupted flashing could leave a badge in a broken state; EEPROM storage is listed as a future improvement.
Source note: Official PN26 Electronic Badge writeup.
firmware-release scope · repository documentation · needs deeper artifact inventory
Software claims stay tied to the README, release path, and Minino documentation rather than treating the repository as a fully inventoried final production archive.
Source note: ElectronicCats/badge-hackgdl-2025 README, releases page, and Minino firmware guide.
firmware-scope caveat · source-backed but intentionally narrow · documented
The entry records the verified soldering badge and hacking surface without inventing software behavior.
Source note: CarolinaCon 12 badge section and instruction manual.
firmware-scope caveat · repository audit · documented
Software claims remain limited to user-supplied electronics and do not invent a Remoticon 2020 badge firmware platform.
Source note: flummer/remoticon2020-badge repository contents and README.
firmware-source caveat · source-backed but incomplete · needs deeper archive recovery
The catalogue records verified hardware, game behavior, and recovery workflow while leaving full firmware preservation and challenge reconstruction for a later pass.
Source note: Hackaday.io THOTCON 0x8 project links and project logs.
firmware-source caveat · source-backed but incomplete · documented; monitor newly surfaced 2022 badge archives
The record documents verified hardware and archive surfaces while avoiding unsupported badge-game or firmware-behavior claims.
Source note: NorthSec 2022 badge hardware tree, challenge directory, and competition write-ups index.
firmware-source caveat · repository tree and decoded sketches · needs deeper firmware inventory
Software claims stay tied to the README instructions, visible firmware tree, and decoded example sketches rather than treating the repository as a complete final production firmware archive.
Source note: ElectronicCats/Badge-BugCON-2022 firmware tree, Blink_Bug sketch, AudioWAV sketch, and Edge_impulse.txt.
firmware-source gap · project logs but incomplete source recovery · needs artifact-level archive
Software and protocol claims are kept to the public project statements rather than treating development notes as a complete release package.
Source note: Hackaday.io LayerOne 2017 details and logs.
firmware-source gap · official guide but incomplete source recovery · needs badge-team archive
The record describes verified assembly and interaction evidence without inventing unrecovered firmware behavior or treating every MiniBadge as source-open hardware.
Source note: SAINTCON 2022 archive, MiniBadges-of-2022 assembly guide, and MiniBadge standard source trail.
firmware-source gap · source-backed but incomplete · needs archive recovery
The software section records the verified staff-flashing workflow without inventing firmware behavior or challenge internals.
Source note: Hackaday WOPR Summit field report and Russell Handorf WOPR 0x00 build guide.
firmware-source gap · source-limited · unrecovered
Software behavior is kept conservative until firmware or attendee documentation surfaces.
Source note: 2015 HackRVA build post.
firmware-source scope caveat · repository review and project page · documented with caution
The record preserves verified hardware/software surfaces while leaving deeper MSP430 firmware archaeology for later work.
Source note: Great Scott Gadgets badge page and toorcamp2018badge repository.
firmware-version caveat · source-backed but incomplete · needs deeper artifact inventory
The catalogue records the verified hardware and update workflow while leaving complete firmware archaeology for a later artifact-level pass.
Source note: DEF CON 26 archive firmware notice, Hackaday.io solving project, and DEF CON forum curated content.
firmware/backend boundary · public firmware archive · documented
The software section describes the recovered badge firmware without overclaiming complete event infrastructure publication.
Source note: irq5.io firmware writeup and geekman/badger repository.