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
2209 matching issue record(s)
BSidesPDX 2015 Badger Badge note

technical-source caveat · public source archive · needs final production archive

The public PCB and firmware archives document the design files and ESP8266 badge behavior, but this pass did not recover BOM notes, assembly instructions, final flashed release tag, manufacturing order, workshop handout count, or post-event challenge results.

Hardware and firmware claims remain limited to the public repository files and official schedule wording.

Source note: pdxbadgers/pcb-2015, pdxbadgers/fw-2015 README, badger.ino, and BSidesPDX 2015 schedule.

BSidesPDX 2016 ATTiny85 Badge note

technical-source caveat · public hardware and firmware archive · needs final production archive

The public repository exposes Eagle board, schematic, BOM, and an Arduino sketch, but this pass did not recover final Gerbers, assembly instructions, production photos, challenge docs, release tags, or a post-event firmware history.

Hardware and firmware claims remain limited to the public repository files plus event-context wording.

Source note: pdxbadgers/pcb-2016 BoM.csv, badge.sch, badge.brd, and badge.ino.

BSidesPDX 2017 BMD-300 Badge note

technical-source caveat · public hardware archive · needs firmware and production archive

The public repository exposes Eagle board, schematic, BOM, and library files, but this pass did not recover final firmware, challenge docs, production photos, Gerber release, or a talk transcript explaining intended badge behavior.

Hardware and software claims remain limited to the public repository files and official schedule/speaker wording.

Source note: pdxbadgers/pcb-2017, BSidesPDX 2017 schedule, and BSidesPDX 2017 speakers page.

BSidesPDX 2018 ATTiny861 Badge note

technical-source caveat · public source archive · needs final production archive

The public repository exposes KiCad, BOM, LED mapping, and test firmware files, but this pass did not recover final firmware release notes, challenge docs, production photos, or a full talk transcript explaining intended gameplay.

Hardware and firmware claims remain limited to the public repository files and official schedule/speaker wording.

Source note: pdxbadgers/badge-2018, BSidesPDX 2018 schedule, and BSidesPDX 2018 speakers page.

BSidesPDX 2019 Multnomah Badge note

technical-source caveat · public source archive · needs final production archive

The public repository exposes KiCad, BOM, and simple firmware files, but this pass did not recover assembly instructions, final firmware release notes, challenge docs, production photos, or talk notes explaining intended gameplay.

Hardware and firmware claims remain limited to the public repository files and official schedule wording.

Source note: pdxbadgers/badge-2019 and BSidesPDX 2019 schedule.

BSidesPDX 2020 Presenter LED Mask note

technical-source caveat · public firmware and README archive · needs final production archive

The public repository exposes README wiring notes and one Arduino sketch, but this pass did not recover fabrication notes, final quantity, presenter handout list, production photos, source license, or post-event maintenance history.

Hardware and software claims remain limited to the public repository files and official all-digital event context.

Source note: pdxbadgers/2020-mask README and 2020-mask.ino.

CactusCon 2014 PCB Badge note

technical-source caveat · first-hand writeup · needs design archive recovery

The first-hand writeup proves the PCB badge concept, count, giveaway, assembly materials, and board-function ideas, but this pass did not recover schematics, Gerbers, BOM, fabrication files, firmware, exact LED circuit, or a design repository.

The catalogue preserves the physical badge lineage while avoiding unsupported component-level or reproducibility claims.

Source note: Robot Ambassador CactusCon PCB Badges writeup.

BSides Athens 2024 Electronic Circuit Badge note

technical-source gap · source-backed but incomplete · needs artifact-level archive

The public trail recovered so far does not expose the badge schematic, PCB files, BOM, firmware, chip list, challenge binary, flashing workflow, or production quantity.

The catalogue limits the record to the electronic circuit badge, soldering light-up path, breadboard reuse, and hidden-secrets claims explicitly supported by recovered sources.

Source note: BSides Athens 2024 official site and recovered wrap-up PDF.

BSides Tallinn 2022 DIY Soldering Badge note

technical-source gap · source-backed but incomplete · needs artifact-level archive

The public source trail does not expose the badge schematic, PCB files, BOM, component list, firmware, power design, challenge code, or final assembly guide.

