Hacker Con Badges

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.

Reset
2166 matching issue record(s)
Station 562 Badge (DEF CON 34) note

BLE, proximity, MIDI, puzzle, CTF, and privacy gap · maker-described feature list · interaction claims without public behavior or data documentation

The feature list names BLE proximity, a number-station puzzle, red-versus-blue play, a social/dance mode, MIDI, tamper evidence, and an optional hardware CTF, but does not publish radio settings, range, identifiers, pairing/consent behavior, data collection/retention, player safety, puzzle rules, score handling, CTF target/rules, accessibility, abuse controls, or privacy/security testing.

The record does not claim wireless interoperability, participant tracking behavior, a safe game design, data practices, live puzzle availability, or an authorized security-testing target.

Source note: Station 562 maker announcement.

BSides Bournemouth 2025 Skull Badge note

BOM provenance, final hardware, power, and electrical-safety gap · public repository review · reference parts statement and design files public; production/safety result unrecovered

The repository names an ATtiny402, button, two CR2032 clips, and 5050 NeoPixel but says its listed parts are the same as a BSides Cheltenham 2024 badge reference. The reviewed sources do not establish an exact final Bournemouth 2025 BOM, component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline and its reference-list limitation without treating it as a complete fabrication, repair, electrical-safety, or universal final-unit specification.

Source note: punk-security/bsides-bournemouth-2025-badge README, EAGLE source, and Gerber archive.

BadgeLife Village Badge (DEF CON 34) note

BadgeLife village association, allocation, and DEF CON credential boundary · Badge.Life badge guide and village index · pre-event village badge documented; distribution and credential status unverified

Badge.Life labels the artifact its Badgelife Village Badge for DC34 / 2026 and indexes it in its DEF CON 34 village material. No reviewed source for this record says DEF CON designed, issued, sponsors, or will distribute it; that it is a Human badge, registration entitlement, or admission credential; or who is eligible, how many exist, what it costs, whether it ships, or whether any pickup, delivery, or completed handoff occurred.

The catalogue records a source-documented village electronic badge without representing it as DEF CON's main badge, a guaranteed attendee item, an access credential, or a completed transaction.

Source note: Badge.Life DC34 Village Badge guide and current village index, reviewed 2026-08-05.

Celestial Wayfinder Badge (DEF CON 34) note

CAD, web-companion, and reusable-media licensing boundary · GitHub repository metadata and source review · needs explicit license and media permission

The Fusion360/STL Wayfinder-CAD repository and Wayfinder web-companion repository are publicly visible but GitHub reports no detected license for either. The CAD repository's README includes GitHub user-attachment images, while firmware README images are externally hosted; neither situation establishes reusable media or a blanket license for models, code, documentation, or rendered product assets.

Public source links remain available for inspection without labeling CAD/PWA material as open licensed, copying imagery, or implying a deployed/maintained companion service.

Source note: WyrdWyrks/Wayfinder-CAD and WyrdWyrks/wayfinder-web-companion repository metadata and README review.

Dante's Inferno Badge (DEF CON 32) note

CR123A battery, shipping, and safety boundary · maker product/shipping wording · battery included and air-removal wording published; engineering context incomplete

The listing says the badge runs on an included CR123A and says it ships ground with the battery in the United States while the seller will remove the battery for air shipping. It does not identify the cell chemistry/brand/protection, holder, polarity protection, current draw, charging behavior, thermal/short-circuit precautions, storage/transport conditions, replacement compatibility, legal shipping compliance, or test evidence.

The catalogue records the published battery and shipment wording without treating it as a complete safety, transport, charging, or replacement-battery procedure.

Source note: Dante's Inferno Tindie listing.

Disobey 2026 Badge note

CTF firmware release caveat · official badge page · source still pending

The official badge page still says the CTF challenge firmware source code will be released after the event, but the public sources checked in this pass did not expose that release.

The catalogue keeps the CTF flashing-station workflow as source-backed event behavior while avoiding a false claim that the CTF firmware source has already been published.

Source note: Disobey 2026 badge page and public repository refresh.

DOJOConf Panamá 2026 Electronic Badge note

