Not just specs

Issues & Camp Impact

Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.

Reset
2204 matching issue record(s)

event-date archive inconsistency · primary organizer-hosted archive · needs dated archive recovery

The current OzSec 2025 archive contains October 23-24 wording in its headline and FAQ but October 10-11 wording in its schedule, indicating that the retained page mixes date fragments. This record therefore associates the badge archive with OzSec 2025 and the Hyatt Regency Wichita venue without asserting an exact event date.

The record avoids turning a stale or mixed archive page into an incorrect precise date claim and leaves the date open for a dated official programme, ticket, or post-event report.

Source note: OzSec 2025 event archive.

event-date, sale, and fulfillment boundary · official event-date offer plus public source release · event dates elapsed; fulfillment unverified

The official offer said the badge was limited, available only to ticket holders as a separate purchase, and deliverable only during the conference dates. The public archive and pre-event v1.0 release establish a source trail but not payment, stock, production, recipient allocation, pickup, delivery, refund, support, or post-event badge handoff.

The catalogue records a real advertised 2026 artifact and a source release without representing either as a universal attendee entitlement, confirmed sale, completed delivery, or completed event program.

Source note: DOJOConf Panamá official event page, Electronic Cats public post, and badge-dojocon-2026 v1.0 release.

event-service lifecycle caveat · archived official guide · post-event service state not preserved

The archived guide documents internet-connected ESP-NOW base stations and an online scoreboard, but the public source trail does not provide a durable service-status commitment, full score export, base-station implementation archive, or post-event operation guarantee.

The record treats the score and synchronization system as documented event-time behavior, not a permanently available badge service.

Source note: DEF CON Singapore Official Badge Laser* Tag archive.

event-unit hardware and firmware parity gap · attributed event device identification plus manufacturer baseline · generic Blinky 2350 platform documented; event configuration unrecovered

The app documentation identifies a Pimoroni Blinky 2350 and badgeware runtime, while Pimoroni documents generic retail-platform features. Reviewed sources do not confirm the exact event-unit revision, board configuration, radio setup, battery, case, lanyard, artwork, serialisation, customisation, firmware image or version, installed apps, firmware license, source release, production run, or hardware-design authorship.

Manufacturer facts are labelled platform baseline only, and no retail configuration is presented as a universal or event-specific Workday build.

Source note: Mainak Sarkar's devcon-badge-pet README and Pimoroni Blinky 2350 product documentation.

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 public roster supplies an explicit phrase and describes randomized illumination of two words; the maker page characterizes an unlabeled card as romantic and raunchy. No reviewed source identifies the artwork/message author, rights holder, intended audience, content rating, venue suitability, recipient consent, permission for the phrase/artwork, or authorization, affiliation, or endorsement from DEF CON or another person/organization.

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.

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

external antenna caveat · primary FAQ · documented

The FAQ warns external-antenna installation can disturb a tiny AC-coupling capacitor, explains the capacitor protects downstream RF parts from DC and low-frequency high-power signals, and says the external antenna must be selected in settings.

The catalogue records the optional antenna path while preserving the modification risk and RF-protection context.

Source note: AV Badge FAQ external antenna section.

external media caveat · source-backed but rights-limited · documented

Public YouTube, Flickr, WIRED, Hackaday, Forbes, MAKE, CNET, and NetworkWorld references exist for the badge and hacks, but they are used only as pointers unless their reuse rights and exact badge-image provenance can be reconciled.

The catalogue avoids importing media from social/gallery/press surfaces while preserving source links for future review.

Source note: Grand Idea Studio documentation links and DEF CON 17 official contest-results media list.

fabrication and handoff gap · organizer archive but future event · needs post-event fabrication and distribution evidence

The September 22, 2026 organizer repository publishes the full Alice Controller design, firmware, production packages, and challenge, but the November 11, 2026 event has not happened yet, so fabrication, attendee handout, and final challenge outcomes remain unproven.

The record keeps the published design archive while avoiding shipped-hardware, allocation, or outcome claims until the event passes.