The catalogue describes only the participant badge, DIY soldering project, custom configuration, and named design credit supported by official sources.

Source note: BSides Tallinn 2022 official page and current BSides Tallinn archive.

BSides Prague 2025 Electronic Badge note

technical-source gap · source-backed but incomplete · needs artifact-level archive

The recovered public trail proves an electronic PCB badge, multiple processors, two integrated systems, chip-based challenges, and nickname display, but does not expose schematics, PCB files, BOM, component identities, firmware, challenge binaries, protocol docs, or production files.

The catalogue keeps the record useful without inventing part numbers, exact processors, firmware behavior, or board-source availability.

Source note: BSides Prague official Sched page and Hung Ngo organizer retrospective.

BSides Kristiansand 2026 Shield Badge note

technical-source gap · official and post-event source-backed limitation · needs public hardware and firmware archive

The public trail proves a custom hackable electronic shield badge, all-attendee distribution, design credit, and broad programming/flash/test activity, but it does not expose a controller identifier, component list, schematic, BOM, PCB files, power details, stock firmware, binary, source repository, challenge implementation, or reuse license.

The catalogue records the verified artifact and its supported narrative without treating an event description or post-event story as a complete technical release.

Source note: BSides Kristiansand 2026 event site and organizer article, Billetto event archive, and published Shield Badge post-event account.

NolaCon 2025 Patches Badge note

technical-source gap · official source but incomplete · needs badge-team archive

The official badge page proves Patches, soldering tradition, customization, and Voodoo Heart continuity, but this pass did not recover a schematic, BOM, controller, firmware repository, badge guide, battery details, LED count, production count, or complete challenge archive.

The catalogue records the verified 2025 badge artifact and avoids inventing unsupported electronics or firmware behavior.

Source note: NolaCon badge page, talks archive, sponsor pack, and badge.gallery inclusion policy.

BSides San Diego 2026 Cyberpunk Bunny Badge note

technical-source gap · official badge guide with limited hardware depth · needs deeper archive recovery

The official badge guide proves an ESP32-powered Cyberpunk Bunny portable CTF with accelerometer, crypto challenges, BLE co-op behavior, and hidden flag path, but no schematic, BOM, PCB files, firmware source, exact module revision, battery details, or production count were recovered.

The catalogue records verified badge behavior without inventing component-level electronics, source-release status, or shipped-hardware internals.

Source note: BSides San Diego Badge Challenge page.

BSidesKC 2025 Badge note

technical-source gap · badge-maker production and binary-delivery sources with limited archive depth · binary delivery documented; needs schematic, BOM, source, and deployment recovery

The public sources prove an ESP32 touchscreen badge batch with Wi-Fi, SD card slots, PCBWay assembly, customs/tariff logistics, and a selectable ESP32-S3 binary manifest. They still do not recover a schematic, BOM, Gerbers, source code, changelog, signed release, challenge files, battery details, full component placement record, or source-to-event deployment mapping.

The catalogue records the verified chip-family flashing target and maker-announced continuation while avoiding unsupported board, firmware-source, challenge, and production claims.

Source note: Badge Pirates tariff/shipping updates, public 2026 Ad Astra update, and BSidesKC 25 flash manifest.

BSidesROC 2019 Electronic Badge note

technical-source gap · official source but incomplete · needs badge-team archive

The official source documents ATTINY85, SAO ports, programming connector parts, reprogrammability, and contest framing, but this pass did not recover a schematic, BOM, Gerbers, firmware repository, flashing guide, badge challenge source, or final production file archive.

Hardware and software claims remain limited to the official badge-page text and avoid unsupported electronics or firmware behavior.

Source note: BSidesROC 2019 badge page and public website-source repository.

SECCON 2026 PCB Badge note

technical-source gap · official source but incomplete · needs schematic, firmware, and repository recovery

The official ticket page proves a PCB badge with CTFs and features, but this pass did not recover component identifiers, schematic, BOM, Gerbers, firmware, challenge source, badge guide, production photos, or repository evidence.

The catalogue records only the verified official badge scope and avoids unsupported hardware, software, and challenge claims.

Source note: SECCON ticket page and current public-source search.

AvengerCon VIII 8-8-8 Badge note