CTF role, challenge, and software scope gap · organizer-controlled intended-use statement and public README · high-level framework context; mechanics not represented

The organizer says the badge will be useful in the CTF, and the public README names PwnPet with virtual-pet and CTF context at a high level. The recovered sources do not establish an event-specific challenge archive, target authorization, final firmware image, unit configuration, participant data practice, results, or a verified attendee experience. The catalogue deliberately does not reproduce setup, connection, configuration, or challenge procedures.

The record does not present source-described context as a shipped challenge, a defined security-testing target, a privacy practice, or a verified participant outcome.

Source note: ComunidadDOJO 2026 CTF update, Electronic Cats public post, and badge-dojocon-2026 README.

PWNEDCR 0x08 Electronic Badge note

CTF, distribution, and credential scope gap · named post-event account · event interaction documented; issuance terms unknown

The report links the badge to CTF hacking and describes hidden challenges, but does not document participant eligibility, badge count, price, registration tier, badge distribution, pickup, delivery, access-control role, challenge rules, scoring, data handling, completion, support, or whether every attendee received one.

The badge is not presented as an admission credential, universal attendee entitlement, complete CTF platform, or verified distribution record.

Source note: Best of PWNEDCR 0x08 by Simón Correa.

Puzzled Hackers LED Badge (DEF CON 34) note

CTF, free-redemption, giveaway, and account-data boundary · first-hand Team announcement · acquisition statements only

The Team identifies a top-50 CTF redemption route and a possible random giveaway after the paid cap, but does not publish final puzzles, rules, score verification, account/QR-data retention, eligibility disputes, identity checks, selection method, inventory split, recipient outcomes, or a claim that CTF software is installed on the LED badge.

The catalogue retains the public community-acquisition context without supplying private account details, challenge content, player data, unsupported redemption mechanics, or badge-software claims.

Source note: Puzzled Hackers Team Meetup Post #4.

FrogStar Badge (DEF CON 33) note

CTF, game, GIF, and secret-content rules gap · maker feature description · high-level interaction claims only

The maker describes a frog-themed CTF, unlockable GIFs/bling/secrets, and a frogger-like built-in game but does not publish challenge rules, intended player scope, solution or reset path, scoring, service availability, networking, telemetry, content provenance, data handling, archival plan, accessibility, or security testing.

The catalogue treats these as source-described interactive features rather than asserting a verified challenge system, live service, privacy posture, or preserved gameplay archive.

Source note: BigTaro FrogStar 2025 project and seller listings.

NaClCON 2026 3D-Printed NFC Conference Badge note

CTF, game, and authorship boundary · official schedule and named first-hand announcements · activity relationship source-backed; artifact roles unresolved

The official registration pairs a badge and CTF access, the founder says the badge could be used in Pieces of Eight / Pirate Scavenger Hunt play, the official schedule credits DEAD MEAT SOCIETY and SHIPSTONE for a CTF and Badge Intro, and Matt Aragon announces two NFC games. The reviewed sources do not publish the exact badge-to-game mapping, operation, scoring, rewards, results, participant privacy/data flow, or a reliable badge designer/manufacturer attribution.

Schedule and announcement context remains discoverable without attributing badge design to the game host or scheduled organizations, or inventing a finished challenge system.

Source note: NaClCON registration and schedule, Luke McOmie announcement, and Matt Aragon announcement.

NoNameCon 2019 NoNameBadge note

CTF/backend archive boundary · public firmware and write-up sources · partial archive

The public firmware and write-up repositories document major badge CTF surfaces, but this pass does not prove that every private backend, provisioning script, factory image, key, leaderboard implementation, or organizer service has been published.

Software claims stay limited to the recovered TechMaker post, public firmware tree, public CTF writeups, and talk material.

Source note: NoNameBadge public firmware project and Coders in UA CTF write-up repository.

NoNameCon 2020 Air Quality Badge note

CTF/backend archive boundary · public article, firmware tree, and write-up sources · partial archive

The public firmware archive omits the private CTF portion by TechMaker's own framing, and the CTF write-up repository reconstructs public challenge paths rather than proving that every backend, provisioning, leaderboard, key, or organizer service was released.