Source note: BSidesTLV 2026 Hardware Village page and the bsidestlv-2026-badge organizer repository.

fast-flash photosensitivity and optical-safety boundary · maker describes a wide flash-rate trimmer · no reviewed optical-safety guidance identified

The listing says the trimmer can move the LEDs from a slow pulse to a very fast strobe-like rate, but gives no defined frequency range, brightness/current values, user warning, photosensitivity guidance, accessibility option, test data, or optical-safety evidence.

The catalogue records the stated visual control without presenting fast flashing as safe, suitable for every viewer, or a substitute for appropriate user caution.

Source note: SAO HackThePlanet product page.

fast-flash photosensitivity and optical-safety boundary · maker describes fast visual patterns · no reviewed optical-safety guidance identified

The listing says the effects include fast flashing patterns but does not define frequency, brightness/current, duty cycle, a user warning, photosensitivity guidance, accessibility option, or optical-safety test evidence.

The catalogue records the stated visual effects without presenting them as safe or suitable for every viewer.

Source note: #NOICE SAO product page.

field-report scope caveat · official docs plus secondary field report · needs schematic-level review

The Hackaday report is useful for attendee-facing behavior and lore, but detailed component claims should still be checked against the official Badge.Team hardware repositories and schematics.

The dossier can use the report for mesh gameplay and relay-interface lore while keeping low-level hardware claims anchored to primary sources.

Source note: Hackaday field report and Badge.Team HackerHotel 2024 docs.

field-writeup scope caveat · first-hand writeup · documented

The 2025 Conference badge and Soldering village writeups document practical reverse engineering and challenge solving from an attendee perspective, but they are not a complete official challenge archive or manufacturing release.

The catalogue uses them to enrich firmware and challenge behavior while keeping authoritative hardware-source claims tied to the official NorthSec repository.

Source note: NorthSec competition write-up index and Jean Privat's 2025 badge writeups.

final component, standards, firmware-release, and support scope · public repository documentation · needs final release confirmation

The README's overview and feature list use different LED labels, while the repository does not identify a tagged production firmware, flashed-unit hash, final BOM/revision, standards conformance report, host test matrix, support path, update/recovery process, or distributed-unit configuration.

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.

Source note: `keeloi79/not-a-crosswalk-sao` README, source tree, and licensing declaration.

final configuration and firmware lifecycle boundary · public build and firmware documentation · design and baseline firmware public; event-specific final state unpublished

The sources document a baseline ESP32-S3-Zero/eight-LED configuration and WLED v0.15.5-aligned binaries, but do not establish each workshop unit's exact component source, board revision, solder quality, power source, flashed binary, Wi-Fi/client configuration, customization, firmware update history, security review, or post-event maintenance path.

Readers can reproduce the documented public design without mistaking one source configuration for a verified event-wide production, security, or support state.

Source note: Hackropole hardware, assembly, and WLED documentation.

final delivery and distribution gap · organizer-linked repository and historical event archive · event record and design archive not reconciled

The current repository describes the badge as work in progress and says it will be built, while the event archive identifies OzSec 2025. The reviewed public sources do not confirm a final manufacturing run, ticket or attendee allocation, pickup, shipment, firmware deployed at the event, or individual receipt.

The catalogue preserves the real design/archive trail without treating a planning repository as proof of a final issued conference badge.

Source note: OzSec 2025 event archive and OzSecICT badge-crashandburn README.

final hardware and software release boundary · official pre-event badge update and repository review · limited planned revision surface public; final unit and release unrecovered

Public sources identify an RP2350, three-AAA plan, and a multi-application software ambition, but do not identify the final board revision, display, controls, connectors, dimensions, schematic, BOM, manufacturing package, component substitutions, electrical limits, tests, final firmware image, application inventory, release tag, source license, deployment record, support policy, or recovery process.

The record preserves the published V2 direction without presenting it as a finished specification, operating guide, safe configuration, or final hardware/software release.

