scheduled workshop and post-event fulfillment boundary · official schedule, ANSSI listing, and public source tree · ten sessions and build documentation published; individual attendance and completed handoff unverified
The compendium can preserve a concrete workshop artifact and buildable design without treating a schedule or a public repository as proof that every listed slot ran or that any specific person received and completed a badge.
Source note: leHACK workshop schedule and leLAB page; ANSSI leHACK listing; FCSC-FR hackropole-badge repository.
scheduled-drop and completed-distribution gap · published schedule and seller context · scheduled event activity documented; handoff outcome not recovered
The DEF CON 33 attachment rests on a documented scheduled activity without turning it into a claim of universal attendee distribution or a completed event outcome.
Source note: DEF CON 33 Creator Events List and FrogStar Tindie listing.
scheduled-drop and completed-distribution gap · published schedule and preorder wording · scheduled event activity documented; handoff outcome not recovered
The DEF CON 33 attachment rests on a documented scheduled activity without turning it into a universal attendee distribution or completed event-outcome claim.
Source note: DEF CON 33 Creator Events List and Submarine Badge & Pirate SAO listing.
scheduled-drop and completed-distribution gap · published schedule and seller availability state · scheduled event activity documented; handoff outcome not recovered
The DEF CON 33 attachment rests on a documented scheduled activity without turning it into a universal attendee distribution, event outcome, or sale-allocation claim.
Source note: DEF CON 33 Creator Events List and FightDystopia 2025 Badge listing.
scheduled-drop, current recurrence, and completed-distribution gap · published schedules, seller listing, and vendor list · 2025 activity and planned 2026 recurrence documented; outcomes and revision unconfirmed
The catalogue preserves a 2025 origin and planned 2026 recurrence without turning either schedule entry into a universal attendee distribution, completed event outcome, sale, allocation claim, or distinct DEF CON 34 badge.
Source note: Recovered DEF CON 33 schedule, Badge.Life DC34 Village Schedule, Masonic33 Tindie listing, Hak4Kidz profile, and Hacker Couture product list.
schematic-link caveat · repository source review · documented
Hardware claims use the current hardware specification text and repository tree instead of relying on the stale embedded link alone.
Source note: BSidesFW2025Badge HARDWARE.md and repository tree.
scope boundary · source-conservative public archive · documented caveat
The dossier presents the badge as a real Area41 2018 artifact while keeping image rights and distribution-depth claims narrow.
Source note: Compass Security wrap-up and le-krogoth/proteus repository.
screen import and reveal delay · official podcast, machine-transcribed locally · open; reveal pending
The badge reveal and possibly screen availability depend on a pending cross-border shipment. The organizer calls it not a real killer for the badge process, so the record notes the dependency without forecasting a delivery problem.
Source note: Hackaday Podcast Episode 392, opening segment, transcribed locally from the official MP3 with WisprCLI large-v3.
screen, AAA battery, and power-safety gap · host-linked pre-event battery statement · AAA requirement and screens named; electrical details unpublished
The entry does not turn a bring-your-own-battery reminder into an electrical specification or a safety recommendation.
Source note: IQSEC-host-linked public WomenCon update.
secondary-source technical caveat · contemporary secondary source · needs primary technical corroboration
The entry stays conservative and keeps the official event page as event context while treating the Arduino and running-order claims as secondary-source technical evidence.
Source note: The Register event report and BSides Canberra 2016 event page.
sensor population caveat · RIOT OS board documentation · documented
The hardware description keeps the TVOC claim tied to source context and records that not every physical badge necessarily carried the same populated sensor set.
Source note: 37C3 Hacking the HiP Badge page and RIOT OS HiP Badge docs.
sensor, hardware, power, and electrical-safety documentation gap · current maker description is high-level only · various-sensors wording documented; implementation unreported
The record avoids inventing a sensor suite, electronic design, power path, safety state, accessibility behavior, or data-collection capability from the badge name or historical product association.
Source note: MakeItHackin DEF CON 34 roster response and separately named historical Tricorder SAO sources.
separate TOG hardware-flags boundary · first-hand TOG post-event account · distinct projects not equated
The record preserves related physical-hardware context without merging separate maker provenance, hardware counts, designs, allocations, or authorship into one unsupported badge claim.
Source note: TOG Building Hardware Flags for WICC 2026 post and commit-pinned OzmoOzmo SecurityConferenceCTFBadge README.
service-scaling caveat · event report · documented with caution
The record preserves the voice/audio ambition without overstating default deployed service behavior.
Source note: Hackaday LayerOne 2018 badge report and CharlieX ESP32_Alexa repository.
shipped firmware bugs · repository README · historical
The archive should treat the tagged release as historically important even where later source changes may differ from the build attendees actually used.
Source note: BruCONbadge2018 README and BruCON0xA release.
shipping and fulfillment boundary · primary maker storefront source · needs delivery confirmation
The catalogue preserves the seller-stated schedule and scope without converting it into confirmed pre-event or attendee delivery.
Source note: Pfarrside Creations badge-only product listing.
short-notice hardware caveats · RIOT OS board documentation · historical
The catalogue records the shipped board as a real attendee badge while preserving the known build limitations.
Source note: RIOT OS HiP Badge board documentation.
shutter fit caveat · official customizer notice · documented limitation
Printed shutters may need adjustment; the record makes no fit or tolerance claim.
Source note: PN27 Badge Customizer, checked 2026-10-21.
single-source artifact boundary · first-hand attendee toolkit plus official event page · organizer badge statement outstanding
The catalogue records the observed badge console and LED system without asserting organizer design intent, quantities, ticket-class scope, or any official firmware release.
Source note: OFFZONE official site and d8rt8v offzone-led-customizer, checked 2026-09-26.
soft-brick safety caveat · official walkthrough · documented
The badge page preserves the original risk context for firmware modification instead of presenting the challenge as routine or risk-free.
Source note: CyberThreat A Nice Edit walkthrough PDF.
software and puzzle archive gap · official event posts and agenda · puzzle role documented; implementation unreleased
The entry does not turn the verified puzzle framing into unsupported CTF, firmware, networking, or credential claims.
Source note: BSides Maine badge puzzle post and 2026 agenda.
software archive depth · source-backed but incomplete · needs deeper archive recovery
The record preserves verified software-release context and leaves deeper artifact inventory as an archive task.
Source note: DEF CON 22 event archive and Parallax badge downloads.
software lifecycle caveat · project page and repository · documented
The software record stays tied to the published architecture and shard references instead of inventing an endpoint, app-store, or locked release stream model.
Source note: cyberwatch codeberg docs and 39C3-release_board README.
software release, security, and operating-procedure boundary · Retia repository release history and immutable source snapshot · later public package trail; 2024 installed state and supported use unrecovered
The record links historical source evidence without presenting a later archive as confirmed 2024 event software, a secure deployment, a supported modification workflow, or operational instruction.
Source note: Retia immutable source-release commit/README and public release-history page.
software, NFC protocol, data, privacy, and security gap · public team self-submission · after-con code or firmware mentioned; no implementation material linked at recheck
The catalogue presents only the stated NFC game concept, not a defined communications protocol, software release, privacy practice, security guarantee, or safe operating guidance.
Source note: Public DEF CON 34 BadgeLife roster SR-71 self-submission.
software, artwork, third-party, media, and trademark license boundary · root MIT license, README credit, and project documentation · software/documentation license published; other rights kept separate
The catalogue can cite the software/documentation licensing trail while retaining image, artwork, logo, trademark, and dependency-specific rights boundaries.
Source note: FirstBuild DefCon34-Badge LICENSE, README, THIRD_PARTY_NOTICES, and badge.gallery image policy.
software-source caveat · badge-maker writeup · needs software archive recovery
The catalogue records verified hardware and firmware-access surfaces while avoiding unsupported claims about the badge's full event game or OTA backend.
Source note: Badge Pirates CactusCon 11 Badge writeup.
software-source caveat · repository tree inspection · needs final firmware recovery
The record keeps software claims limited to QA-code context and hardware-programming surfaces.
Source note: BadgePiratesLLC/CactusCon-12 CODE tree.
software-source caveat · repository tree inspection · needs firmware archive recovery
The catalogue records verified hardware/manufacturing evidence while avoiding unsupported claims about badge software behavior.
Source note: BadgePiratesLLC/CactusCon13 repository tree.
software-source caveat · repository tree inspection · needs firmware archive recovery
The catalogue records the verified hardware archive while avoiding unsupported claims about badge applications, games, OTA behavior, or event infrastructure.
Source note: BadgePiratesLLC/CactusCon14 README and repository tree.
soil-sensing feature, field behavior, and outcome boundary · maker repository description · high-level feature documented; use and field result unrecovered
The catalogue makes the source-described badge feature discoverable without inferring tested performance, universal participation, a completed challenge, individual outcomes, or a safe operating workflow.
Source note: bsides-newcastle-2024-badge README and public archive.
soldering, 18650, USB-C, and hardware-safety specification boundary · official BadgeLife guide · parts and safety reminders documented; engineering validation unrecovered
The source-linked record retains the documented physical work without becoming a battery, soldering, USB, SAO, electrical, or repair endorsement.
Source note: Badge.Life DC34 Village Badge guide.
source and media boundary · official event source but incomplete technical archive · needs badge-team archive
The record keeps claims tied to the official archive page, Sched listing, venue page, and MiniBadge standard, and leaves the page image-free until a rights-cleared original photo or official render is available.
Source note: SAINTCON 2021 archive, MiniBadges page, venue page, Sched listing, MiniBadge standard README, and badge.gallery image policy.
source and media boundary · official event source plus community catalogue but incomplete archive · needs badge-team archive
The record keeps hardware claims to official FAQ language, community data-export fields, and the MiniBadge standard instead of inventing missing per-badge technical detail.
Source note: SAINTCON 2023 official site, FAQ, MiniBadge Wiki export, MiniBadge standard README, and badge.gallery image policy.
source and media boundary · official page but incomplete technical archive · needs badge-team archive
The record keeps hardware/protocol claims to the MiniBadge standard and official trading-page wording, and leaves the page image-free until a rights-cleared original photo or official render is available.
Source note: SAINTCON 2024 MiniBadge trading page, linked build-guide PDF, MiniBadge standard README, and badge.gallery image policy.
source archive, binary, and software-release scope · MIT source archive · substantial earlier archive; current release scope undocumented
The catalogue links the preservation source without misrepresenting it as a complete, current, supported, reproducible 2026 field-update package or a full release of every historic CTF component.
Source note: `btv_dc32_badge` README and code quickstart.
source attribution, pre-event availability, and fulfillment boundary · single public post and official event-context source · announced offer; account relationship and outcome unverified
The catalogue records the concrete pre-event offer while leaving attribution, seller relationship, availability, sale, fulfillment, and event outcome explicitly unresolved.
Source note: Sneakreaper limited edition defcon badge! and official DEF CON 34 Las Vegas announcement.
source date discrepancy · official pages and founder announcement · official date retained
The event and badge record follow the repeated official May 31-June 2 date while preserving the conflicting first-hand pre-event wording for future archive recovery.
Source note: NaClCON official pages, Multipass ticket page, and Luke McOmie announcement.
source depth · source-backed but compact · documented caveat
The record keeps its claims to documented kit distribution, assembly, and sample-code behavior rather than inventing on-site gameplay or contest lore.
Source note: BSides PR 2019 badge docs, repository README, and Security BSides wiki page.
source inventory caveat · repository tree and releases · needs deeper artifact inventory
Software and production claims stay tied to README, releases, firmware README, visible hardware tree, and named release assets rather than treating the repository as a fully inventoried manufacturing archive.
Source note: ElectronicCats/Badge-bsides-cdmx-2025 repository tree, firmware README, and releases page.
source license and reuse gap · public repository inspection · needs explicit license statement
The record may describe the publicly visible technical material but does not treat availability as a license to redistribute source, hardware, firmware, or images.
Source note: dczia/mk9-badge repository root, public file tree, and GitHub metadata endpoint.
source preservation and attribution boundary · official registration changed after event; secondary tier capture · official context retained; historical tier details incompletely preserved
The catalogue uses the secondary listing narrowly for its captured ticket wording and price while preserving the absence of a primary artifact specification, maker attribution, delivery record, and reusable image authority.
Source note: HackNWA official event page and registration link; AllEvents ticket listing.
source publication, physical unit, and fulfilment boundary · publisher-controlled repository · public project source; physical and distribution outcome unverified
The catalogue preserves a real source-documented electronic-badge project without presenting it as a delivered product, attendee issue, or verified physical run.
Source note: Aask42 MidWestCoastBadge repository snapshot and MVP note.
source recovery · public archive · needs deeper recovery
The page is sourceable, but the image remains empty until a licensed original badge photo is cleared.
Source note: Fahrplan, media.ccc.de, CCC Event Blog, and archived OpenBeacon site.
source release, deployed-firmware, and interaction boundary · repository chronology and maker wording · post-event Arduino source visible; event deployment and support unrecovered
The catalogue does not expose connection or challenge details, claim a current working service, offer configuration guidance, infer a released event firmware, or treat public source visibility as a broad license or support commitment.
Source note: HackTheBadge commit history, post-event source-release commit, README, and repository metadata review.
source-archive caveat · public-source recheck · needs archive recovery
The record avoids stronger open-hardware or source-release claims until a complete repository or archive mirror is recovered.
Source note: AND!XOR DC27 project logs, Hackaday hands-on review, and current public-source check.
source-archive gap · public-source recheck · needs archive recovery
The record cites the available project logs and model archive while avoiding stronger open-hardware/source-code claims until the missing repository or an archive mirror is recovered.
Source note: AND!XOR DC25 postmortem, Hackaday.io files area, and current public GitHub search.
source-code and production gap · official event archive plus public badge docs · needs badge-team archive
The record preserves verified public hardware and workflow facts without inventing unrecovered firmware internals, board-source details, or manufacturing data.
Source note: SAINTCON 2016 archive, venue map, badge assembly, upload-code, and registration documentation.
source-code archive caveat · official site audit · needs public repository recovery
The record documents source-backed behavior while avoiding claims about open firmware availability.
Source note: Kernelcon 2025 badge about and activities pages.
source-code archive gap · source-backed but incomplete · needs public firmware or schematic recovery
The dossier records the verified badge behavior while avoiding unsupported pinout, firmware, protocol, or source-release claims.
Source note: Hackster Wombat badge writeup, Hackerware badge page, and soldering tutorial PDF.