physical-artifact caveat · source-backed but incomplete · needs deeper artifact inventory
The catalogue records verified badge lineage and customization surfaces while leaving full physical artifact documentation for a later pass.
Source note: DEF CON call for badge designers, badge news, vendor profile, media-server badge assets, and InfoconDB badge-talk metadata.
physical-artifact caveat · source-backed but incomplete · needs deeper artifact inventory
The catalogue records verified badge lineage and interaction surfaces while leaving full artifact photography and challenge reconstruction for a later pass.
Source note: Mar Williams Art announcement, DEF CON creator-talk page, and DEF CON media-server badge directory.
physical-form, hardware, and NFC-role boundary · public team self-submission · NFC game modes named; artifact construction unreleased
The record does not infer an electronic PCB, active reader, passive tag, NFC chip model, radio placement, power budget, safety profile, or interoperability from high-level game wording.
Source note: Public DEF CON 34 BadgeLife roster SR-71 self-submission.
physical-format, artwork, and post-event archive gap · current public source pass · details unrecovered while event is in progress
The catalogue keeps the current entry factual and image-free until a source-backed artifact record and any necessary rights information are available.
Source note: BSides Las Vegas 2026 official home, registration, ticketing, volunteer-guide, and CFP sources; badge.gallery image policy.
pinout documentation caveat · official docs · documented
The catalogue records the pinout as a hacking reference while avoiding manufacturing-grade claims until final design files appear.
Source note: ConfiBadge 2026 pinout page.
planned badge and fulfilment boundary · official 2026 event and registration pages · planned event; post-event evidence pending
The catalogue treats this as a source-backed planned badge challenge rather than a confirmed distributed 2026 conference artifact.
Source note: CyberThreat official event page and SANS CyberThreat 2026 registration page.
planned badge form, electronics, and production specification gap · official organizer sponsorship sources · badge run and logo surface documented; artifact specification unreleased
The record remains a planned identity artifact rather than an inferred electronic badge, a specific physical credential, or a manufactured technical product.
Source note: BSides Peoria 2026 Call For Sponsors post and organizer-hosted sponsorship prospectus.
planned badge, price, stock, and on-site fulfillment boundary · public self-submission and current event timing · pre-event $80 on-site sale statement; outcome unconfirmed
The record preserves a concrete pre-event acquisition statement without treating it as a finished distribution, retail outcome, or attendee entitlement.
Source note: DEFCON 34 Badgelife Form response and Red Team Village DEF CON 34 event page.
planned drop, manufacture, distribution, and event-fulfillment boundary · first-hand project posts · drops and event experience announced, not outcome-confirmed
The catalogue records a real planned artifact system without representing it as manufactured, acquired, delivered, stocked, or experienced by a confirmed attendee population.
Source note: DEF CON 34 Badge Project Early Look and Zombie Badge Info Dump.
planned identity-artifact classification and physical/technical form gap · official 2026 ticket and agenda page · ticket inclusion documented; artifact specification unreleased
The record remains a planned identity artifact rather than an inferred electronic badge or a more specific physical credential unsupported by the official wording.
Source note: Security BSides Kraków official 2026 ticket and agenda page.
planned identity-artifact classification and physical/technical form gap · official 2026 ticket page · ticket inclusion documented; artifact specification unreleased
The record remains a planned identity artifact rather than an inferred electronic badge or a more specific physical credential unsupported by the official wording.
Source note: Security BSides Kraków official 2026 ticket page.
planned identity-artifact classification and physical/technical form gap · official 2026 registration and pass-comparison pages · Student Pass badge pickup documented; artifact specification unreleased
The record remains a planned student-pass identity artifact rather than an inferred electronic badge or a more specific physical credential unsupported by the official wording.
Source note: Black Hat Europe 2026 official registration and pass-comparison pages.
planned identity-artifact classification and physical/technical form gap · official 2026 DEF CON-registration and attendee-resource pages · printed symbol and hole-punch workflow documented; artifact specification unreleased
The record stays an identity artifact with a documented marking workflow rather than an inferred electronic badge or a more specific physical credential unsupported by the official wording.
Source note: Black Hat USA 2026 official DEF CON-registration and attendee-resource pages.
planned issuance, access, and allocation boundary · official ticket and credential-policy sources · event outcome unconfirmed
The record preserves the planned access-credential evidence without claiming universal attendee entitlement, individual receipt, completed event operations, or technical access behavior.
Source note: DefCamp 2026 ticket page and DefCamp terms and conditions.
planned production and fulfillment gap · official current event pages · future event; delivery unverified
The entry preserves a concrete planned event promise without representing it as a completed badge build or universal attendee delivery.
Source note: BSidesLisbon 2026 official home and About page.
planned run, donation, allocation, and fulfillment boundary · maker and organizer source wording · 40-unit plan and may-receive process published; outcomes unconfirmed
The catalogue records the announced limited-run and philanthropic path without treating it as a completed sale, charitable outcome, manufactured quantity, or delivery report.
Source note: 2026 eChallengeCoin page and Choose Your Own Charity submission form.
planned staff identity-artifact classification and physical-form gap · official 2026 volunteer terms · staff-badge commitment documented; form and technology unspecified
The record is deliberately modeled as a planned staff identity artifact rather than an electronic badge or a more specific physical credential unsupported by the organizer's public wording.
Source note: GrrCON official 2026 volunteer terms.
planned v2, price, preorder, and fulfillment boundary · public maker roster and first-hand maker thread · Coming soon and $20 wording published; outcome unconfirmed
The catalogue records a concrete pre-event maker announcement without presenting it as a completed DEF CON sale, a guaranteed preorder, or an attendee entitlement.
Source note: DEFCON 34 Badgelife Form response and u/Truth-Miserable MF Doom SAO v2 Reddit post.
planned/pre-event classification · primary sources · awaiting post-event evidence
The catalogue can track the upcoming Canberra lineage while avoiding claims about final badge hardware, firmware, production, or attendee delivery.
Source note: BSides Canberra 2026 Humanitix ticketing page and official CFP.
planned/pre-event identity-artifact classification · primary source · awaiting post-event evidence
The catalogue can track the upcoming Perth badge without claiming final manufacturing, distribution, electronics, or challenge behavior.
Source note: BSides Perth 2026 event page.
planning, prototype, manufacture, and final-unit boundary · commit-pinned README, hardware tree, and dated project-status document · design source published; prototype and production evidence unrecovered
Public design files are preserved as evidence of a planned artifact without being presented as proof of a fabricated, functioning, final, distributed, or event-deployed badge.
Source note: HRV SSTV Badge README, hardware tree, and project-status document.
platform classification · primary docs · editorial caveat
badge.gallery models it separately from event editions so add-ons, apps, and firmware can continue evolving without rewriting a historical event page.
Source note: Konsool Badge.Team docs.
platform scope · primary docs · documented
Future updates should be modeled as lifecycle resources rather than a static one-weekend artifact.
Source note: Hackaday.io and CH405 Labs hardware/firmware articles.
post-assembly challenge soldering · badge guide · historical
The badge intentionally blurs software play with hands-on hardware rework; the compendium tracks that as a lifecycle/challenge caveat.
Source note: Hackerware Security Fest Piano CTF Badge guide.
post-camp distribution gap · official event page, organizer repositories, and closing slides · camp completed; badge count and handoff details unpublished
The record describes the released design and firmware for a completed camp without asserting a badge count, inclusion with every ticket, or on-site behaviour.
Source note: RomHack 2026 event page, participant FAQ, CTF page, CyberSaiyanIT/rhc2026-badge, rhc2026-resources, and badge.romhack.io, checked through 2026-10-15.
post-event allocation and production boundary · official wrap-up, badge sale notice, and post-conference support page · event completed; aggregate allocation and manufacturing record unrecovered
The catalogue can treat the official electronic Human badge as completed without implying that every registration produced the same physical unit, that every holder received or retained one, or that a public source proves a complete manufacturing and fulfillment record.
Source note: DEF CON 34 news archive and DEF CON 34 Badge Help Page, reviewed 2026-08-24.
post-event app and source-license scope boundary · public repository and MIT license · Glyph source licensed; event artifact and media rights unresolved
The entry remains image-free and keeps app-source licensing separate from badge, event, and media rights.
Source note: devcon-badge-pet repository, README, LICENSE, Workday sources, Pimoroni product page, and badge.gallery image policy.
post-event archive boundary · official badge and event pages · needs deeper source recovery
Hardware claims stay limited to the official component list and pinout table, and software claims stay limited to the official Badge Hub, package-hub, and stated firmware/challenge goals.
Source note: ConfiBadge 2026 page, hardware page, pinout page, Badge Hub, media page, CONFidence FAQ, PROIDEA event page, and official rules PDF.
post-event artifact-source gap · official source but artifact-incomplete · needs artifact-level archive
The catalogue marks the record as source-backed but artifact-incomplete and should be refreshed if badge-team documentation appears.
Source note: BSides Porto official site, Eventbrite event page, and official organizer feed.
post-event confirmation gap · official event page, badge-team guide, and attendee writeup · held per attendee source; official wrap-up and allocation unpublished
The record treats the badge as a real event artifact without asserting attendee-wide or Champion-wide delivery, and the edition is not marked completed until Ekoparty publishes post-event evidence.
Source note: Ekoparty Buenos Aires 2026 event page, organizer-linked Champion ticket page, marsfactory web guide, and zapf.dev writeup, checked 2026-10-21.
post-event distribution gap · official in-event homepage notice · sold out; count unpublished
The record treats the badge as distributed at the event without asserting a quantity or attendee-wide availability.
Source note: JawnCon official homepage, rechecked 2026-10-21.
post-event fulfillment and ticket-tier relationship gap · official registration and FAQ plus commit-pinned attendee community record · event passed; community badge context published, individual handoff unverified
This remains an official advertised ticket-tier artifact record with a bounded community post-event signal, not a claim that every buyer received a particular board, that owl badges map to a specific tier, that tiers were technically distinct, or that fulfillment succeeded.
Source note: SecretCon 2026 registration listing and FAQ plus the commit-pinned SecretCon 26 attendee community README.
post-event fulfillment boundary · primary official sources · scheduled dates elapsed; final outcome unreported
The catalogue preserves a documented hardware project and host tooling without converting a lapsed schedule into a fulfilled-badge, completed-CTF, or delivery claim.
Source note: Car Hacking Village official event listing, sponsorship agreement, badge announcement, and CTF announcement.
post-event media rights boundary · local image policy and post-event source review · documented without local image reuse
The record keeps the already-cleared MIT repository badge photo and does not copy post-event article media as an event-floor replacement.
Source note: LeccoOnline post-event report and badge.gallery image policy.
post-event release scope · repository release trail plus first-hand community post · post-event firmware release found; latest rechecked
The record is stronger for firmware artifacts but remains classified as community/unofficial unless an official DEF CON source identifies it as the official conference badge.
Source note: HFSDR v1.0 and v1.1 release pages, GitHub API releases listing rechecked 2026-05-21, r/Defcon HFSDR preorder post, and DEF CON Singapore event page.
post-event reuse classification · primary workshop source · documented
The record treats 37C3 as lifecycle and reuse evidence while keeping the badge assigned to Hacking in Parallel Berlin 2022.
Source note: 37C3 Hardware Hacking Area Hacking the HiP Badge page.
post-event source gap · official and post-event source wording · documented; monitor deeper archive
The catalogue records only the official development-board, Hackplayers recap, and repository-backed RP2350/RISC-V challenge claims while withholding exact board-design and manufacturing claims.
Source note: h-c0n CTF BADge announcement, Hackplayers post-event write-up, and hcon2026hwctf repository.
post-event source-depth boundary · public-source recovery · dated programme sources plus one profile-surfaced attendee outcome
The entry distinguishes a corroborated reported build from a comprehensive post-event technical, manufacturing, fulfillment, or image-provenance record.
Source note: Reviewed CyberSC, BSidesGVL/Mike Holcomb, and Brian Herring public sources.
post-event status and distribution gap · official site and community firmware notes · event dates passed; no wrap-up
The edition is not marked completed, and the record makes no claim about badge count or allocation.
Source note: ozsecurity.org and jvishnefske/conagotchi design notes, checked 2026-10-26.
post-event usage evidence · primary docs · documented field trail
The entry can keep hardware/software specifics while explicitly tracking remaining gap areas (errata, production notes, and end-user bug/coverage updates that are still not published).
Source note: BornHack 2026 event page, teams page, and Badge.Team Cyber Ægg docs rechecked 2026-08-03.
post-event wifi dependency · primary author source · documented
The record documents the operational dependency that affects reuse of surviving badges.
Source note: AndrewNohawk BSides Badge Config post.
power and electrical-safety documentation gap · public hardware reference · power outline and caveat documented; validation unrecovered
No safety, battery-life, interoperability, or reliable wireless-operation claim is inferred from the visible board documentation.
Source note: BSides Vancouver badge HARDWARE.md and CHANGELOG.md.
power and minibadge caveat · primary documentation · documented
The record preserves operational and add-on-design constraints rather than presenting the badge as a frictionless reference platform.
Source note: SAINTCON 2018 badge README and minibadges README.
power and programming caveat · primary writeup · documented
The record documents practical handling and programming risks rather than presenting the badge as a frictionless reference design.
Source note: Security-Bits H2HC 2018 badge writeup.
power, IR, and user-context boundary · technical README · needs operational and safety context
The catalogue records their existence at a high level but does not publish operational configurations or represent them as tested, unrestricted, or universally fitted features.
Source note: Security Fest 2026 Badge README.
power, charging, and electrical-safety configuration boundary · primary firmware checklist · source-published configuration cautions; deployed settings unrecovered
The catalogue surfaces the published operational caution without presenting the badge as electrically validated, safe to charge, or safe to flash under every firmware/configuration combination.
Source note: CDC Badge firmware checklist and open-hardware repository.
power, interface, and electrical-safety boundary · KiCad component and board-text review · experimentation surfaces documented; operating constraints unreleased
No power, interface, expansion, battery-life, electrical-safety, or universal peripheral-compatibility claim is inferred from source footprints and exploratory board text.
Source note: FAEI26_Clean.kicad_pcb source and project README.
power, motion, LED, factory-test, and electrical-safety boundary · public README and project documentation · behavior and target components documented; safety/test outcome unverified
Public firmware behavior is not a battery-runtime guarantee, electrical-safety endorsement, factory-pass record, motion-accuracy claim, or safe-modification instruction.
Source note: FirstBuild DefCon34-Badge README and software specification materials.
power, sensor, and electrical-safety gap · public archive review · design materials visible; safety validation unrecovered
The record documents a real completed electronic badge collection without treating open project material as independently validated operating, fabrication, repair, or safety guidance.
Source note: MNSEC2025BADGE public source tree and Beelog MNCERT CC Electronic Badge Project.
power, thermal, electrical, and host-safety documentation gap · maker-documented design but incomplete validation material · needs final engineering and test evidence
The record does not convert a component/design narrative into a safety endorsement, universal host-power guarantee, electrical specification, or modification instruction.
Source note: `keeloi79/not-a-crosswalk-sao` README and public source-tree description.