Source note: Software You Can Love 2026 official updates, Matthew Knight organizer post, and ZigEmbeddedGroup/sycl-badge repository review.

final hardware population caveat · official hardware and module documentation · source design detailed; attendee population unresolved

The source tree documents a display socket, dual side ports, optional CC1101 and sound modules, multiple module populations, and shared GPIO constraints. It does not establish the display, radio/audio/storage module, power source, battery, antenna, enclosure, lanyard, exact board revision, assembly quality, or physical configuration that each issued attendee device actually carried.

The record distinguishes open design capability from a claimed uniform production configuration or a complete inventory of event-issued variants.

Source note: OnionDAO Badge README, Hardware Overview, and Swappable Modules documentation.

final hardware, companion, power, and electrical-safety gap · public repository review · design outline and source files public; production/safety result unrecovered

The repository names an ATtiny402, button, CR2032 clip, and 5050 NeoPixel for the badge and preserves separately named companion source/model material, but reviewed sources do not establish final component substitutions, battery brand/capacity, power budget, electrical limits, production revision, chest count, companion configuration, field placement, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves source-backed badge and companion context without treating public project material as a fabrication, repair, deployment, electrical-safety, or universal final-unit specification.

Source note: punk-security/bsides-exeter-2025-badge README, EAGLE source, Gerber archives, and companion material.

final hardware, manufacturing, and electrical-safety gap · KiCad source, BOM, and production-file snapshot · production-ready design documented; final board unconfirmed

The reviewed files now publish Gerbers, a drill set, a production BOM, and a CPL file, but they still do not document a placed order, received boards, assembly, powered test, measured current budget, battery life, thermal or fault behavior, cell inclusion, compliance result, or a final populated revision.

Readers can inspect a manufacturing-ready source design without treating it as a completed, safe, validated, or reproducible attendee device.

Source note: hardware/bsidesorl-v1.kicad_sch, hardware/bsidesorl-v1.kicad_pcb, and hardware/jlcpcb/ production files.

final hardware, power, and electrical-safety gap · inherited technical documentation · board context public; final 2026 configuration unconfirmed

The V4 document describes a capable ESP32/LiPo platform and includes a warning about operation without a battery, but no reviewed 2026 source establishes the final PCB revision, component population, displays, battery inclusion or chemistry, wiring, mechanical assembly, firmware/power interaction, current draw, charging behavior, thermal result, test record, compliance, or safe field configuration for the ticketed e-badge.

Readers can inspect inherited technical context without treating it as a safety validation, complete specification, compatibility guarantee, or reproducible final device.

Source note: BSidesFW2026Badge Hardware Specifications V4 and public 2026 repository tree.

final hardware, power, and electrical-safety gap · firmware README and repository-tree review · partial hardware summary public; production device unconfirmed

The public source names controller, radio, LEDs, shift register, and USB roles, but it does not publish a native schematic, PCB layout, BOM, fabrication file, board dimensions, enclosure, button/connector map, antenna design, battery/power architecture, charge/protection circuit, electrical limits, thermal result, production test, compliance result, or final populated-board revision.

The catalogue preserves the narrow source-backed hardware outline without representing it as a complete build specification, safety assessment, compatibility guarantee, or fabrication recipe.

Source note: Eagle 5 README, repository tree, and initial-release commit.

final hardware, power, and electrical-safety gap · public source archive review · native source visible; production/safety evidence unrecovered

The public KiCad archive and team posts name a controller and FPGA, but reviewed sources do not establish a reconciled manufactured BOM, component substitutions, exact power/battery architecture, charge/protection behavior, electrical limits, thermal result, assembly/test plan, compliance result, enclosure, connector map, or final populated-board condition for physical summit units.

The catalogue preserves the source-backed design trail without calling it a fabrication recipe, tested device specification, safety assessment, or compatibility guarantee.

Source note: SemiTO-V repository tree, KiCad sources, README, and primary team posts.