Software claims stay limited to the recovered TechMaker article, public firmware tree, schematic, and CTF write-up repository.

Source note: NoNameBadge 2020 public firmware project and Coders in UA CTF write-up repository.

DEF CON 34 Badge note

Call Center Village Telephone Booth SAO host-voltage, current, assembly, and final-build boundary · official project source plus current roster · design and current offer documented; host and fulfillment outcomes unconfirmed

The Call Center Village repository describes a power-only SAO v2 with a 1206 LED and 330 ohm resistor connected from VCC to GND, and frames SAO v2 power as nominally 3.3 V. DEF CON's own DC34 specification instead documents 3.0 V VDD and a 100 mA tested total supply across both SAO ports. The sources do not publish LED electrical characteristics, actual host current, measured brightness, DC34 fit test, reverse-orientation protection, ESD/current protection, kit/pre-soldered population, assembly quality, final production revision, or safety validation.

The catalogue can document the simple published design and its source files without calling the generic SAO v2 description a verified DC34 electrical match, a universal host compatibility result, a safe assembly procedure, or a completed unit/fulfillment record.

Source note: Call Center Village Telephone Booth SAO repository and public DEF CON 34 Badgelife response, read with the official DEF CON 34 SAO specification.

BTV Camera Badge (DEF CON 34 Fundraiser) note

DC32 design lineage and 2026 revision boundary · primary organizer listing and MIT archive · current fundraiser tied to an earlier documented design

The 2026 Eventbrite listing offers a BTV Camera Badge, while the linked public technical archive calls its project a DEF CON 32 indie badge. The current list and historical guide both use `ESP23` wording, while the historical parts list identifies an ESP32 board. The reviewed sources do not identify a current 2026 schematic/BOM/PCB revision, manufacturing run, exact firmware commit, build hash, component substitutions, or a definitive mapping from the offered units to the DC32 archive.

The record preserves a justified DC32-source lineage without asserting an undocumented new DC34 board revision, a byte-for-byte 2026 firmware identity, or an error-free production BOM.

Source note: BTV Eventbrite fundraiser, BTV at DEF CON 32 page, and `btv_dc32_badge` archive.

NilbinSec Power Glove Re-release SAO (DEF CON 34) note

DC32-to-2026 re-release revision boundary · current roster name plus historical repository scope · current re-release announced; exact technical lineage unconfirmed

The current roster calls the item a Power Glove Re-release, while the public design repository is explicitly DC32-named and last documents an older fabrication/assembly surface. No reviewed source provides a 2026 project URL, board revision, change log, BOM comparison, gerber release, photo with technical annotation, firmware/release mapping, manufacture record, or statement that 2026 units are mechanically/electrically identical to the older design.

Readers can follow the historical public trail without treating the re-release label as proof of unchanged design, 2026 manufacture, backward compatibility, or a new engineering revision.

Source note: NilbinSec DEF CON 34 roster response and DC32-Power-Glove-SAO repository.

Portal Gun SAO (DEF CON 34) note

DC33-named repository, 2026 revision, and historical-lineage boundary · repository names and current roster association · current DEF CON 34 association evidenced; earlier/revision history not reconstructed

Both public source repositories are named `portal-gun-sao-dc33` while the roster calls the artifact a new DEF CON 34 SAO. This pass did not recover a source-backed DEF CON 33 distribution record, an exact earlier hardware/firmware release, a changelog, a 2026 manufacturing revision, a proof that the public files match final DC34 units, or a historical relationship to each Portal Badge version.

The record can link an especially useful implementation trail without falsely assigning a definitive prior event release, treating a `dc33` repository label as a DC33 artifact record, or claiming that 2026 units are new/unchanged/equivalent to the archived files.

Source note: portal-gun-sao-dc33 and portal-gun-sao-dc33-code repository roots plus DEFCON 34 Badgelife Form response.

Dante's Inferno Badge (DEF CON 32) note