technical-source gap · source-backed but incomplete · needs deeper archive recovery

The public Army source proves the first electronic AvengerCon badge, 8-8-8 naming, scavenger-hunt behavior, hack-bypass option, in-person distribution until supplies ran out, more-than-300 build, and Capt. Richard Shmel maker credit, but it does not publish schematics, BOM, firmware, controller identity, protocol docs, or manufacturing files.

The catalogue records the verified badge lineage without inventing component-level details or open-source status.

Source note: U.S. Army AvengerCon VIII public-affairs article.

Recon Village DC25 The Original Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves the electronic badge lineage, spy silhouette, die-cut shape, hardwear.io lanyard, and first-badge framing, but no schematic, firmware, BOM, controller, battery, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

Recon Village DC26 The Dual Design Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves the two design variants, spy silhouette, skull artwork, and black-and-white aesthetic, but no schematic, firmware, BOM, controller, battery, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

Recon Village DC27 The Skull Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves the skull-shaped PCB, steampunk mechanical design, LED eye illumination, and CREW variant, but no schematic, firmware, BOM, controller, battery, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

Recon Village DC30 The Radar Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves the circular radar design, world map overlay, teal and emerald color scheme, compass markings, and coordinate markings, but no schematic, firmware, BOM, controller, battery, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

Recon Village DC31 The Spy Silhouette Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves die-cut silhouette shape, LED illumination, speaker-badge variant, and custom Recon Village lanyard, but no schematic, firmware, BOM, controller, battery, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

Recon Village DC32 The Recon Soldier Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves multi-layer PCB construction, red and blue LED eyes, 3D assembled design, and military helmet design, but no schematic, firmware, BOM, controller, battery, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

Recon Village DC33 The Cyber Owl Badge note

technical-source gap · official archive with limited hardware depth · needs deeper archive recovery

The official page proves the cyberpunk owl design, glowing pink LED eyes, detailed mechanical artwork, and metallic blue-gray finish, but no schematic, firmware, BOM, controller, battery, challenge protocol, or production files were recovered.

The catalogue records the verified artifact without inventing component-level electronics or source-release status.

Source note: Recon Village Badge Life page.

BSides Goa 2024 SecOps Hackable Badge note

technical-source gap · source-backed but incomplete · needs hardware archive

The public source lists badge components and challenge behavior, but no schematic, BOM, PCB files, firmware image, source repository, challenge binaries, or exact chip identity were recovered in this pass.

The hardware and software notes stay at the exact level supported by the public SecOps writeup until a badge-team archive appears.

Source note: SecOps Hack the Badge page.

BSides Agra 2025 IOTSRG Badge note

technical-source gap · source-backed but incomplete · needs hardware archive

The recovered source trail proves Badge Sponsor, all-attendee collectible badge framing, and soldering-village context, but does not expose the final badge circuit, component list, schematic, board files, firmware, badge challenge, or shipped quantity.

The catalogue keeps the Agra badge record conservative and avoids converting sponsor/social evidence into unsupported component-level claims.

Source note: Archived BSides Agra site and official BSides Agra LinkedIn trail.

DEF CON 34 Badge note

third-party capture-ring geometry, mechanical-fit, port-orientation, and safety boundary · maker-published design; no independent fit or electrical verification · public pre-event STL design; physical outcome unverified

Make It Hackin's public README proposes a two-piece capture ring for the DEF CON 34 badge and says its geometry was derived photogrammetrically rather than from an official DEF CON drawing. The maker's README also asserts that an incorrect orientation could reverse pins and create a short-circuit risk, but this pass did not independently verify that assertion or any physical or electrical effect.

The catalogue records an optional third-party mechanical design without treating it as an official accessory, a fit result, a port-orientation diagnosis, an electrical-safety conclusion, or a finished product. The source does not establish print material, assembly quality, mechanical loads, badge/port clearance, pinout/orientation outcome, safety validation, production, sale, delivery, support, or image reuse rights.

Source note: MakeItHackin/DC34AnyAnglePirateWheelBadge README, reviewed 2026-08-05.

NorthSec 2026 Badge note

third-party firmware license caveat · repository metadata audit · source visible; license unspecified