final hardware, power, and electrical-safety gap · README and KiCad archive review · component outline and source tree visible; production/safety record unrecovered

The archive identifies selected components, inputs, battery-holder footprint, headers, and native KiCad files, but reviewed sources do not establish a reconciled delivered BOM, component substitutions, battery chemistry/capacity, protection/charging behavior, electrical limits, current draw, thermal result, assembly quality, test plan, compliance result, final assembled configuration, or safe SAO/power compatibility.

The record preserves the documented design and component outline without calling it a fabrication recipe, safety assessment, universal compatibility result, or final production specification.

Source note: Open Sauce 2026 Badge README and native KiCad source tree.

final hardware, power, and electrical-safety gap · public repository review · design outline and source files public; production and safety result unrecovered

The repository names an ATtiny402, button, CR2032 clip, NeoPixel, and 3528 blue LED and preserves board/design material, but reviewed sources do not establish final component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline without treating public project material as a fabrication, repair, electrical-safety, or universal final-unit specification.

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

final hardware, power, and electrical-safety gap · public repository review · design outline and source files public; production/safety result unrecovered

The repository names an ATtiny412, button, CR2032 clip, and 5050 NeoPixel and preserves board/design material, but the reviewed sources do not establish final component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline without treating public project material as a fabrication, repair, electrical-safety, or universal final-unit specification.

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

final hardware, power, and electrical-safety gap · public repository review · design outline and source files public; production/safety result unrecovered

The repository names an ATtiny412, button, CR2032 clip, 5050 NeoPixel, and LIS2MDLTR magnetometer and preserves board/design material, but reviewed sources do not establish final component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline without treating public project material as a fabrication, repair, electrical-safety, or universal final-unit specification.

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

final hardware, power, and electrical-safety gap · public repository review · design outline and source files public; production/safety result unrecovered

The repository names an ATtiny1614, buttons, two CR2032 clips, 5050 NeoPixel, trimmer, capacitor, transistor, and infrared LEDs and preserves board/design material, but reviewed sources do not establish final component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline without treating public project material as a fabrication, repair, electrical-safety, or universal final-unit specification.

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

final hardware, power, case, and electrical-safety gap · public repository review · design outline and source files public; production and safety result unrecovered

The repository names an ATtiny402, button, CR2032 clip, and 5050 NeoPixel and preserves board/design/case material, but reviewed sources do not establish final component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, production revision, case-fit outcome, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline without treating public project material as a fabrication, repair, case-fit, electrical-safety, or universal final-unit specification.

Source note: punk-security/bsides-cheltenham-2024-badge README, EAGLE source, Gerber archive, and case material.

final hardware, power, radio, and physical-unit boundary · Retia immutable README and KiCad source tree · high-level design and fabrication source public; final unit/manufacturing evidence unrecovered

The source documents a hardware design and preserves KiCad/fabrication files, but it does not establish a final board revision, component substitutions, display or radio population, antenna configuration, battery brand/capacity, power-path limits, runtime, charging behavior, power safety, radio compliance, electrical test results, manufacture, quality control, or a physical-unit inventory.

Source-backed component and interface references remain a bounded design trail rather than a universal physical-badge specification, safety certification, performance claim, manufacturing record, or operating guidance.

Source note: Retia DEF CON Badge (2024) README, KiCad source, schematic PDF, and fabrication-output tree.

final hardware, power, safety, firmware-release, and support boundary · maker README and public source tree · high-level hardware and build path published; final-unit validation unrecovered

The maker documents an RP2040, LED matrix, USB-C, motion/ambient-light inputs, buttons, touch, Pico SDK build context, and a UF2 upload path, but the reviewed public material does not establish a complete BOM, PCB revision or production package, battery or power design, charger/protection behavior, current/thermal measurements, mechanical specification, electrical/EMC/compliance testing, signed/versioned release, release-to-unit mapping, rollback/recovery package, security review, warranty, or support lifecycle.

The archive remains useful for provenance and study without becoming a universal assembly, modification, update, electrical-safety, or support recommendation.