DEF CON 32 origin, DEF CON 33 vendor list, and completed-distribution gap · maker launch wording, later vendor list, and seller state · origin and later vendor recurrence documented; event handoffs unconfirmed

The product was introduced for DefCon 32, later appears on a DEF CON 33 Hacker Couture list, and the Tindie page says it sold out in September 2024. This pass did not recover a production count, event schedule, booth location, receipt, purchaser/recipient list, attendee report, pickup/shipping record, vendor after-action, unit history, or proof that the 2025 vendor listing used an identical run or remaining 2024 inventory.

The record preserves the maker-stated 2024 origin and the separate 2025 listing without creating a duplicate DC33 badge or treating either listing as confirmed event distribution.

Source note: Dante's Inferno Tindie listing and Hacker Couture DEFCON 33 Product List.

SAO Many SAOs Badge (DEF CON 33) note

DEF CON 33 origin, 2026 roster recurrence, price, and fulfillment boundary · official product page and public maker self-submission · historical artifact plus later update-to-existing listing; outcome unconfirmed

The product page identifies a DEFCON 33 badge and displays a historical $70 sale from $100, while the July 2026 roster says Update to Existing and $80. Neither source demonstrates the original run's quantity, event distribution, whether the older price or current price was transacted, stock, payment, order acceptance, manufacturing, refund, pickup, shipment, delivery, recipient, support, or a distinct 2026 revision.

The catalogue preserves two time-specific maker statements without calling either a completed event sale, a current in-stock guarantee, or a new DEF CON 34 badge.

Source note: Coruscant Ventures SAO Many SAOs product page and DEFCON 34 Badgelife Form response.

Darknet-NG SMAO (DEF CON 34) note

DEF CON association and credential boundary · maker, project, and marketplace sources · independent DEF CON 34-associated maker product

Darknet-NG's own project page, maker profile, and product listing place the SMAO in its DEF CON 34 contest context, and the sources use the phrase official DEF CON build for its stated initial configuration. No reviewed DEF CON organizer source names the SMAO as a conference-issued product, says it is included with registration, grants access, substitutes for a Human badge, confirms organizer support, or independently validates the configuration label.

The catalogue treats the SMAO as an independent contest-associated add-on, not a DEF CON credential, admission artifact, organizer endorsement, or verified conference firmware distribution.

Source note: Darknet-NG official home and badge page plus Uberflux maker profile and product page.

Gunslinger-B-Gone Badge and Sheriff SAO Combo (DEF CON 33) note

DEF CON vendor-list and completed-distribution gap · published vendor list and seller state · vendor availability documented; purchase and handoff outcome not recovered

The product appears in a DEF CON 33 Hacker Couture list and a seller page later says it is sold out, but this pass did not recover a booth location, inventory count, receipt/purchase record, production total, recipient list, attendee report, vendor after-action, pickup/shipping result, or a link between vendor-list stock and later Tindie stock.

The record preserves its documented event-vendor association without equating a product list or sold-out state with a confirmed attendee handoff or completed distribution.

Source note: Hacker Couture DEFCON 33 Product List and Gunslinger-B-Gone Tindie listing.

MidWestCoast Badge (DEF CON 34) note

DEF CON, MidWestCoast Party, and credential boundary · maker source plus official DEF CON event context · independent pre-event association only

The repository supplies MidWestCoast Party and DEF CON 34 labels, while DEF CON's registration page independently establishes the conference dates and venue. Neither source says DEF CON designed, issued, endorsed, approved, or will distribute this project; neither identifies a party organizer, party date or venue, permission to operate at the conference, registration inclusion, attendee entitlement, admission role, or access-control use.

The record remains an independently published pre-event project associated by its source with DEF CON 34, not an official conference badge, party credential, organizer program, or access item.

Source note: Aask42 MidWestCoastBadge repository/firmware README and DEF CON 34 registration page.

DFIU SAO (DEF CON 34) note

DFIU theme, named-person/show, attribution, and endorsement boundary · maker language and public self-submission only · seller framing recorded; authority and reuse rights unsubstantiated

