Masonic theme, terminology, and affiliation boundary · maker theme wording only · Freemasonry-inspired presentation; affiliation unsubstantiated
The catalogue documents the source's creative framing without inferring religious, fraternal, organizational, legal, or licensing relationships beyond that stated theme.
Source note: Masonic33 Tindie listing and Hacker Couture DEFCON 33 Product List.
Micro-USB, USB-C, touch-count, and Coin M0 mapping conflict · conflicting linked primary sources · unresolved source discrepancy
Readers should not select cables, infer a connector, design touch software, rely on a touch count, or assume final board parity from either page alone.
Source note: AoSC 2026 eChallengeCoin page and CircuitPython Bradán Lane STUDIO Coin M0 profile.
Mind fundraiser, assembly, participant, and outcome boundary · maker repository description · limited fundraiser account documented; contribution and completion outcome unrecovered
The catalogue retains the source-reported charity context without turning it into a verified fundraising audit, universal attendee experience, exact manufacturing total, completed-badge count, or individual donation claim.
Source note: bsides-cheltenham-2023-badge README and public archive.
Morse-game participation and outcome boundary · maker repository description · venue-sign game documented; participant outcome unrecovered
The catalogue records the documented badge interaction without claiming a completed CTF, universal player participation, or any individual outcome.
Source note: bsides-newcastle-2025-badge README and signs directory.
NFC data, protocol, privacy, and security boundary · official NFC Battle programme and organizer closing update · NTAG215 and completed exchange activity documented; implementation unreleased
The record exposes the completed NFC interaction without implying a specific protocol, data model, privacy practice, security property, reader/writer capability, or safe handling guidance.
Source note: HITCON 2026 events page, NFC Battle description, and HITCON / @HacksInTaiwan closing update.
NFC hardware and implementation gap · founder announcement only · 3D-print/NFC terms announced; technical details unreleased
The catalogue does not turn the word NFC into claims about a powered electronic badge, a contactless credential, a specific radio protocol, personal-data handling, or a reproducible implementation.
Source note: Luke McOmie NaClCON 2026 conference announcement.
OLED variant and distribution gap · repository but incomplete · needs final-population confirmation
The catalogue records the full hardware and challenge surface without asserting the exact populated OLED variant or the physical distribution scope.
Source note: ElectronicCats/badge-recon-2026 repository footprints and release notes.
PAC-MAN theme, authorship, and endorsement boundary · source labels only · maker title documented; rights and relationships unsubstantiated
The dossier preserves the maker's terminology while not asserting ownership, franchise relationship, sponsorship, endorsement, authorship, or permission to reuse artwork/photos.
Source note: NilbinSec roster response, Bluesky post, Spectre Sniffer listing, and maker profile.
Pirate Flag SAO and Gunslinger-B-Gone interaction boundary · seller bundle and interaction prose · bundle and companion named; interface undocumented
The catalogue preserves the named bundle and cross-badge relationship without inventing an interface standard or claiming every companion unit will work together.
Source note: Submarine Badge & Pirate SAO product listing.
Portal theme, audio, and third-party intellectual-property boundary · public design document and asset tree · needs rights/permission clarification
The catalogue describes the maker's published theme at a high level but does not represent the project as officially licensed, authorize reuse of themed art/audio, or make a legal conclusion about the source materials.
Source note: Portal Badge design document and public sound/source project trees.
Portal theme, third-party IP, attribution, and endorsement boundary · maker language and public self-submission only · seller/self-submission wording recorded; authority and rights unsubstantiated
The entry retains factual source wording without claiming that a franchise rights holder, DEF CON, or any other party authorized, sponsored, designed, endorsed, licensed, or approved the SAO or its media.
Source note: BigFuckingBadge DEF CON 34 page, DEFCON 34 Badgelife Form response, and portal-gun-sao-dc33 repository.
Power Glove theme, authorship, and endorsement boundary · source labels only · theme and maker labels documented; rights/relationships unsubstantiated
The dossier preserves the maker's title and event context without asserting ownership, cultural/franchise relationship, sponsorship, endorsement, authorship, or permission to reuse artwork or photos.
Source note: NilbinSec DEF CON 34 roster response and DC32 Power Glove repository.
QMK and final configuration boundary · public project documentation · partially documented
The record distinguishes current CircuitPython documentation and documented hardware capability from an asserted shipping QMK configuration or final delivery configuration, and flags the firmware-label contradiction instead of resolving it.
Source note: DCZia MK9 repository README, firmware README, August 7 relabel commit, and launch announcement.
RAIN, QR, identifier, and data-use boundary · official badge documentation · high-level identifier framing documented; implementation and data practices unpublished
The entry retains the source's non-personal identifier wording without presenting it as a complete privacy assessment, a tracking/non-tracking guarantee, a reader protocol, a data-use policy, or a deployed-service specification.
Source note: IEEE RFID 2026 RFID Badges page.
REV. 0 build and revision caveat · Garoa primary hardware documentation · documented; final 2026 revision unresolved
The record does not turn the documented REV. 0 platform into a claim that every 2026 badge had the same corrected board, components, physical build, or event-ready firmware.
Source note: Garoa Badge REV. 0 documentation and BadgeGaroa_r2 commit-pinned tree.
RF antenna limitations · primary wiki · documented caveat
The badge was a real SDR, but practical RF work still required antenna knowledge and sometimes soldered hardware changes.
Source note: rad1o antennas and troubleshooting wiki pages.
RF experiment caveat · primary-source backed · documented
The catalogue records the intended mesh-chat behavior without implying that every RF condition, channel plan, or conference-floor routing outcome was solved before the event.
Source note: Hackaday Communicator Badge reveal and firmware README RF Frequency Control section.
RF frequency caveat · primary-source backed · documented
The record should not imply identical RF operating conditions, channel plans, or range behavior between Pasadena and Lecco.
Source note: Hackaday Europe 2026 CFP article.
RF legality and safety caveat · product disclaimer plus firmware source · documented
The catalogue records the existence of those code paths as evidence only and does not provide operating instructions or imply that transmitting, jamming, or replaying RF signals is lawful in any jurisdiction.
Source note: Rabbit-Labs product-page legal disclaimer and RocketGod firmware source.
RTC hardware omission · designer writeup · historical
The badge still had useful modes, but the entry records the documented feature limitation instead of implying a fully working clock.
Source note: DORS/CLUC 2025 Badge writeup.
Red Team Village association and credential boundary · official Village context plus self-submitted sale statement · village-associated planned badge; credential status not documented
The catalogue preserves the source-backed Village association without portraying RTV D20 as an official DEF CON credential, admission badge, universal attendee handout, or verified access token.
Source note: Red Team Village @ DEF CON 34 event page and DEFCON 34 Badgelife Form response.
SAINTCON-named archive, 2026 revision, and historical-lineage boundary · public hardware-tree filename and current maker/roster association · current DEF CON 34 listing evidenced; prior/revision history not reconstructed
The record preserves a valuable public source trail without treating an archive filename as proof of a prior conference handout or claiming that the current listed unit is new, unchanged, or technically identical to the archived design.
Source note: Beelzebub hardware tree, product page, and DEFCON 34 Badgelife Form response.
SAINTCON-named archive, 2026 revision, and historical-lineage boundary · public hardware-tree filename and current maker/roster association · current DEF CON 34 listing evidenced; prior/revision history not reconstructed
The record preserves a valuable public source trail without treating an archive filename as proof of a prior conference handout or claiming that the current listed unit is new, unchanged, or technically identical to the archived design.
Source note: Krampus hardware tree, product page, and DEFCON 34 Badgelife Form response.
SAO and companion-artifact compatibility gap · primary maker listing · needs connector and companion documentation
The record does not infer standard-wide interoperability, electrical safety, external-SAO compatibility, or a particular companion SAO configuration from a product-description sentence.
Source note: Spectre Sniffer Badge listing.
SAO host-power, LED, and hardware-safety specification boundary · live maker component and compatibility wording · high-level add-on surface published; electrical validation unrecovered
The record makes the stated add-on surface discoverable without converting a generic compatibility sentence into a universal electrical, mechanical, or safety guarantee.
Source note: Brooke's Bytes Badge Crown SAO Uberflux listing.
SAO orientation, power, current, and host-compatibility boundary · repository README source note · source-reported integration context; full validation absent
The catalogue preserves a relevant source note without declaring the official badge defective, safe for hot-swapping, or universally compatible.
Source note: MalO_SAO repository README and linked DEFCON34 MICD reference.
SAOv3, I2C, host-compatibility, ARP, and hot-plug boundary · maker product page · proposal-level interface with explicit unsupported features
The record does not promote a proposal into a universal standard, treat an advertised feature family as cross-host compatibility, or imply safe hot plugging or ARP support.
Source note: Firefly Jar SAO product page.
SEAL development-source linkage boundary · self-described public project source plus unlinked organizer record · pre-event source exists; physical-prototype assignment unverified
The public source is available as a separately scoped development trail, but this record does not assign its Pico W code, later ESP32 code, BLE behavior, components, or authorship to a specific physical 2026 prototype or all-attendee bare PCB.
Source note: SEAL-Embedded Conference-Badge commits 565a05c1a1349623cbc244925c0e38599ed1f709 and 5c1caea03cd18def8ac66bf23b8e7c5581addcaa; IEEE Rising Stars 2026 Badge Project page.
Sheriff battery, soldering, magnet, and wearable-safety boundary · maker assembly guide · assembly steps published; engineering and safety context incomplete
The catalogue records a source-backed build path without treating it as a complete safety procedure or an endorsement of every battery, body placement, or modification.
Source note: Sheriff SAO Standalone Build Guide.
Star Trek theme, authorship, and endorsement boundary · maker title and product framing only · theme and maker labels documented; rights/relationships unsubstantiated
The dossier preserves source-published terminology and creative context without asserting ownership, franchise relationship, sponsorship, endorsement, sole authorship, or permission to reuse artwork, photos, or video.
Source note: Hak4Kidz DEF CON 34 roster response, H4K-Dave video, and Hak4Kidz Lab Tindie listing.
Star Trek theme, authorship, and endorsement boundary · maker title and 60th-anniversary wording only · theme and maker labels documented; rights/relationships unsubstantiated
The dossier preserves source-published terminology and creative context without asserting ownership, franchise relationship, sponsorship, endorsement, sole authorship, or permission to reuse artwork, photos, or video.
Source note: MakeItHackin DEF CON 34 roster response and historical Tricorder SAO sources.
TensorFlow Lite memory caveat · NearForm technical article · documented
The machine-learning feature is documented as an experimental constrained-device implementation rather than a broad general-purpose on-watch AI platform.
Source note: NearForm Running TensorFlow Lite on NodeWatch/Bangle.js article.
UPDI programming and modification boundary · maker interface label only · UPDI-compatible interface named; use conditions undocumented
The catalogue records an explicit programming surface without presenting it as a risk-free, universally compatible, authorized, or supported reflashing path.
Source note: Masonic33 Tindie listing.
USB HID safety caveat · primary writeup · documented
The record treats the badge as a teaching artifact for keystroke injection and preserves operational risks instead of presenting it as a harmless novelty.
Source note: Security-Bits H2HC 2017 badge writeup.
USB electrical safety caveat · official badge guide · historical
The badge page preserves the original safety context instead of presenting USB HID payload experimentation as risk-free.
Source note: 44CON Getting Started With Your HIDIOT Badge.
Uber Badge caveat · official registry · documented; no 2026 awardee claimed
The catalogue treats Uber Badges as an award lineage attached to the challenge and avoids naming unverified 2026 winners.
Source note: BSides Tampa Uber Badge registry page, rechecked 2026-05-21.
VOC measurement, air-quality, and safety boundary · explicit first-party product disclaimer · novelty use only; no accuracy claim
The entry does not treat a playful indication or a sensor part number as an air-quality monitor, medical/safety device, exposure warning, or replacement for appropriate ventilation and professional guidance.
Source note: Volatile Organic Canary SAO product page.
WHY2025 lineage divergence · secondary hands-on report plus public project context · historical context
The record links the standalone Tanmatsu/Konsool platform to the same Dutch camp badge-history branch as WHY2025 without treating it as the shipped WHY2025 attendee badge.
Source note: Hackaday Tanmatsu hands-on report.
Wi-Fi monitoring, foxhunt, privacy, and authorization boundary · public source implementation and maker description · 2.4 GHz packet counting and BSSID/RSSI behavior documented; use context unreported
Readers can understand the documented research surface without treating it as permission to monitor or follow third-party wireless activity, a privacy-safe product guarantee, a precise locating instrument, or a validated security tool.
Source note: GigaGeiger maker product page, README, and GG_OTA_061025.ino.
Wi-Fi, power, electrical-safety, and privacy boundary · public technical reference and sample archive · capability and power paths documented; operating policy unrecovered
No live network, privacy, lawful-operation, battery-life, charging, or electrical-safety claim is inferred beyond the documented reference behavior.
Source note: Circuit Board Medics commit-pinned Carolina Code Conference 2026 Badge README and organizer event-week guide.
activation and delivery boundary · official product page capture and post-event source recheck · official shop source offline after the event; outcome unreviewed
The catalogue records announced game and logistics context and a post-event source outage, not a completed physical run, completed server activation, delivered firmware, or observed attendee experience.
Source note: AND!XOR DC34 official product page capture and September 25, 2026 shop and GitHub rechecks.
active and Bluetooth protocol boundary · public package documentation · generic protocol material not assigned to event unit
The record does not claim Bluetooth, BLE, a battery, or active-radio behavior for the actual conference badge merely because the reusable package documents additional protocol families.
Source note: friends_badge README, BadgeSpecification, BLE_FORMAT, and NFC_FORMAT documentation.
active documentation · manufacturer manual and update · ongoing
The compendium should revisit the platform periodically rather than treating this page as a frozen historical badge entry.
Source note: Tanmatsu user manual and March 2025 update.
activity material, participant, and outcome boundary · maker repository description · on-day printed-material statement documented; content and outcome unrecovered
The catalogue records the historical printed-material statement without exposing activity instructions or inferring universal participation, a completed challenge, individual outcomes, or current availability.
Source note: bsides-cheltenham-2024-badge README and public archive.
add-on scope caveat · event report · documented
The catalogue avoids implying that every 2019 badge had an onboard camera, Wi-Fi-capable core, or face-recognition hardware.
Source note: Hackaday LayerOne 2019 badge report and charlie-x/layerOne2019 source trail.
advocacy, beneficiary, proceeds, and attribution boundary · maker-published product statement · maker statement not independently verified
The catalogue can transparently preserve the maker's stated context without recasting it as an independently verified political, legal, charitable, or organizational claim.
Source note: #NOICE SAO product page and its linked beneficiary URL.
ai-authored firmware provenance · repository README · documented as machine-authored
The catalogue preserves this provenance explicitly rather than presenting the firmware as a purely hand-written engineering artifact.
Source note: dissecto GmbH scapycon-2026-badge-firmware README and breachlabz ScapyCon26-EVSE README.
allocation and CTF-access boundary · official CTF announcement · needs post-event fulfillment report
The catalogue does not infer universal distribution, a guaranteed participant badge, a completed CTF, or a final allocation count from the announced CTF access route.
Source note: Car Hacking Village DEF CON 34 CTF announcement.
allocation and credential boundary · organizer-published app source · event-linked artifact confirmed; allocation unverified
The catalogue records a factual event-linked electronic badge and companion workflow without upgrading it to an all-attendee entitlement, admission credential, or distribution ledger.
Source note: Flutter & Friends organizer-published conference-app commit, badge UI source, schedule data, and friends_badge repository.
allocation and fulfillment boundary · official product page · planned distribution only
The catalogue does not infer a universal attendee issue, final recipient count, or completed giveaway from the planned distribution model.
Source note: AND!XOR DC34 official product page.