CTF-linked acquisition route
The Puzzled Hackers Team says the top 50 participants had Free Badge Redemption attached to their CTF accounts before its final puzzle announcement. It does not publish the leaderboard, account criteria, rank calculation, redemption count, code-delivery mechanics, challenge archive, score review, anti-abuse process, or proof that every eligible participant collected a physical badge.
Compatibility: Puzzled Hackers LED Badge (DEF CON 34)
SAO add-on bundle
The listed kit includes a top SAO PCB with pre-soldered lights plus three SAOs and a connector set containing six unsoldered NeoPixels; the maker says those NeoPixels are sufficient to populate one included bottom SAO. No public connector pinout, SAO standard confirmation, or electronic design is claimed.
Compatibility: NYC Badge (DEF CON 34)
SAO and companion artifact
The listing says the badge has an SAO v1.69bis connector with I2C and includes one Pac-Man Ghost SAO in one of four colors. It does not disclose the connector's electrical characteristics, pinout, voltage, companion firmware, color allocation, compatibility test results, or reuse rights for the companion artwork.
Compatibility: Spectre Sniffer Badge (DEF CON 34)
SAO expansion
The listing calls both ports fully connected and 1.69bis-compliant, with dedicated GPIO, UART, and I²C connections per port. It does not publish pinouts, voltage/current limits, board layout, test results, or compatibility evidence for every SAO.
Compatibility: Shitty Kitty V2 (DEF CON 34)
DEF CON 34 Badge
official shop plus current public roster; pre-event outcome unconfirmed
SAO kit and optional pre-soldered add-on
Call Center Village's official shop describes a $5 pickup-only Solder-It-Yourself Telephone Booth SAO Kit for the DEF CON 34 badge. Its current public Badgelife roster row separately lists a $5 kit and $10 pre-soldered option. These source statements establish offered configurations and planned event context, not final inventory, payment, assembly, pickup, shipment, delivery, refund, replacement, or support outcome.
Compatibility: DEF CON 34 Badge
SAO purchase bundle
A separate Pfarrside Creations listing offers the badge with two SAOs for $140. The source establishes the optional bundle but does not identify the SAOs' electronic design, pinout, compatibility, software, or final allocation.
Compatibility: Cult of Cthulhu Indie DEF CON 34 Badge
add-on connector
The official DC34 SAO specification documents 3.0 V VDD, 100 mA tested total supply across both SAOs, GPIO pins, I2C devices at 0x3C and 0x19, and mirrored unkeyed 6-pin SAO headers.
Compatibility: DEF CON 34 Badge
announced acquisition and project context
The early project post says the maker intends to do drops and make receiving a badge part of the experience; it also says a second variant is necessary for the interaction. It does not publish quantities, price, sales channel, dates, selection method, pickup or shipping terms, allocation, recipient list, completed drop, or final count of variants.
Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)
announced community distribution
The Team says that after the paid cap is reached, distribution moves to random giveaways during the events. It does not identify giveaway quantity, timing, eligibility, selection method, organizer, physical allocation, handoff site, recipient list, or completed result.
Compatibility: Puzzled Hackers LED Badge (DEF CON 34)
announced contest-linked distribution
The repository says winners of the 2026 Beverage Chilling Contraption Contest receive copies while stock lasts, and BCCC's official page locates the contest at DEF CON 34. This does not prove award recipients, winner quantity, qualification rules beyond the contest page, stock allocation, event outcome, or that the marketplace presale and winner copies are the same final unit run.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
announced event challenge
The storefront says each badge unlocks a live hacking challenge and frames progression as completing stages to climb a scoreboard. No reviewed source identifies challenge rules, format, tooling, endpoints, account model, scoring method, prize, operational schedule, data collection, accessibility, or a post-event archive; no software is inferred to run on the physical artifact.
Compatibility: FloridaMan 2026 Badge
announced handoff route
The checkout lists Linq 3535 / Circle Bar pickup on Wednesday August 5 and Thursday August 6 from 7–10 PM PT and says there is no shipping. It says a receipt and offline QR claim code are sent after checkout; the Team says a badge must be collected at a meetup or by separately arranging DEF CON handoff, and the QR may be given to someone else. Those terms do not confirm venue access, checkout completion, code delivery, identity verification, handoff, or redemption outcome.
Compatibility: Puzzled Hackers LED Badge (DEF CON 34)
announced software readiness
The author says that most listed capability categories will not be ready out of the box and that only LED colour/brightness adjustment, a hidden software CTF or scavenger hunt, and NFC read/write are available on DEF CON day 1. That is an announced capability boundary, not a public firmware release, working demonstration, final event outcome, or guarantee of feature availability for every unit.
Compatibility: Sneakreaper Limited-Edition Badge (DEF CON 34) source-starred day-one feature set
availability and fulfillment record
The live DC801 page lists the badge at $120, says local-pickup scheduling emails were planned for July 20, targets remote shipping by July 27, and warns that orders placed after July 23 may arrive after DEFCON. These are seller terms and targets, not proof of inventory, payment, manufacture, shipment, pickup, arrival, refund, replacement, support, or event-time handoff.
Compatibility: Helgatchi Badge (DEF CON 34)
badge challenge
The official product page says BENDER hacking challenges will appear on the CTFd-hosted server at 10:00 Vegas time on Friday, August 7 because the badges are part of a DEF CON Contests & Events challenge, with activation instructions promised for the same day.
Compatibility: AND!XOR DC34 5N4CK3Y Badge
badge challenge and user-installed component surface
The guide says Badgey Bodgerton uses a supplied bodge wire plus a user-installed 3 mm LED, 1 kΩ resistor, and polarized buzzer in challenge work. It describes the parts and their badge-local challenge context without revealing answers or proving every badge shipped with identical parts, that a participant completed the work, or that any assembly is safe or successful.
Compatibility: Documented BadgeLife Village Badge challenge context; do not treat as a universal assembly or repair recommendation
badge creator and silicon announcement
DEF CON's July 31 official reveal names Bunnie Huang as the badge creator and says the badge features his open-source, fully inspectable Baochip; it does not announce final firmware, board files, or distribution details.
Compatibility: DEF CON 34 Badge
badge expansion interface
The current kit list includes a 2×3 SAO connector with wrong-way prevention. The archived assembly guide describes fitting the polarized six-pin header on the top PCB. Neither source publishes a final 2026 pinout, voltage, current budget, connector compatibility matrix, or tested accessory list.
Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)
badge game and story
The listing describes a 13-chapter Ritual with story, screen, and LED animations; six side-quest challenges; and Bling, The Corrupt Ritual, R'lyeh Arena, Another Adventure, Exploit, and Rick Roll unlockable modes. No firmware archive or full game-rule source is published.
Compatibility: Cult of Cthulhu Indie DEF CON 34 Badge
badge lineage and checkout options
The organizer calls Electric Fist its third EFF BadgeLife design for DEF CON and says reruns of NSA "All Your Data" Eagle and Privacy Badger can be added at checkout. It does not document component changes, quantities, physical variants, or whether every listed option is ultimately fulfilled.
Compatibility: EFF "Electric Fist" BadgeLife (DEF CON 34)
badge-hosted CTF progression
The public guide frames The Shattered Shard as a ten-chapter rune-restoration quest with sequentially unlocked progress and per-badge state. It establishes a planned game surface, not a full challenge archive, final scoring system, prize, winner record, completion ledger, event deployment, or permission to reproduce solutions or probe anything beyond an assigned badge and its advertised services.
Compatibility: The Shattered Shard challenge badge assigned to a participant; final availability and event deployment unverified
badge-to-badge communication
The application source documents an SX127x-class 915 MHz LoRa mesh and a PingMessage carrying sender name, RGB theme color, latitude/longitude, and a short status; the product calls its mesh self-healing with minimal configuration. It does not prove final RF parameters, privacy choices, message authentication, interference behavior, or regulatory suitability in every jurisdiction.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
badge-to-badge game system
The maker names Acolyte, Glyph, Elder God, and redacted Cthulhu badge types. Its Séance description says four badges complete a circuit and beacon to nearby badges, without identifying radio hardware, a wireless protocol, role counts, or on-site distribution confirmation.
Compatibility: Cult of Cthulhu Indie DEF CON 34 Badge
co-pickup purchase option
One sold-out $150 storefront option adds the separately-made Laser* Tag Badge DS from Dani.pink, which the maker says can be picked up alongside the Monorail badge. This records a bundled purchase/co-pickup statement, not shared hardware, firmware, manufacture, ownership, event affiliation, or a guarantee of either badge's delivery.
Compatibility: Monorail Con Badge (DEF CON 34)
community-event badge preorder
Hack Your Lives' current listing is sold out and says each assembled-badge order includes an additional blank PCB offered for in-person DEF CON 2026 pickup; uncollected blanks would ship with the assembled order. It says paid orders will be assembled and shipped by September 30. These seller statements do not establish paid-order count, completed assembly, shipment, delivery, pickup, replacement, refund, or that every order receives an identical final unit.
Compatibility: DEFCON Furs 2026 programme offer; not a DEF CON Human badge or a completed fulfillment record
completed event presentation context
Packet Hacking Village's official programme lists the completed Saturday Friend or Foe presentation at DEF CON 34. It links the documented project to a completed village programme but does not say the village made, distributed, sponsored, sold, or endorsed badges, or that attendees received one.
Compatibility: DEF CON 34 Packet Hacking Village programme context only; not a conference credential or allocation record
configuration and maintenance
The listing names a configuration PWA and USB-C updating. The firmware README describes one RPC registry exposed through web, USB serial, and BLE, including settings, saved messages/locations, OTA update, and system functions. The companion PWA repository is public but unlicensed and does not establish a deployed service, credential, or data-retention model.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
controller and power components
The listing names a pre-flashed ATMEGA328, 16 MHz crystal, two capacitors, resistor, two through-hole tactile switches, power switch, and AAA battery holder. It says three AAA cells are required but not included, without publishing wiring, voltage, charging, or a complete assembly guide.
Compatibility: NYC Badge (DEF CON 34)
current maker availability and price statement
BigFuckingBadge advertises the Portal Badge at $120 before DEF CON 34 and $150 through hackerwarehouse during the con, while its live page says presale is open and quantities are limited. This is a maker-stated current offer, not proof of a completed order, payment, manufacturing run, stock count, hackerwarehouse availability, pickup, delivery, refund, replacement, or post-event sale outcome.
Compatibility: Portal Badge (DEF CON 34); independent maker offer, not a DEF CON admission credential
current marketplace availability and event-drop statement
The live Brooke's Bytes listing displayed $10, 10 remaining, 20 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop. Badge.Life separately lists Brookes Bytes Badge and SAOs in its Friday 4 PM schedule slot. These time-sensitive statements do not establish a completed payment, final inventory, production run, product-to-slot allocation, completed drop, pickup, shipment, delivery, refund, replacement, or post-event outcome.
Compatibility: Badge Crown SAO (DEF CON 34); independent maker offer, not a DEF CON admission credential
current marketplace availability and event-drop statement
The live Brooke's Bytes listing displayed $10, 17 remaining, 33 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop. Badge.Life separately lists Brookes Bytes Badge and SAOs in its Friday 4 PM schedule slot. These time-sensitive statements do not establish a completed payment, final inventory, production run, product-to-slot allocation, completed drop, pickup, shipment, delivery, refund, replacement, or post-event outcome.
Compatibility: Hacker Boba Badge Kit (DEF CON 34); independent maker offer, not a DEF CON admission credential
current marketplace availability and event-drop statement
The live Brooke's Bytes listing displayed $60, 19 remaining, 11 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop. Badge.Life separately lists Brookes Bytes Badge and SAOs in its Friday 4 PM schedule slot. These time-sensitive statements do not establish a completed payment, final inventory, production run, product-to-slot allocation, completed drop, pickup, shipment, delivery, refund, replacement, or post-event outcome.
Compatibility: Agency Wand (DEF CON 34); independent maker offer, not a DEF CON admission credential
current marketplace availability and event-drop statement
The live Tw0nkus listing displayed an $80 price, five remaining, four sold, and a Defcon34 drop label. Badge.Life separately schedules Bread Badge by Tw0nkus in its current Friday DC34 village programme. These are time-sensitive availability and schedule statements, not proof of a completed payment, final stock count, production run, exact drop location/time, pickup, delivery, refund, replacement, or post-event outcome.
Compatibility: Breadbadge (DEF CON 34); independent maker offer, not a DEF CON admission credential
display and controller platform
The maker lists two 0.96-inch 80x160 color IPS screens, an RP2040 dual-core Arm Cortex-M0+ described as running at 200 MHz, 264 kB SRAM, and 16 MB Quad SPI flash. The listing does not publish a board schematic, display part number, clocks, or electrical measurements.
Compatibility: Shitty Kitty V2 (DEF CON 34)
distribution model
AND!XOR says its limited philanthropy sale reserves a badge for supporters while helping manufacture additional badges to give away; it says more than 84 percent are planned for free distribution through convention challenges, contests, and events.
Compatibility: AND!XOR DC34 5N4CK3Y Badge
documented audio and progression system
Source initializes SD-card SPI and DAC/DMA sound playback at 22,050 Hz, with a no-SD state, amp-enable pin, and on-chip fallback settings. Separate flash-state code records diode, SAO, badge-to-badge, game, and sphere unlock flags. The sources do not establish installed media, speaker/amplifier hardware, volume, content rights, storage-card provisioning, power/runtime behavior, or final event software configuration.
Compatibility: Portal Badge (DEF CON 34)
documented badge add-on
The README separately lists a companion SAO PCB, a six-pin male header, and four RGB LEDs, then says its LEDs light when connected to the main badge's six-pin female header. It does not establish an SAO version, pinout, voltage/current limits, LED model, electrical protection, hot-plug behavior, compatibility with any other host, assembly quality, or final distribution.
Compatibility: DC34 CompuNet Badge main project only; no universal SAO compatibility claim
documented badge interaction
The README says included slides or other RFID tags can be scanned to change what appears on the round display and mentions additional images intended for sharing or trading. It does not identify RFID frequency/protocol, tag type, reader configuration, stored content, data collection, authentication, access control, privacy practices, security properties, final gameplay rules, or a confirmed live event deployment.
Compatibility: Project interaction described in the public README; reader/tag protocol and final event behavior unverified
documented controller and power design
The README identifies a CH32V003 F4P6 RISC-V MCU and describes 3.3 V SAO-host input stepped to 5 V plus an automatic boost-disable path when USB-C 5 V is detected. It does not publish finalized USB-C hardware, board power budget, current/thermal measurements, fault behavior, host limitations, or safety/compliance results.
Compatibility: Not Just a Crosswalk SAO (DEF CON 34)
documented earlier firmware behavior
The Eventbrite listing says an appropriate mode can show deauthentication activity or nearby Flipper Zeros. The archived `camera_badge_rev01` source filters Wi-Fi management/data traffic, counts deauthentication frames while hopping channels, and performs BLE scans that increment a count for two source-labelled Flipper MAC prefixes. That is a source trail, not a validated 2026 alerting, identification, accuracy, privacy, or RF-compliance claim.
Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)
documented earlier hardware platform
The current list names a screen, an `ESP23 Dev Board /w connector`, switch, PCBs, and headers. The archived DC32 parts/assembly documentation identifies a 1.28-inch 240×240 GC9A01 round TFT plus an ESP32 Lite V1.0.0 / ESP32 REV1 Type-C Wi-Fi/Bluetooth board with LiPo connection and charging circuit. The sources do not map that documented platform to a verified final 2026 production revision.
Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)
documented electronic badge kit
The public README lists one PCB, ESP32 Dev Module, round LCD, RFID reader, microSD reader/card, slide switch, Schottky diode, RGB LED, six-pin female SAO header, battery holder, four AAA batteries, foam tape, stand, slides, and RFID sticker tags. It documents a project inventory, not a verified finished unit, component variants, electrical design, safe assembly/operation result, quantity, allocation, or completed event handoff.
Compatibility: DC34 CompuNet Badge project as documented in the public README; final unit and distribution unconfirmed
documented extension and challenge surface
The design document says a connected Portal Gun SAO, a two-badge USB connection, and a back-side soldered diode can unlock features. Current source implements 9,600-baud serial status handling, portal-SAO and badge-to-badge counters, a retained I²C pin setup, and a directional diode check. It does not publish a final compatible accessory, connector pinout, USB electrical design, I²C behavior, voltage/current budget, or test matrix.
Compatibility: Portal Badge (DEF CON 34)
documented firmware interaction
The project describes an infinity-mirror LED ring whose blue/cyan water effect follows gravity with damping, with selectable modes, dim/off behavior, motion wake, inactivity handling, watchdog recovery, and sensor-fault indication. This describes public intended software behavior, not final LED optics, battery runtime, motion accuracy, accessibility, production-firmware parity, or operation of a distributed badge.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
documented firmware interaction
The README says palette and effect indices persist in CH32V003 flash memory and identifies a PD3 effect button and PD2 palette button. It does not establish a final firmware build, power-loss behavior across all revisions, input accessibility, user guide, release process, or recipient experience.
Compatibility: Not Just a Crosswalk SAO (DEF CON 34)
documented game and interaction design
The design document describes Standby, Game, and Nyan modes plus a four-level puzzle in which spheres move through portals while users avoid or extinguish fire. The committed source contains standby, nyan, game, Simon, fire, display, random, and unlock modules. Design notes include TBD/possibly-change language, so this is a documented pre-event design and implementation trail rather than proof of final gameplay or attendee instructions.
Compatibility: Portal Badge (DEF CON 34)
documented lighting and input surface
The firmware defines 85 24-bit LED pixels and fourteen active-low input positions labelled for four personality spheres, four portals, radio, camera, Nyan, Aperture, turret, and cake. The design document calls these button/touch interactions. The sources do not confirm the final physical input technology, LED package, enclosure, brightness, current draw, or accessibility behavior.
Compatibility: Portal Badge (DEF CON 34)
documented lighting surface
The README consistently specifies eighteen side-emitting addressable LEDs, while using `WS2812-2020` in the overview and `SK6812D-EC3210R` in its feature list. The record retains the shared count and source labels without deciding which part number, brightness, color order, current draw, or final layout was manufactured.
Compatibility: Not Just a Crosswalk SAO (DEF CON 34)
documented microcontroller and build platform
The committed PlatformIO configuration targets `genericCH32V303CBT6` using the `ch32v` platform and `ch32v003fun` framework; firmware configuration enables the CH32V30x family and declares 128 KiB flash. No source identifies a final flashed event binary, board configuration, toolchain lockfile, test report, or recovery path.
Compatibility: Portal Badge (DEF CON 34)
educational source archive
The repository publishes starter scripts, a helper library, and code-challenge material for the named Cyber-Cat project. The release page reports no releases. This provides a public educational source trail, not a final installed event image, a configuration or operating guide, a supported update path, a source-to-device mapping, or a code/media reuse authorization.
Compatibility: Cyb3rBytes404 Cyber-Cat project documentation only
engineering and software source surface
Pips801 publishes drawings, front/back PCB and test-jig directories plus firmware and UI trees; the Software README names an older PlatformIO build/erase/filesystem/upload path. The current public archive does not itself establish final production parity, a stable release, a complete build environment, a warranty-safe flashing path, an explicit license, or permission to republish source media.
Compatibility: Helgatchi Badge (DEF CON 34)
event access context
The official storefront says entry is badge-only and that every attendee needs a valid event badge for venue access. It does not explain credential validation, name transfer, whether the listed product alone is sufficient, age/guest/sponsor conditions, venue capacity, door policy, or whether this party badge has any relationship to a DEF CON registration credential.
Compatibility: FloridaMan 2026 Badge
event-associated pre-event project
FirstBuild's public repository identifies a DefCon 34 washer/dryer badge and a FirstBuild / GE Appliances context, while DEF CON's own event source separately identifies the Baochip Human badge. Separately, a public Reddit author says they will give away 100 badges from a stated GE Appliances IoT Village booth. No reviewed official organizer source confirms that booth arrangement, and the sources do not say this washer/dryer project is a Human badge, is included with registration, grants admission, is issued by DEF CON, or has completed event availability.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
firmware and user interface
The listing describes SkittyOS graphics demos, scrolling text, font/character settings, independent screen modes, and flash-persisted settings, and announces future firmware with new graphics and puzzles. No firmware release, source, binary, flashing guide, or license is linked.
Compatibility: Shitty Kitty V2 (DEF CON 34)
firmware build surface
The public code repository defines a PlatformIO `ch32v` / `genericCH32V003F4U6` / `ch32v003fun` environment and provides C implementation material. It does not publish a final binary, release notes, version mapping, programmer details, full build prerequisites, flashing/recovery steps, signed update path, security review, support policy, or explicit license grant.
Compatibility: DFIU SAO (DEF CON 34)
firmware release and build workflow
The firmware repository is detected as MIT and documents PlatformIO `hardware-v3` and older-revision environments; v4.0.0 publishes v3 and v2 binary assets. The source depends on a side-by-side local `esp32-utilities` repository and does not establish a supported update path for every physical unit or a released v1 v4 binary.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
first-person pre-event acquisition statement
The maker post says there is only a small batch, the badges are not for sale, and they will be given away randomly throughout ‘the con.’ It does not establish a quantity, eligibility rule, selection method, exact times/locations, reservation system, partner, recipient list, actual handoff, shipment, replacement, or post-event result.
Compatibility: Cyb3rBytes404 Cyber-Cat Badge (DEF CON 34) pre-event maker statement only
first-person public pre-event giveaway update
The public r/Defcon author says another 100 free badges are planned at the stated GE Appliances booth in IoT Village and that an unspecified number will be given away each day. The statement does not give a daily split, distribution dates or hours, eligibility, queue or pickup process, recipient list, completed build count, final physical stock, completed handoff, or official organizer confirmation.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
first-person public provenance statement
In a public comment, the author says the badge was designed in-house at FirstBuild and that employees created the artwork, PCB design, and software. This preserves a narrow public provenance statement without identifying individuals, establishing the author's employment or authority, independently verifying every contribution, assigning image rights, or extending the statement into a formal FirstBuild, GE Appliances, or DEF CON attribution.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
fundraising and project relationship
The listing says BadgeLife proceeds support EFF's mission, and its FAQ says the project is officially affiliated with EFF but organized independently by H4r0ld and V3rbaal, with EFF aware of and supportive of the fundraising efforts. The source does not publish financial or donation-accounting terms.
Compatibility: EFF "Electric Fist" BadgeLife (DEF CON 34)
hardware and fabrication archive
The hardware repository visibly contains KiCad board/schematic/project material, BOM/position files, front/back/order Gerbers, and acrylic directories/files. The published tree is traceability evidence, but this pass did not reconcile it to a final 2026 populated board, fabrication order, component sourcing, acrylic process, assembly/test procedure, host connector/power design, or explicit license.
Compatibility: Portal Gun SAO (DEF CON 34)
hardware and user interface
The maker lists an ESP32, USB-C, rechargeable Li-Po, ten LEDs, a screen, and one button. It describes short presses as scrolling and long presses as selecting, but does not publish component variants, circuitry, pinout, power details, or electrical documentation.
Compatibility: Cult of Cthulhu Indie DEF CON 34 Badge
hardware design archive
The hardware repository visibly contains a KiCad PCB and schematic plus BOM, position, Gerber, backup, and layout files. The published tree is useful for traceability, but this pass did not reconcile it against a final populated board, fabrication output, BOM sourcing, test procedure, connector pinout, power design, or any explicit source license.
Compatibility: DFIU SAO (DEF CON 34)
hardware design archive
The hardware repository visibly contains KiCad board/schematic/project material, BOM/position data, front/back/prototype Gerbers, backup files, and a PFC161 datasheet. The published tree is traceability evidence, but this pass did not reconcile it to a final populated unit, fabrication order, component sourcing, test procedure, connector/power design, or explicit license.
Compatibility: IFLFU SAO (DEF CON 34)
hardware kit and assembly
The maker describes a beginner-friendly kit in which the bridge and back-layer NeoPixels are pre-soldered and the builder solders header pins plus through-hole chip parts. The listed board set is the back layer, bridge, top SAO, city, water, and frame PCBs.
Compatibility: NYC Badge (DEF CON 34)
hardware preservation and fabrication material
The companion hardware repository includes KiCad project/schematic/PCB material, Gerber and production directories, board variants, position data, acrylic DXF/SVG files, and manufacturing-oriented archives. Recent commits include board bug fixes and acrylic SVG work. GitLab shows no detected license, and the source does not establish a final approved BOM, build instructions, production completion, or safe redistribution/assembly permission.
Compatibility: Portal Badge (DEF CON 34)
historical first-run delivery choices
The official shop displayed free pickup at DEF CON, U.S. shipping priced at $20–$30 plus tax, and contact-based global shipping, with order caps. The current page now hides ordering and displays a no-payment second-run interest form because all first-run inventory is sold out. These past/current storefront terms do not prove buyer handoff, event pickup, shipment receipt, future rates, or a completed second run.
Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge
historical product-context record
Hak4Kidz Lab's live same-name Tindie listing calls v2.2 an upgrade from a 2019 v1 and says it was made for DC31; it currently displays $30. The roster's current DEF CON 34 row instead says new and approximately $35 at Hacker Warehouse. The sources do not say whether those sales paths use identical stock, components, finish, packaging, installation parts, price, or revision.
Compatibility: Star Trek SAO Phaser v2.2 (DEF CON 34)
historical product-lineage record
MakeItHackin's live $30 Tindie listing, repository, and tutorial describe a differently named Tricorder SAO, including separate rechargeable-battery and badge-powered forms. The current roster calls its $125 artifact an Original Series Tricorder badge with various sensors. The sources provide no formal revision, parts, behavior, price, or stock mapping between the two products.
Compatibility: Original Series Tricorder Badge (DEF CON 34)
historical public fabrication reference
NilbinSec's DC32 repository lists two 470-ohm resistors, three flashing RGB LEDs, one cloudy red LED, and a 2×3 shrouded SAO header, with Gerber files and assembly orientation notes. It supplies a traceable older design surface but does not prove that every planned 2026 unit uses the same PCB, component values, LED speed/colors, header, finish, or behavior.
Compatibility: NilbinSec Power Glove Re-release SAO (DEF CON 34); historical NilbinSec DC32 Power Glove source
in-progress code surface
The game repository references ST77xx display libraries, NimBLE, QR-code support, and a buzzer-oriented sound module. It does not publish a stable radio protocol, user-consent model, player-data practice, safe electrical design, final UI, host compatibility matrix, or proof that these modules ship together in a DEF CON artifact.
Compatibility: CPEC DC34 MechBattle Badge
kit hardware and assembly
The current kit inventory and DC32 guide enumerate three addressable LEDs, five blue LEDs, one bright white LED, eight 47 Ω resistors, three capacitors, a 3.7 V / 1,200 mAh LiPo, battery adhesive, JST/PH wiring, and board-to-board headers. The guide calls for through-hole assembly and battery wiring, not a safe modification or battery-service authorization.
Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)
linked-primary-source hardware description
AoSC describes Micro-USB, one large touch pad, three NeoPixel groups, a small speaker, and no battery. The linked Coin M0 profile instead describes native USB-C, three capacitive touch pads, three RGB-NeoPixel groups, and a speaker. The shared lighting/audio concepts are source-backed, but the exact connector, touch count, board revision, LED count/current, speaker part, power path, and final 2026 configuration remain unresolved.
Compatibility: 2026 eChallengeCoin (DEF CON 34)
local control and development interface
The source maps a left multi-press mode selector, right Attack/Trigger switch, four color-coded status LEDs, optional 9600-baud UART debug output, and ATtiny1614 serialUPDI programming context. The README gives an avr-gcc/ATtiny device-pack/avrdude outline and says a later convention reflash may happen, but no supported end-user programmer, fuse configuration, tagged release, update package, recovery guide, or warranty is published.
Compatibility: NilbinSec DC34 Main Badge Fuzzer SAO
main-badge interface probe
The README says Mode 1 cycles GPIO1/GPIO2 on the left badge port. The current source drives four two-bit patterns, releases the lines, samples them, and then listens for edges. NilbinSec explicitly warns that this mode may harm a main badge depending on its GPIO configuration, so the source does not establish a safe, supported, or authorized use on any connected device.
Compatibility: NilbinSec DC34 Main Badge Fuzzer SAO; intended public-information target is the DEF CON 34 main badge
main-badge interface probe
The README describes Mode 2 as triggering the open-drain CPU wake-up interrupt on GPIO4 of the right SAO port. The source holds its configured GPIO line low while the Attack/Trigger switch is pressed, then releases it to high impedance. This documents the public implementation, not a safe/authorized use, final badge compatibility, or successful challenge result.
Compatibility: NilbinSec DC34 Main Badge Fuzzer SAO; right-side target-port interpretation
main-badge interface probe
The README broadly says Mode 3 cycles 0x00–0x7F while listening as an I²C slave. The source instead documents passive bus observation over 0x08–0x77 and explicitly skips 0x19 and 0x3C. It says it does not drive SDA/SCL or ACK, but this is still not a guarantee of target compatibility, complete address coverage, bus safety, or authorized testing.
Compatibility: NilbinSec DC34 Main Badge Fuzzer SAO; intended main-badge I²C surface
maker and public-documentation hardware surface
The sources name an ATtiny1616, five reverse-mounted addressable LEDs, rear ambient-light LED, handle setup LEDs, two physical controls, CR2032 power with polarity protection, a more efficient 3.6 V boost converter, and external MOSFET gate. They do not establish final PCB/schematic/BOM, exact LED or power configuration, current draw, runtime, electrical limits, fabrication, test result, safety validation, or that all delivered units use the documented REV1 design.
Compatibility: Agency Wand DC34 documentation; final physical-unit parity unverified
maker and repository physical configuration
The repository README calls Beelzebub a holder for five minibadges, while the store says the board is assembled except for minibadge headers and an optional battery holder, and excludes shown minibadges. Those statements do not establish the exact slot layout, header/pinout, MiniBadge standard, power/clock/data behavior, soldering skill or safety requirements, attachment force, mechanical fit, contents of every unit, or compatibility with a particular minibadge.
Compatibility: Beelzebub Minibadge Holder (DEF CON 34); externally supplied minibadges
maker and repository physical configuration
The repository README calls Krampus a holder for six minibadges, while the store says the board is assembled except for minibadge headers and an optional battery holder, and excludes shown minibadges. Those statements do not establish the exact slot layout, header/pinout, MiniBadge standard, power/clock/data behavior, soldering skill or safety requirements, attachment force, mechanical fit, contents of every unit, or compatibility with a particular minibadge.
Compatibility: Krampus Minibadge Holder (DEF CON 34); externally supplied minibadges
maker firmware and provisioning release
The source release includes a UF2, user-preferences delta, build notes, provisioning GUI/script, and hardware-independent tests. It names a Meshtastic `event/defcon34` relationship and documents its own source-published configuration boundary, but it is not treated as a post-event support commitment, exact delivered-unit inventory, or a general-purpose flashing procedure.
Compatibility: RAK4630-based Darknet SMAO source design; not a universal user-update recommendation
maker technical release
The reviewed maker release contains the v1.4 KiCad project, DRC/ERC reports, Gerber archive, BOM/placement/netlist production files, board documentation, populated-board media, and NanoVNA tuning material. The repository calls its production outputs the exact files from which its run was built; the catalogue preserves that as a maker statement rather than independent manufacture, quality-control, or field-performance proof.
Compatibility: Darknet-NG SMAO v1.4 technical source project; physical unit parity and host compatibility unverified
maker-announced pre-event availability
The Exploitee.rs announcement says a new Hacker Pager revision is being brought to DEF CON 34, describes online availability windows, BadgeLife Village pickup, and no on-site sales. It does not publish a final inventory, price, order ledger, vendor authorization, completed sale, pickup, delivery, refund, replacement, or post-event availability result.
Compatibility: Independent Hacker Pager project associated by its maker with DEF CON 34; not a DEF CON admission badge
maker-described SAO components
The listing says the Sphere SAO works with upside-down SAO ports and the High Roller SAO has blinky lights. The source does not provide a pinout, electrical requirement, LED count/type, firmware, published design, host test matrix, or general compatibility guarantee.
Compatibility: Monorail Con Badge (DEF CON 34)
maker-described acquisition and manufacturing context
AoSC says a confirmed $100-or-greater donation to a youth-STEM-supporting charity may receive a 2026 eChallengeCoin by U.S. mail or DEF CON pickup, and says the first 20 recipients are intended to have brass blanks created by students from a local high-school engineering program. These statements do not establish charity status, tax treatment, donation validation, privacy/retention practice, quantity awarded, recipient eligibility, shipping, pickup, school identity, manufacturing quality, payment, or final delivery.
Compatibility: 2026 eChallengeCoin (DEF CON 34)
maker-described analog lighting surface
HogFillet describes a 555 timer clocking a ten-bit ripple counter, eight counter outputs driving eight LEDs, and an onboard trimmer controlling the timing rate. The source does not name component variants or values, flash-rate range, LED current, supply limits, power draw, electrical protection, schematic, BOM, PCB files, or final unit test results.
Compatibility: HackThePlanet SAO (DEF CON 34)
maker-described audio and storage surface
The product page says the speaker SAO plays monorail-themed sounds and has a mini SD card for adding MP3 files. It does not identify audio hardware, controller, firmware, MP3 limits, file workflow, source audio, media license, volume/safety behavior, or final shipped implementation.
Compatibility: Monorail Con Badge (DEF CON 34)
maker-described audiovisual behavior
The maker says the badge has three pre-programmed sound effects with accompanying light shows, including a gong effect. It does not identify audio hardware, firmware version, sound files, copyright/recording rights, controls, runtime, accessibility, configuration, or final shipped behavior.
Compatibility: Whose Slide Is It Anyway? 10 Year Anniversary Badge
maker-described badge game
The maker says the 2026 coin presents as a serial device when connected to a computer and hosts the Sara and the Missing Artifacts terminal text adventure. It also says new firmware can support other adventures. No public game source, binary, command reference, release/version mapping, host test matrix, reset/save guide, accessibility documentation, or support policy was recovered.
Compatibility: 2026 eChallengeCoin (DEF CON 34)
maker-described badge game
The project page describes a Game Boy-inspired top-down adventure with 30-plus CTF puzzles, while the live listing describes 35-plus CTF and puzzle challenges. Both frame the badge as a playable adventure with unlockable bling; no public challenge archive, final count, solution policy, ruleset, scoring system, accessibility review, or completed game behavior is published.
Compatibility: Wordweaving Badge (DEF CON 34)
maker-described badge interaction
The project page says badges can link up to 50 units, while the live listing says participants can create more than 1,000 unique words and phrases with other badges. Neither source publishes the transport, pairing, range, privacy/security model, player-data handling, protocol, connectivity requirement, interoperability, or final event behavior.
Compatibility: Wordweaving Badge (DEF CON 34)
maker-described badge purpose
The README says the badge lets users display an estimate for when the AI singularity will occur, with front buttons that shift that estimate, eight seven-segment displays, and a real-time clock. It documents a source-project interaction concept, not an assembled unit, final screen/readout behavior, calibrated clock, usability result, event challenge, prize, or completed distribution.
Compatibility: DC-34 Countdown to Singularity project as described by its public README; final physical unit unverified
maker-described companion appearance
The Spectre Sniffer listing says one included Pac-Man Ghost SAO comes in one of four colors. It does not name those colors, explain random or selected allocation, provide variant photos with reuse rights, map colors to the 1,000-unit giveaway, or establish identical artwork, PCB, components, behavior, or mechanical compatibility across all artifacts.
Compatibility: NilbinSec PAC-MAN Ghost SAO (DEF CON 34); Spectre Sniffer Badge (DEF CON 34)
maker-described companion artifact
A direct NilbinSec Bluesky reply says a Spectre Sniffer purchase includes a PAC-MAN Ghost SAO and helps fund over 1,500 free SAOs for Vegas. This is a product-bundle statement, not proof that the included companion is the same board, color, quantity pool, or configuration as the separately announced 1,000-unit giveaway.
Compatibility: NilbinSec PAC-MAN Ghost SAO (DEF CON 34); Spectre Sniffer Badge (DEF CON 34)
maker-described companion behavior
The roster says touching the gun's end changes animated colors and that it interacts with the PORTAL Badge; the maker page describes blue portal, orange/red portal, and off modes and calls it a companion to the year's Portal Badge. Those claims do not publish a final interaction protocol, connector/pinout, input/output voltage/current budget, compatibility matrix, required Portal Badge revision, test results, or guarantee that any two units interoperate.
Compatibility: Portal Gun SAO (DEF CON 34) and Portal Badge (DEF CON 34)
maker-described companion-app connection
The product page says configuration and messaging use the Meshtastic app over BLE and that each unit has its own BLE PIN printed on its bag. The catalogue does not store PINs, identify a pairing workflow, claim a privacy/security review, or describe shared mesh traffic as private.
Compatibility: Darknet-NG SMAO (DEF CON 34)
maker-described companion-controller surface
The listing names an onboard ATtiny814 connected to two RGB LED eyes, with power from the SAO connector or an included CR2032 battery. It does not publish default firmware, LED electrical data, power budget, battery runtime, voltage limits, connector pinout, host matrix, or final behavior.
Compatibility: UPDeeDeeI SAO (DEF CON 34)
maker-described compatibility boundary
The listing says v1.0 changes labeling and swaps I2C and GPIO pins from v0.1. It explicitly says the SAO does not support SAOv3 ARP or hot-plugging features. This does not establish final firmware behavior, electrical hot-plug safety, backwards compatibility, host-specific behavior, completed testing, or a full SAOv3 implementation.
Compatibility: Firefly Jar SAO (DEF CON 34)
maker-described controller and lighting surface
The maker lists an ESP32-C3 and 24 RGB LEDs. The source does not identify the exact module, board revision, LED package/layout, power budget, radio configuration, antenna, electrical characteristics, or test results.
Compatibility: Whose Slide Is It Anyway? 10 Year Anniversary Badge
maker-described core hardware and reprogramming surface
The listing names an ATtiny1616-S, two-character fourteen-segment display driven through shift registers, RGB LED, timer-based non-hardware-PWM behavior, and reprogramming through a separate UPDI adapter. It does not publish final firmware, exact parts/configuration, code, flashing instructions, electrical design, display/LED behavior contract, or support policy.
Compatibility: Volatile Organic Canary SAO (DEF CON 34)
maker-described core hardware surface
The live listing names an RP2350 with 4 MB flash, 16 RGB addressable LEDs, and a 128x128 grayscale display; the maker project page calls the display a 128x128 OLED. The source does not identify exact part numbers, wiring, final layout, revision, component list, schematic, PCB, test data, or a complete screen/LED specification.
Compatibility: Wordweaving Badge (DEF CON 34)
maker-described core hardware surface
The listing names seven orange reverse-mounted LEDs, an ATtiny824, and reprogramming with a separately obtained UPDI adapter. It does not publish exact LED electrical data, power budget, controller configuration, final firmware, wiring, flashing instructions, or a board-revision test record.
Compatibility: Firefly Jar SAO (DEF CON 34)
maker-described detection and alert surface
The product and repository describe configurable matching against BLE and Wi-Fi identifiers such as MAC/OUI/manufacturer/device-name/service/SSID fields, with LED, vibration, screen-wake, and scan-setting choices. They do not publish detection range, radio state timing, false-positive/false-negative rates, rule precedence, actual target databases, data retention, export, device consent, security controls, or a universal detection guarantee.
Compatibility: Helgatchi Badge (DEF CON 34)
maker-described development and host interface
The source tree documents USB-C, UF2, SWD pads, a rear 2x3 SAO header, and a claimed SAO v1.69bis fit. It does not establish a pinout or electrical limit for every host, a supported-host matrix, a safe user workflow, or a general compatibility guarantee.
Compatibility: Darknet-NG SMAO v1.4 source design
maker-described electrical design surface
The technical release documents a four-layer board, chip-antenna feed/match design, u.FL test points, SAO-or-USB-C power mux, no battery, and source-published tuning data. Its claimed measured and power-budget context remains maker evidence, not a blanket electrical-safety, host-compatibility, or performance guarantee.
Compatibility: Darknet-NG SMAO v1.4 source design
maker-described electronic add-on surface
The maker says the Crown is fully soldered and assembled, names one SAO connector, three flashing red LEDs, and three resistors, and says it needs no separate battery or programming. The listing says only to use a compatible badge; it does not identify the connector standard, pinout, supply range, current draw, flashing circuit, LED/resistor parts, polarity/protection, host matrix, or safe attachment result.
Compatibility: Badge Crown SAO (DEF CON 34); host-badge compatibility unverified
maker-described electronic feature surface
The maker describes twenty-four NeoPixel LEDs, an ATtiny 814, USB-or-battery power, and custom or pre-programmed themes. The public firmware defines four eye and twenty wing LED arrays plus color/mode code. The sources do not establish LED model/current, exact final color order, controller package/fuses, USB/power implementation, power budget, battery type, safety, or final production parity.
Compatibility: Beelzebub Minibadge Holder (DEF CON 34)
maker-described electronic feature surface
The maker describes five NeoPixel LEDs, an ATtiny 814, development-pin access, USB-or-battery power, and custom or pre-programmed themes. The public firmware defines a five-element LED array plus color/mode code. The sources do not establish LED model/current, exact final color order, controller package/fuses, development-pin or USB/power implementation, power budget, battery type, safety, or final production parity.
Compatibility: Krampus Minibadge Holder (DEF CON 34)
maker-described electronics and assembly surface
The maker lists a Hacker Boba PCB badge, keychain, power switch, CR2032 holder, included CR2032, three flashing RGB LEDs, and three resistors. It says the kit arrives unsoldered and needs basic soldering supplies. The listing does not establish a final board/BOM, part specifications, holder polarity/protection, LED current, runtime, power budget, switch rating, soldering quality, test process, or safe assembled result.
Compatibility: Hacker Boba Badge Kit (DEF CON 34); final assembly and electrical behavior unverified
maker-described firmware capability surface
The listing advertises display/LED animations, UPDI ping/erase/flash functions with raw HEX loading from internal storage, I2C tools, and voltage/current/power sensing. It documents claimed capability at a high level, not an audited firmware build, target-safe programming procedure, access-control model, data integrity guarantee, complete toolchain, user guide, release, or support commitment.
Compatibility: Breadbadge (DEF CON 34); source-to-unit firmware and target-device behavior unverified
maker-described firmware provenance feature
The project owner says the firmware is signed and each badge has its own key pair. No public material identifies the signature/key algorithm, trust anchor, key generation/storage/backup/rotation/revocation model, hardware security boundary, verification path, source, binary, build provenance, update procedure, or external review.
Compatibility: Station 562 Badge (DEF CON 34)
maker-described firmware target and interaction surface
The README says the firmware targets an ESP32-C3 driving a 240×320 ST7789 IPS panel with a capacitive touch controller at I2C 0x15, controlled by swipes and taps with no buttons. It does not identify exact modules, panel/controller variants, PCB integration, power path, touch calibration, gesture thresholds, final unit behavior, or hardware test results.
Compatibility: MidWestCoast source-described target only; not a final hardware compatibility claim
maker-described game software
The team says the CTF lives in firmware, is multi-stage and not solo-completable, uses real protocols, and unlocks backend pages through progress. No code, binary, challenge archive, protocol specification, endpoint, scoring system, access policy, data policy, or final running service is published in the reviewed sources.
Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)
maker-described hardware and prototyping surface
The maker lists an RP2354A, INA3221 I2C voltage/current/power monitor, ST7789 SPI display, six WS2812 RGB LEDs, navigation joystick/back button, and breadboard-compatible prototyping platform. The listing does not establish schematic/BOM/revision, component configuration, monitor calibration, exact breadboard fit, power/current limits, test results, or safe operation.
Compatibility: Breadbadge (DEF CON 34)
maker-described hardware challenge
The live listing says that soldering additional components unlocks CTF challenges. It does not identify the components, modification points, tools, difficulty, required safety precautions, challenge behavior, allocation, assembly instructions, or support scope.
Compatibility: Wordweaving Badge (DEF CON 34)
maker-described hardware form factor
The official Standard description calls Clip-Boy a wrist-mounted ESP32-S3 electronic badge and says the Standard enclosure is 3D printed in gunmetal gray. The maker says Pro and RAD editions have the same features, with different color/edition presentation. No reviewed source supplies the final PCB, mechanical drawings, enclosure material/process parameters, component list, dimensions, power system, antenna design, or production revision.
Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge
maker-described hardware surface
The seller names a CH32V003, 12-LED Charlieplexed matrix, single-layer circular board with exposed traces/no protective enclosure, hand-soldered two-AA configuration, and a 16 KB flash / 2 KB SRAM claim. It does not publish a circuit, parts list, board files, dimensions, battery chemistry, voltage/current limits, power or protection design, component values, assembly/test method, safety guidance, or measured runtime.
Compatibility: Ouroboros Badge (DEF CON 34)
maker-described host GPIO interaction
The maker says GPIO 1 and GPIO 2 each have separate hardware, switches, LEDs, and button-input options, independent of the animation engine and I2C controls. It says a host can drive an LED path or receive button input, with selectable logical polarity. No schematic, safe-voltage/current envelope, host-pin map, test matrix, or compatibility guarantee is published.
Compatibility: Root Access SAO (DEF CON 34)
maker-described host attachment
The listing calls the header standard 2 by 3 SAO and says the LED lights when connected to the DC34 badge with no adapter needed. It does not publish connector orientation, voltage/current limits, pinout, host matrix, protection circuitry, test result, or a universal compatibility guarantee.
Compatibility: Luna SAO (DEF CON 34)
maker-described host interaction
The listing says a button can be shorted to the odd or even GPIO of the DEF CON badge SAO header and that the outcome depends on the attached badge. It also explicitly says the SAO has no firmware and no I2C handshake. No source publishes the exact host pin map, circuitry, switch behavior, voltage/current limits, or a tested result on a particular badge.
Compatibility: HackThePlanet SAO (DEF CON 34)
maker-described initial software state
The maker's release names an exact source-published UF2 version, `event/defcon34` relationship, CLIENT_MUTE role, 10 dBm configuration delta, and per-unit provisioning material. It does not prove that every offer or collected item used that exact image, and it is not a post-event update or support guarantee.
Compatibility: Darknet-NG SMAO v1.4 source design
maker-described input and sensor surface
The sources name capacitive touch, a 10 kOhm potentiometer, buzzer, microphone, hall-effect sensor, LSM6DS3TR IMU, ambient-light sensor, internal temperature sensing, and input-voltage monitoring. They do not publish final calibration, microphone privacy behavior, sensor accuracy, environmental limits, sampling policies, current build completeness, or user safety guidance.
Compatibility: MalO SAO (DEF CON 34)
maker-described interaction hardware surface
The team says the project consists of two objects with ESP32-S3, IR, NFC, BLE, and a buzzer; one transmits while another was built to counter it. The source does not identify exact modules, electrical design, radio configuration, protocol, range, antenna, power system, test method, final revision, or delivered behavior.
Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)
maker-described interaction surface
The maker describes a BLE number-station puzzle, red-versus-blue proximity game, autonomous social/dance mode, expressive BLE MIDI instrument, tamper-evident mode, Setup menu, and optional hardware CTF. The source does not describe BLE services, radio range, pairing, player/account data, game protocol, MIDI mapping, tamper condition, CTF rules, security controls, or final behavior.
Compatibility: Station 562 Badge (DEF CON 34)
maker-described interaction surface
The Standard product description advertises customizable LEDs, a theremin, and more than 90 collectibles; the shop's social metadata also names a 3D-code scanner. No reviewed source explains the underlying components, collectible encoding, scanner modality, data storage, interoperability, game rules, accessibility, privacy, service availability, or post-event preservation. These are maker-described features, not a verified technical specification.
Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge
maker-described interface and development surface
The listing names UART, UPDI selected by a DPDT slide switch sharing the UART port, I2C, 5 V, 3.3 V, internal RP2350 debug, and external debug breakouts. It does not publish a pin map, connector type, voltage/current envelopes, target matrix, switching isolation, debugger implementation, electrical protection, or safe integration instructions.
Compatibility: Breadbadge (DEF CON 34); external-target compatibility unverified
maker-described light and assembly surface
The maker says v2 has either blue or yellow LED colors, is a kit requiring soldering, and uses components that are 1206 or larger. It does not publish LED count/model/current, circuit, resistor values, BOM, PCB files, assembly order, required tools, soldering/ESD precautions, battery safety, runtime, test procedure, firmware, or electrical-safety validation.
Compatibility: Day of the Dead Turkey v2 (DEF CON 34)
maker-described light and assembly surface
The maker says v1 has either blue or yellow LED colors, is a kit requiring soldering, and uses components that are 1206 or larger. It does not publish LED count/model/current, circuit, resistor values, BOM, PCB files, assembly order, required tools, soldering/ESD precautions, battery safety, runtime, test procedure, firmware, or electrical-safety validation.
Compatibility: Day of the Dead Turkey v1 (DEF CON 34)
maker-described lighting artifact
The maker says the unit is fully assembled, uses a standard 2 by 3 pin header, and its red eye glows when powered through the SAO header. It does not publish LED current, circuit, controller, power budget, voltage limits, pinout, host matrix, schematic, BOM, PCB files, dimensions, final revision, safety guidance, or test data.
Compatibility: METROPOLIS AI SAO (DEF CON 34)
maker-described measurement behavior
The maker lists SGP40 VOC and SHT4x temperature/humidity sensors, a raw-reading option, and a relative VOC-index algorithm with an approximately ten-minute warmup. It expressly says no accuracy claims are made and the device must not be relied on for accurate air-quality measurements. The source does not publish calibration, environmental test, threshold, exposure, health, safety, or certification evidence.
Compatibility: Volatile Organic Canary SAO (DEF CON 34)
maker-described no-code and external-service surface
The maker explicitly says the kit has no microcontroller or firmware to configure and says a back QR code opens a Google Maps Boba Shop search. It documents a narrow no-code and convenience feature only; it does not publish the exact QR payload, application terms, data behavior, source/design files, search accuracy, service availability, or a support commitment.
Compatibility: Hacker Boba Badge Kit (DEF CON 34); QR destination and external-service behavior unverified
maker-described physical art direction
The product page says it includes a silkscreen replication of the Whose Slide gong artwork, a design mentored by Blenster, and custom rear artwork by 1DarkOne. The source does not provide source-art files, authorship chain, individual reuse permissions, a production-art proof, or a cleared hero-image asset.
Compatibility: Whose Slide Is It Anyway? 10 Year Anniversary Badge
maker-described physical artifact
The product says Luna is approximately 57 mm by 50 mm, fully assembled and tested, with a yellow LED in the forehead. It does not identify the LED, circuit, controller, component values, materials, power budget, production method, final revision, electrical test method, or safety information.
Compatibility: Luna SAO (DEF CON 34)
maker-described physical badge surface
The maker describes a small monorail on a track, a clip for storing a paper monorail ticket that is not included, and a three-SAO structure. No source identifies the final materials, mechanics, SAO layout, connector pinout, manufacturing method, dimensions, transit-ticket compatibility, or final unit photographs as reusable documentation.
Compatibility: Monorail Con Badge (DEF CON 34)
maker-described physical configuration
The maker calls v2 either an oversize minibadge or a standalone lanyard-pinned badge and says standalone use is powered by a CR2032. The roster instead calls the offering a standalone small badge or Saintcon minibadge. Neither source settles the final form, dimensions, attachment method, battery holder, polarity, on/off control, minibadge standard, connector/pinout, electrical interface, host compatibility, or which configuration a buyer receives.
Compatibility: Day of the Dead Turkey v2 (DEF CON 34); external minibadge or standalone use
maker-described physical configuration
The maker calls v1 either an oversize minibadge or a standalone lanyard-pinned badge and says standalone use is powered by a CR2032. The roster instead calls the offering a standalone small badge or Saintcon minibadge. Neither source settles the final form, dimensions, attachment method, battery holder, polarity, on/off control, minibadge standard, connector/pinout, electrical interface, host compatibility, or which configuration a buyer receives.
Compatibility: Day of the Dead Turkey v1 (DEF CON 34); external minibadge or standalone use
maker-described physical connection surface
The maker says the FPC tongue contains functional USB pads and can act as a USB cable when folded for tension, alongside a USB-C connector. It says the tongue is durable but may crumple with repeated use. The source does not publish cable-current limits, orientation details, USB signal testing, cycle testing, mechanical precautions, device compatibility, or warranty/support terms.
Compatibility: UPDeeDeeI SAO (DEF CON 34)
maker-described physical construction
The listing says the cedar was grown on a creator farm in Tennessee, milled at home, and paired with the PCB by hand; it also says the header pins break out to labelled solder pads on both sides. The source does not give wood treatment, dimensions, mechanical durability, fire-safety, sourcing chain, production count, assembly instructions, or final quality-control information.
Compatibility: Root Access SAO (DEF CON 34)
maker-described physical lighting surface
The listing names sixteen side-emitting XL-1606SURC red LEDs shining through FR4 PCB material and includes a lobster-clasp lanyard. It does not publish LED current, placement drawing, board dimensions, materials details beyond FR4, power budget, schematic, BOM, PCB files, final revision, or production-quality record.
Compatibility: #NOICE SAO (DEF CON 34)
maker-described physical package
The marketplace describes a roughly 100 mm beer-cup SAO with a waterproof temperature sensor on an approximately 200 mm lead and an included 180-degree adapter for DEF CON 34's upside-down host ports. The source does not provide final board outline, connector mechanical drawing, probe ingress/sanitation rating, adapter circuit/pinout, force/strain limits, physical compatibility matrix, or confirmation that all units use the same parts.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
maker-described power and compatibility surface
The maker says the canary can run from the SAO connector or an included CR2032 battery. Its v1.0 note says hardware I2C was disconnected from the SAO connector and separate lines were used to reduce the chance of sensor-bus collisions. It does not identify voltage/current limits, battery runtime, connector pinout, I2C electrical characteristics, multi-device test data, or universal host compatibility.
Compatibility: Volatile Organic Canary SAO (DEF CON 34)
maker-described power and expansion surface
The maker lists a rechargeable LiPo via USB-C and a fully addressable SAO port. It does not publish battery capacity, chemistry/protection details, charger/power path, voltage/current limits, runtime, thermal data, connector pinout, SAO version, supported devices, electrical test matrix, safety guidance, or universal compatibility guarantee.
Compatibility: Wordweaving Badge (DEF CON 34)
maker-described power and interaction surface
The maker says one tactile button cycles effects, the last effect persists after host power loss or disconnection, the input range is 2.7–3.7 V, and visual patterns include fast/slow flashing, heartbeat, and breathing/fade. No controller, timing range, memory mechanism, regulator design, host test matrix, electrical protection, or optical-safety information is published.
Compatibility: #NOICE SAO (DEF CON 34)
maker-described power surface
The maker lists a regulated 3.3 V supply powered by two AAA batteries. It does not identify battery chemistry/brand, holder, polarity protection, regulator, current draw, runtime, charging behavior, voltage limits, thermal behavior, transport guidance, certification, or safety documentation.
Compatibility: Monorail Con Badge (DEF CON 34)
maker-described pre-event distribution
NilbinSec's public roster says 1,000 PAC MAN Ghost SAOs will be given out for free, with drops announced through social media and a supply transferred to villages. The event had not yet occurred in this source pass, so it does not establish manufacture, quantity completed, village transfer, exact drops, allocations, recipient count, completed handoff, replacement, or support.
Compatibility: NilbinSec PAC-MAN Ghost SAO (DEF CON 34)
maker-described pre-event distribution
NilbinSec's public roster row says the Power Glove Re-release is free and that 500 Power Glove SAOs will be given away at DEF CON, with drops announced on social media and at the Badgelife Village. The event had not yet occurred in this source pass, so it does not establish manufacture, inventory, drop schedule, village handoff, recipient count, completed distribution, replacement, or support outcome.
Compatibility: NilbinSec Power Glove Re-release SAO (DEF CON 34)
maker-described pre-event sales channel
Hak4Kidz Lab's public roster says Star Trek SAO Phaser v2.2 can be purchased from Hacker Warehouse at DEF CON for approximately $35. DEF CON 34 had not yet begun in this source pass, so this does not establish Hacker Warehouse inventory, booth location, payment terms, units, event-exclusive configuration, completed sale, buyer allocation, pickup, fulfillment, support, or a relationship beyond the maker's own sales-channel statement.
Compatibility: Star Trek SAO Phaser v2.2 (DEF CON 34)
maker-described pre-event sales channel
MakeItHackin's public roster says the Original Series Tricorder badge will be available on-site at DEF CON through Hacker Warehouse for approximately $125. DEF CON 34 had not yet begun in this source pass, so the statement does not establish venue inventory, booth location, units, payment terms, event-exclusive configuration, completed sale, buyer allocation, pickup, fulfillment, replacement, support, or a relationship beyond the maker's own sales-channel wording.
Compatibility: Original Series Tricorder Badge (DEF CON 34)
maker-described production and physical form
AoSC says the 2026 edition is a limited release with a plan for 40 brass eChallengeCoins, each weighing 46 grams. It does not establish a finished quantity, serialized allocation, component parity, production date, inventory, recipients, shipping/pickup outcomes, replacements, resale, or post-event availability.
Compatibility: 2026 eChallengeCoin (DEF CON 34)
maker-described programming capability
The listing says a CH340E USB-to-serial converter can program UPDI devices such as ATtiny microcontrollers and names configurable 3.3 V or 5 V UPDI voltage. It does not publish wiring, driver requirements, target support, protocol configuration, level validation, fuse/lock-bit handling, recovery procedure, or a safe universal programming guarantee.
Compatibility: UPDeeDeeI SAO (DEF CON 34)
maker-described proposed host interface
The maker says the SAO implements Rare Circuit's proposed SAOv3 I2C interface, exposing vendor/product IDs, port and custom-command information, generic LED control, and its own lighting modes. It does not publish a final protocol version, command schema, IDs, host implementation, interoperability result, standard-ratification status, or broad compatibility guarantee.
Compatibility: Firefly Jar SAO (DEF CON 34)
maker-described proximity communication
The marketplace and README describe IR send/receive plus a 13.56 MHz RFID/NFC component, while the diary discusses a planned short-message interaction over infrared. The sources do not establish a final message format, range, pairing/discovery rules, encryption/authentication, collision handling, data retention, interoperability, regulatory status, or user-consent model.
Compatibility: MalO SAO (DEF CON 34)
maker-described publication plan
The current roster says the re-release will be posted to NilbinSec GitHub on DEF CON Day 1. Before the August 6 event, the reviewed account already had only the older DC32 Power Glove repository, so no 2026-specific source, firmware, release, revision note, licence, or final production mapping was available.
Compatibility: NilbinSec Power Glove Re-release SAO (DEF CON 34)
maker-described radio hardware surface
The maker's v1.4 source identifies an nRF52840 on a RAK4630, a Semtech SX1262 LoRa radio on US 915 MHz, and Johanson chip antennas for 915 MHz LoRa and 2.4 GHz BLE. It includes board, component, and measurement sources, but does not amount to a certification, independent RF assessment, universal host result, or final-unit inspection.
Compatibility: Darknet-NG SMAO v1.4 source design
maker-described security-research feature
The official product description says the badge has Wi-Fi and Bluetooth analysis tools and a deauthentication detector. The seller says shipped units are passive and listen-only; no configuration, range, accuracy, traffic handling, target-identification, privacy, RF, legal, or operating procedure is published here. This dossier does not provide use instructions or describe the badge as suitable for any particular environment.
Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge
maker-described software and protocol surface
The product and maker post describe bare-metal/pure RISC-V assembly on CH32V003 and a custom UART puzzle at 115200 baud; the product describes fourteen stages, Davies-Meyer, SPECK-128/256, a constant-time MAC, and an 8 MHz low-power mode. These claims do not substitute for matching released firmware, binaries, build or flash instructions, test vectors, benchmark method, security review, recovery process, or proof that any shipped unit matches the description.
Compatibility: Ouroboros Badge (DEF CON 34)
maker-described software experience
The sources describe games, puzzles, screensavers, messages, user modification through USB-C, a compiled C library, and an evolving Python/C++ two-core arrangement. No reviewed material supplies a tagged final firmware, end-user build/flash guide, challenge archive, stable UI specification, release hashes, update policy, test report, or final behavior guarantee.
Compatibility: MalO SAO (DEF CON 34)
maker-documented badge experience
The maker README describes local DJ mixes played through headphones and a music-linked light show. This documents a stated badge experience, not a particular playlist, licensed media set, audio level/safety result, event programme, radio broadcast, attendee allocation, final firmware configuration, or confirmed conference deployment.
Compatibility: DEF CON Silent Disco Badge as described by its maker; headphone/media/firmware parity across physical boards unverified
maker-documented badge-to-badge interaction
The README says two badges can use infrared to converge on track position and light timing, while the firmware notes document revision-specific infrared context. This is a high-level maker-published interaction claim, not an interoperability guarantee, protocol specification, privacy/security assertion, reliable-range result, safe operating instruction, or evidence of an event-wide synchronized session.
Compatibility: DEF CON Silent Disco Badge project only; revision, line-of-sight, and event-use parity unverified
maker-documented electronic badge platform
Public documentation identifies an RP2040, microSD/local media, LiPo power path, 3.5 mm audio chain, addressable LEDs, USB-C, infrared components, and an SAO header. It records a high-level technical surface rather than a verified final BOM, pinout, voltage/current budget, cell specification, charger protection result, electrical test, compatibility matrix, compliance record, or safe-modification guide.
Compatibility: Maker's documented Silent Disco Badge design; exact revision and physical-unit component parity unverified
maker-documented hardware interface
The maker targets DC34's right SAO port, identifies a 2 by 3 SAO 1.69bis header, and describes 3.0 V badge or USB-C power. This is an implementation-specific maker statement, not a universal fit, rail budget, hot-plug, electrical-safety, or compatibility guarantee.
Compatibility: DEF CON 34 right-side SAO design target only; other hosts and configurations unverified
maker-documented hardware platform
The maker describes one badge as an uplink/display XIAO ESP32-S3 and two XIAO ESP32-S3 scanners that share one scanner image but receive BLE-primary and Wi-Fi-primary roles at runtime. It is a source-described architecture, not proof of a universal production revision, board provenance, field reliability, or authorized radio deployment.
Compatibility: Friend or Foe Badge project only; not a general DEF CON, Packet Hacking Village, Android-device, or RF-device compatibility statement
maker-documented host interface
The guide identifies I2C address 0x50 and documents built-in-mode selection, all-off control, raw discrete and RGB LED writes, plus a two-byte status response. It says malformed raw writes are rejected without partial state changes. This is a published operating interface, not a warranty of host compatibility, electrical safety, bus arbitration, command support by a particular badge, or a software library.
Compatibility: Root Access SAO (DEF CON 34)
maker-documented interaction and software surface
The project describes passive observation of nearby broadcast RF evidence and a USB-C Android companion for live views, display controls, and diagnostics. It does not establish detection accuracy, identification certainty, legal authority, range, data retention, user consent, secure transport, a cloud-free operation in every mode, or a safe field-use procedure.
Compatibility: Friend or Foe badge/project context only; no surveillance, identification, or operational recommendation
maker-documented local challenge interface
The guide says the badge exposes a local Wi-Fi/browser quest interface and includes an explicit assigned-badge-and-advertised-services boundary. The catalogue preserves that narrow interaction fact without publishing connection identifiers, credentials, local addresses, hidden resources, browser instructions, or exploitation details, and without treating a CTF surface as general conference infrastructure or a production security model.
Compatibility: The Shattered Shard challenge badge only; network configuration and authorization beyond the guide's assigned-badge context unverified
maker-documented local operation
The guide identifies an ATtiny1616, ten addressable RGB pixels, eleven discrete LEDs, fifty animations, a button, and non-volatile USERROW storage for a favorite and last-played animation. It describes tap and hold behavior, but does not supply firmware source, a binary release, electronics test data, a battery/runtime profile, or final-unit verification.
Compatibility: Root Access SAO (DEF CON 34)
maker-documented physical interaction surface
The Player Guide names a CP2102 programming connector, a serial-terminal chapter, an LED-panel observation, and one physical task using only labelled SAO GPIO1/GPIO2 contacts. It does not establish connector wiring, pinout, voltage/current limits, toolchain, serial-command set, safe procedure, firmware image, general compatibility, or permission to attach hardware outside the assigned-badge context.
Compatibility: The Shattered Shard challenge badge as described in its Player Guide; physical/unit parity and safe interaction outcome unverified
maker-documented software surface
The public README and handoff describe GIF channels, a device puzzle, settings, USB-drive loading, and the V4-to-V5 firmware history. This preserves the published software surface without making a safe flashing, recovery, support, security, or source-to-unit version claim.
Compatibility: INSPECTRON 34 only; final installed firmware and every-host behavior are unverified
maker-proposed interactive hardware
The README describes a camera, display, and microSD-based image surface within the planned badge. It establishes the intended project concept, not functioning capture, encoding, storage, display, interoperability, data handling, privacy, final firmware, event operation, or a delivered-unit result.
Compatibility: Proposed HRV SSTV Badge design only; hardware and software parity unverified
maker-proposed radio hardware
The README describes separate carrier boards for a radio module as part of the planned SSTV concept. The catalogue records that high-level design claim without reproducing setup, configuration, frequency, transmission, or radio-operation procedures, and without asserting a tested assembly, authorization, license status, performance, safety, or compliance outcome.
Compatibility: Proposed HRV SSTV Badge design only; no radio-operation or completed-event claim
maker-published fabrication archive
The hardware guide publishes a board BOM, single-board and panel Gerber jobs, and a battery-cage STL, and says the DEF CON run used a three-radio ESP32-S3 arrangement with external patch antennas. The files are preservation evidence, not a safe construction guide, a current supplier quote, a complete editable design-source release, or final-unit evidence.
Compatibility: Friend or Foe Badge source-design context; fabrication, battery, and regulatory outcomes remain unverified
maker-published source and firmware trail
The repository publishes KiCad/fabrication material, MicroPython-based firmware, a native MP3-decoder path, and a prebuilt universal UF2. This supports a public technical trail, not an audited/reproducible build, signed release, source-to-device mapping, third-party dependency audit, installation instruction, event-installed media package, warranty, support channel, or security review.
Compatibility: Public project archive; matching firmware on every physical board unverified
mechanical accessory source surface
The hardware archive includes several `iflfu-sao-spacer` model-file variants in OBJ, MTL, and 3MF forms. Their presence documents an accessory-design trail, not a shipped spacer, a particular revision, a compatible host, printed-material safety, fit, durability, included accessory, or permission to republish model or image assets.
Compatibility: IFLFU SAO (DEF CON 34)
mechanical customization
The listing says parts are customizable and interchangeable. The Wayfinder-CAD repository describes a one-piece clamshell case, rails/keyway, snap-on accent plates, compliant-mechanism cautions, knobs, Fusion360 source, and STL files. The repository has no detected license and its author warns the CAD is incomplete/complex, so it is a documented trail rather than a blanket redistribution or safety authorization.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
navigation surface
WyrdWyrks describes GPS plus Wi-Fi geolocation for indoor/outdoor finding and a WS2812B LED compass ring. The repository documents GPS coordinate/status traffic, saved waypoints, navigation wiring, and v3 61 LEDs, but does not provide final location accuracy, geolocation-service terms, indoor performance, or range validation.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
official board-platform documentation
AoSC links CircuitPython's Bradán Lane STUDIO Coin M0 build specifically for the eChallengeCoin. CircuitPython says Coin M0 has an ATSAMD21G1A with 4 MB flash and supports CircuitPython or Arduino plus USB serial, MIDI, HID, and disk uses; AoSC suggests a one-button macropad after the game. The sources do not prove final 2026 firmware, every-unit compatibility, user-safe reflashing, or a detailed implementation/license trail for the eChallengeCoin game.
Compatibility: 2026 eChallengeCoin (DEF CON 34)
official documented hardware surface
The official site lists an ESP32-S3, SX1262 LoRa radio, 192×64 LCD, microSD, USB-C, rechargeable LiPo, buttons, speaker, vibration motor, 48 addressable LEDs across RGB/UV groups, resin body, acrylic panels, and related package items. It is a published platform description, not a verified 2026 per-unit configuration, electrical test result, or safe operating specification.
Compatibility: Hacker Pager project as described by Exploitee.rs; exact DEF CON 34 unit parity unverified
official firmware-recovery documentation
Badge.Life documents a USB CDC serial CLI and a DFU/BOOTSEL path for copying a correct firmware.uf2. It is a public documentation trail, not a published firmware release, a source-to-badge mapping, an integrity guarantee, a complete recovery package, or a recommendation to modify hardware.
Compatibility: BadgeLife Village Badge guide only; cable, host, firmware, and successful-update compatibility unverified
official published hardware surface
Badge.Life lists an RP2354 with integrated flash, eight addressable RGB NeoPixel LEDs, three buttons, an infrared receiver, two Simple Add-On v2 headers, USB-C, and a single-cell 18650 battery with charging and protection circuitry. This is a published platform description, not a complete schematic/BOM, a final manufactured configuration, an SAO compatibility guarantee, or an electrical-safety result.
Compatibility: BadgeLife Village Badge documentation only; exact final-unit configuration and compatible add-ons unverified
official software and interoperability description
The official site says the Pager runs Meshtastic-powered software for standalone messaging with Meshtastic-compatible devices and optionally pairs with the official mobile application. The description does not establish default radio enablement, channel/key configuration, data practices, performance, legal operating context, or a final DEF CON 34 firmware image.
Compatibility: Hacker Pager project; no event-network or final firmware configuration asserted
official update-status record
The maker's update page calls 2.7.26.pager the latest Hacker Pager firmware release and adds a DEF CON 34 label. It does not identify every code change, cryptographic release verification, hardware-revision mapping, installed-unit population, successful update record, support outcome, or permission to reproduce update steps here.
Compatibility: Hacker Pager devices supported by the maker update page; event-unit deployment unverified
official village event association
Red Team Village's official page places the Village at DEF CON 34 on August 6-9 in the Las Vegas Convention Center Red Team Village area and announces workshops, activities, swag, and more. It does not state that RTV D20 is included with registration, used in a workshop/CTF, issued to all attendees, or grants access to any Village or conference space.
Compatibility: RTV D20 Badge (DEF CON 34)
open-source licensing
The project's licensing declaration assigns CERN-OHL-S v2 to hardware, GPLv3 to firmware, and CC BY-SA 4.0 to listed documentation and creative works. This supplies a clear technical-source trail, but its itemized scope does not by itself establish a cleared publication basis for each repository photo or a final event-unit configuration.
Compatibility: Not Just a Crosswalk SAO (DEF CON 34)
planned badge expansion
The maker labels Not Just a Crosswalk a Simple Add-On designed for DEFCON 34 and says it is SAO V1.69bis/V2.0 compatible. The repository does not provide a final unit, a standard-specific test report, a host-badge matrix, connector orientation proof, electrical budget, or universal interoperability guarantee.
Compatibility: Not Just a Crosswalk SAO (DEF CON 34)
planned firmware distribution process
The distribution guide says physical-badge firmware should map to a permanent GitHub release with source, notices, relinkable objects, hashes, and installation information. The public releases surface had no release or tag on 2026-08-05, so the guide is recorded as a planned compliance path, not evidence of an installed final binary, completed distribution, or production traceability.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
planned in-person interaction
The team describes crew members as roaming live transmission zones, fixed but unmapped Cure Stations, and hidden 3D-printed medkit props. This is a planned game surface, not proof of venue approval, final locations, staff participation, accessibility, safety review, implementation, participant effect, prize, or event outcome.
Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)
planned technical release
The maker says hardware documentation and a stub firmware will be provided after the conference. That is a public future-release statement, not a currently available repository, license, binary, final firmware, completed design release, or guarantee of timing/scope.
Compatibility: Wordweaving Badge (DEF CON 34)
post-publication hardware and firmware source trail
Lepi Labs' repository named 5-dc34-canary-badge contains native KiCad board/schematic material and a PlatformIO Arduino source tree with components matching the source-described Canary. The source is useful technical provenance, but no reviewed maker page links it directly to the sold product, and its release page reports no releases. It is not treated as a final v1.0 event firmware, final board revision, calibration record, safe operating guide, or source license.
Compatibility: Volatile Organic Canary SAO (DEF CON 34) only; product-to-repository and repository-to-physical-unit parity remain unverified.
power and wearability
NilbinSec lists a protected 18650 battery and lanyard. The listing does not identify capacity, cell make/model, protection circuit, charging method, charger, connector, runtime, electrical limits, safety testing, or replacement procedure.
Compatibility: Spectre Sniffer Badge (DEF CON 34)
power system
The maker lists an included 2,000 mAh LiPo, BQ24072RGT battery-management controller, TPS63051RMWR 3.3 V buck-boost supply, thermal monitoring, and up-to-1.5 A fast-charging support. The public listing does not include a battery specification, charger settings, measurements, operating guide, or independent safety verification.
Compatibility: Shitty Kitty V2 (DEF CON 34)
power system
The SAO spec states that the badge is powered by two AA batteries and that USB-C power-bank operation keeps the badge continuously on.
Compatibility: DEF CON 34 Badge
pre-event acquisition plan
The maker says buyers may select DEF CON pickup this year or shipment by early August, with pickup location/time to follow. The source does not establish a final pickup schedule, venue authorization, customer notice, shipment posting, customs handling, delivery receipt, replacement policy, or a completed handoff.
Compatibility: Whose Slide Is It Anyway? 10 Year Anniversary Badge
pre-event availability and acquisition record
The live listing shows $10, six sold, 44 remaining, on-site-only DEF CON 34 pickup, and tentative Friday/Saturday BadgeLife Village times. These seller statements do not prove final inventory, paid orders, actual schedule, pickup, delivery, refund, support, or venue authorization.
Compatibility: Luna SAO (DEF CON 34)
pre-event availability and acquisition record
The live listing shows $20, 20 sold, ten remaining, a free Saturday DEF CON 34 BadgeLife Village pickup label, and pickup wording for DEF CON 34 or BSidesLV. These seller statements do not prove final inventory, payment, schedule, handoff, shipping, refund, or event authorization.
Compatibility: METROPOLIS AI SAO (DEF CON 34)
pre-event availability and acquisition record
The live page shows $20, eight sold, 92 remaining, DEF CON 34 BadgeLife Village, LineCon, and Queercon Mixer drop labels, plus post-DEF-CON CONUS shipping. These seller-published terms do not prove final run size, paid orders, onsite allocation, pickup, shipment, delivery, refund, replacement, or event authorization.
Compatibility: #NOICE SAO (DEF CON 34)
pre-event availability and acquisition record
The official checkout lists $20 including tax and says all online stock allocations are exhausted. The Puzzled Hackers Team says paid sales were capped at a break-even point. Neither source publishes a unit count, payment ledger, production total, in-person stock, completed sale, delivery, refund, replacement, or post-event availability result.
Compatibility: Puzzled Hackers LED Badge (DEF CON 34)
pre-event availability and acquisition record
The live product page lists $24 and a seller state of 19 sold from a listed total of 23, plus two stated DEF CON 34 Badge Life Booth pickup times. It says a missed drop can be mailed or refunded. These seller-published terms do not prove final inventory, payment, pickup, shipment, delivery, refund, venue authorization, or event outcome.
Compatibility: HackThePlanet SAO (DEF CON 34)
pre-event availability and acquisition record
The live Lepi Labs product page shows a $25 price, 25 sold, zero remaining, and a DEF CON 34 drop label. The team separately announces scheduled BadgeLife Village drops. These time-specific states do not prove final run size, paid-order ledger, physical stock, exact drop allocation, handoff, delivery, or post-event outcome.
Compatibility: Firefly Jar SAO (DEF CON 34)
pre-event availability and acquisition record
The live Lepi Labs product page shows a $35 price, seven sold, zero remaining, and a DEF CON 34 drop label. The team separately announces scheduled BadgeLife Village drops. These current source statements do not establish final run size, paid-order status, physical stock, exact drop allocation, handoff, delivery, refund, or post-event outcome.
Compatibility: UPDeeDeeI SAO (DEF CON 34)
pre-event availability and acquisition record
The live Lepi Labs product page shows a $45 price, 11 sold, zero remaining, and a DEF CON 34 drop label. The team separately announces scheduled BadgeLife Village drops. These time-specific source states do not prove the final run size, paid-order ledger, physical stock, timing, handoff, delivery, refund, or post-event outcome.
Compatibility: Volatile Organic Canary SAO (DEF CON 34)
pre-event availability and acquisition record
The observed live product payload reports $45, 150 total units, 28 sold, 122 remaining, `presale: true`, no shipping options, and two announced DEF CON 34 BadgeLife Village pickups: Friday August 7 at 1 PM and Saturday August 8 at 1 PM. This is a time-specific maker marketplace snapshot, not proof of paid-order count, completed manufacture, venue authorization, onsite inventory, pickup, delivery, refund, support, or final availability.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
pre-event availability and acquisition record
The live MakeItHackin page lists $50 and a seller state of 15 sold from a listed total of 100, plus drops labelled BSides Las Vegas 2026 and two Linq Circle Bar nights. These time-specific seller figures do not prove final run size, paid-order ledger, onsite allocation, collection, shipment, delivery, refund, event authorization, or post-event support.
Compatibility: Root Access SAO (DEF CON 34)
pre-event availability and acquisition record
The live listing shows $50, 43 sold, 57 remaining, and a DEFCON34 drop label. The repository and project diary describe online sale and intended August handout/pickup. These sources do not prove final run size, paid-order ledger, exact drop allocation, production, attendee handoff, shipment, delivery, refund, or post-event support.
Compatibility: MalO SAO (DEF CON 34)
pre-event availability and acquisition record
The live product payload reports a $120 100-unit presale with 41 sold, a DEF CON 34 pickup option, and a seller-published $140 at-con plan. This is a time-specific maker marketplace snapshot, not proof of final production, paid orders, finished units, onsite inventory, booth authorization, pickup, shipment, delivery, donation, refund, or customer support outcome.
Compatibility: Wordweaving Badge (DEF CON 34)
pre-event availability and acquisition record
The live product payload identifies a $55, 125-total pre-sale for DEF CON 34, currently reports 125 sold and zero remaining, lists no shipping options, and directs collection to the Darknet-NG contest booth. This preserves a time-specific maker marketplace state, not evidence that the total run is manufactured, paid, assembled, collected, delivered, or supported after the event.
Compatibility: Darknet-NG SMAO (DEF CON 34)
pre-event availability and acquisition record
Red Team Village's public DC34 Badgelife response labels RTV D20 as a new badge, says it will be available on site at DEF CON through RTV, and gives an $80 price. The statement does not prove inventory, payment, manufacture, final price, sale location/time, venue authorization, pickup, recipient allocation, refund, support, or a completed handoff.
Compatibility: RTV D20 Badge (DEF CON 34)
pre-event availability and acquisition record
The maker page says preorders are sold out and may have a few extras to trade in person. The current payload marks its $65 base, $150 Laser* Tag bundle, and $80 voluntary-extra-payment options unavailable. This is a current storefront snapshot, not proof of a sale count, physical inventory, finished build, payment, trade, pickup, delivery, refund, or post-event support outcome.
Compatibility: Monorail Con Badge (DEF CON 34)
pre-event availability and configuration statement
The maker says about 55 badges had been made with roughly ten boards left, a few may be given to the first roughly five signal-intel puzzle solvers, most or all RGB units are accounted for, a few non-RGB units may be sold at cost, and some RGB blank boards may be given away. These comments do not establish a production ledger, final build count, exact price, payment, eligibility, pickup site/time, receipt, donation, assembly, delivery, support, or post-event outcome.
Compatibility: Station 562 Badge (DEF CON 34)
pre-event availability and edition record
The official current inventory endpoint lists 86 $120 Standard, 25 $130 Pro, and five $140 RAD first-run units—152 total—all with zero current availability. The shop says the first run is gone and all 152 shipped, while the present form only gauges interest in a possible second run. This is a current storefront snapshot, not a production audit, proof that every buyer received a unit, or a second-run promise.
Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge
pre-event availability and edition record
The maker's product page says only 100 badges are planned at $75 each. Its public Shopify payload currently marks the single variant unavailable, but emits no inventory quantity. This records a stated limited-run plan and time-sensitive unavailable state, not proof that all 100 units exist, sold, shipped, or reached buyers.
Compatibility: Whose Slide Is It Anyway? 10 Year Anniversary Badge
pre-event availability and revision statement
The roster gives MF Doom SAO v2 a $20 Coming soon entry, while the maker's Reddit thread says preorders will be handled by direct message and describes local handoff near the Las Vegas Convention Center. The public statements do not prove final stock, price, manufacture, payment, venue authorization, exact meeting point, pickup, shipment, refund, replacement, support, recipient allocation, or completed delivery.
Compatibility: MF Doom SAO v2 (DEF CON 34)
pre-event badge teaser
DEF CON's official badge-alert post says DEF CON 34 is an electronic badge year, that the badge comes from a hardware hacking legend, and that the SAO spec sheet is early support for add-on projects.
Compatibility: DEF CON 34 Badge
pre-event distribution
The organizer says orders are currently DEF CON 34 pickup at Demo Labs from 10 AM to noon on Friday and Saturday, online orders only with no onsite sales. It says unclaimed orders will be donated to a broke hacker; neither source confirms completed pickup or recipient outcomes.
Compatibility: EFF "Electric Fist" BadgeLife (DEF CON 34)
pre-event fulfillment
The listing says pickup only, no shipping, with drops at BadgeLife Village and announced LVCC locations on a published schedule; it says missed drops are donated to a hacker at closing ceremonies. At the August 3 source pass, the listing displayed 80 sold and zero remaining.
Compatibility: Spectre Sniffer Badge (DEF CON 34)
pre-event fulfillment
At the August 3 source pass, the $150 product is marked PRE with 5 sold and 95 remaining. Its drop options are DC34 Reddit Meetup Wednesday, DC34 Reddit Meetup Thursday, DEF CON 34 BadgeLife 1, and DEF CON 34 BadgeLife 2; no shipping option or location/date detail is present in the reviewed product payload.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
pre-event fundraiser and fulfillment
BTV lists a $120 assembled badge with lanyard and a $60 intermediate-to-advanced soldering kit, for in-person pickup only during DEF CON in Las Vegas. The listing directs buyers to the West Hall second-floor W213-215 Infobooth during Friday-Sunday village hours and says no refunds after August 10; these terms do not establish completed handoff or fulfillment.
Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)
pre-event maker and self-submission availability record
BigFuckingBadge's page presents a limited DEF CON 34 presale and an unlabeled $20 OffensiveSAO card, while the public Badgelife response names that artifact DFIU SAO and likewise gives $20. These published statements do not prove current inventory, payment, final price, manufacturing completion, shipment, pickup, event sale, refund, replacement, support, recipient allocation, or a completed handoff.
Compatibility: DFIU SAO (DEF CON 34)
pre-event maker and self-submission availability record
The BigFuckingBadge page supplies a limited DEF CON 34 presale setting and an unlabeled $20 OffensiveSAO card, while the public Badgelife response names IFLFU SAO as an update to an existing item and gives $20. Those source statements do not prove current inventory, payment, final price, manufacture, shipment, pickup, event sale, recipient allocation, refund, replacement, support, or a completed handoff.
Compatibility: IFLFU SAO (DEF CON 34)
pre-event maker and self-submission availability record
BigFuckingBadge's page provides a limited DEF CON 34 presale context and a $20 Portal-gun companion card, while the public Badgelife response names the new PORTAL gun SAO and likewise gives $20. These statements do not prove inventory, payment, final price, completed manufacture, shipment, pickup, event sale, recipient allocation, refund, replacement, support, or a completed handoff.
Compatibility: Portal Gun SAO (DEF CON 34)
pre-event maker availability and acquisition statement
The K Badges Tindie page displays a $29.99 price and an out-of-stock state, says a new order is coming, and says the maker hopes to bring some to DEF CON. The maker's Reddit post separately offers to arrange pickup/refund shipping for buyers. Neither source proves inventory, production completion, payment acceptance, arrival, pickup scheduling, handoff, shipping, refund, support, or delivery.
Compatibility: Ouroboros Badge (DEF CON 34)
pre-event marketplace availability record
The official v2 product page displayed $12 and available in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory count, paid order count, manufacture, pickup email/location/time, completed handoff, shipment, refund, replacement, support, or post-event availability.
Compatibility: Day of the Dead Turkey v2 (DEF CON 34)
pre-event marketplace availability record
The official v1 product page displayed $12 and available in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory count, paid order count, manufacture, pickup email/location/time, completed handoff, shipment, refund, replacement, support, or post-event availability.
Compatibility: Day of the Dead Turkey v1 (DEF CON 34)
pre-event marketplace availability record
The official product page showed $45 and sold out in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory history, payment, manufacture, drop location/time, email notice, completed pickup, shipment, refund, replacement, or support outcome.
Compatibility: Krampus Minibadge Holder (DEF CON 34)
pre-event marketplace availability record
The official product page showed $45 and sold out in this August 4, 2026 pass, and says buyers should select DC pickup only when planning DEFCON pickup on August 6-8. These statements do not establish inventory history, payment, manufacture, drop location/time, email notice, completed pickup, shipment, refund, replacement, or support outcome.
Compatibility: Beelzebub Minibadge Holder (DEF CON 34)
pre-event product and availability
The official product page lists the FloridaMan 2026 Badge at $90 and currently marks it out of stock; its short product context says it is no longer shipping and directs attendees toward DEF CON. This is a listing-status snapshot, not proof of order volume, sale completion, shipped goods, pickup, refund terms, remaining inventory, or an eventual handoff.
Compatibility: FloridaMan 2026 Badge
pre-event production and remedy plan
The listing says v1.0 boards were ordered and that if v0.1 issues remain or later problems cannot be resolved before DEF CON, buyers could receive a full refund or have their SAO shipped after the event. This is a contingency statement, not evidence that any issue was resolved, a final revision shipped, a refund occurred, or a delivery obligation was completed.
Compatibility: Volatile Organic Canary SAO (DEF CON 34)
pre-event revision and remedy plan
The maker says v1.1 boards were ordered and lists CH340E decoupling, power-select, UPDI-select, GPIO, CR2032-holder, and FPC-fuse corrections from v0.1. It says unresolved prototype issues or later pre-event problems could lead to a full refund or shipment after DEF CON. These are maker-described plans, not proof of final validation, shipped v1.1 units, correction outcome, refund, or delivery.
Compatibility: UPDeeDeeI SAO (DEF CON 34)
pre-event schedule context
The official party page schedules FloridaMan Party 2026 for Thursday, August 6, 2026 from 9:00 PM to 1:00 AM PT in Las Vegas, Nevada, and says the location is provided upon purchase. The page does not establish a final venue, pickup/entry process, actual attendance, or a completed party outcome.
Compatibility: FloridaMan 2026 Badge
pre-event self-submitted event association
DC801 + 801 Labs' public Badgelife response labels Helgatchi as a new badge for DEF CON 34 and supplies approximate pricing and feature wording. It is a visible maker/team submission, not a DEF CON organizer issuance, venue authorization, registration inclusion, Human-badge replacement, access entitlement, or completed distribution record.
Compatibility: Helgatchi Badge (DEF CON 34)
project provenance and licensing record
The repository publishes public design/source directories, names HotGlewd for PCB/sticker/promotional artwork, BitAssembly for pixel artwork, and declares the work CC BY-SA 3.0. The marketplace separately credits the SCP-1471 source. These statements provide traceable project provenance but do not clear a particular product image, confirm every dependency's licensing, or prove that every third-party lore asset may be republished.
Compatibility: MalO SAO (DEF CON 34)
public badge customization utility
The public `bunnie/dc34-image` README identifies a Python utility for uploading a black-and-white 128×128 image to a DC34 badge over USB serial. It documents a customization path, not physical display technology, a selected shipped image, a final embedded firmware build, or event-unit parity.
Compatibility: DEF CON 34 Badge; physical display and shipped state unverified
public badge programming utility
The public `bunnie/dc34-bio` README identifies a Python utility for loading a BIO program to a DC34 badge over USB serial, with documented SAO-I/O selection and clock configuration. It documents a user-side tooling path, not complete embedded firmware, final connector mapping, safe settings, a supported end-user workflow, or event-unit parity.
Compatibility: DEF CON 34 Badge; final firmware, connector topology, and supported settings unverified
public build and production tooling
The source tree documents a versioned `thermometer-v1.1.0.uf2`, USB BOOTSEL flashing, `flash_and_test.py` serial verification, and soak-log/report scripts for batch programming. Those tools demonstrate a public intended workflow, not a signed release, independently audited production test, all-unit pass record, final factory process, repair policy, or guaranteed recovery path.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
public companion add-on design source
CPEC's companion repository says it contains design files for SAO plug-in modules for the CPEC DC 34 badge. Its commit-pinned source tree contains KiCad project, PCB, and schematic paths for fist, gatling, laser, missile, panel, and sword-named variants, an Arduino source file, and BOM/placement artifacts. The catalogue records that scoped design-source availability without inferring a populated board, hardware behavior, wiring, pinout, firmware result, safe electrical envelope, standard/version match, or working connection to a CPEC badge.
Compatibility: Source names the CPEC DC34 badge only; SAO version, pinout, electrical behavior, mechanical fit, host compatibility, firmware parity, and physical-unit availability are unverified
public documentation and source-lineage boundary
The product links an Ouroboros How It Works PDF and a GitHub repository. The repository describes a distinct AVR-assembly ATmega328P authentication framework and GitHub marks its license field Other; it is not a released CH32V003 badge firmware, board, build package, or clear license grant. The linked PDF similarly does not establish a reusable media or source license.
Compatibility: Ouroboros Badge (DEF CON 34)
public firmware behavior
The repository says core 0 samples DS18B20 temperature about every second and updates the display buffer, while core 1 multiplexes three digits at about 333 Hz; revision 1.3 or later cycles four brightness levels. It does not establish the exact binary deployed to every sold unit, final timing/accuracy under load, error handling, field behavior, update cadence, or supported configuration matrix.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
public firmware build and test surface
The README documents Arduino-compatible firmware and PlatformIO profiles for normal, demo, and factory-test builds, including tests for LED order, orientation, and shake sensing. The code and documentation do not establish a public tagged event release, production test log, safe user modification path, support obligation, or actual configuration in an assembled badge.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
public firmware interaction surface
The public PFC161 source defines a four-entry color buffer, blue/orange/off state values, touch initialization, a 470 pF touch-capacitor note, thresholded button logic, and timer-driven LED updates. This is source-level evidence for touch-controlled animated-color behavior, not a claim about the physical LED model/count/order, touch sensitivity, final modes, brightness, latency, power draw, safety, accessibility, or behavior of every produced unit.
Compatibility: Portal Gun SAO (DEF CON 34)
public firmware interaction surface
The public C source includes PFC161 headers, configures active-low PA4/PA5 LED outputs, keeps separate LFSR state per channel, derives individual delay targets, and flashes channels from its main loop. This is source-level evidence for a two-channel randomized-light implementation, not proof of the exact final illuminated words, distribution of outcomes, timing, brightness, physical LED population, or behavior of every produced unit.
Compatibility: IFLFU SAO (DEF CON 34)
public firmware interaction surface
The public firmware declares ten LED modes, button-driven cycling, per-pixel color output, and pins labelled for minibadge clock control. This documents a possible firmware interaction surface without claiming that all current units expose the same button, pins, timing, modes, firmware revision, programming path, accessibility behavior, or support.
Compatibility: Krampus Minibadge Holder (DEF CON 34)
public firmware interaction surface
The public firmware declares ten LED modes, button-driven cycling, per-pixel color output, and pins labelled for minibadge clock control. This documents a possible firmware interaction surface without claiming that all current units expose the same button, pins, timing, modes, firmware revision, programming path, accessibility behavior, or support.
Compatibility: Beelzebub Minibadge Holder (DEF CON 34)
public firmware interaction surface
The source initializes touch ADC support, reads PD2 through `ReadTouchPin`, starts audio after a threshold, and updates the source-declared D/F/I/U and display LED outputs from timer-driven code. This is source-level evidence of the intended interaction, not a claim that every physical unit behaves identically or that its touch sensitivity, sound volume, audio content, LED population, timing, accessibility, or reliability has been independently tested.
Compatibility: DFIU SAO (DEF CON 34)
public firmware-development and update documentation
The public documentation names exposed UART pins for an XMODEM bootloader and describes a rapidly developed codebase with some unresolved bugs, while the repository exposes current source/firmware material. It documents an implementation and update trail without reproducing flashing steps or claiming a tagged/reproducible firmware release, verified binary-to-board mapping, secure update, rollback/recovery package, support policy, or safe owner modification.
Compatibility: Agency Wand public documentation and repository only; host, adapter, firmware, and update-success compatibility unverified
public firmware-feature surface
The maker and README describe roughly five or six lighting programs, a favourite-colour setting, motion enable/disable, random or sequential program selection, a handle program button, and rear setup button. The README describes a star touch sensor but says it might not work by DC34, and describes the SC7A20H accelerometer while separately documenting a REV1 motion-interrupt limitation. This preserves high-level source claims without promising final program count, touch behavior, motion reliability, or user experience.
Compatibility: Agency Wand DC34 public documentation only; configuration and motion feature availability unverified
public hardware design and fabrication archive
Call Center Village's public source calls this a phone-booth-shaped, power-only SAO v2: one 1206 LED and one 330 ohm current-limiting resistor are wired in series from VCC to GND, with no microcontroller or I2C and the SDA, SCL, GPIO1, and GPIO2 pins left unconnected. The repository includes KiCad project, schematic, PCB, connector symbol, BOM, placement, netlist, Gerber packages, and a CC BY-SA 4.0 license. It does not prove final kit or pre-soldered population, per-unit quality, current draw under an actual host, final production revision, DC34 electrical test result, user assembly outcome, or general host safety.
Compatibility: Call Center Village Telephone Booth SAO Kit; source describes an SAO v2 2 by 3 connector, while actual host compatibility remains unverified
public hardware-design source
The maker's commit-pinned hardware tree contains native KiCad project files for a main badge board and separate carrier boards. This is a source-availability record only; it does not confirm a final design revision, Gerbers, component sourcing, fabrication, assembly, testing, safe behavior, production quantity, or DEF CON handoff.
Compatibility: Maker-published HRV SSTV Badge source project only; no completed-unit or host-compatibility claim
public open-hardware documentation
The electronics repository publishes the PCB design in KiCad with schematic PDF and BOM exports, and its companion case repository publishes case/button/acrylic design files; both state CERN-OHL-S-2.0 for design files. Those releases document modifiable design sources, not a promise that every commercial unit matches them, a safe build recommendation, source-code license scope, or image-reuse permission.
Compatibility: Hacker Pager source repositories only; physical unit and media provenance remain separately bounded
public pre-event firmware source
The project's MVP note identifies the Arduino/C++ tree as the live implementation and describes visual/interactions work. This establishes accessible current project source, not a tagged release, reproducible build, compiled attendee image, device configuration, flashing/support workflow, final feature set, or proof that it ran on a distributed badge.
Compatibility: Pre-event project source; deployment and final hardware parity unverified
public repository and maker hardware description
The repository identifies an RP2350B, 16 MB flash, USB-C, and a 1.5-inch 128 by 128 grayscale SSD1327 OLED. The listing says over fifty LEDs, while the diary describes two 24-device red-green LED banks. This creates a useful documented surface but not a final populated-unit specification, current budget, assembly record, or universal performance guarantee.
Compatibility: MalO SAO (DEF CON 34)
public seller-posted availability statement
The post says only 100 would be available at a Sneakreaper Industries booth. In replies, its author gives $150 and Hall W4. The source does not document a checkout page, seller identity, order count, stock ledger, payment, refund/replacement terms, exact booth authorization, completed manufacture, handoff, delivery, remaining stock, or post-event outcome.
Compatibility: Sneakreaper Limited-Edition Badge (DEF CON 34) public offer only
public technical and licensing archive
The FirstBuild repository publishes a schematic PDF, firmware tree, and MIT license for software and associated documentation. These sources establish a valuable design and software trail, but do not automatically cover credited artwork, photographs, trademarks, every third-party dependency, a final hardware manufacturing package, or a selected reusable badge image.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
publicly documented core hardware
The repository specifies an RP2350A QFN-60, W25Q16 2 MB flash, USB-C for programming and serial debug, RUN/BOOTSEL/brightness buttons, and a three-pin SWD header. The marketplace adds 3.0 V tolerance and says non-power SAO pins are routed to the RP2350. These sources do not establish a final board revision, voltage/current budget, level shifting, overload protection, SAO standard conformance, electrical testing, or universal host compatibility.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
publicly documented sensing and display surface
The source tree names a DS18B20 one-wire sensor on GPIO 16 and three common-anode seven-segment displays multiplexed through a 74HC595, while the listing describes a waterproof probe and triple display. The firmware source says a missing DS18B20 produces a display fallback and logs die temperature to USB serial. No reviewed source provides temperature calibration, traceability, environmental limits, response time, error bounds, food-contact certification, or a suitable-use guarantee.
Compatibility: The Beer SAO / BCCC Temperature Badge (DEF CON 34)
published firmware-development trail
The README points to an Arduino 1.8.5 firmware directory and says stock AVR chips need a one-time bootloader step before normal Arduino flashing. This preserves an implementation trail without reproducing programming commands or claiming a safe procedure, final fuse/programmer configuration, reproducible build, tagged firmware, deployed badge binary, recovery path, support, or warranty.
Compatibility: DC-34 Countdown to Singularity project source tree; event-unit firmware parity unverified
published hardware target
The README names an STM32G031F8P6 Cortex-M0+ controller, MXC6655XA I2C accelerometer, and eight SK6805SIDE-G-003 side-emitting RGB LEDs as the current production target. It is source-backed design intent, not proof that this exact hardware was manufactured, placed on every board, tested, or distributed.
Compatibility: FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34)
published hardware-design inventory
The README's BOM names an ATmega328P-PU, PCF8523T real-time clock, three pushbuttons, seven 2×3 SAO connectors, a 9 V jack/battery path, regulator parts, LEDs, display components, and an ISP port. It identifies a design inventory, not a verified final board, complete/electrically accurate BOM, component availability, safe power path, SAO pinout/current budget, host compatibility, or tested build.
Compatibility: DC-34 Countdown to Singularity public design project; final hardware and safe operation unverified
publisher-supplied event and party context
The public repository calls the project a MidWestCoast Badge for a MidWestCoast Party and its firmware README labels the code DEF CON 34 badge firmware. These labels establish a publisher-supplied pre-event association, not party operation, organizer affiliation, date or venue, DEF CON endorsement, on-floor authorization, allocation, sale, pickup, attendee entitlement, or access control.
Compatibility: Independent pre-event project association, not an official DEF CON or party credential
registration artifact
DEF CON's official ticket page says preregistration guarantees a DEF CON 34 Human badge when the ticket is redeemed onsite in Las Vegas.
Compatibility: DEF CON 34 registration
repository-described hardware and learning surface
The commit-pinned README names an RP2040 microcontroller, MPU-6050 gyro/accelerometer module, thirty WS2812 RGB LEDs, and MicroPython. It does not establish a complete board design, exact component variants, power design, final manufactured revision, individual-unit functionality, performance, safety, or compatibility.
Compatibility: Cyb3rBytes404 repository-described cyber badge only; physical-giveaway parity remains unverified
seller-described hardware and sensing
The listing names a XIAO ESP32S3 and calls the badge's EMF detector live, saying it actively samples electromagnetic fields and renders a real-time spike graph. It does not identify the sensor, calibration, display/indicator hardware, sample rate, accuracy, or operating limits.
Compatibility: Spectre Sniffer Badge (DEF CON 34)
seller-described hardware platform
The listing names ESP32-S3, custom four-layer PCB, 128×128 OLED, five Cherry MX-compatible switches, and a tactile encoder. The firmware README documents an ESP32-S3 v3 variant with 128×128 SH1107 OLED and separately describes four face buttons plus an encoder; no final offered-board revision or full BOM is mapped by the sources.
Compatibility: Celestial Wayfinder Badge (DEF CON 34)
seller-described interaction
NilbinSec describes a Spirit Box with a randomized word bank whose output rate is driven by its stated EMF signal, plus one- and two-player arcade games. The source supplies neither the implementation nor game, signal, audio, or firmware documentation.
Compatibility: Spectre Sniffer Badge (DEF CON 34)
silicon architecture source
The upstream Baochip-1x repository publishes open-source chip-hardware elements, taped-out RTL, VexRiscv configuration, simulation/FPGA material, and a CERN-OHL-W-2.0 license. It documents the announced chip context rather than a complete DC34 badge board or firmware image.
Compatibility: DEF CON 34 Badge
software and documentation source
The public project exposes Arduino-sketch, SD-card-asset, hardware, and license areas, while the root MIT license names slash128 for repository software/documentation. The README also refers to a driver installer and third-party Arduino board/library dependencies. This is a source-access record, not an endorsement, audit, binary provenance confirmation, build reproducibility result, final event firmware, support/recovery promise, or license statement for every bundled/external dependency.
Compatibility: Public project source tree; exact physical-badge firmware parity unverified
software and operating-mode statement
Coruscant Productions says Clip-Boy ships in passive listen-only mode, while an optional research build with additional capabilities may be loaded by the user for authorized testing. The public sources do not provide the build, a final image/hash, a flashing process, support policy, compatibility matrix, rollback/recovery method, feature list, or license. The statement is preserved as a high-level boundary rather than a user guide.
Compatibility: Clip-Boy: The Unofficial DEF CON 34 Electronic Badge
source-described companion add-on
The team announces a brain-in-a-jar SAO and says tapping it causes something to happen to transmission objects in range. The source does not publish connector/pinout, electrical requirements, host compatibility, radio or proximity mechanism, availability, final behavior, safety guidance, or technical archive.
Compatibility: H4irl1n3 M0gg3r5 Zombie Badge (DEF CON 34)
source-described creative and naming context
The listing says the SAO is inspired by Maria, the art-deco automaton from Fritz Lang's 1927 Metropolis, and uses AI in the product title. The technical description identifies only a powered red LED and does not describe a model, application, inference, sensor, network, or programmable behavior.
Compatibility: METROPOLIS AI SAO (DEF CON 34)
source-described fundraising context
The listing frames #NOICE around the maker's stated concerns about immigration enforcement and says a portion of proceeds goes to the Immigrant Defenders Law Center. It does not publish the amount, percentage, accounting, transfer date, recipient confirmation, formal partnership, campaign terms, or outcome.
Compatibility: #NOICE SAO (DEF CON 34)
source-described host interface boundary
The repository points to a DEFCON34 MICD source and says the badge's SAO port is installed upside-down from the cited standard orientation, with a 3.0 V supply and 100 mA maximum-current context. It also says the MalO header can be inverted with a switch and jumper. This is a source-reported design consideration, not an official defect finding, a complete electrical specification, or proof of safe interoperability.
Compatibility: MalO SAO (DEF CON 34)
source-named electronic artifact
The official checkout calls the physical item a limited-edition LED badge. It does not identify a PCB, programmable controller, LED count/color, power system, firmware, radio, connector, or any other engineering surface, so the record preserves the narrow source classification rather than reconstructing electronics.
Compatibility: Puzzled Hackers LED Badge (DEF CON 34)
source-named hardware surface
The post names an ESP32-S3-MINI-1-N8 with Wi-Fi, Bluetooth, 13.56 MHz NFC, and programmable LEDs. It does not provide a schematic, BOM, antenna/NFC design, power path, interface specification, final revision, performance measurement, safety guidance, or proof that every proposed unit has that exact hardware population.
Compatibility: Sneakreaper Limited-Edition Badge (DEF CON 34) claimed hardware surface
source-published community-event credential rule
The official Furry Village schedule says a DEFCON Furs badge was required for the group's 2026 event space, while the store says the badge does not get someone into DEF CON. Those published statements distinguish the community-event access claim from DEF CON admission; they do not disclose a technical access mechanism, prove an individual access result, or establish an ongoing credential.
Compatibility: DEFCON Furs 2026 event space only; separate DEF CON registration required
source-published firmware framework
The `.ino` source uses Arduino APIs and the README credits MegaTinyCore as a foundation. It establishes a published firmware lineage, not an exact MCU selection, tagged event release, reproducible build, source-to-unit mapping, open-source licence, support commitment, or permission to reuse the source.
Compatibility: OWASP SAO (DEF CON 34); exact MCU, final firmware, and physical unit unverified
source-published interaction firmware
The public Arduino sketch defines 15 addressable RGB pixel positions and comments that the original badge has three PTC touch nodes; it changes its visual mode through the source's touch-handling path. This records a code-level interaction surface, not exact LEDs or electrodes, tested hardware, final installed behavior, or a safe operating procedure.
Compatibility: OWASP SAO (DEF CON 34); physical board, SAO specification, and host compatibility unverified
source-published interaction surface
The CPEC repositories publish menu, pilot-record, game-state, display, sound, and game modules, and the earlier repository calls its code a non-final second iteration. Those sources establish an in-progress planned interaction surface, not final gameplay, player outcomes, a completed CTF, physical controls, accessibility behavior, or a deployed event experience.
Compatibility: CPEC DC34 MechBattle Badge
source-published programming surface
The README says UPDI is exposed on the SAO header for reprogramming. It does not provide or establish a pinout, voltage levels, programmer compatibility, access-control policy, safe procedure, supported recovery path, final-board implementation, or successful event-unit result.
Compatibility: OWASP SAO (DEF CON 34); header specification and safe compatibility unverified
source-targeted development platform
The game repository's PlatformIO configuration targets an Adafruit Feather ESP32-S3 no-PSRAM board with Arduino and a LittleFS configuration. This records an intended development target only; it does not identify a final badge PCB, assembly, controller population, storage, boot flow, power design, or a manufactured event unit.
Compatibility: CPEC DC34 MechBattle Badge
technical preservation source
The DC32 repository publishes Arduino sketches, setup/compile/upload scripts, KiCad project files, Gerbers, CAD/fabrication material, a parts list, and assembly instructions under an MIT repository license. Its documentation also notes a then-precompiled CTF library, and no reviewed source establishes that every current fundraiser unit ships a specific repository commit or complete CTF source.
Compatibility: BTV Camera Badge (DEF CON 34 Fundraiser)
third-party 3D-printed lanyard-orientation accessory
Make It Hackin publishes one STL intended to be printed twice as a two-piece capture ring that lets a wearer suspend the official DC34 badge at different rotations, using user-supplied M3 hardware or zip ties and a dual-clip lanyard. The maker says its geometry was photogrammetrically derived and is not an official DEF CON drawing; this is a design file, not a shipped, tested, or DEF CON-approved accessory.
Compatibility: DEF CON 34 Badge; maker-intended external capture ring, physical fit and port/orientation outcome unverified
third-party SAO orientation adapter
Uberflux maker `bud-lightbeer` lists a $4 180-degree SAO adapter for the DEF CON 34 ports, which the maker describes as upside-down relative to the intended SAO 2.0 orientation. The listing says the adapter does not change the badge's 3.0 V supply and warns complex SAOs may not tolerate it; its current marketplace snapshot shows 593 sold, seven remaining, and Friday/Saturday Badge Life Booth pickup. This is a third-party compatibility product, not an official finding of a port defect or a universal compatibility guarantee.
Compatibility: DEF CON 34 Badge
third-party power and use claim
The listing says a standard USB wall brick or portable battery pack can power the Power Back, that an SAO totem can run multiple SAOs, and that it runs three #NOICE or Not Just a Crosswalk SAOs where a regular CR2032 does not have enough power. It does not publish a pinout, USB-C or USB-PD behavior, cable requirements, regulator/protection design, output-current limit, voltage tolerance, heat test, electrical-safety certification, tested SAO matrix, or universal compatibility result.
Compatibility: USB-C Power Back for SAOs; maker-described standalone use only
third-party standalone SAO power/display companion
caelyb's Uberflux listing describes a USB-C-to-SAO Power Back with maker-described 5 V-to-3.3 V conversion that lets SAOs run without a host badge, including desk or shelf display. As reviewed on 2026-08-04 it showed $7, 59 sold, 81 remaining, DC34 BadgeLife Village/LineCon/Queercon pickup labels, and post-DC34 CONUS shipping. It is a third-party standalone SAO companion associated by the maker with DEF CON 34, not an official conference item or a main-badge-mounted add-on.
Compatibility: DEF CON 34 SAO ecosystem; standalone hostless SAO power/display use, not an attachment to the official badge
AI, firmware, source, and licensing gap · product title versus supplied technical description · AI title only; no software function documented
The catalogue does not turn branding or creative language into an artificial-intelligence, software, security, or open-source claim.
AI-assisted art and static-graphic image provenance boundary · official maker AI/tooling disclosure · image media remains excluded
No shop artwork, collectible art, static graphic, or media thumbnail is treated as a cleared factual image of the physical badge or copied into the public catalogue.
BLE, Wi-Fi, privacy, detection, and lawful-use boundary · maker feature description only · configurable scan and alert claims; no independent validation recovered
The dossier records the advertised research/detection surface without claiming reliable identification, safety, legal compliance, privacy preservation, target classification, or suitability for surveillance, counter-surveillance, or emergency use.
BLE, proximity, MIDI, puzzle, CTF, and privacy gap · maker-described feature list · interaction claims without public behavior or data documentation
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.
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
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.
CAD, web-companion, and reusable-media licensing boundary · GitHub repository metadata and source review · needs explicit license and media permission
Public source links remain available for inspection without labeling CAD/PWA material as open licensed, copying imagery, or implying a deployed/maintained companion service.
CTF, free-redemption, giveaway, and account-data boundary · first-hand Team announcement · acquisition statements only
The catalogue retains the public community-acquisition context without supplying private account details, challenge content, player data, unsupported redemption mechanics, or badge-software claims.
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 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.
DC32 design lineage and 2026 revision boundary · primary organizer listing and MIT archive · current fundraiser tied to an earlier documented design
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.
DC32-to-2026 re-release revision boundary · current roster name plus historical repository scope · current re-release announced; exact technical lineage unconfirmed
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.
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
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.
DEF CON association and credential boundary · maker, project, and marketplace sources · independent DEF CON 34-associated maker product
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.
DEF CON, MidWestCoast Party, and credential boundary · maker source plus official DEF CON event context · independent pre-event association only
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.
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 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.
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 record preserves the maker's narrow coin-cell and kit caution without becoming a soldering, battery, child-safety, electrical, or assembly endorsement.
GPIO host behavior, interoperability, and safety boundary · maker-described selectable GPIO paths · behavior depends on the connected host
Readers can identify the intended experimentation surface without assuming every host, GPIO mode, cable, orientation, or shared bus configuration is safe or interoperable.
GPIO stimulation, damage, safety, and consent warning · explicit maker warning plus public implementation · Mode 1 may harm a badge; no safe-use validation published
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.
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 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.
I2C guide, firmware, source, and licensing gap · public repository root reviewed · operating guide published; implementation archive not identified
The catalogue links the documented interface without presenting it as an open-source firmware release, reproducible hardware design, or supported integration package.
IR, NFC/RFID, microphone, privacy, and interaction-safety boundary · maker-described communication and sensing claims · no final policy or protocol release identified
The record does not turn a feature list into a privacy guarantee, secure messaging claim, surveillance assurance, or universally suitable interaction model.
I²C address-range and bus-behavior documentation discrepancy · conflicting README and source details · implementation more specific than README; target behavior unresolved
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.
LED, CR2032, soldering, and electrical-safety documentation gap · maker product wording only · high-level light, battery, and kit terms published; engineering details absent
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.
LED, CR2032, soldering, and electrical-safety documentation gap · maker product wording only · high-level light, battery, and kit terms published; engineering details absent
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.
LiPo, charging, and kit-assembly safety boundary · current kit list and historical assembly guide · needs final safety and operating documentation
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.
LoRa, Wi-Fi, BLE, radio-performance, and privacy boundary · maker listing and MIT firmware repository · technical behavior documented with operational limits unknown
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
analog hardware, power, and GPIO electrical gap · maker-described component-level summary · needs circuit and host testing documentation
The record does not treat the product description as a circuit design, electrical integration guide, or safe compatibility guarantee.
artifact form, hardware, connector, and electrical-safety documentation gap · maker names SAO but publishes no specifications · physical companion status documented; technical form unreported
The record preserves a real announced companion artifact without upgrading it into a programmable, electrically safe, standard-compliant, or universally compatible electronic badge.
artifact form, hardware, power, and safety documentation gap · public badge label only · technical and material form undisclosed
The catalogue models a real planned named artifact without inventing its physical or electronic form, operating characteristics, safety profile, or engineering completeness.
assembly and electrical specification gap · primary storefront source · needs assembly and engineering documentation
The catalogue does not turn a retail component list into a complete construction, operating, or electrical-safety guide.
battery, EMF, and electrical-safety boundary · primary maker listing · needs technical and safety documentation
The catalogue does not turn the seller's protected-battery and EMF language into a safety endorsement, electrical-service guide, calibrated-instrument claim, or paranormal-detection claim.
battery, charging, and modification safety boundary · maker listing, firmware README, and CAD repository · needs final operating and safety documentation
The catalogue does not turn public power or CAD material into a battery-service guide, electrical-safety endorsement, charging claim, or safe-modification authorization.
battery, charging, and modification safety boundary · primary maker storefront source · needs operating and safety documentation
The record does not convert component names or marketing language into an electrical-safety endorsement, battery-service guide, or safe-modification claim.
battery, power, and SAO host-compatibility gap · official high-level product description · needs technical and safety documentation
The catalogue preserves the seller's limited power/SAO statements without treating them as safe-use instructions, universal host compatibility, a battery-safety endorsement, or an electrical specification.
battery, power, antenna, radio, and safety documentation gap · maker component-level claims · needs final engineering documentation and testing
The record retains source-named components without presenting the badge as electrically complete, radio-compliant, safe to charge/carry, or suitable for every configuration.
challenge, multiplayer, privacy, and behavior boundary · official maker pages · marketing-level behavior only
The catalogue preserves the game and collaboration claims without inventing a final challenge count, protocol, network/privacy guarantee, completed event experience, or solution material.
challenge-details, participant-data, software-release, support, and license boundary · public Player Guide only · high-level player guide published; complete archive and terms unrecovered
The catalogue intentionally does not reproduce connection credentials, network or local-service details, flags, hidden resources, challenge hints, serial commands, reset steps, or exploit material; it also does not imply a privacy/security review, safe operational configuration, reproducible build, legal reuse, or ongoing support.
community-event access-rule and final-event-outcome boundary · official DEFCON Furs event-space and meetup schedules · badge-required event-space wording published; implementation and outcome unrecovered
The catalogue records the published DEFCON Furs event-space boundary without inventing a technical access-control system or a record of individual access.
companion SAO documentation and image-provenance boundary · official BadgeLife companion page and badge guide · companion page is WIP; no cleared badge image selected
No unverified SAO is added and no Badge.Life image is copied into the public catalogue; the record remains source-useful while awaiting completed add-on and image-rights evidence.
companion SAO scope, interface, fabrication, and compatibility boundary · commit-pinned CPEC companion source · design archive published; interface and physical result unverified
The catalogue keeps the files attached to the MechBattle record as a source-published companion design trail without representing them as a plug-and-play accessory, a safe wiring or flashing guide, a completed add-on lineup, or a distributed DEF CON artifact.
creative reference, rights, and image-provenance boundary · maker names a film inspiration · specific artifact and per-asset rights not established
The catalogue preserves the maker's stated creative reference without republishing related art or inferring a license for the product image, board art, or source material.
current badge and historical Tricorder SAO identity boundary · same-maker but separately named product sources · related maker lineage documented; hardware and distribution parity unconfirmed
Readers can follow the useful same-maker historical context without treating it as an undocumented specification for the new DEF CON 34 badge.
current marketplace availability, BadgeLife drop, and credential boundary · live maker listing and current BadgeLife schedule · $10 / 10-remaining / 20-sold snapshot and August 7 4 PM drop published
The catalogue retains a time-specific independent maker offer and village context without treating it as an official credential, guaranteed handoff, or completed transaction.
current marketplace availability, BadgeLife drop, and credential boundary · live maker listing and current BadgeLife schedule · $10 / 17-remaining / 33-sold snapshot and August 7 4 PM drop published
The catalogue retains a time-specific independent maker offer and village context without treating it as an official credential, guaranteed handoff, or completed transaction.
current marketplace availability, BadgeLife drop, and fulfillment boundary · live maker listing and current BadgeLife schedule · $60 / 19-remaining / 11-sold snapshot and August 7 4 PM drop published
The catalogue preserves a time-specific independent-maker listing and schedule association without turning it into a fulfillment report, guaranteed handoff, or completed transaction.
current marketplace availability, DC34 drop, and fulfillment boundary · live maker listing and current BadgeLife schedule · $80 / five-remaining / four-sold snapshot and planned schedule published
The catalogue preserves a time-specific maker listing and schedule association without turning it into a fulfillment report or guaranteed handoff.
current-event and historical-revision identity boundary · same-name sources with no formal 2026 mapping · same title and maker/product linkage; exact 2026 parity unconfirmed
Readers can trace the useful v1/DC31 history without assuming the current planned sale is a newly engineered board, an unchanged old run, or a fully mapped revision.
design, firmware, and license archive gap · primary storefront and maker-profile sources · needs public archive or terms
The record can describe the listed components and pre-flashed-controller statement without claiming reproducible hardware, inspectable firmware, update support, or reusable design files.
detection, privacy, security, software-release, and operational-use boundary · maker repository documentation · high-level RF and software behavior documented; validation and operating terms unrecovered
The record avoids converting a project description into surveillance guidance, an identification claim, a privacy/security assurance, a supported update process, or a guarantee of behavior on any deployed badge.
documentation, circuit archive, and licensing gap · reviewed first-party listing only · no technical archive identified
The entry is a narrow source-backed analog-artifact record, not a reproducible open-hardware or software dossier.
documentation, source-license, and support boundary · live maker listing and current public-source review · product description published; design/source/support terms unrecovered
The catalogue retains the maker's concrete sales description without claiming a reproducible design, supported repair path, open-source release, or lifetime product maintenance.
documented DC34 REV1 power, accelerometer, and hardware-revision warning · public TrueControl DC34 README · source labels critical REV1 issues; field-correction and event outcome unrecovered
Readers can see the source-published REV1 limitation without receiving an unsafe repair prescription or an unsupported claim about a later board revision, battery behavior, accelerometer reliability, or field fix.
donation proof, privacy, tax, and charity-verification scope · public form fields and organizer wording · collection flow published; policies not recovered
Readers can distinguish the organizer's philanthropic request from financial, tax, legal, privacy, or data-security advice and should not assume a particular validation, deduction, confidentiality, retention, or delivery outcome.
draft code and physical-artifact boundary · primary CPEC repositories · planned project and companion design sources; physical artifacts unverified
The catalogue records a real named planned badge project and a source-published companion design trail, but does not turn source files into proof of physical, safe, completed, or distributed hardware artifacts.
draft game-design and media-rights boundary · source-linked draft document and local image-policy review · creative context only; no reusable media basis
The record remains image-free and does not reproduce draft lore, repository previews, screenshots, logos, board renders, or any generated/approximate badge image.
engineering archive, pinout, and compliance gap · primary maker storefront source · needs public engineering documentation
The catalogue retains precise maker-published components without treating a storefront specification as a fully reproducible design or universal SAO compatibility guarantee.
event association, availability, and credential boundary · CPEC repository wording and official DEF CON event context · independent association; allocation and authorization unconfirmed
The badge is classified as an independent planned project associated with DEF CON 34, not an official conference badge, registration benefit, access credential, organizer-endorsed product, or confirmed distribution.
event association, distribution, and credential boundary · repository's DEF CON 34 description and official DEF CON event context · independent pre-event source project; authorization and handoff unrecovered
The catalogue preserves the exact public event label without presenting this small source project as an official DEF CON item, a confirmed BadgeLife artifact, a completed delivery, or an access credential.
event association, distribution, and credential boundary · repository's exact DEF CON label and official DEF CON event context · independent pre-event source project; official relationship and handoff unrecovered
The exact public event label remains discoverable without turning it into evidence of OWASP or DEF CON endorsement, a physical run, availability, a completed delivery, or a credential.
event association, distribution, credential, and Agency-lineage boundary · repository's exact DEF CON 34 label and official DEF CON event context · independent pre-event source project; authorization, distribution, and shared lineage unrecovered
The catalogue preserves an exact event label without inventing official status, availability, ownership, attendee access, or a relationship to another Agency-themed record.
explicit message, authorship, content, and endorsement boundary · maker language and public self-submission only · seller/self-submission wording recorded; authority and content rights unsubstantiated
The entry preserves factual source language without claiming that any named/unnamed party authored, approved, sponsored, designed, endorsed, licensed, or consented to the message, artwork, or presentation.
fast-flash photosensitivity and optical-safety boundary · maker describes fast visual patterns · no reviewed optical-safety guidance identified
The catalogue records the stated visual effects without presenting them as safe or suitable for every viewer.
fast-flash photosensitivity and optical-safety boundary · maker describes a wide flash-rate trimmer · no reviewed optical-safety guidance identified
The catalogue records the stated visual control without presenting fast flashing as safe, suitable for every viewer, or a substitute for appropriate user caution.
final component, standards, firmware-release, and support scope · public repository documentation · needs final release confirmation
The catalogue preserves the documented architecture and declared licenses without asserting a particular part population, full standard conformance, reproducible attendee firmware, or a final supported release.
final hardware, schematic, manufacturing, and configuration gap · public README and schematic source · current production target and schematic published; final build not confirmed
Hardware claims stay tied to public source targets and documentation rather than becoming a final board specification, manufacturing result, complete build recipe, or evidence that any given unit contains a specific component set.
final revision and engineering archive gap · official product description · maker says final version may vary
The dossier keeps the stated feature set intentionally narrow and does not promote it into a final reproducible engineering design or a manufacturing-quality claim.
firmware binary, compatibility, and update-scope boundary · public source and commit history · no tagged release identified
Source-level game and interface behavior remains discoverable without labeling the branch as a final, universally flashable, supported event firmware package.
firmware release and licensing gap · primary maker storefront and profile sources · awaiting announced firmware release
The record can describe the maker's announced feature surface without claiming a released, reproducible, inspectable, or reusable firmware archive.
firmware release, bootloader, source-license, support, and image-rights boundary · public README and repository-tree review · firmware directory and instructions published; release/license/support terms unrecovered
The catalogue can link the source project without turning development instructions into a recommendation to program hardware, treating visible files as a final/reproducible deployment, claiming legal reuse, or publishing a repository visual without complete image provenance.
firmware release, code license, network, and data boundary · public source snapshot and MVP note · current source exists; release, deployment, and operational terms unverified
The catalogue links public project material without treating source visibility as a completed firmware release, security guarantee, network/data practice, or reusable code grant.
firmware release, configuration, and licensing boundary · commit-pinned maker firmware and license documentation · versioned maker release published; delivered-unit state unverified
The dossier records a concrete source release without asserting source-to-sale identity for every unit, a complete dependency/security audit, a warranty, or a safe user update path.
firmware release, dependency, and update-scope boundary · MIT repository and v4.0.0 release · public source and partial binary coverage
The catalogue can link the MIT source and named binaries without treating them as a universal, final, supported field-update package.
firmware release, deployed-revision, and support boundary · repository and license · public source exists; delivered-unit scope unverified
The record links the public workflow without representing it as a final reproducible, supported, audited, or universally deployed firmware release.
firmware release, license, and operating-procedure boundary · repository metadata, root-tree, README, and source review · source snapshot published; tagged release, explicit licence, and supported workflow unrecovered
The public code is linked as evidence without being presented as licensed, supported, reproducible, safe to reprogram, or equivalent to a delivered event firmware image.
firmware release, toolchain, dependencies, and software-license gap · repository and diary describe evolving work · implementation materials exist; final user release not identified
The dossier links the public work without presenting it as a finished end-user firmware or support package.
firmware release, update, support, and licence gap · public source-tree review · source and compiled artifacts visible; explicit release/licence/support terms absent
The catalogue can link the implementation without presenting it as licensed open hardware/software, a stable release, a reproducible final build, a safe reflashing process, or an ongoing support commitment.
firmware, CTF, gameplay, source, and licensing gap · no artifact-level technical source recovered · no implementation or interaction documentation located
Readers are not led to assume that the D20 name denotes an electronic game, an access pass, a CTF device, or any documented implementation.
firmware, CTF, protocol, backend, and licensing gap · team-announced software claim · no public technical release identified
The record does not convert a game announcement into a reproducible software release, operational service, security claim, data-handling guarantee, or solution guide.
firmware, UART/XMODEM bootloader, release, source-license, and support boundary · public README and repository-tree review · current public branch and documentation visible; formal release/license/support terms unrecovered
The catalogue links a substantive public development trail without treating a branch label or bootloader documentation as a complete supported release, a safe flashing guide, a legal reuse grant, or proof of every event unit's firmware.
firmware, UPDI operations, source-license, and support boundary · live maker firmware-feature listing · feature list published; release and target-operation assurance unrecovered
The catalogue records the published high-level feature surface without supplying programming steps, treating it as an audited firmware release, promising safe behavior on attached devices, or reusing marketplace media.
firmware, VOC algorithm, release, and licensing boundary · maker product description, maker-owned source archive, and public release page · source tree public; no release, license, or event-unit mapping recovered
The catalogue can cite the public source archive without presenting it as a finalized event release, validated VOC algorithm, supported update path, secure deployment, operating instruction, or a code/artwork/media reuse grant.
firmware, audio, media, and license gap · official product description and source review · no public implementation archive identified
The record describes the maker-published audio/storage intent without asserting reproducible firmware, media-reuse rights, final playback behavior, or user-operation instructions.
firmware, audio, source, and intellectual-property scope gap · official product description and source review · no public technical release identified
The record describes the stated audiovisual/art surface without asserting reproducibility, software availability, audio/art reuse rights, final content, or support scope.
firmware, cryptography, performance, and source-license boundary · maker-described product claims and adjacent repository review · claims are not independently validated; matching release and clear license absent
The catalogue does not characterize the badge as secure, audited, reproducible, open source, performant, or suitable for a security-sensitive purpose solely from maker marketing or an adjacent framework.
firmware, data, license, and source-scope boundary · commit-pinned firmware material, project status, and root license text · source files published; final software and rights scope unverified
The catalogue links the public source archive without treating it as an audited or finished firmware release, authorizing users to follow its procedures, or treating the root license as broad hardware/media/image permission.
firmware, documentation, and licensing gap · primary maker product statement · maker promises post-con material; no current release identified
The dossier records the promise as a future source lead without asserting software availability, reproducible builds, final feature behavior, or reuse rights.
firmware, feature-readiness, and security-behavior boundary · author's explicit day-one qualifier · only source-starred features described as available day 1
The record does not represent deferred or merely hardware-capable categories as shipped functions, supported workflows, secure behavior, or final user experience.
firmware, installer, dependency, data, and license-scope boundary · public software tree, README, and root MIT license · public source/documentation trail; final firmware and third-party provenance unverified
The catalogue records public code and documentation without asking readers to run installers, treating the project title as a security claim, or representing the repository as a complete/audited/reproducible event-firmware release.
firmware, interaction-protocol, and licensing gap · primary maker storefront source · needs public archive or terms
The catalogue does not infer radio technology, cryptographic behavior, exploit mechanics, interoperable networking, source availability, or redistribution rights from promotional game language.
firmware, key-pair, signing, and protocol gap · maker claim · high-level signed-firmware claim only
The catalogue does not translate a security-oriented maker claim into a cryptographic assurance, vulnerability claim, identity guarantee, or implementation recommendation.
firmware, license, artwork, and image-provenance boundary · repository metadata and commit-pinned README review · source tree public; license, production release, and reusable-image permission unrecovered
Code and design material remain linked as evidence, while the record stays image-free and does not present the repository as an open-hardware, software, artwork, or media-reuse grant.
firmware, programmable behavior, current GitHub, and licence gap · current roster plan and historical repository review · Day-1 GitHub plan stated; 2026 technical archive absent before event
The catalogue does not turn a future publication promise, flashing LED component labels, or an old Gerber archive into a claim of programmable behavior, open source, reproducible current firmware, or licensed reuse.
firmware, programming, release, and source-license gap · public repository and source review · development source visible; final release and explicit license unconfirmed
The catalogue links a public implementation trail without converting marketing language into a legal reuse grant, reproducible build, supported reflashing path, final firmware release, or warranty.
firmware, programming, release, and source-license gap · public repository and source review · development source visible; final release and explicit license unconfirmed
The catalogue links a public implementation trail without converting marketing language into a legal reuse grant, reproducible build, supported reflashing path, final firmware release, or warranty.
firmware, radio, privacy, and license boundary · public repository review · in-progress source and Arduino file with no reviewed final release or root license
The record does not offer configuration or operating instructions, claim secure or private interaction, assert a released firmware, or treat public code as a license grant.
firmware, release, and licensing boundary · public repository and release page · educational source is public; final release and reuse terms unrecovered
Public source visibility is recorded without treating it as a finished event release, reliable operating path, security assurance, or permission to copy code, artwork, project branding, photographs, or screenshots.
firmware, release, flashing, and source-license gap · public repository and current root review · development source visible; release and license unconfirmed
The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.
firmware, release, flashing, and source-license gap · public repository and current root review · development source visible; release and license unconfirmed
The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.
firmware, release, flashing, and source-license gap · public repository and current root review · development source visible; release and license unconfirmed
The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.
firmware, release, source-license, and support gap · public repository and current metadata review · public development tree; final release and license unconfirmed
The catalogue can link the public engineering trail without representing the badge as fully open source, reproducibly buildable, support-guaranteed, secure, licensed for reuse, or equivalent to every shipped unit.
firmware, research-build, and source-release scope · official seller statement and public repositories · final Clip-Boy release not identified
The dossier links relevant public context without representing it as an available, reproducible, supported, or authorized Clip-Boy firmware package.
firmware, security, source, and licensing gap · reviewed first-party listing only · no technical archive identified
The catalogue does not treat marketing jokes as a reliability, security, firmware, or open-hardware claim.
firmware, software, source, and license gap · no implementation source recovered · no software or source documentation located
Readers are not led to assume electronic behavior, firmware availability, open-source status, video-game functionality, or a supported modification path from the artifact name alone.
firmware, source, and security-state boundary · official support page and creator-published repositories · public update and source paths available; unit-by-unit state unrecovered
The catalogue links the public archive and records the documented state transition without recommending installation, claiming that a later source tree exactly matches every badge, or presenting the token and QR features as independently validated or permanently supported.
firmware, source, authorship, and license gap · public product and roster sources · no implementation or rights archive recovered
The catalogue retains first-party product wording without turning it into a programmable-badge, open-source, reproducible-design, authorship, cultural-affiliation, endorsement, or reusable-media claim.
firmware, source, authorship, and license gap · public product and roster sources · no implementation or rights archive recovered
The catalogue retains first-party product wording without turning it into a programmable-badge, open-source, reproducible-design, authorship, cultural-affiliation, endorsement, or reusable-media claim.
firmware, source, behavior, and licensing gap · reviewed first-party listing only · no technical archive identified
The entry does not turn simple listed behavior into an open-source, programmable, or security-verified badge claim.
firmware, source, release, and licence gap · public maker source review · no public implementation/archive identified
The record does not turn a documented blinky add-on into a programmable badge, released source project, reproducible build, or legal reuse grant.
firmware, source, release, privacy, and licence gap · current public-source review · no current implementation or policy archive identified
The catalogue does not present a proposed sensor badge as a released software project, a programmable device, a privacy-reviewed tracker, a reproducible build, or a legal reuse grant.
firmware, source-code, challenge, and recovery boundary · official BadgeLife guide · high-level recovery documentation published; firmware release and support unrecovered
The record makes the public documentation discoverable without turning it into an invitation to bypass challenges, a verified update path, a final firmware archive, or a supported modification procedure.
firmware, support, third-party-media, and image-rights boundary · maker README, handoff, and repository license · V5 source history public; third-party-media and gallery-image rights unresolved
The catalogue links a substantive source and firmware trail but publishes no repository image or artwork and does not present a later source revision as a supported update or all-unit state.
firmware, toolchain, programming workflow, and licensing gap · official product description and cited basis · no public technical release identified
The catalogue credits the public source basis without supplying unverified programming steps, device-specific firmware claims, a reproducible build, or reuse terms.
firmware, update, radio/data, and software-license scope boundary · official project/update pages and public firmware fork · active project/update surface published; deployed configuration and assurance unrecovered
The catalogue links a real public project without implying that a labelled firmware build is complete, audited, installed on every unit, safe for a particular radio/data context, or accompanied by a support guarantee.
firmware, vendor-command, secret-content, and licensing gap · official product-level behavior description · no public technical release identified
The catalogue records public behavior claims without exposing or inventing challenge content, protocol messages, source availability, update steps, or reuse rights.
first-run shipping, second-run interest, and fulfillment boundary · official shop and current inventory · first run sold out; second run not committed
The catalogue records a current sold-out/interest state without calling every unit delivered, treating a signup as an order, or claiming a future run will occur.
game firmware, update, source, and license gap · maker game claims and public board binary context · CircuitPython build available; eChallengeCoin game/release trail incomplete
The catalogue points to a public board platform without representing the shipped game or final coin as open source, reproducibly buildable, safe to reflash, supported, security-reviewed, or licensed for redistribution.
generated-art source and image-provenance boundary · primary repository README · generated artwork remains excluded
No board art, product imagery, source preview, or derivative is treated as a rights-cleared factual hero image merely because the code/design source is public or broadly licensed.
giveaway, purchase-included, color, and revision relationship boundary · multiple first-party statements but no mapping · separate source claims retained; relationship unresolved
Readers should not assume that a purchased companion is the same as a free-drop item, that every color is available in every channel, or that all public claims describe one identical physical run.
hardware and firmware archive gap · official product page and GitHub inspection · awaiting announced activation material
The record does not turn marketing references to hardware, firmware, or GPIO into an unverified electronic-badge specification.
hardware revision, bill-of-material, power, and safety boundary · public source tree · multiple source artifacts; final physical unit undocumented
The record does not transform source tree names and schematic/fabrication material into a verified production bill of materials, safety endorsement, repair guide, or field-operating recommendation.
hardware revision, final bill-of-material, and interface boundary · maker listing and MIT firmware repository · multiple revisions documented
The record retains supported feature families while avoiding a claim that the live offering exactly matches one repository branch, older board revision, or a complete production BOM.
hardware revision, power, connector, and safety documentation gap · public hardware tree and firmware pin declarations · source files published; final electrical and mechanical specification incomplete
The entry can point to a concrete design archive without presenting the SAO as electrically complete, interoperable with every host, safe for every power source, fabricated, tested, or compliance-validated.
hardware, 9 V power, SAO, assembly, and electrical-safety specification boundary · public README, BOM, and native board tree · design sources published; final engineering validation unrecovered
The record links a real design trail without presenting it as a complete electrical specification, a validated battery/adapter recommendation, a universal SAO compatibility claim, a safe assembly guide, or a manufactured quality record.
hardware, AA power, enclosure, and safety documentation gap · maker product description · high-level physical claims published; engineering documentation absent
The record does not turn a maker-described bare board and battery arrangement into a safe-use instruction, a battery-life guarantee, or a universal hardware-compatibility claim.
hardware, LiPo, USB-C, RF, and mechanical safety boundary · official project site and public design repositories · source-published components/design files; engineering validation unrecovered
The record provides the documented hardware surface without becoming an electrical, radio, battery, fabrication, or repair endorsement.
hardware, OLED, LiPo, ESP32, and variant gap · maker comment · component names only for an intended RGB full-board configuration
The entry does not turn an availability comment into a complete BOM, safe battery-use statement, final product configuration, or engineering specification.
hardware, SAO, measurement, and safety validation gap · repository and maker descriptions · detailed source but no final validation evidence
The dossier does not turn an open technical design into an accuracy guarantee, safe-use endorsement, electrical compatibility certificate, or universally compatible host accessory.
hardware, battery, SAO, and I2C compatibility gap · maker product description plus maker-owned KiCad source · source schematic/PCB public; final unit and host testing unresolved
The record can link a source-published design trail while withholding a final physical specification, safe battery-use claim, collision-free bus guarantee, or universal SAO compatibility assertion.
hardware, battery, radio, and safety-validation boundary · maker-proposed technical documentation · design-stage hardware claims; engineering validation unrecovered
The record retains high-level source-backed design claims without treating them as an electrical specification, a battery-safety statement, a radio-compliance claim, a universally compatible SAO result, or operational advice.
hardware, battery, radio, electrical-safety, and compliance boundary · maker README and hardware guide · component and build caveats published; broad validation unrecovered
Public fabrication material and candid build notes remain discoverable without becoming a universal build, battery-service, radio-operation, or electrical-safety recommendation.
hardware, connector, coin-cell, and electrical-safety documentation gap · maker product description · high-level LED and SAO claims documented; full safety specification absent
The catalogue records the source-published LED and connection context without claiming universal host compatibility, a ready coin-cell wearable, electrical safety, soldering safety, or a complete engineering specification.
hardware, firmware, and licensing archive gap · reviewed maker sources · no public technical archive identified
Maker-published feature language remains traceable but is not treated as a reproducible build, released firmware, open hardware, free software, or permission to reuse technical or visual material.
hardware, power, LED, and host-compatibility gap · maker physical-form summary · needs technical documentation and host testing
The record does not convert a direct-DC34 marketing claim into a general electrical or mechanical compatibility guarantee.
hardware, power, RFID, SAO, and assembly-safety documentation boundary · public README inventory and assembly documentation · component-level kit inventory published; engineering validation unrecovered
The record preserves the documented kit surface without converting it into an electrical specification, safe-build/use instruction, radio/RFID compatibility claim, battery-life estimate, or universal SAO-host guarantee.
hardware, power, SAO, and electrical-safety boundary · maker README and engineering notes · design and caveats published; broad validation unrecovered
Readers can inspect the source-described hardware and its own caveats without treating it as a universal plug-and-play, electrically safe, or fully validated device.
hardware, power, USB, FPC, and UPDI safety gap · maker-level feature and revision description · needs final electrical documentation and validation
The record does not turn product-level programming and cable claims into a universal target-support list, safe-voltage recommendation, USB certification, durable-cable guarantee, or complete electrical design.
hardware, power, USB, and electrical-safety documentation gap · high-level source descriptions only · feature-level hardware claims published; engineering documentation absent
The record retains a traceable hardware surface without presenting the coin as electrically characterized, safe for every cable/host, reproducible, compliance-tested, or suitable for unsupervised modification.
hardware, power, Wi-Fi, connector, and physical-interaction safety boundary · public Player Guide identifies only high-level surfaces · limited player-facing hardware context published; engineering specification unrecovered
The record describes its source-backed interaction surface without turning it into a hardware specification, a safe connection/modification guide, a wireless-security claim, a universal SAO-compatibility result, or a validated physical-unit record.
hardware, power, and SAO specification gap · official high-level maker descriptions · needs technical release
The record does not turn product-level specifications into a complete electrical design, safe-use instruction, repair guide, certification claim, or universal SAO guarantee.
hardware, power, and physical-specification gap · immutable repository README and first-person PCB statement · component-level source trail; physical design unreleased
The record retains the documented components without converting them into a complete electrical design, power-safety claim, performance statement, production specification, or repair/build procedure.
hardware, power, and physical-specification gap · public high-level component claim · needs technical release or documented final unit
The record preserves named hardware without turning it into a complete, electrically safe, interoperable, or production-verified design.
hardware, power, and safety specification gap · primary maker storefront source · needs engineering archive
The record reports specific listed features without presenting the badge as electrically characterized, reproducible, or safe for any unsupported modification.
hardware, power, and two-object specification gap · team-announced high-level hardware claims · needs a technical release or documented final unit
The dossier preserves the published technical nouns without treating them as a complete electrical design, interoperable standard, safe-use instruction, or confirmed production specification.
hardware, power, breakout, debug, and target-safety boundary · live maker component and interface listing · high-level hardware surface published; engineering validation unrecovered
The dossier remains technically useful without becoming a reference design, external-target compatibility assurance, power specification, or hardware safety endorsement.
hardware, power, connector, and electrical-safety documentation gap · historical BOM/assembly notes only · older component list published; operating limits unreported
The record documents a real LED SAO design trail without presenting either the old or planned re-release as electrically characterized, safe for every host, mechanically compatible, or suitable for unsupervised modification.
hardware, power, connector, and electrical-safety documentation gap · public schematic/BOM and source but incomplete operating documentation · design inputs visible; practical limits unreported
The dossier links an inspectable design trail without asserting that every source-derived board is electrically compatible, safely assembled, safe to attach, or suitable for unattended modification.
hardware, power, connector, and safety documentation gap · public hardware tree and firmware pin declarations · source files published; final electrical and mechanical specification incomplete
The entry can point to a concrete archive without representing the SAO as electrically complete, interoperable with every host, safe for every power source, fabricated, tested, or compliance-validated.
hardware, power, connector, host interaction, and safety documentation gap · public hardware tree and firmware pin declarations · source files published; final electrical and mechanical specification incomplete
The entry can point to a concrete archive without representing the SAO as electrically complete, compatible with every Portal Badge or host, safe for every power source, fabricated, tested, or compliance-validated.
hardware, power, firmware, and electronic-specification gap · official checkout terminology only · LED badge with no technical archive identified
The entry does not turn an LED-badge product label into a claimed circuit, operating behavior, repair path, certification, or safety assurance.
hardware, power, host-interface, and safety boundary · commit-pinned README and public KiCad tree · high-level design surface published; final electrical and physical validation unrecovered
The entry keeps its useful electronic-design trail visible while avoiding an electrical guarantee, universal SAO compatibility claim, safety endorsement, or do-it-yourself operating instruction.
hardware, power, memory, and SAO compatibility gap · maker component-level summary · needs technical documentation and host testing
The record does not convert a maker-described lighting surface into a universal electrical compatibility or reliability guarantee.
hardware, power, radio, and host-compatibility validation gap · commit-pinned maker hardware and RF documentation · detailed maker release published; independent validation still absent
The entry can accurately describe the released engineering material while withholding a universally safe host/power claim, compliance finding, independent performance guarantee, or repair/modification recommendation.
hardware, power, radio, and safety specification gap · official high-level product description · needs technical release
The record does not convert promotional/high-level descriptions into an electrical specification, RF certification claim, charging recommendation, repair/modification guide, or safety endorsement.
hardware, power, radio, and safety specification gap · official high-level product description · needs technical release
The dossier keeps precise seller-described features without turning them into a complete electrical specification, safety endorsement, repair guide, or RF/compliance claim.
hardware, power, red LED, and host-compatibility gap · maker physical-form summary · needs technical documentation and host testing
The record does not promote a decorative power-on statement into a general electrical compatibility or reliability guarantee.
hardware, power, touch, and interoperability documentation gap · commit-pinned firmware README · high-level interface components identified; production design unreleased
The entry reports the named firmware target and interaction surface without inferring a complete electrical design, reliable touch behavior, safe power path, or compatibility with external hardware.
hardware, power, wood, and SAO-host electrical gap · maker component and interface summary · needs final electrical and mechanical documentation
The dossier does not convert a useful product and how-to description into an electrical integration certificate, universal host fit, or material-safety guarantee.
hardware, software, radio, NFC, and safety specification boundary · official product-description review · high-level planned electronics published; technical release unrecovered
The record makes the organizer-published design intent discoverable without converting sales copy into a finalized, safe, interoperable, privacy-reviewed, or source-released device.
hardware, surface-mount, and connector documentation gap · maker SAO label and high-level surface-mount statement · artifact class and one fabrication change named; engineering details undisclosed
The record preserves the verified artifact classification and v2 fabrication statement without inventing electronics, connector behavior, or electrical safety properties.
hardware-source and production-revision boundary · published directory structure only · source-tree scope not reconciled with manufactured units
The directory structure is recorded as a useful maker trail without treating it as a complete released hardware package or confirmation that all sales share one documented revision.
horror theme, authorship, and endorsement boundary · maker wording and source labels only · creative framing recorded; rights and affiliation unsubstantiated
The dossier records source-described creative framing without asserting ownership, franchise/religious or cultural affiliation, sponsorship, endorsement, authorship, or media-reuse authority.
horror theme, authorship, and endorsement boundary · maker wording and source labels only · creative framing recorded; rights and affiliation unsubstantiated
The dossier records source-described creative framing without asserting ownership, franchise/religious or cultural affiliation, sponsorship, endorsement, authorship, or media-reuse authority.
image provenance · maker-controlled repository license and pinned upstream asset · licensed official render added
The catalogue now shows a source-licensed official upstream render without copying the Uberflux gallery, project-page media, social imagery, a screenshot, placeholder, or synthetic approximation.
image-provenance boundary · repository image/vector review and local image policy · no selected factual artifact image with complete reusable provenance
The project remains image-free rather than publishing board previews, vector artwork, Gerber renderings, screenshots, source graphics, synthetic imagery, or an approximate badge image.
in-person game, wireless, player-data, and safety boundary · team-announced proximity and event-interaction claims · planned behavior only
Readers can see the intended collaborative game context without assuming that proximity effects, wireless behavior, data use, safety, or onsite logistics were implemented, authorized, or suitable for every participant.
incomplete software, IR, data, and safety boundary · commit-pinned source header and repository review · handshake, infrared, and logging explicitly not wired up; release and review state unrecovered
The listed source remains useful as a development snapshot while users are warned not to infer functional infrared/game behavior, safe operation, data handling, or a supported release.
independent BCCC / DEF CON association and credential boundary · official contest page and maker sources · independent contest-linked BadgeLife artifact
The catalogue classifies the artifact as an independent contest-linked Simple Add-On rather than an official conference credential, access substitute, or confirmed universal contest prize.
independent BadgeLife and DEF CON credential boundary · primary maker listing · documented as an independent pre-event release
The catalogue classifies it as an independent BadgeLife record rather than an official DEF CON Human badge or a substitute for conference registration.
independent BadgeLife classification · primary storefront source · documented pre-event
The record is connected to DEF CON 34 for BadgeLife discovery while remaining distinct from the official Human badge and any general-attendee allocation.
independent BadgeLife classification and edition allocation gap · primary organizer event listing · documented pre-event
The record remains a separately organized BadgeLife fundraiser linked to DEF CON 34 discovery, distinct from the official Human badge and from unverified allocation claims.
independent DC34 association and official credential boundary · live maker page and primary public source hierarchy · independent pre-event maker/project association
The dossier treats the Portal Badge as an independently sourced DC34 maker/project, not an official DEF CON credential or a substitute for registration.
independent DEF CON and Packet Hacking Village association, allocation, and credential boundary · official village programme plus maker repository · completed independent village-associated project; organizer issuance and allocation unrecovered
The dossier preserves a completed event-associated electronic artifact without treating it as an official DEF CON Human badge, village credential, general attendee entitlement, or proof that any specific person received a unit.
independent DEF CON association and MF DOOM affiliation boundary · public maker self-submission and fan-themed product name · independent planned BadgeLife artifact; credential and rights status undocumented
The catalogue records a real independent maker-announced SAO while avoiding an official credential claim or an inference of artistic/trademark authorization.
independent DEF CON association and credential boundary · maker storefront and public Badgelife self-submission · independent planned electronic holder associated with DEF CON 34
The catalogue records a source-backed independent event association without portraying the holder as official conference hardware, an admission credential, a universal attendee benefit, or confirmed organizer distribution.
independent DEF CON association and credential boundary · maker product and announcement · independent Lepi Labs SAO with a planned DC34 drop
The catalogue classifies the canary as an independent pre-event BadgeLife artifact associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · r/Defcon maker post plus official event-context source · independent pre-event giveaway project
The catalogue classifies this as an independently documented pre-event project associated with DEF CON 34, not an official conference credential, organizer-issued badge, attendee entitlement, or verified event activity.
independent DEF CON association and credential boundary · maker page and public Badgelife self-submission · independent planned SAO associated with DEF CON 34
The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or a completed official distribution.
independent DEF CON association and credential boundary · maker Defcon34 label and BadgeLife village schedule · independent pre-event maker badge associated with DC34
The record preserves a real independent BadgeLife event association without presenting Breadbadge as an official DEF CON credential or access item.
independent DEF CON association and credential boundary · maker page and public Badgelife self-submission · independent planned SAO associated with DEF CON 34
The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or completed official distribution.
independent DEF CON association and credential boundary · maker pickup wording and current-event index · independent planned eChallengeCoin associated with DEF CON 34
The catalogue connects this independent maker artifact to its cited DEF CON 34 discovery/pickup context without presenting it as official conference hardware, an access item, a universal attendee benefit, or a completed organizer distribution.
independent DEF CON association and credential boundary · maker product listing · independent pre-event SAO associated with DEF CON 34
The catalogue classifies METROPOLIS AI SAO as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker product, repository, and diary · independent planned SAO associated with DEF CON 34
The catalogue classifies MalO as an independent pre-event Simple Add-On associated with DEF CON 34, not an official conference credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker product and announcement · independent Lepi Labs SAO with a planned DC34 drop
The catalogue classifies the Firefly Jar as an independent pre-event BadgeLife artifact associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker roster wording · independent planned BadgeLife giveaway association documented
The catalogue records a public independent event association without portraying the SAO as official conference hardware, a registration benefit, an access credential, a sanctioned village artifact, or proof of organizer endorsement.
independent DEF CON association and credential boundary · maker project and marketplace sources · independent DC34-associated badge
The catalogue classifies Wordweaving as an independent BadgeLife project associated with DEF CON 34, not an official conference credential, admission item, organizer-issued badge, or confirmed authorized sales presence.
independent DEF CON association and credential boundary · maker product and announcement · independent Lepi Labs SAO with a planned DC34 drop
The catalogue classifies the moth as an independent pre-event BadgeLife artifact associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker storefront plus contest-context sources · independent DC34-associated badge
The catalogue classifies it as an independent commemoration associated with DEF CON 34 rather than an official conference credential, admission item, or organizer-issued product.
independent DEF CON association and credential boundary · maker DEF CON 34 listing, public project documentation, and BadgeLife village schedule · independent pre-event maker badge associated with DC34
The record retains a documented maker, public-project, and village association without presenting Agency Wand as DEF CON's official badge or an access credential.
independent DEF CON association and credential boundary · maker product listing · independent pre-event SAO associated with DEF CON 34
The catalogue classifies #NOICE as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker product and guide · independent pre-event SAO associated with DEF CON 34
The catalogue classifies Root Access as an independent pre-event Simple Add-On associated with DEF CON 34, not an official credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker self-submission and product statements · independent planned BadgeLife association documented
The catalogue tracks a public independent event association without presenting the SAO as official conference hardware, an access credential, a registration benefit, a sanctioned village item, or proof of organizer endorsement.
independent DEF CON association and credential boundary · maker listing and public Badgelife self-submission · independent BadgeLife artifact associated with DEF CON 34
The catalogue records a real independent badge/event association without turning it into an official conference credential, organizer-issued hardware, access item, or universal attendee handout.
independent DEF CON association and credential boundary · maker storefront and public Badgelife self-submission · independent planned electronic holder associated with DEF CON 34
The catalogue records a source-backed independent event association without portraying the holder as official conference hardware, an admission credential, a universal attendee benefit, or confirmed organizer distribution.
independent DEF CON association and credential boundary · maker self-submission and marketplace sources · independent planned event-market association documented
The catalogue tracks a public independent event association without presenting a maker sale as official conference hardware, a registration benefit, an access credential, an organizer endorsement, or a completed vendor commitment.
independent DEF CON association and credential boundary · first-hand project posts · independent planned BadgeLife-style project
The catalogue classifies the Zombie Badge as an independent pre-event project associated with DEF CON 34, not an official conference credential, organizer-issued badge, admission item, or verified event activity.
independent DEF CON association and credential boundary · public offer post and official date announcement · independent pre-event artifact associated with DEF CON 34
The catalogue presents a real independent event-associated badge offer without misclassifying it as an official conference credential, organizer product, admission item, or verified vendor-booth activity.
independent DEF CON association and credential boundary · maker self-submission and historical marketplace sources · independent planned event-market association documented
The catalogue tracks a public independent event association without presenting a maker sale as official conference hardware, a registration benefit, an access credential, organizer endorsement, or a completed sales relationship.
independent DEF CON association and credential boundary · maker product listing · independent pre-event SAO associated with DEF CON 34
The catalogue classifies HackThePlanet as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker repository wording · independent pre-event challenge-tool association documented
The catalogue keeps the target relationship searchable while classifying this as independent BadgeLife hardware rather than official conference hardware, an access credential, a universal attendee item, or evidence of organizer endorsement.
independent DEF CON association and credential boundary · maker storefront and first-person maker announcement · independent pre-event maker offering associated with DEF CON 34
The catalogue classifies Ouroboros as an independent BadgeLife offering tied to maker intent, not an official conference credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker page and public Badgelife self-submission · independent planned SAO update associated with DEF CON 34
The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or completed official distribution.
independent DEF CON association and credential boundary · maker storefront and public Badgelife self-submission · independent planned kit associated with DEF CON 34
The catalogue records a source-backed independent event association without presenting v2 as official conference hardware, an access item, a universal attendee benefit, or confirmed organizer distribution.
independent DEF CON association and credential boundary · maker product listing · independent pre-event SAO associated with DEF CON 34
The catalogue classifies Luna as an independent pre-event Simple Add-On, not an official conference credential, organizer-issued badge, or access item.
independent DEF CON association and credential boundary · maker storefront and public Badgelife self-submission · independent planned kit associated with DEF CON 34
The catalogue records a source-backed independent event association without presenting v1 as official conference hardware, an access item, a universal attendee benefit, or confirmed organizer distribution.
independent DEF CON association, RM-Cyber relationship, allocation, and credential boundary · public repository description and Player Guide · pre-event source project documented; organization relationship and handoff unverified
The catalogue preserves the source's current event association and distinct project name without presenting it as an official DEF CON badge, an RM-Cyber-issued artifact, a guaranteed attendee benefit, an access credential, a completed release, or proof that any participant received one.
independent DEF CON association, allocation, and credential boundary · public maker repository, commit-pinned README, and physical-production update · source-publisher physical maker run documented; organizer relationship and recipient handoff unverified
The catalogue records a documented independent physical DEF CON 34-associated maker badge, not an official DEF CON artifact, organizer-issued silent-disco credential, guaranteed attendee benefit, access pass, or completed conference distribution.
independent DEF CON association, allocation, and credential boundary · maker README, engineering notes, and post-conference handoff · maker documents completed independent DC34 sales; official relationship and allocation unrecovered
The record retains a source-backed completed independent event association without representing the add-on as an official Human badge, a conference credential, a ticket benefit, or an audited distribution run.
independent DEF CON association, availability, pickup, and credential boundary · first-hand maker announcement and official project site · planned pre-event DEF CON 34 presence; order and handoff outcomes unverified
The catalogue records a real maker-announced DEF CON-associated BadgeLife artifact without representing it as an official Human badge, conference credential, completed transaction, or guaranteed handoff.
independent DEF CON association, company authorization, allocation, and credential boundary · public project repository and README · pre-event independent source project; authorization and delivery unverified
The catalogue classifies the artifact as a planned independent DC34-associated badge kit rather than an official DEF CON badge, a company-issued item, an authorized event activation, an access credential, or a completed distribution.
independent DEF CON association, production, allocation, and credential boundary · public repository and README · pre-event independent source project; authorization and handoff unverified
The catalogue records a named, technically documented independent project without presenting it as an official DEF CON badge, an attendee entitlement, a credential, a completed physical run, or proof that any participant received one.
independent DEF CON/HRV association, availability, and credential boundary · maker repository description and official Ham Radio Village event page · maker-associated planned project; official relationship and handoff unverified
The catalogue classifies this as an independent planned project associated with the event context, not an HRV-issued or DEF CON-issued badge, a guaranteed attendee benefit, a venue-authorized activation, a Human badge, an access credential, or proof that anyone received a physical unit.
independent EFF relationship and donation-accounting boundary · primary organizer event listing · limited to published organizer statement
The catalogue records the organizer's exact public relationship and benefit statements without presenting independent organizers as EFF staff, claiming an EFF retail product, or inferring unannounced donation details.
independent badge and role-allocation classification · primary maker storefront source · documented pre-event
The record is connected to DEF CON 34 for BadgeLife discovery while remaining distinct from the official Human badge and from unverified role/allocation claims.
independent badge classification · official project page and DEF CON context · documented pre-event
The record can sit under the DEF CON 34 event without confusing the independent BadgeLife project with the official conference-access badge.
independent meetup and DEF CON credential boundary · first-hand Team announcement and official checkout · independent community meetup artifact
The catalogue models a real Puzzled Hackers community badge associated with DEF CON 34 while keeping it distinct from official admission, organizer issuance, and verified event access.
independent monorail, DEF CON, and credential boundary · primary maker storefront and first-person announcement · independent DEF CON 34-associated maker product
The catalogue treats this as an independent themed badge, not a transit artifact, fare instrument, official DEF CON credential, admission item, or sponsored product.
license and image-provenance boundary · GitHub repository metadata and source-tree review · no detected repository license or rights-cleared image trail
The badge remains image-free and the code is linked as evidence rather than treated as a license grant, image-reuse permission, or complete open-hardware release.
live challenge, scoreboard, and data-handling scope · official storefront statement · public concept only
The record keeps the organizer-published challenge framing discoverable without assuring a particular technical experience, safe data practice, fair scoring, accessibility, availability, or a final public result.
maker-announcement and technical-archive gap · first-hand maker announcement · no public repository or technical release recovered
The dossier records direct maker claims while withholding a reproducible architecture, complete evidence trail, or independent technical corroboration.
maker-post, repository, and project-identity boundary · shared public project name across two sources · physical maker post and repository context retained without account-identity merge
The catalogue can cite the corroborating project-name trail without stating that u/ProfessionalPea2218 controls Cyb3rBytes404 on GitHub, authored all code, or holds any formal nonprofit, DEF CON, or media-rights role.
manufacture, allocation, and distribution boundary · dated first-party project commit · 1,000-made claim recorded; final run and handoff unrecovered
Readers can find the direct maker claim without treating its quantity as an independently audited manufacturing total, a promise to a particular attendee, a distribution ledger, or proof that the event handoff occurred.
minibadge configuration, headers, power, and safety documentation gap · maker product wording and repository README · holder behavior and interface need final documentation
Readers can identify a real electronic holder without treating it as universally interchangeable, electrically safe, mechanically compatible, or ready to use with every minibadge.
minibadge configuration, headers, power, and safety documentation gap · maker product wording and repository README · holder behavior and interface need final documentation
Readers can identify a real electronic holder without treating it as universally interchangeable, electrically safe, mechanically compatible, or ready to use with every minibadge.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The current record remains source-backed and image-free rather than copying Shopify product photos, repository images, KiCad previews, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying the maker listing image, rendered revision imagery, Reddit media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying Reddit media, repository graphics, code screenshots, social posts, thumbnails, placeholders, or generated approximations.
missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying the repository photo, README graphic, Reddit media, schematic preview, event graphics, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository PNGs/previews, schematics, screenshots, placeholders, or generated imagery.
missing rights-cleared image · local project policy · needs licensed original replacement
The source-backed record remains image-free rather than copying storefront/gallery media, raw GitHub images, launch-video frames, social posts, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The pre-event record remains source-backed and image-free instead of copying marketplace imagery, screenshots, social-media media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States pre-event record remains source-backed and image-free rather than copying shop imagery, GitHub media, social posts, screenshots, placeholders, or generated approximations.
missing rights-cleared image · public source and repository media review · needs selected, attributable, cleared original
The record remains image-free rather than copying repository media, code screenshots, event graphics, social posts, renders, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The pre-event record remains source-backed and image-free instead of copying marketplace photos, thumbnails, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository WebP/PNG/SVG assets, KiCad/schematic renders, acrylic previews, screenshots, placeholders, or generated imagery.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying project photos, CircuitPython board artwork, embedded video, form images, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace art, product media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying product art, project renders, prototype photos, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying the maker listing image, prototype/renders, Reddit media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying roster media, GitHub user-attachment images, Gerber previews, screenshots, social-media posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The pre-event record remains source-backed and image-free instead of copying storefront media, screenshots, social-media posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The planned 2026 record remains source-backed and image-free rather than copying village media, roster-linked social material, screenshots, placeholders, or generated imagery.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying maker renders/photos, game screenshots, marketplace images, social-media media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying the maker listing image, prototype/renders, Reddit media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy and maker license declaration · needs selected, attributable, cleared original
The planned record remains source-backed and image-free rather than copying repository photos, README media, renders, screenshots, third-party posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying Shopify product photos, PCB/back images, gong/Aaron media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace photographs, promotional graphics, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying Reddit media, previews, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The pre-event record remains source-backed and image-free rather than copying marketplace artwork, externally hosted README media, CAD screenshots, user attachments, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying listing photographs, repository images, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace photos, GitHub/Bluesky media, social previews, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The 2026 record remains source-backed and image-free rather than copying store photos, repository previews, self-submission media, screenshots, placeholders, or generated imagery.
missing rights-cleared image · local project policy · needs licensed original replacement
The record remains image-free rather than copying source-labelled generated product art, social media, storefront screenshots, party graphics, placeholders, or synthetic approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The current record remains source-backed and image-free rather than copying Shopify product photos, repository images, KiCad previews, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace photos, video frames, social previews, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying Reddit photos, previews, screenshots, social-media media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying Reddit media, previews, screenshots, social posts, thumbnails, placeholders, or generated approximations.
missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace photos, repository previews, contest media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The current fundraiser and its technical lineage remain source-backed and image-free instead of copying event-listing photos, documentation screenshots, repository media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry stays image-free rather than copying official news/support graphics, ticket media, media-server diagrams, social-media or press previews, repository screenshots, or generated badge art.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying Shopify photos/video frames, the Reddit preview, social-media material, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The planned record remains source-backed and image-free rather than copying marketplace photos, repository media, video frames, social previews, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace photos, video previews, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying the checkout photo, Reddit media, screenshots, social posts, thumbnails, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The planned record remains source-backed and image-free rather than copying Reddit previews, roster-linked media, screenshots, placeholders, or generated imagery.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying repository previews, GitHub user-attachment images, screenshots, social-media media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The source-backed pre-event record remains image-free instead of copying repository previews, board exports, screenshot-like documentation material, Portal-themed art, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying storefront photos, Reddit media, GitHub PNG/PDF material, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository previews, KiCad/schematic renders, spacer-model previews, screenshots, placeholders, or generated imagery.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The current record remains source-backed and image-free rather than copying Shopify product photos, roster-linked media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The pre-event record remains source-backed and image-free instead of copying storefront media, social posts, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying marketplace product media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The pre-event record remains source-backed and image-free instead of copying Eventbrite media, screenshots, social-media photos, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs selected, attributable, cleared original
The current record remains source-backed and image-free rather than copying Shopify product photos, roster-linked media, screenshots, social posts, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
no-MCU, QR/external-service, design-source, and support boundary · live maker listing and current public-source review · no-code and QR-search claims published; technical/service terms unrecovered
The catalogue records the stated no-MCU and QR-search feature without inventing firmware, treating the QR as an audited or privacy-neutral service, claiming an open design, or promising product support.
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.
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.
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.
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.
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.
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.
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.
planned badge, price, stock, and on-site fulfillment boundary · public self-submission and current event timing · pre-event $80 on-site sale statement; outcome unconfirmed
The record preserves a concrete pre-event acquisition statement without treating it as a finished distribution, retail outcome, or attendee entitlement.
planned drop, manufacture, distribution, and event-fulfillment boundary · first-hand project posts · drops and event experience announced, not outcome-confirmed
The catalogue records a real planned artifact system without representing it as manufactured, acquired, delivered, stocked, or experienced by a confirmed attendee population.
planned run, donation, allocation, and fulfillment boundary · maker and organizer source wording · 40-unit plan and may-receive process published; outcomes unconfirmed
The catalogue records the announced limited-run and philanthropic path without treating it as a completed sale, charitable outcome, manufactured quantity, or delivery report.
planned v2, price, preorder, and fulfillment boundary · public maker roster and first-hand maker thread · Coming soon and $20 wording published; outcome unconfirmed
The catalogue records a concrete pre-event maker announcement without presenting it as a completed DEF CON sale, a guaranteed preorder, or an attendee entitlement.
planning, prototype, manufacture, and final-unit boundary · commit-pinned README, hardware tree, and dated project-status document · design source published; prototype and production evidence unrecovered
Public design files are preserved as evidence of a planned artifact without being presented as proof of a fabricated, functioning, final, distributed, or event-deployed badge.
post-event allocation and production boundary · official wrap-up, badge sale notice, and post-conference support page · event completed; aggregate allocation and manufacturing record unrecovered
The catalogue can treat the official electronic Human badge as completed without implying that every registration produced the same physical unit, that every holder received or retained one, or that a public source proves a complete manufacturing and fulfillment record.
power, motion, LED, factory-test, and electrical-safety boundary · public README and project documentation · behavior and target components documented; safety/test outcome unverified
Public firmware behavior is not a battery-runtime guarantee, electrical-safety endorsement, factory-pass record, motion-accuracy claim, or safe-modification instruction.
power, thermal, electrical, and host-safety documentation gap · maker-documented design but incomplete validation material · needs final engineering and test evidence
The record does not convert a component/design narrative into a safety endorsement, universal host-power guarantee, electrical specification, or modification instruction.
pre-event DEF CON 34 pickup and sales-state boundary · primary maker storefront source · awaiting DEF CON 34 outcome
The catalogue records a source-backed sold-out pre-event offer without changing sales counters into a completed fulfillment report.
pre-event activation and delivery boundary · official product page · awaiting DEF CON 34 outcome
The catalogue records announced game and logistics context, not a completed physical run, completed server activation, delivered firmware, or observed attendee experience.
pre-event allocation, availability, and credential boundary · official FirstBuild repository, DEF CON event source, and first-person public announcement · 100-free-badge daily giveaway announced; event outcome unverified
The catalogue records the specific public 100-badge pre-event plan while treating the artifact as a distinct FirstBuild / GE Appliances project associated with DEF CON 34, not an official Human badge, universal attendee entitlement, registration credential, organizer-issued artifact, confirmed event availability, or completed distribution.
pre-event availability, distribution, and credential boundary · maker announcement and official event context · maker-stated limited plans; fulfillment unconfirmed
Station 562 is modelled as an independent pre-event BadgeLife project associated with DEF CON 34, not an organizer-issued Human badge, admission item, universal attendee benefit, or confirmed on-floor distribution.
pre-event availability, distribution, and fulfillment boundary · maker repository source only · public technical project documented; distribution outcome unreported
The catalogue records a real public project without portraying it as a completed physical distribution, a universally available SAO, a confirmed sale/giveaway, or a completed DEF CON handoff.
pre-event availability, shipment, pickup, and fulfillment boundary · maker product listing and current event timing · seller terms published; outcome not recovered
Readers can distinguish an active maker listing and planned timeframes from a completed DEF CON distribution or a finished production report.
pre-event drop, production, and fulfillment boundary · first-party product and first-hand maker announcement · listing is sold out; event/drop outcome unconfirmed
The catalogue preserves a real current offer without claiming a completed DEF CON distribution or fulfilled collector population.
pre-event drop, production, remediation, and fulfillment boundary · first-party product and first-hand maker announcement · listing is sold out; event/drop outcome unconfirmed
The catalogue preserves current offer and remediation language without converting it into a completed DEF CON distribution report.
pre-event drop, production, revision, and fulfillment boundary · first-party product and first-hand maker announcement · listing is sold out; v1.1 and event outcome unconfirmed
The catalogue retains current offer and remedy language without claiming completed distribution or a finalized production run.
pre-event giveaway, allocation, and fulfillment boundary · first-person maker post · small-batch non-sale giveaway announced; outcome unverified
The entry records a planned independent distribution model without presenting an announced free giveaway as manufactured stock, a confirmed recipient benefit, a completed DEF CON handoff, or a public fulfillment ledger.
pre-event manufacture, acquisition, and DEF CON association boundary · maker-owned public repository · planned source project; event outcome unconfirmed
The catalogue records a real, explicitly DC34-associated public design without upgrading it into an official badge, a conference credential, a completed physical distribution, or a sale/fulfillment claim.
pre-event manufacture, allocation, pickup, and fulfillment boundary · live maker page and public source trail · limited presale/prices published; event outcome undocumented
The catalogue preserves a live maker offer and active DC34 design trail without turning either into evidence of units built, distributed, sold, collected, or received.
pre-event pickup and fulfillment boundary · primary storefront source · awaiting DEF CON 34 outcome
The catalogue records a documented pre-event marketplace run without converting sales-state evidence into a delivery report.
pre-event pickup and fulfillment boundary · primary organizer event listing · awaiting DEF CON 34 outcome
The catalogue preserves the announced distribution plan without converting it into a completed delivery or event report.
pre-event pickup, refund, and fundraiser-outcome boundary · primary organizer listing · scheduled current fundraiser
The catalogue records BTV's current terms and 501(c)(3) purpose without converting them into proof of fulfilled orders, completed donations, or a finished event.
pre-event pickup, stock, and fulfillment boundary · first-party marketplace source · pickup-only terms and tentative times published; outcome unconfirmed
The catalogue preserves a current pre-event offer without presenting it as a completed DEF CON distribution.
pre-event presale, pickup, and fulfillment boundary · primary maker listing · active presale marketplace snapshot
The catalogue records current seller-published marketplace terms without converting them into proof of completed manufacture, purchase, delivery, meetup attendance, or convention-wide distribution.
pre-event price, stock, and fulfillment boundary · maker page, public self-submission, and current event timing · limited presale and $20 claim published; outcome not recovered
Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.
pre-event price, stock, and fulfillment boundary · maker page, public self-submission, and current event timing · limited presale and $20 claim published; outcome not recovered
Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.
pre-event price, stock, and fulfillment boundary · maker page, public self-submission, and current event timing · limited presale and $20 claim published; outcome not recovered
Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.
pre-event price, stock, pickup, and fulfillment boundary · live first-party product page · observed $45 sold out; DEF CON pickup condition published
The catalogue preserves an observed marketplace state and intended pickup path without presenting it as a completed limited run or delivery report.
pre-event price, stock, pickup, and fulfillment boundary · live first-party product page · observed $45 sold out; DEF CON pickup condition published
The catalogue preserves an observed marketplace state and intended pickup path without presenting it as a completed limited run or delivery report.
pre-event price, stock, pickup, and fulfillment boundary · live first-party product page · observed $12 available; conditional pickup published
The catalogue preserves a current marketplace snapshot and intended pickup path without presenting either as completed production or delivery.
pre-event price, stock, pickup, and fulfillment boundary · live first-party product page · observed $12 available; conditional pickup published
The catalogue preserves a current marketplace snapshot and intended pickup path without presenting either as completed production or delivery.
pre-event production, availability, and fulfillment boundary · primary maker storefront · stated limited run; current variant unavailable
The catalogue records the maker's limited-run and currently-unavailable state without translating it into a sold-out claim or a fulfillment report.
pre-event quantity, drop, allocation, and fulfillment boundary · maker self-submission · 500-unit giveaway announced; outcome unconfirmed
The catalogue preserves the planned free giveaway without treating it as a completed run, confirmed attendee entitlement, universal handout, or delivered artifact.
pre-event quantity, village transfer, drop, allocation, and fulfillment boundary · maker self-submission · 1,000-unit giveaway announced; outcome unconfirmed
The catalogue records an announced free distribution rather than a completed, universally accessible, organizer-provided, or delivered artifact.
pre-event sale, drop, manufacture, and fulfillment boundary · first-party marketplace source · availability and drop labels published; outcome unconfirmed
The catalogue preserves a dated seller snapshot without converting it into a completed DEF CON or Hacker Summer Camp distribution report.
pre-event sale, manufacture, handout, and fulfillment boundary · first-party product, repository, and diary · sale and DEFCON34 handout intent published; outcome unconfirmed
The catalogue preserves a current, well-documented planned artifact without presenting it as a shipped or universally received conference item.
pre-event sale, pickup, mail, refund, and fulfillment boundary · first-party marketplace source · availability and pickup terms published; outcome unconfirmed
The catalogue preserves public offer terms without implying that all orders or drops were successfully fulfilled.
pre-event sale, pickup, shipping, and fulfillment boundary · first-party marketplace source · availability and acquisition terms published; outcome unconfirmed
The catalogue preserves a dated seller snapshot without treating it as a completed event or mail fulfillment report.
pre-event sale, pickup, stock, and fulfillment boundary · first-party marketplace source · availability and pickup terms published; outcome unconfirmed
The catalogue preserves a dated seller snapshot without representing it as a completed event handoff.
pre-event sale, stock, fulfillment, and party-outcome boundary · primary current listing · out of stock; outcome undocumented
A live/pre-event commerce snapshot is not presented as proof that badges were delivered, an access promise was honored, or the party/challenge happened as announced.
pre-event sales, pickup, and closing-ceremony donation boundary · primary maker listing · sold-out pre-event marketplace snapshot
The catalogue records the seller's current marketplace state and stated policy without converting them into evidence of completed fulfillment or an event-wide distribution result.
pre-event sales, price, allocation, and fulfillment boundary · maker self-submission and live seller listing · approximately $35 DEF CON channel announced; $30 marketplace state observed; outcome unconfirmed
The catalogue preserves both published price contexts without treating either as a completed transaction, guaranteed inventory, final price, DEF CON entitlement, or delivery outcome.
pre-event sales, price, allocation, and fulfillment boundary · maker self-submission · approximately $125 channel announced; outcome unconfirmed
The catalogue records an announced acquisition path rather than a completed sale, guaranteed stock, organizer-provided benefit, or delivered item.
pre-sale capacity, availability, and pickup fulfillment boundary · primary maker marketplace payload and maker technical archive · 125-total pre-sale; current 125-sold/zero-remaining snapshot
The catalogue records both the observable availability snapshot and the maker-published production-file claim without translating either into a sold-and-delivered production report.
pre-sale, pickup, shipping, and fulfillment boundary · primary live maker marketplace payload · 100-total pre-sale; observed 41-sold snapshot
The catalogue retains the seller's current acquisition terms without presenting them as a completed run, confirmed onsite sale, guaranteed shipping/pickup, or verified charitable transfer.
pre-sale, pickup, winner-copy, and fulfillment boundary · primary marketplace payload and repository · 150-total pre-sale; observed 28-sold snapshot
The catalogue preserves announced independent acquisition paths without converting a live counter or contest promise into a confirmed completed distribution.
preorder fulfillment, allocation, and DEF CON credential boundary · official programme site, current sold-out listing, and past-dated pickup schedules · sold-out preorder and planned September shipping published; delivery outcome unrecovered
The catalogue retains the current sold-out preorder and stated fulfillment window without calling it a shipped badge, a completed recipient allocation, a DEF CON Human badge, or a DEF CON admission credential.
preorder, extras, pickup, and fulfillment boundary · primary maker storefront and corroborating first-person post · preorders stated sold out; possible extras mentioned
The catalogue records a live sold-out and pickup-oriented source state without turning it into a confirmed fulfilled run or a guaranteed opportunity to acquire an extra.
proceeds, beneficiary, and accounting boundary · primary maker product statement · stated excess-proceeds intention only
The catalogue preserves the public maker intention without presenting it as a completed charitable transfer, family endorsement, financial audit, tax determination, or quantified benefit.
prototype, component, power, and final-revision gap · first-hand project diary and repository · ongoing project; final unit not established
Readers can see substantive development evidence without mistaking a working or revised prototype trail for a finished, safety-qualified production specification.
radio monitoring, false-positive, privacy, and regulatory boundary · current listing and reviewed source code · feature family documented with operational limits unknown
The dossier does not characterize the badge as a reliable detector, a complete Flipper identifier, a private/passive tool in every context, a regulatory-approved radio, or operational guidance for monitoring nearby people/devices.
radio, BLE privacy, and regulatory-use boundary · maker product and technical documentation · requires operator, regional, and event-context assessment
The catalogue does not expose individual credentials or turn maker radio/network statements into legal, privacy, security, compliance, or operational advice.
release, installed-firmware, and production-parity gap · public release surface and distribution guide · tagged release required by project guide; none public when reviewed
The catalogue does not treat repository main as a released production image, a firmware actually installed on badges, a reproducible event build, or a completed compliance archive.
revision, production, power, audio, and firmware-parity boundary · versioned maker hardware and firmware documentation · physical boards reported assembled; final design, validation, and per-unit state unrecovered
The record preserves the documented hardware/software trail without treating it as a complete electrical specification, safety assessment, support promise, security claim, universal compatibility result, or unit-by-unit production record.
sensor, hardware, power, and electrical-safety documentation gap · current maker description is high-level only · various-sensors wording documented; implementation unreported
The record avoids inventing a sensor suite, electronic design, power path, safety state, accessibility behavior, or data-collection capability from the badge name or historical product association.
shipping and fulfillment boundary · primary maker storefront source · needs delivery confirmation
The catalogue preserves the seller-stated schedule and scope without converting it into confirmed pre-event or attendee delivery.
software, artwork, third-party, media, and trademark license boundary · root MIT license, README credit, and project documentation · software/documentation license published; other rights kept separate
The catalogue can cite the software/documentation licensing trail while retaining image, artwork, logo, trademark, and dependency-specific rights boundaries.
soldering, 18650, USB-C, and hardware-safety specification boundary · official BadgeLife guide · parts and safety reminders documented; engineering validation unrecovered
The source-linked record retains the documented physical work without becoming a battery, soldering, USB, SAO, electrical, or repair endorsement.
source archive, binary, and software-release scope · MIT source archive · substantial earlier archive; current release scope undocumented
The catalogue links the preservation source without misrepresenting it as a complete, current, supported, reproducible 2026 field-update package or a full release of every historic CTF component.
source attribution, pre-event availability, and fulfillment boundary · single public post and official event-context source · announced offer; account relationship and outcome unverified
The catalogue records the concrete pre-event offer while leaving attribution, seller relationship, availability, sale, fulfillment, and event outcome explicitly unresolved.
source publication, physical unit, and fulfilment boundary · publisher-controlled repository · public project source; physical and distribution outcome unverified
The catalogue preserves a real source-documented electronic-badge project without presenting it as a delivered product, attendee issue, or verified physical run.
source-declared collaboration, event association, and credential boundary · maker repository, commit-pinned README, and official event calendar · maker-labelled DEF CON project; organizer and external collaboration confirmation unrecovered
The catalogue retains the named maker project and its source-declared collaboration without promoting it into a DEF CON-issued Human badge, a ticket benefit, an admission item, a confirmed sponsor deliverable, an externally verified iFixit product announcement, or a completed attendee handoff.
source-labelled generated product-media boundary · official storefront media filenames · not publishable under catalogue image policy
The catalogue preserves the product evidence and explains the image gap without treating generated marketing art as a picture of the actual badge or as an allowed public image asset.
source-to-2026-revision, production, and image-provenance boundary · maker announcement, project site, and repository release context · new-revision claim published; exact physical revision and cleared media unrecovered
The record remains image-free and source-conservative rather than treating open design files or promotional media as proof of exact 2026 unit parity or reusable catalogue artwork.
stock, replenishment, pickup, and fulfillment boundary · first-party storefront and maker announcement · sold out; future order and DEF CON pickup are stated as tentative
The catalogue preserves dated seller and maker intent without representing the item as available, delivered, or confirmed for DEF CON.
story, organization, authorship, and endorsement boundary · maker story and manufacturing wording only · creative and contributor context recorded; relationships unsubstantiated
The dossier preserves source-named narrative and manufacturing context without assigning ownership, cultural/institutional relationship, approval, sponsorship, final manufacturing responsibility, or image rights beyond the published statements.
target revision, interface, compatibility, and authorization boundary · maker purpose statement and pre-event timing · built against initial public information; final compatibility unknown
Readers should not treat the public source as a compatibility guarantee, a target-specific exploit claim, an endorsement to connect the SAO, or authorization to interact with another attendee's hardware.
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
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.
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 catalogue credits named sources without republishing lore artwork, product media, or project images on an assumed license basis.
third-party standalone SAO power companion boundary · first-party maker storefront · pre-event marketplace listing
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.
touch, audio, LED, content, and accessibility boundary · maker wording and public implementation source · intended interaction evidenced; final experience and accessibility unverified
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.
unlicensed source, fabrication, and media reuse boundary · GitLab project metadata and source review · no detected project license
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.
unnamed source, firmware, license, and publishing boundary · repository metadata, root-tree, and one-commit review · repository description and initial source files only; documentation/release/license unrecovered
The entry uses a handle-qualified index title and links the raw source while avoiding invented technical behavior, a formal release, a legal reuse grant, or a stronger creator claim than the evidence supports.
unofficial DEF CON affiliation and credential boundary · primary official maker wording · independent DEF CON 34 badge
The catalogue classifies Clip-Boy as an independent BadgeLife artifact associated with DEF CON 34 rather than an official conference credential or admission substitute.
update lineage and prior-edition boundary · public roster update label and v2 repository name · current update evidenced; prior lineage not reconstructed
The record preserves the visible update/v2 trail without inventing a previous event, assigning an exact earlier version, merging unknown revisions, or treating the seller card as standalone proof of historical IFLFU distribution.
v1/v2, form-factor, and Saintcon-lineage boundary · separate product titles and roster wording · separate v2 listing documented; technical distinction and historical link unreported
The catalogue keeps v2 distinct because its own listing is distinct while avoiding an invented hardware revision, size, Saintcon history, or universal compatibility claim.
v1/v2, form-factor, and Saintcon-lineage boundary · separate product titles and roster wording · separate v1 listing documented; technical distinction and historical link unreported
The catalogue keeps v1 distinct because its own listing is distinct while avoiding an invented hardware revision, size, Saintcon history, or universal compatibility claim.
village fundraiser and DEF CON credential boundary · primary organizer listing · documented independent village offering
The catalogue classifies it as a source-backed Blue Team Village fundraiser artifact rather than a substitute for conference registration or the official DEF CON badge.
wireless, NFC, and lawful-use boundary · source-named Wi-Fi, Bluetooth, and NFC surface · no operational or compliance guidance identified
Readers can identify the announced wireless/NFC surface without treating the record as a sanctioned operational guide, a privacy guarantee, a compliance claim, or permission to use the badge against systems or media they do not own or control.
wireless-security capability, legal, and authorized-use boundary · official seller disclaimer · high-level feature claims only
The catalogue does not provide guidance for active testing, characterize any security feature as safe or legal everywhere, or turn a seller disclaimer into a compliance determination.