The maker's card invokes a Hacker Jeopardy vibe, Lintile's face, and the "Don't Fuck It Up" cheer track, while the roster names DFIU. No reviewed source establishes rights-holder permission, an affiliation, endorsement, participant attribution, performer consent, audio/artwork provenance, or image/media reuse authority for those references.

The entry retains the factual seller framing while avoiding an inference that the named person, show, DEF CON, or any performer/rights holder authorized, sponsored, designed, endorsed, or licensed the SAO or its media.

Source note: BigFuckingBadge DEF CON 34 page and DEFCON 34 Badgelife Form response.

Hacker Boba Badge Kit (DEF CON 34) warning

DIY soldering, CR2032, LED, and hardware-safety warning · live maker component and caution wording · kit and basic caution published; assembly and electrical validation unrecovered

The maker says the kit is unsoldered, needs a soldering iron and basic supplies, uses an included CR2032, and is not intended for small children; it says the coin cell should be handled carefully and kept away from children and pets. The source does not establish component polarity/orientation, battery-holder protection, short-circuit/reverse-current behavior, LED current/thermal behavior, soldering quality, supervision requirements, test procedure, battery-life data, compliance, or a safe assembled result.

The record preserves the maker's narrow coin-cell and kit caution without becoming a soldering, battery, child-safety, electrical, or assembly endorsement.

Source note: Brooke's Bytes Hacker Boba Uberflux listing.

WomenCon 2026 Digital Morpher Badge note

Electronic Cats role, hardware-license, and authorship boundary · organization-level source statements · designer/developer organization named; scope and license unpublished

WomenCon describes the badge as designed or developed by Electronic Cats, while a community repost thanks Electronic Cats for making the device possible. The sources name no individual contributors, task-by-task engineering or manufacture scope, repository, license, intellectual-property ownership, contractual role, endorsement scope, or image-reuse authority.

Credits stay at the named organization level and do not infer an open-hardware release, named-person authorship, production responsibility, ownership, or reusable-image permission.

Source note: WomenCon organizer posts and WoSEC México public update.

Root Access SAO (DEF CON 34) note

GPIO host behavior, interoperability, and safety boundary · maker-described selectable GPIO paths · behavior depends on the connected host

The maker describes separate GPIO LED-output and button-input options, but does not publish a current/voltage envelope, signal-timing specification, host pin mapping, a DC34 host result, contention protection analysis, switch-state guidance, or tests with other SAO devices. The source's general standard-SAO compatibility claim does not close those gaps.

Readers can identify the intended experimentation surface without assuming every host, GPIO mode, cable, orientation, or shared bus configuration is safe or interoperable.

Source note: Root Access SAO product page and RootAccess Interactive SAO How-To Guide.

NilbinSec DC34 Main Badge Fuzzer SAO warning

GPIO stimulation, damage, safety, and consent warning · explicit maker warning plus public implementation · Mode 1 may harm a badge; no safe-use validation published

NilbinSec explicitly warns that Mode 1 may harm the main badge depending on how GPIO pins are configured. The source drives GPIO1/GPIO2 through patterns before sampling them, but does not provide final target specifications, current limits, isolation, protection analysis, electrical test results, safe operating procedure, consent model, or recovery guidance.

The catalogue preserves the warning so the artifact is not mistaken for a harmless universal add-on. Do not infer electrical safety, non-destructive behavior, authorization, warranty coverage, or suitability for an unfamiliar badge.

Source note: NilbinSec DC34 Main Badge Fuzzer SAO README and Firmware/main.c.

NilbinSec PAC-MAN Ghost SAO (DEF CON 34) note

GitHub, firmware, source, release, and licence gap · planned Day-1 posting versus pre-event public-source review · 2026 publication announced; no archive identified before event

The roster says the PAC MAN Ghost SAO will be released on NilbinSec GitHub on DEF CON Day 1, but the event had not yet begun. No reviewed source exposes a 2026 repository, source code, firmware/binary, build or flashing instructions, release/tag, protocol, configuration, software/hardware/documentation licence, security review, support policy, or warranty.

The catalogue keeps the future-posting statement useful without presenting it as an existing source release, a programmable behavior claim, a reproducible build, or a legal reuse grant.