Source note: Cobalt DC34 Badge README and current public repository tree, reviewed 2026-09-07.

final hardware, power, sensing, and electrical-safety gap · public repository review · design outline and source files public; production, sensing, and safety result unrecovered

The repository names an ATtiny402, button, CR2032 clip, 5050 NeoPixel, and 6.8 kΩ resistor and preserves board/design material, but the reviewed sources do not establish final component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, sensing-circuit calibration, measurement accuracy, environmental range, manufacturing test plan, assembly quality, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline and soil-sensor description without treating public project material as a fabrication, repair, measurement, electrical-safety, or universal final-unit specification.

Source note: punk-security/bsides-newcastle-2024-badge README, EAGLE source, EasyEDA project, and Gerber archive.

final hardware, schematic, manufacturing, and configuration gap · public README and schematic source · current production target and schematic published; final build not confirmed

The README names a current production target and the repository publishes a schematic PDF, while retaining a different KB2040 prototype profile. Reviewed sources do not provide a final hardware revision, native CAD project, complete BOM, PCB/fabrication package, sourced component list, enclosure, battery/power design, board measurement, production record, factory result, per-unit configuration, or confirmation that the named target was built.

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.

Source note: FirstBuild DefCon34-Badge README, schematic PDF, and repository tree.

final revision and engineering archive gap · official product description · maker says final version may vary

The maker says final versions may have minor variations while expecting the main components to remain. No reviewed source publishes a final board/SAO revision, schematic, PCB/Gerbers, BOM, component identifiers, dimensions, materials, assembly guide, test report, certification, or manufacturing evidence.

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.

Source note: Zach's Hacks product page and public product payload.

final-hardware archive gap · source-backed but incomplete · needs post-event technical source

Ticketing proves a cool badge and the prospectus proves electronic badge design/build was available as a supporter item, but this pass did not recover final schematics, board files, firmware, BOM, or component-level documentation.

The record does not claim processor, display, radio, CTF, battery, or shipped electronic features beyond the public sources.

Source note: BSides Brisbane 2025 Humanitix page and 2025 sponsorship prospectus.

finicky Arduino-clone caveat · badge text quoted in field writeup · historical

The quoted badge text says the board is loaded with an Arduino Leonardo bootloader and can be treated as an Arduino clone, but warns that getting everything to work and fit can be finicky.

The compendium records this as a practical attendee caveat rather than an unresolved defect: the badge was intentionally open and modifiable, but not frictionless.

Source note: Zeta-Two field writeup quoting the challenge badge text.

firmware TODO caveat · primary README · work in progress

The README says the documentation and firmware were work-in-progress and lists missing or incomplete areas including SD-card FAT32 packet capture/replay files, button-controlled GUI, protocol state machines, Modbus Rx, MCP2518FD drivers, I2C/SPI pass-through, and better docs.

The record documents intended and exposed firmware surfaces without implying that every listed protocol or feature was complete during DEF CON 33.

Source note: Differential Destroyer README firmware TODO section.

firmware absence caveat · source-backed but intentionally narrow · documented

The recovered sources describe a soldered RGB blinky badge, transparent PCB design, and coin-cell power, but do not document a programmable MCU, firmware, serial shell, repository, or CTF behavior for the AVTOKYO 2019 badge.

The dossier keeps the artifact as a beginner soldering-village blinky badge instead of inventing software behavior.

Source note: Hackster.io blinky-badge writeup and AVTOKYO 2019 event page.

firmware and app release boundary · official documentation and MIT firmware repository · partly documented / post-event source pass

The public firmware and App Store paths establish a programmable platform, but they do not prove the final attendee firmware image, final pre-installed app set, App Store inventory or availability during camp, final game payloads, or post-event support. The firmware README also documents a manual headset-output configuration choice.

The catalogue records the released software architecture and recovery workflow without converting a public repository into claims about final attendee experience.

Source note: Fri3d Camp 2026 badge documentation and badge_firmware_MicroPythonOS README.