The public marx314/nsec-badge-2026-nfc-webhook project has no GitLab license metadata, root LICENSE or LICENSE.md file, tag, or release that declares reuse terms. Its visible source must therefore not be represented as Apache-2.0, officially released by NorthSec, or otherwise reusable by default.

Readers can inspect the custom firmware trail, but the catalogue does not imply permission to redistribute, modify, or reuse it and keeps it distinct from NorthSec's separately published Apache-2.0 source archive.

Source note: marx314/nsec-badge-2026-nfc-webhook project metadata, default-branch tree, README, and license-file checks on 2026-08-04; nsec/badge-2026 LICENSE for the separate official source-release boundary.

Disobey 2026 Badge note

third-party game license caveat · repository metadata · license not granted

GitHub's public metadata reports `license: null` for the CyberSlayer repository, and its current repository-root listing has no LICENSE file.

The catalogue can describe the game's badge compatibility and installation workflow, but must not treat its code or README image as cleared for reuse or as a catalogue image asset.

Source note: alavesa/cyberslayer GitHub metadata and repository root, checked 2026-08-03.

MalO SAO (DEF CON 34) note

third-party lore, art, attribution, and reuse-rights boundary · source-named creative attribution and project credit · project-level attribution recorded; per-asset publication rights not established

The marketplace credits SCP-1471 to LurkD and links a CC BY-SA 3.0 source; the repository credits HotGlewd and BitAssembly and declares a CC BY-SA 3.0 work license. Those public statements are preserved as provenance, but no reviewed source establishes a cleared original image, the exact license chain for every product/render/diary asset, final third-party-IP treatment, or a local-publication permission basis for badge.gallery.

The catalogue credits named sources without republishing lore artwork, product media, or project images on an assumed license basis.

Source note: MalO SAO product page, MalO_SAO repository credits/license statement, and Creative Commons license reference.

DEF CON 34 Badge note

third-party standalone SAO power companion boundary · first-party maker storefront · pre-event marketplace listing

The caelyb marketplace listing says its USB-C Power Back lets SAOs run without a host badge. It does not say the item mounts to, ships with, has been tested on, or is approved by DEF CON's main badge, and it does not publish a pinout, output-current limit, USB-C or USB-PD behavior, regulator/protection details, electrical-safety certification, or a host test matrix.

The catalogue records a source-backed third-party standalone SAO power/display companion without treating its maker-described 3.3 V conversion or multiple-SAO example as official main-badge support, a universal-compatibility claim, or a safety endorsement.

Source note: caelyb / Uberflux USB-C Power Back for SAOs listing, reviewed 2026-08-04.

HackerOne BUG HUNT 2026 Access Pro Badge note

ticket allocation, attendance, and handoff boundary · official package and partner event listing · sold-out package and past-date event context published; recipient outcome unrecovered

The official site marks the Access Pro package sold out, and the partner listing describes a January 10 on-site event. The sources do not publish an attendee list, ticket count, payment/registration ledger, badge quantity, production details, pickup point, shipment, check-in outcome, individual issue, replacement policy, or post-event delivery report.

The record does not assume that every ticket holder attended, received, wore, retained, or used a badge.

Source note: BUG HUNT 2026 official site and IEEE club-partner listing.

Hack Glasgow 2026 Attendee Name Badge note

ticket eligibility, allocation, and delivery boundary · official event, FAQ, and post-event statistics review · event completed; entitlement and individual handoff unrecovered

The official pages refer to an attendee badge and the post-event statistics page reports ticket and check-in reporting, but none establishes which ticket categories, speakers, volunteers, sponsors, press attendees, or guests received one; who supplied it; ticket-to-badge mapping; quantity; price; pickup procedure; presentation requirements; loss/replacement policy; shipment; receipt; or a completed delivery ledger.

The catalogue preserves the organizer's credential language without presenting it as a ticket-wide entitlement, admission requirement, or proof that any individual received a badge.

Source note: Hack Glasgow official home/FAQ, 2026 event-detail, and public statistics pages.

BSides Peoria 2026 Planned Conference Badge note

ticket eligibility, allocation, and delivery boundary · official event and sponsorship source review · planned badge production mentioned; recipient and handoff terms unrecovered