Source note: DEFCON 34 Badgelife Form response, NilbinSec Bluesky post, and public maker sources.

Root Access SAO (DEF CON 34) note

I2C guide, firmware, source, and licensing gap · public repository root reviewed · operating guide published; implementation archive not identified

The README documents behavior and control traffic, but the reviewed repository root contains only that README and an images directory. No firmware source, release binary, build toolchain, flash procedure, schematic, hardware-design archive, test suite, dependency list, code license, documentation license, or update/recovery policy was identified.

The catalogue links the documented interface without presenting it as an open-source firmware release, reproducible hardware design, or supported integration package.

Source note: MakeItHackin/RootAccess repository root and README.

Gunslinger-B-Gone Badge and Sheriff SAO Combo (DEF CON 33) note

IR TV-control and laser-tag safety, consent, compatibility, and authorized-use gap · vendor high-level feature claims · IR interactions claimed; operation and boundaries undocumented

The vendor list says the Sheriff can play laser tag, light friends' badges, and send an IR blast that powers down TVs, but does not disclose carrier/protocol/code set, range, target behavior, laser classification, eye safety, consent expectations, authorized-use guidance, third-party-device compatibility, failure modes, regulatory context, or test evidence.

The catalogue does not present the product as a safe, legal, reliable, universally compatible, or acceptable means of controlling another person's badge or television.

Source note: Hacker Couture DEFCON 33 Product List.

MalO SAO (DEF CON 34) note

IR, NFC/RFID, microphone, privacy, and interaction-safety boundary · maker-described communication and sensing claims · no final policy or protocol release identified

The sources describe IR message exchange, NFC/RFID, a microphone, motion/light/environmental sensors, games, and social interactions, but do not publish a final communications protocol, authentication/security model, user consent flow, microphone activation/data behavior, local storage/retention policy, pairing/discovery rules, radio/IR performance limits, accessibility policy, moderation plan, or incident guidance.

The record does not turn a feature list into a privacy guarantee, secure messaging claim, surveillance assurance, or universally suitable interaction model.

Source note: MalO SAO product page, MalO_SAO repository, and MalO SAO developer diary.

NilbinSec DC34 Main Badge Fuzzer SAO note

I²C address-range and bus-behavior documentation discrepancy · conflicting README and source details · implementation more specific than README; target behavior unresolved

The README says Mode 3 increments through I²C addresses 0x00–0x7F, whereas the current C source sweeps 0x08–0x77 and skips 0x19 and 0x3C. The source calls its listener passive and says it does not ACK, but no final badge-bus trace, target firmware, revision mapping, bus-speed validation, or test evidence was recovered.

The record retains both source statements instead of presenting the README range as an exact implementation or claiming coverage, reliability, safety, or compatibility for a final target I²C bus.

Source note: NilbinSec README and Firmware/main.c.

Day of the Dead Turkey v1 (DEF CON 34) note

LED, CR2032, soldering, and electrical-safety documentation gap · maker product wording only · high-level light, battery, and kit terms published; engineering details absent

The source names blue/yellow LEDs, CR2032 standalone power, and 1206-or-larger components requiring soldering, but does not disclose the circuit, components, LED current, resistor values, voltage/current limits, battery holder/polarity/protection, runtime, overheating/short-circuit risks, switch, connector/pinout, assembly order, tools, soldering/ESD precautions, test results, user instructions, or compliance evidence.

The record documents a real kit surface without representing it as electrically characterized, risk-free to assemble, safe for every CR2032 setup, or compatible with every minibadge/host.

Source note: Day of the Dead Turkey v1 product page.

Day of the Dead Turkey v2 (DEF CON 34) note

LED, CR2032, soldering, and electrical-safety documentation gap · maker product wording only · high-level light, battery, and kit terms published; engineering details absent

The source names blue/yellow LEDs, CR2032 standalone power, and 1206-or-larger components requiring soldering, but does not disclose the circuit, components, LED current, resistor values, voltage/current limits, battery holder/polarity/protection, runtime, overheating/short-circuit risks, switch, connector/pinout, assembly order, tools, soldering/ESD precautions, test results, user instructions, or compliance evidence.

