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.
firmware/manual errata caveat · project-owner discussion · documented
The record treats manuals, firmware binaries, and repository artifacts as living owner-support evidence, not as proof that every recovered file represents a bug-free Pasadena production state.
Source note: BADGE FOR SUPERCON.6 / November 2022 Hackaday.io technical page and repository manuals/firmware archive.
first-run diode errata · primary README · documented fixed-revision note
The catalogue preserves the battery/USB safety erratum and does not treat all Hackbat boards as identical to the fixed public revision.
Source note: Hackbat DEF CON 32 README diode-placement warning.
flashing caveat · primary wiki and firmware repository · documented
The badge was hackable, but deeper firmware work assumed AVR tooling and care around fuse configuration.
Source note: EMF Badge Wiki flashing/fuse notes and SiNE-Firmware repository.
fulfillment caveat · badge-maker fulfillment update · documented
The record presents the badge as a real post-event delivery effort with documented logistics friction instead of implying frictionless on-site distribution.
Source note: Badge Pirates BSidesKC 2025 shipping update and tariff writeup.
guide-title caveat · official page plus PDF context · documented
The catalogue treats the PDF title as an edition-number wording issue rather than a separate 2012 event claim.
Source note: CarolinaCon 12 official page and linked badge.pdf.
hackathon scope caveat · organizer sources · documented
The record is included as a hackable hacker-culture event artifact while keeping the event type explicit.
Source note: NUS Hackers Hack&Roll 2026 recap and Friday Hacks #287 talk page.
hands-on assembly dependency · primary writeup · historical
This is a useful lifecycle record: the badge was partly a shipped object and partly an on-site hardware workshop artifact.
Source note: Hackster.io Gothenburg Skyline Badge writeup.
hardware and firmware archive gap · source-backed but incomplete · needs artifact-level archive
Component and software claims remain intentionally withheld until artifact-level sources appear.
Source note: BSides Porto official site, about page, agenda page, and ticketing page.
hardware and firmware archive gap · first-hand finalist source but incomplete technical archive · needs public challenge archive
Hardware and software claims stay limited to the finalist writeup's challenge description.
Source note: U-Zyn Chua TISC@DEFCON Singapore 2026 Finals writeup.
hardware and firmware archive gap · source-backed but incomplete · needs public technical archive
The catalogue preserves the official badge and activity evidence while avoiding unverified security, blockchain, or component-level claims.
Source note: HITCON CMT 2018 events and ticketing pages.
hardware and firmware source gap · source-backed but incomplete · needs artifact-level archive
The catalogue records the electronic-badge programme while withholding unsupported component, software, distribution, and interaction claims.
Source note: BSidesLisbon 2025 about page, sponsors page, CTF page, and Eventbrite listing.
hardware and firmware source gap · source-backed but incomplete · needs public technical archive
Component and firmware claims remain limited to the public product and announcement text, with no invented electronics or implementation details.
Source note: DEF CON forum announcement, RENXCHANGE product page, and DC33 schedule mirror.
hardware archive gap · source-conservative public archive · needs schematic or BOM recovery
The hardware section intentionally avoids component-level claims beyond public sources until an original hardware archive or transcript is recovered.
Source note: Compass Security wrap-up, Proteus README, and platformio.ini.
hardware archive gap · official walkthroughs · needs deeper archive recovery
Hardware and software fields stay limited to the official challenge walkthrough evidence.
Source note: CyberThreat Echo Service and A Nice Edit walkthrough PDFs.
hardware archive gap · post-event report and attendee observation · needs badge-team archive
The catalogue records observed hardware and software behavior while avoiding unrecovered component, board-source, and manufacturing claims.
Source note: Noroff post-event report, BSides Kristiansand recordings page, and Cryptax technical write-up.
hardware archive gap · official talk abstract · needs deeper recovery
Hardware and software descriptions stay limited to what the sources explicitly support.
Source note: r2con 2017 official page and post-event report.
hardware archive gap · current public archive · needs deeper recovery
Hardware claims stay limited to the organizer posts, repository README, code, component registry, and acknowledgements.
Source note: nushackers/hnr26-badge-workshop repository and Espressif Component Registry entry.
hardware archive gap · source-backed but incomplete · needs technical archive recovery
The dossier keeps the electronic-badge claim tied to official sponsor-kit wording and avoids unsupported hardware or software details.
Source note: ROOTCON 11 archive and partnership kit.
hardware archive gap · source-backed but incomplete · needs technical archive recovery
The dossier keeps the electronic-badge classification conservative and avoids unsupported hardware or software details until a technical archive or first-hand design writeup is recovered.
Source note: ROOTCON 12 archive, ROOTCON 12 quick guide, and Jay Turla / @shipcod3 maker post.
hardware archive gap · source-backed but incomplete · needs technical archive recovery
The dossier keeps the programmable-badge claim tied to the official sponsor prospectus and avoids unsupported hardware or software details.
Source note: ROOTCON 13 archive, quick guide, media directory, and sponsors prospectus.
hardware archive gap · official source but incomplete · needs deeper archive recovery
The dossier records the verified anniversary-badge context while avoiding unsupported component-level claims.
Source note: HITBSecConf2019 Amsterdam archive.
hardware archive gap · official source but incomplete · needs deeper archive recovery
The dossier records distribution and hacking context while avoiding unsupported component-level claims.
Source note: HITBSecConf2018 Dubai archive and regional press coverage.
hardware archive gap · source-backed but incomplete · needs schematic or BOM recovery
The record stays at source-backed hardware surfaces and avoids unsupported component-level claims.
Source note: Hackster Packet Hack Badge project and GitHub firmware repository.
hardware archive gap · source-backed but incomplete · needs schematic or PCB archive
The record keeps hardware claims to the build PDF and repository README instead of inventing board-layout, distribution-volume, or licensing detail.
Source note: RuxBadge instruction sheet, Darkglade source-release post, and ruxconhhv2016 repository.
hardware archive gap · source-backed but incomplete · needs schematic or PCB archive
The record keeps component claims to ESP8266/NodeMCU evidence and avoids unsupported board-layout or production-run detail.
Source note: Ruxcon 2017 HHV page, Darkglade writeups, source-release post, and ruxconhhv2017 repository.
hardware archive gap · source-backed but incomplete · needs primary badge archive
The catalogue records the verified electronic-badge behavior while avoiding unsupported claims about circuit design, parts, firmware, or challenge features.
Source note: BSides Canberra 2016 event page and The Register event report.
hardware archive gap · source-backed but incomplete · needs board repository recovery
The entry keeps claims to the official component list and training context while avoiding unsupported board-revision, driver-source, or manufacturing-quantity details.
Source note: LCA2019 E-ALE page, E-ALE Linux.conf.au 2019 page, and Floral Bonnet walkthrough.
hardware archive gap · source-backed but incomplete · needs stable public hardware archive
The entry describes the public conference-badge programme and keeps component-level claims limited to sourced high-level evidence.
Source note: LCA2021 Open Hardware Miniconf, SwagBadge talks, and Adafruit Daily secondary note.
hardware archive gap · source-backed but incomplete · needs stable public hardware archive
The entry captures the event-backed kit and badge lineage while avoiding unsupported chip-part, board-revision, firmware, or shipped-behavior claims.
Source note: LCA2022 ticketing news, Open Hardware Miniconf page, and schedule/talk pages.
hardware archive gap · source-backed but incomplete · needs public badge-team archive
Hardware and software fields stay limited to the attendee writeup, licensed photos, and public event context.
Source note: elmo writeup, AiSP event listing, and current Off-By-One site.
hardware archive scope · source-backed but incomplete · needs post-event production reconciliation
Hardware claims are limited to preorder text, repository structure, README behavior, and host-guide protocol documentation.
Source note: r/Defcon preorder post, rhgndf/hfsdr README, host guide, and CH32V305 firmware README.
hardware caveat · primary docs · documented caveat
Users running LED-heavy apps needed to understand power limits and hardware context.
Source note: CampZone 2019 hardware mod documentation.
hardware caveats · primary docs · documented caveat
The page is a useful example of good badge documentation: it records what can be hacked and where users should be careful.
Source note: Entropia GPN17 badge page.
hardware detail caveat · official source with limited technical detail · documented
The catalogue records the badge's existence and challenge context without inventing electronics.
Source note: NorthSec past-editions page.
hardware detail caveat · official article but narrow technical detail · needs public technical archive
The record documents the verified village badge artifact without inventing electronics, firmware, production, or distribution details.
Source note: HTX launch article, HTX Public Safety Village page, and HTX preview article.
hardware detail gap · source-backed but incomplete · needs deeper archive recovery
The entry intentionally avoids component-level claims until primary technical documentation is recovered.
Source note: Ekoparty 2023 registration and announcement pages.
hardware errata caveat · repository README · documented
The record presents the badge as a real hardware lab platform with documented errata rather than a polished reference design without caveats.
Source note: LayerOne 2025 GLiTCh BadgE README.
hardware license caveat · GitHub API and repository tree recheck · no visible hardware license
Hardware files are cited as evidence, but repository images are not copied locally and reuse claims stay limited.
Source note: jellyjellyrobot/neander GitHub API and repository tree recheck.
hardware power caveat · source-backed · documented
Surviving-badge hacking and firmware flashing should respect the documented power and flash-write constraints.
Source note: Hackaday production article.
hardware privilege boundary · public badge guide · historical
For a learning badge this is useful lore rather than a production vulnerability: it shows how physical access and debug interfaces were deliberately part of the challenge surface.
Source note: Jump ESP, jump! badge guide.
hardware production caveats · primary writeup · historical
These caveats make the record useful beyond specs: future badge teams can learn from the production failure modes.
Source note: Insinuator TROOPERS19 badge hardware post.
hardware source gap · source-backed but incomplete · needs public hardware archive
Hardware claims stay limited to the product page, pinout text, and firmware constants without inventing board layout, production quantity, or undocumented circuit details.
Source note: Rabbit-Labs product page, badge pins.txt, and globals.h.
hardware variant evidence caveat · README and repository tree · documented with caution
Hardware claims stay tied to visible source files rather than inferring which variant shipped, how many boards were produced, or whether every tree name matches the final production board identity.
Source note: BugCON 2023 README, ESP32-S3 schematic, SAMD11-named RP2040 schematic, and repository tree.
hardware-archive caveat · source-backed but incomplete · needs schematic, PCB, and BOM recovery
The entry can now describe the badge hardware and firmware from primary sources while avoiding unsupported board-layout, production-run, or image-reuse claims.
Source note: Tony Mamacos making-of post, tonym128 firmware repository, 8bitresearch post, and Hackster project.
hardware-detail and archive gap · official badge page but incomplete · needs artifact-level archive recovery
The catalogue records the verified official badge surface without inventing component-level display, input, power, or design-archive details.
Source note: THcon 2026 official B.A.D.G.E. page.
hardware-detail caveat · source-backed but incomplete · needs schematic or firmware recovery
The catalogue records only the verified badge behavior and avoids inventing electronics beyond the public BBV Badge 2025 source.
Source note: Bug Bounty Village BBV Badge 2025 page.
hardware-detail caveat · primary badge page · documented
The catalogue treats the BIC Pick as a physical commemorative and identity artifact, not as an electronic badge unless primary technical documentation appears.
Source note: BIC Pick badge page and BIC Village 2025 event summary.
hardware-detail caveat · source-backed but intentionally narrow · needs schematic or BOM recovery
The catalogue keeps the record as a source-backed kit badge and avoids inventing electronics beyond the published discrete marquee description.
Source note: Hackaday.io BSides Orlando 2018 Badge project.
hardware-detail caveat · official registration source · needs hardware archive recovery
The catalogue records the badge as a real registration-tier artifact without upgrading it into a specific PCB platform or game badge.
Source note: CactusCon registration update and Friday/Saturday registration pages.
hardware-detail caveat · corroborated but incomplete · needs deeper archive recovery
The catalogue avoids claiming pinouts, radio firmware internals, LED counts, or final production files until an official or creator archive is found.
Source note: MaxVT attendee report, Hackaday.io project-owner log, and ShmooCon organizer deck.