The reviewed official home, sponsor call, and prospectus do not say which ticket types, speakers, volunteers, sponsors, press attendees, or guests receive a badge; nor do they publish price, quantity, allocation, registration relationship, pickup, shipment, loss/replacement, receipt, or completed delivery information.

The catalogue records an organizer-confirmed planned artifact without treating it as attendee-wide inclusion, proof of individual receipt, admission credential, or final fulfillment record.

Source note: BSides Peoria 2026 official home, Call For Sponsors post, and sponsorship prospectus.

BSides Mumbai 2026 Badge Pickup note

ticket eligibility, allocation, and fulfilment boundary · official programme and ticket-page review · pickup planned; ticket and recipient scope unrecovered

The current pass page lists ticket tiers and goodies but does not say that every pass includes a badge. Combined with the provisional schedule, reviewed sources do not establish eligibility, ticket-to-badge mapping, ticket cutoff, quantity, variant, stock, pickup procedure, handoff, recipient count, loss/replacement policy, shipment, completed collection, or an attendee delivery ledger.

The catalogue preserves the planned registration cue without treating it as a ticket-wide entitlement, a promised material object, or evidence that anyone has received a badge.

Source note: BSides Mumbai 2026 official programme and ticket page.

BSides Kraków 2026 Exclusive Badge note

ticket entitlement, allocation, and pickup boundary · official 2026 ticket and agenda page · future ticket inclusion and registration wording published; fulfillment unverified

The reviewed official page lists the general and student ticket inclusions and says badges are collected at registration/check-in, but does not publish ticket quantities, a recipient list, an allocation policy, an issuer, a pickup procedure, shipment, loss/replacement terms, completed collection, receipt, or delivery ledger.

The catalogue records the advertised planned inclusion without treating it as proof that a particular attendee will receive or has received a badge.

Source note: Security BSides Kraków official 2026 ticket and agenda page.

HOPE 26 Digital In-Person Admission Ticket note

ticket fulfilment and admission boundary · official ticket listing · historical delivery statement; generated-ticket and entry process unverified

The official listing said tickets would be generated asynchronously and emailed before the event, but reviewed sources do not establish a delivered ticket, recipient, format, email timing, transfer procedure, account process, entry scan, access-control operation, support path, refund exception, replacement, or individual admission outcome.

The catalogue records the advertised digital-ticket identity artifact, not a confirmed credential implementation, completed delivery, or successful event access.

Source note: TICKETS TO HOPE 26 official 2600 store listing and current HOPE event home.

HackNWA 2026 VIP Assembled Badge note

ticket tier, allocation, and fulfillment boundary · official completed-event context plus contemporaneous tier capture · advertised VIP tier documented; purchase and handoff unverified

The reviewed ticket capture identifies a USD 109 VIP Assembled Badge category, while the official registration page now says sales ended. Neither source publishes the number offered or sold, purchaser identities, purchase terms, contents, pickup location, redemption process, allocation, manufacturing, delivery, receipt, replacement, refund, or post-event handoff outcome.

The catalogue records a concrete advertised ticket tier without treating it as proof of completed production, distribution, inclusion with every attendee, or individual possession.

Source note: HackNWA 2026 registration and contemporaneous AllEvents ticket listing.

WomenCon 2026 Digital Morpher Badge note

ticket, allocation, and distribution scope gap · official ticket posts and completed-event source trail · included-ticket intent and event completion documented; unit allocation unknown

The ticket posts say the badge was included and describe phase-one/phase-two price and capacity snapshots; the host-linked trail announces kit handoff and later event use. Neither source provides a final ticket ledger, inventory, production total, allocation between attendees/speakers/staff, redemption record, pickup result, package contents, replacements, post-event support, or confirmation that every participant received or used a working board.

The record does not present limited-capacity sales language, a registration announcement, or a high-level functional post as a complete distribution, entitlement, or support record.

Source note: WomenCon official ticket posts and IQSEC-host-linked public trail.

CypherCon 2026 Digital / Circuit Badge note

ticket, fulfillment, and tier-relationship boundary · official registration/FAQ and public timeline mirror · event completion corroborated; individual handoff unverified

