noncommercial-license caveat · visible repository license · documented
The catalogue can publish the selected image as a credited noncommercial reference asset, but downstream reuse should preserve the noncommercial restriction and attribution.
Source note: Tipsy Badge LICENSE and tipsy.ino header.
not-a-watch caveat · field report · historical
The page separates card10's wearable form factor from ordinary smartwatch expectations and keeps the focus on sensors, BLE, and hackability.
Source note: Hackaday hands-on card10 field report.
official 2026 repository-association boundary · convergent official-history and publisher sources · badge-team provenance supported; direct organizer 2026 repo link unrecovered
The catalogue records a real HTH 2026 electronic-badge source trail without claiming an organizer-owned repository, a formal event endorsement, or universal official issuance from affiliation alone.
Source note: HTHackers GitHub organization and J5-ShortCircuit fork metadata; syn-ack-zack account; Eagle 5 repository; HTH official site.
official hardware source and deployment boundary · post-event repository plus official event sources · source and production files documented; event-unit deployment scope remains open
The catalogue can document the verified discrete clock module while avoiding claims about universal deployment, event-day source availability, firmware, radio, or an exact recipient ledger.
Source note: bsidesbrisbane/badge-2026 commit 58a7d9b2e9502cb689f52f1f6826bfcaa90e214c, BSides Brisbane 2026 prospectus, Humanitix ticketing, and event-day updates.
official organizer-to-source archive association boundary · official event and convergent public project sources · event and physical badge trail supported; organizer repository link unrecovered
The catalogue records a real event badge and public source trail without turning a convergent designer/attendee archive into an organizer-owned project or general credential claim.
Source note: Open Sauce overview, schedule, and tickets; Caleb Marting archive; putnam attendee archive.
official render caveat · repository audit · documented
The record has a rights-cleared visual without implying that the image is conference-floor photography.
Source note: nsec/nsec-badge hw/2025/badge2025.png, repository LICENSE, and .reuse/dep5.
official repository-association boundary · primary repository self-description plus official event context · direct organizer link unrecovered
The catalogue can report the repository's own official-project claim and its corroborating event relationship without asserting an unproven publication path by the organizer.
Source note: UnknownCon 2026 event page and ElectronicCats Badge-UnknownSecurity-Conference-2026 README.
official timeline date discrepancy · official page plus IEEE partner listing · official home timeline has a year typo; date corroborated externally
The catalogue uses the corroborated January 10, 2026 event date while preserving the primary-page discrepancy instead of silently converting a likely typo into an unverified second event.
Source note: BUG HUNT 2026 official timeline and IEEE club-partner schedule.
official-source caveat · builder-log backed · needs deeper archive recovery
The catalogue keeps the official-badge wording tied to the cited log and avoids claiming complete production ownership, final challenge rules, or released design files.
Source note: Hackaday.io Official Toorcon Badge? log and InfoconDB event metadata.
official-source publication and deployment boundary · commit-pinned official GitHub publication · documented; public source release is post-event
Readers can inspect a real official source release while the catalogue avoids backdating its publication, claiming a particular factory image, or treating one source revision as proof for every badge handed out.
Source note: nsec/badge-2026 commit 4dab9e6c4c0b8efc9a643ee646a49550453ea22c repository tree, commit history, and releases/tags surfaces reviewed 2026-08-04.
online-cap, pickup, QR-claim, and fulfillment boundary · official checkout and Team announcement · online allocation exhausted; handoff still pre-event
The catalogue records a real sold-out online offer without converting it into a complete production or fulfillment report.
Source note: Puzzled Hackers CTF badge checkout and Team meetup announcement.
online-edition distribution caveat · event listing and badge-team source · documented with limits
The record documents a real badge platform but avoids claiming ordinary on-site pickup, universal in-person attendee distribution, or full offline village behavior.
Source note: DOU NoNameCon 2020 listing and TechMaker NoNameBadge 2020 article.
open-hardware lineage caveat · source-backed but incomplete · documented with caution
The catalogue records the public open-hardware path while avoiding stronger claims about every production file until a deeper repository audit is done.
Source note: HOPE XV Electronic Badge wiki and tidklaas/hip-badge GitLab project.
optional add-on sale and fulfillment boundary · organizer ticket listing · offer documented; individual outcome unrecovered
The catalogue can document the real e-badge offer without saying anyone purchased, received, used, or was universally issued the artifact.
Source note: BSides Fort Wayne 2026 organizer ticket listing and calendar timing.
optional identity verification · official how-to page · documented
The dossier separates ticket identity from optional certificate-assurance workflow so the access model is not overstated.
Source note: CampZer0 how-to page.
optional identity verification · official how-to page · documented
The dossier separates ticket identity from optional certificate-assurance workflow so the access model is not overstated.
Source note: Camp++ 2015 how-to page.
optional identity verification · official how-to page · documented
The dossier separates ticket identity from optional certificate-assurance workflow so the access model is not overstated.
Source note: Camp++ 2016 how-to page.
optional-hardware caveat · primary README · documented
The record separates the documented board capability surface from any claim that every workshop board shipped with every optional component populated.
Source note: SpiderOak Demo V2 Board README assembly notes.
organization-role and authorship boundary · source-stated organization-level roles · organization names public; task-level roles unpublished
Credits remain limited to the named organizations and their source-stated roles rather than resolving a collaboration into unsupported individual authorship or ownership claims.
Source note: DOJOConf Panamá official event page and Electronic Cats public post.
organizer affiliation, allocation, handoff, and credential boundary · Retia source archive and DEF CON official archive · independent design documentation public; organizer relationship and distribution unverified
The catalogue treats this as an independently documented event-associated badge, not an official DEF CON 32 attendee badge, credential, universal handout, completed distribution, or organizer-endorsed artifact.
Source note: Retia repository, immutable 2024-labelled source snapshot, and DEF CON 32 official archive.
organizer archive gap · official repositories and designer writeup · hardware and firmware published; BOM file and hardware licence absent
The catalogue cites organizer engineering detail and the designer's quantity directly and leaves hardware reuse terms open.
Source note: hackthenorth/badge-hardware, hackthenorth/badge-firmware, and va3ndf.com writeup, checked 2026-10-21.
organizer association, allocation, and credential boundary · official event home and maker-published repository · event and maker archive documented; organizer linkage and distribution unrecovered
The catalogue records a real source-documented event artifact without converting a maker description into organizer confirmation, universal issuance, a credential claim, or a completed fulfilment record.
Source note: TROPICON official event home and ElectronicCats/Badge_Tropicon-2026 repository.
organizer documentation and completion gap · attendee sources plus official site · attendee-documented; official wrap-up and allocation unpublished
The record treats the badge as a real event artifact without asserting universal allocation, and the edition is not marked completed on official wrap-up evidence.
Source note: GrrCON official site; Redline Cyber Security writeup; securekomodo firmware archive.
organizer issuance and allocation boundary · official event pages plus attributed post-event app documentation · event completed; organizer badge issuance unverified
The catalogue distinguishes attributed post-event device evidence from official organizer confirmation and does not promote the badge into an attendee-wide entitlement or a Workday-published hardware release.
Source note: Workday DevCon official event, pricing, and justification-letter pages plus Mainak Sarkar's devcon-badge-pet README.
organizer-to-maker association, issuance, and allocation boundary · official organizer pages plus maker-published repository · event and electronic-badge context verified; direct project link unrecovered
The catalogue models a real maker-declared event-associated challenge artifact rather than presenting it as organizer-issued, attendee-wide, admission-bearing, or independently confirmed electronic hardware.
Source note: BSides Peoria 2025 ticket announcement; BSides Peoria 2026 sponsor retrospective; Technet8394/HackTheBadge.
package allocation boundary · official conference and diploma pages · diploma scope explicit; standard-ticket equivalence unproven
The entry remains limited to the named diploma package and does not convert general conference-kit, CTF, or entry language into an electronic-badge allocation.
Source note: DragonJARCON 2026 conference and diploma page and official event home.
page-media rights boundary · source-backed but no reusable image basis · needs licensed original replacement
The record remains image-free rather than copying page media, repository assets, screenshots, social photos, or generated approximations without complete provenance.
Source note: BSidesROC 2019 badge page, BSidesROC.github.io repository metadata, and badge.gallery image policy.
page-media rights boundary · local image policy · image withheld
The record remains text-and-source only rather than copying page media, screenshots, social photos, or generated badge art.
Source note: badge.gallery image policy, BSides Goa official site, and SecOps Hack the Badge page.
pandemic-era distribution caveat · source-limited · open
The record is kept as a source-backed badge archive without overstating shipped attendee distribution.
Source note: HackRVA badge2020 repository plus current HackRVA badge overview.
partial-competition archive · repository README and source · partial archive
The record preserves the competition hook without overstating the completeness of the recovered challenge material.
Source note: LayerOne2023 README badge competition note and `keyboard.c` partial parser.
participant allocation and credential boundary · official organizer announcement and maker record · electronic-badge takeaway documented; individual allocation unverified
The catalogue documents a real event-specific electronic artifact without presenting it as a universal attendee entitlement, admission credential, official hardware release, or completed allocation account.
Source note: NUS Greyhats A.YCEP × Greycademy 2026 announcement and Terence Chan Zun Mun's public maker record.
parts-kit and assembly dependency · official brochure · historical
The record models the badge as a build-it-yourself hardware artifact rather than a fully passive giveaway.
Source note: 44CON 2017 brochure.
parts/reward expectation friction · closing talk reaction and field report · historical
The RCA build-up mechanic was part of the fun, but also created expectations around badge parts and prize/reward availability.
Source note: Rabbit Chaos Adventure closing talk and Rabbit Radio report.
party access and DEF CON credential boundary · official event/storefront wording · independent party access context
The catalogue records a DEF CON-adjacent independent party badge rather than representing it as conference registration, an official convention credential, or a substitute for a valid DEF CON badge.
Source note: FloridaMan Party 2026 official page and FloridaMan 2026 storefront.
party-badge classification · repository metadata and README · documented
The catalogue models the artifact as a DC503 party badge and keeps it separate from DEF CON, BSidesPDX, and later DC503 Banglet/5ohBEE lineages.
Source note: pdxbadgers/wagonparty repository metadata, README, and firmware.
party-pager classification · repository description and firmware evidence · documented
The catalogue models 5ohBEE as a DC503 party pager and game artifact while keeping official conference badge lineages separate.
Source note: pdxbadgers/5ohBEE-2019 repository metadata, README, and firmware sketches.
past-date completion and artifact boundary · official event pages rechecked after scheduled dates · scheduled dates elapsed; completion and issuance unconfirmed
The page keeps the Hungarian outdoor camp lineage visible while preventing stale logistics pages from being presented as confirmed event completion, delivered identity artifacts, or PCB badgelife.
Source note: Camp++ 2026 home, ticket, how-to, and CfP pages rechecked 2026-08-25.
patron-tier, source-currency, and handoff boundary · official 2026 conference and ticket pages · past-date benefit statement retained; allocation and fulfillment unrecovered
The catalogue preserves a real organizer-published 2026 patron artifact statement without converting it into proof that every patron, or any particular patron, received a badge.
Source note: BSides Seattle 2026 official conference and ticket pages, reviewed 2026-08-05.
payment-system caution · official wiki workflow · documented
The compendium keeps the badge-history record separate from any operational payment-system use.
Source note: Shadybucks official wiki page.
photo description typo · image source metadata · documented
The image is still usable because the license, attribution, Flickr source, and review status are explicit; the typo is not treated as technical evidence beyond the intended machine-code description.
Source note: Wikimedia Commons File:Berlin, Mar-2023 (52930401548).jpg.
physical artifact and electronics documentation gap · primary product and storefront pages · identity/access artifact only
The record does not invent a PCB, microcontroller, firmware, lanyard, RFID/NFC, app, radio, or other device properties from the word badge alone.
Source note: FloridaMan 2026 Badge product page and official storefront.
physical form and technical-specification gap · official ticket and credential-policy sources · documented source limitation
The catalogue classifies the record as a planned identity artifact and does not invent an electronic or otherwise specified physical badge from policy language.
Source note: DefCamp 2026 ticket page and DefCamp terms and conditions.
physical form, component parity, power, and safety boundary · maker README and source-tree review · high-level parts list visible; physical artifact details unrecovered
The entry records a narrow source-backed electronic challenge-device outline without treating it as a reproducible build, a safe assembly guide, a uniform physical badge, or a completed production run.
Source note: HackTheBadge event-period README, post-event main.ino source, and repository tree.
physical form, hardware, and software documentation gap · primary organizer sources · needs technical documentation
The record does not turn a BadgeLife title, fundraiser context, or pickup plan into an electronic-badge claim, engineering specification, software feature list, or reusable technical archive.
Source note: Eventbrite Electric Fist listing and H4r0ld & V3rbaal organizer profile.
physical hardware, MCU, power, and SAO-interface boundary · commit-pinned README and Arduino-source review · firmware source published; physical artifact and interface unverified
The catalogue records the actual firmware trail without treating source pins or library use as a finished, safe, fabricated, standard-compliant, or plug-and-play add-on.
Source note: DC34-OWASP-SAO commit-pinned README and main.ino source snapshot.
physical hardware, component, SAO interface, and safety boundary · commit-pinned KiCad, schematic, PCB, and Gerber review · design-source files published; physical build and compatibility unverified
The catalogue retains a concrete design-file trail without representing it as a fabricated, tested, safe, standards-compliant, or plug-and-play accessory.
Source note: narengogi/defcon-34-shitty-add-on commit-pinned source tree.
physical hardware, configuration, and production boundary · repository description, commit-pinned code review, and first-person commit history · source-level project with limited local-test claims; physical artifact unverified
Readers can discover the exact source project and its limited publisher-reported hardware work without mistaking either for a completed, compatible, safe, manufactured, or distributed event artifact.
Source note: MadmanTimmy3241/Defcon-badge-V2-RP2040 repository, commit-pinned tree, and 2026-07-21 hardware-test commit.
physical or electronic badge disclosure gap · official completed-event page audit · no physical or electronic conference badge disclosed by reviewed sources
The data model preserves the ticket as an identity artifact and prevents an unsupported claim that HOPE 26 had an electronic or physical conference badge.
Source note: HOPE 26 official event home, HOPE Wiki main page, official schedule, and 2600 ticket listing.
physical revision, production, and unit-configuration boundary · versioned public hardware sources · v1.0/v1.1 source releases public; event-unit mapping unrecovered
Open hardware remains a preservation and reproduction trail without becoming a claim that every 39C3 badge exactly matches a current repository release or bill of materials.
Source note: riatlabs/cdc-badge repository and v1.1 release.
physical-archival status caveat · project docs · documented
The dossier records what is sourced—badge architecture and shard concept—without over-claiming circulation or official distribution scope.
Source note: Cyberwatch project page and 39C3 codeberg documentation.