The record documents a real kit surface without representing it as electrically characterized, risk-free to assemble, safe for every CR2032 setup, or compatible with every minibadge/host.

Source note: Day of the Dead Turkey v2 product page.

BTV Camera Badge (DEF CON 34 Fundraiser) note

LiPo, charging, and kit-assembly safety boundary · current kit list and historical assembly guide · needs final safety and operating documentation

The sources name a 3.7 V / 1,200 mAh LiPo and a board-side LiPo connection/charging circuit. The historical guide cautions against heating or shorting battery wires and says charging requires the switch on. They do not publish the exact current cell/charger/protection configuration, thermal/current test data, replacement procedure, fault behavior, shipping classification, certification, or a final 2026 safety guide.

The catalogue does not turn an assembly guide or parts list into a battery-service procedure, electrical-safety endorsement, charging assurance, or sanctioned modification instruction.

Source note: BTV Eventbrite fundraiser listing and `btv_dc32_badge` parts/assembly documentation.

Laser* Tag Badge DS (DEF CON 34) note

LoRa score-sync reliability caveat · official maker documentation · conditional design

The maker page says LoRa leaderboard syncing depends on RF conditions and may fail to reach planned base stations in a crowded ISM-band environment, with QR codes as the stated fallback. It also describes IR-play limitations from venue lighting and reflections.

The record does not present LoRa connectivity, leaderboard coverage, or all-vs-all IR play as guaranteed DEF CON 34 behavior.

Source note: Dani Weidman official Laser* Tag Badge DS maker page.

Celestial Wayfinder Badge (DEF CON 34) note

LoRa, Wi-Fi, BLE, radio-performance, and privacy boundary · maker listing and MIT firmware repository · technical behavior documented with operational limits unknown

The sources describe an SX127x-class 915 MHz LoRa mesh, GPS/status payloads, Wi-Fi geolocation fallback, and web/USB/BLE RPC configuration. They do not publish an RF certification, final channel/power configuration, range or coexistence testing, message authentication/encryption analysis, Wi-Fi geolocation provider terms, data handling policy, device discovery model, or operational guidance for all jurisdictions.

The record does not represent the badge as a certified radio, private or secure messenger, accurate indoor locator, universally legal deployment, or a performance guarantee.

Source note: Celestial Wayfinder listing and `Celestial-Wayfinder` README.

Masonic33 Indie Puzzle Badge (DEF CON 33) note

Masonic theme, terminology, and affiliation boundary · maker theme wording only · Freemasonry-inspired presentation; affiliation unsubstantiated

The maker describes square-and-compass imagery, 33rd-degree mystique, and secret-society/Freemasonry-inspired modern puzzle elements. No reviewed source establishes sponsorship, endorsement, membership, authority, or affiliation with any Masonic or fraternal organization, nor provides a license for theme/artwork elements.

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.

2026 eChallengeCoin (DEF CON 34) warning

Micro-USB, USB-C, touch-count, and Coin M0 mapping conflict · conflicting linked primary sources · unresolved source discrepancy

AoSC's eChallengeCoin page says Micro-USB and one large touch pad, while the CircuitPython Coin M0 profile that AoSC links as the eChallengeCoin-specific build says native USB-C and three capacitive touch pads. Both sources mention three NeoPixel groups and a speaker. This pass did not recover a revision note, schematic, product BOM, photo with cleared technical annotation, or maker clarification resolving whether the pages describe the same final 2026 unit, a transitional revision, or differing interface vocabulary.

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.

BSides Cheltenham 2023 Delorean Badge note

Mind fundraiser, assembly, participant, and outcome boundary · maker repository description · limited fundraiser account documented; contribution and completion outcome unrecovered

The maker archive says parts to complete badges were sold on the day and raised more than £300 for Mind, but it does not publish an organizer confirmation, campaign terms, payment or donation ledger, purchaser count, parts inventory, unit-to-purchaser mapping, completed assembly count, participant identities, recipient list, final badge distribution, or individual charity outcome. No assembly procedure is reproduced here.

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.