The FAQ describes in-person redemption and the public timeline mirror says CypherCon 9 started and later wrapped, but no recovered source publishes Digital / Circuit Badge inventory, buyer or recipient scope, final production count, pickup completion, shipment, replacement, support, final board image, or whether it shared any hardware with the Extreme tier. The FAQ's general electronic-badge shipping caveat is not an individual delivery record.

This is a documented completed-event ticket artifact, not a claim that every purchaser received a particular board or that the three ticket forms had a known technical relationship.

Source note: CypherCon 2026 registration and FAQ plus the public CypherCon-account timeline mirror.

BSides Chennai 2026 Event Badge note

ticket-offer, source-currency, and fulfilment boundary · official ticket page, official CTF status, and Security BSides global calendar · conference and CTF completed; delivery and allocation unrecovered

The official CTF page says the separate 2026 CTF concluded, and the Security BSides global calendar marks the May 30 conference as passed. The Last Bird page lists an Event Badge but still presents stale sales language. Reviewed sources do not provide an all-ticket scope, stock count, ticket-to-badge mapping, pickup procedure, receipt record, lost-badge policy, shipment, replacement, or completed delivery ledger.

The catalogue treats the conference as completed while preserving the public ticket offer as evidence of an advertised credential, not a current sale, attendee-wide entitlement, or proof that a particular person received a badge.

Source note: BSides Chennai 2026 official ticket, schedule, and CTF pages, plus the Security BSides global community calendar, reviewed 2026-09-17.

BSides Cheltenham 2026 Challenge Coin note

ticket-tier scope and fulfilment boundary · official ticket-package wording · Early Bird inclusion documented; recipient outcome unrecovered

The named coin belongs to the Early Bird package, which the organizer currently marks sold out. The First and Second Release descriptions do not mention the coin. Reviewed material does not establish Early Bird quantity, eligibility details beyond that package, exact purchaser count, allocation, production inventory, registration pickup, recipient receipt, transfer outcome, loss/replacement policy, shipment, refund treatment, or completed delivery.

The catalogue does not turn a sold-out limited package into proof that every ticket holder, every Early Bird purchaser, or any individual attendee has received a coin.

Source note: BSides Cheltenham 2026 official event and ticket-package page.

DFIU SAO (DEF CON 34) note

touch, audio, LED, content, and accessibility boundary · maker wording and public implementation source · intended interaction evidenced; final experience and accessibility unverified

The maker describes face-touch interaction with a cheer track and the code exposes thresholded touch, sampled audio, and LED update logic. Sources do not establish touch sensitivity/calibration across users or environments, sound pressure/volume control, exact final audio content, LED count/color/brightness, latency, continuous-play behavior in shipped units, disability/accessibility accommodations, sensory warnings, language/content rating, audio-rights provenance, or reliability testing.

The catalogue describes the published interaction mechanism without making claims about usability, accessibility, sensory safety, audio licensing, annoyance, final behavior, or suitability in a particular venue.

Source note: BigFuckingBadge DEF CON 34 page and DFIU src/main.c.

BSides Exeter 2025 Pirate Ship Badge note

treasure-chest interaction, participant, and outcome boundary · maker repository description · venue interaction documented; configuration and player outcome unrecovered

The maker archive says attendees used venue treasure chests to unlock additional LED modes and preserves related source/model material. It does not publish a chest count, placement/deployment record, final companion configuration, connection details, challenge values, player count, participation data, score or completion data, participant identities, prize policy, official result, or ongoing service status. No interaction procedure is reproduced here.

The catalogue records the documented badge game without claiming universal participation, a completed CTF, any individual outcome, or a safe/reproducible operating procedure.

Source note: bsides-exeter-2025-badge README and public archive.

Portal Badge (DEF CON 34) note

unlicensed source, fabrication, and media reuse boundary · GitLab project metadata and source review · no detected project license

GitLab reports no detected license for the firmware or hardware project. Public access to C source, KiCad, Gerber, acrylic, CAD, production, sound, and image files does not grant permission to reproduce, modify, fabricate, redistribute, host, or reuse those materials or their media.

The catalogue links the public preservation trail without presenting it as open hardware, free software, a licensed build kit, or a cleared source for images/audio/artwork.

Source note: Portal Badge GitLab project metadata and repository trees.