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-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 and event-deployment boundary · repository chronology and project statements · post-event public firmware trail; 39C3 deployment unknown
Later firmware transparency is useful evidence, but the catalogue does not backdate it into a confirmed Congress software image or user-support commitment.
Source note: riatlabs/cdc-badge repository, CDC Badge v1.1 release, and krim404/cdc-badge-os repository metadata and README.
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.
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.
first-run shipping, second-run interest, and fulfillment boundary · official shop and current inventory · first run sold out; second run not committed
The catalogue records a current sold-out/interest state without calling every unit delivered, treating a signup as an order, or claiming a future run will occur.
Source note: Clip-Boy official shop, public inventory endpoint, and storefront source.
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.
flex-PET, battery, USB-C, and assembly safety boundary · designer retrospective and organizer documentation · design context public; certification and safe-use evidence unrecovered
The record preserves the documented artifact without implying that it is certified, risk-free, suitable for unsupervised modification, or a substitute for qualified technical review.
Source note: Jacopo Franco technical retrospective, Hackaday.io project, and End Summer Camp badge-2025 archive.
formal license and image-provenance gap · repository metadata and project image policy · needs explicit license or permission
Source code can be linked as evidence, but no repository media or event imagery is copied into the public catalogue and the badge remains image-free.
Source note: GitHub repository metadata, README, and project image provenance policy.
formal license and repository-media boundary · GitHub metadata and project image policy · needs explicit license or permission
The public source is linked for evidence, but no repository attachment, official-page image, or social-media image is copied into the catalogue and the badge remains image-free.
Source note: C1B3RTR4CKS 2026 badge repository metadata, README, and project image policy.
format and technical detail gap · official schedule and organizer post-event update · no public design or technical archive recovered
The entry is classified only as a generic identity artifact and must not be upgraded into a physical-card or electronic-badge record without more public evidence.
Source note: AfricaHackOn Cybersecurity Summit 2026 official schedule and organizer post-event update.
fulfillment and cross-year use caveat · badge-maker fulfillment and continuation updates · documented; actual 2026 deployment unconfirmed
The record presents real delivery friction and the announced later programme without implying frictionless 2025 distribution or universal 2026 participation.
Source note: Badge Pirates BSidesKC 2025 shipping update, tariff writeup, and 2026 Ad Astra update.
game firmware, update, source, and license gap · maker game claims and public board binary context · CircuitPython build available; eChallengeCoin game/release trail incomplete
The catalogue points to a public board platform without representing the shipped game or final coin as open source, reproducibly buildable, safe to reflash, supported, security-reviewed, or licensed for redistribution.
Source note: AoSC eChallengeCoin page and CircuitPython Coin M0 download profile.
generated-art source and image-provenance boundary · primary repository README · generated artwork remains excluded
No board art, product imagery, source preview, or derivative is treated as a rights-cleared factual hero image merely because the code/design source is public or broadly licensed.
Source note: `aerospace-venoms/BCCC_Temperature_SAO` hardware-design README and badge.gallery image policy.
giveaway, purchase-included, color, and revision relationship boundary · multiple first-party statements but no mapping · separate source claims retained; relationship unresolved
Readers should not assume that a purchased companion is the same as a free-drop item, that every color is available in every channel, or that all public claims describe one identical physical run.
Source note: NilbinSec roster response, Bluesky post, and Spectre Sniffer listing.
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 · official organizer and credited maker posts · maker identified; technical archive still absent
The dossier can credit the institutional hardware contribution without implying a particular ESP family, SAO wiring standard, or technical behavior beyond the public wording.
Source note: Area41 2026 organizer recap and Technische Fachschule Bern hardware update.
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 · official product page and GitHub inspection · no DC34 archive published; shop source offline
The record does not turn marketing references to hardware, firmware, or GPIO into an unverified electronic-badge specification.
Source note: AND!XOR DC34 official product page capture and official GitHub account rechecks.
hardware and firmware archive gap · named post-event account · electronic and hackable classification only
The catalogue deliberately stops at source-described electronic and interactive behavior rather than inventing a technical architecture or user workflow.
Source note: Best of PWNEDCR 0x08 by Simón Correa.
hardware and firmware archive gap · source-backed but incomplete · needs public DCSG1 archive
The dossier describes only the substantiated hardware and software surface instead of inferring a complete board design or claiming that the separate OpenLASIR repository is DCSG1 firmware.
Source note: Cryptocurrency Village 2026 workbook, DEF CON Singapore Official Badge Laser* Tag archive, and OpenLASIR repository.
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 archive gap · current public source pass · firmware, schematic, and EasyEDA project published; Gerbers and BOM absent
The record describes the published design and firmware as badge-team evidence, now linked from the official event page, and keeps fabrication quantity and the link to the Champion allocation open until Ekoparty or further post-event sources confirm them.
Source note: Ekoparty Buenos Aires 2026 event page, organizer-linked Champion ticket page, and marsfactory/ekoparty-badge-2026, checked 2026-10-21.
hardware and firmware deployment boundary · primary public source archive · public design recovered; deployment evidence incomplete
Component-level and high-level runtime claims remain tied to the published archive rather than being represented as a final shipped-unit specification.
Source note: ElectronicCats Badge-UnknownSecurity-Conference-2026 README, hardware source tree, PwnPet project, and commit history.
hardware and firmware documentation gap · official announcement and public tooling · needs final technical archive
The record retains documented engineering surfaces while withholding a complete implementation claim until Car Hacking Village publishes a final technical archive.
Source note: Car Hacking Village badge announcement and `chv_badgetools` README.
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 and firmware source gap · source-conservative public record · needs primary technical archive
The dossier records the real electronic artifact without treating the term electronic, a ticket-page slogan, or social confirmation as a component-level technical description.
Source note: cackalackycon 2026 CFP, Eventzilla listing, organizer updates, and Jeff Shouse report.
hardware and physical-form archive gap · official event posts · electronic lighthouse and pulsing beacon documented; specifications unreleased
The catalogue records the named artifact and interaction wording without presenting a theme or generic electronic terminology as an architecture or hardware specification.
Source note: BSides Maine electronic badge clue and main attendee reveal posts.
hardware and physical-production gap · implemented software target profile · needs artifact or manufacturing documentation
The entry describes only the source-backed interface and target profile rather than reconstructing unsupported electronics or treating generic documentation as a final physical specification.
Source note: friends_badge BadgeSpecification and NFC documentation.
hardware and production archive gap · public guide and repository review · needs hardware archive
The record stays precise about the documented interface while avoiding claims that the current source tree exactly describes each physical unit.
Source note: C1B3RTR4CKS 2026 badge repository, event guide, and PlatformIO configuration.
hardware and software archive gap · official current About page · electronic-badge term published; implementation unreleased
The catalogue does not turn the electronic-badge wording into assumed hardware, source availability, interaction behavior, or security claims.
Source note: BSidesLisbon 2026 About page.
hardware and software archive gap · official current page · electronic-badge term published; implementation unreleased
The catalogue does not turn the word electronic into assumed powered hardware, NFC, a specific controller, a challenge, or a reproducible software stack.
Source note: DragonJARCON 2026 conference and diploma page.