Hacker Con Badges

Not just specs

Issues & Camp Impact

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

Reset
2204 matching issue record(s)
Div0 Tingkat eBadge (DEF CON Singapore 2026) note

firmware and challenge-safety boundary · commit-pinned README and firmware source · firmware variants documented; production mapping and safe challenge instructions withheld

The README distinguishes older and newer firmware behavior, while the source includes serial-menu, LED/OLED, and challenge modules. The public archive does not supply a tagged production release, signed binary provenance, source-to-unit mapping, complete intended challenge deployment, support policy, or confirmation that each physical artifact used the same firmware. The catalogue deliberately does not republish flashing, serial-access, flag, or challenge-solving procedures from the archive.

The entry retains a useful public firmware trail without turning it into operating instructions, a security challenge walkthrough, a guarantee of USB behavior, or proof of a final event configuration.

Source note: Div0 Tingkak eBadge commit-pinned README and firmware source.

Onion DAO 2026 Hardware Badge note

firmware and licence scope caveat · official repository documentation · public source tree; final event firmware and per-mod licence scope unverified

The repository documents source folders, guides, ESP-IDF v5.5.x tooling, hardware sources under CERN-OHL-S v2 unless a file header says otherwise, and software that defaults to MIT with individual mods allowed to override. Its reviewed public page had no tagged releases, and the sources do not identify a final event firmware image, provisioning state, attendee update path, security review, or a blanket reuse licence for every source, mod, binary, image, and build artifact.

Readers can follow the open source trail while the catalogue avoids treating a default licence statement or development guide as final firmware provenance, a universal binary licence, or a deployment guarantee.

Source note: OnionDAO Badge README, repository release surface, and ESP-IDF guide.

AvengerCon IX Electronic Badge note

firmware and schematic gap · official badge guide with limited hardware depth · needs deeper archive recovery

The official badge page documents CTF behavior, CP2102 serial access, BAT CON battery handling, 9600-baud workflow, unlock codes, and safety instructions, but this pass did not recover firmware source, schematic files, BOM, Gerbers, challenge binaries, or a complete hardware archive.

The catalogue keeps the strong official badge-guide evidence while avoiding unsupported claims about the unrecovered design files or shipped firmware internals.

Source note: AvengerCon IX Electronic Badge guide and linked hints page.

IEEE Rising Stars 2026 Conference Badge Project note

firmware and technical archive gap · official project page · schematic/BOM links visible; organizer-linked code publication remains incomplete

The official page links a schematic PDF and BOM but leaves design description and code publication as TODO items, while only noting that CircuitPython was used for a prototype. A separately published SEAL-Embedded development archive is retained in this record, but it is not linked from the organizer page or assigned to the 2026 prototypes. No organizer-linked, event-unit-matched firmware release, binary, flashing process, software license, full component inventory, board revision, power specification, manufacturing package, test plan, or errata archive was recovered.

The dossier distinguishes an accessible development-source trail from a complete reproducible event-unit release.

Source note: IEEE Rising Stars 2026 Badge Project page and SEAL-Embedded immutable repository snapshots.

Security Fest 2026 RP2040 Badge note

firmware archive and production-parity gap · public repository review · needs hardware archive

The public source tree and README provide firmware and interface facts but no recovered schematic, PCB design, BOM, battery specification, final board revision, factory-test record, or complete production archive.

Hardware detail remains source-bounded, and the catalogue does not claim that every shipped board matched the repository's documented configuration.

Source note: Security Fest 2026 Badge repository, README, and pinout reference.

Hackaday Berlin 2023 Voja4 Badge note

firmware archive boundary · current public source trail · needs deeper archive recovery

The recovered public sources describe the architecture and lineage, but this pass did not recover a Berlin-specific final firmware, schematic, BOM, or Gerber archive.

Software and hardware claims stay limited to Hackaday's compatibility statement, the v0j4 architecture notes, and the original Supercon badge context.

Source note: Hackaday Berlin preview, v0j4 details, and 2022 Supercon badge article.

Hackaday Europe 2025 SAO Badge note

firmware archive boundary · current public source trail · needs deeper archive recovery

The public Hackaday sources announce revamped Europe firmware but this pass did not recover a versioned final Hackaday Europe 2025 firmware release distinct from the upstream Supercon 8 repository trail.

Software claims stay limited to the announced revamped firmware, MicroPython lineage, SAO-port flashing statement, and upstream public repository workflow.

Source note: Hackaday Europe 2025 ticket preview and Hack-a-Day/2024-Supercon-8-Add-On-Badge repository.

GigaGeiger Badge (DEF CON 33) note

firmware behavior, OTA security, release, and design-license scope boundary · public repository and implementation source · MIT repository and source sketch published; release/security scope incomplete

The repository root declares MIT and contains source and build outputs, but the reviewed material does not establish signed firmware, checksums, release notes, binary-to-device mapping, reproducible builds, credential-management policy, secure transport, authentication, rollback/recovery, vulnerability process, support policy, or final production firmware. The current sketch's packet callback increments totals only; its displayed Deauths count is not populated by deauthentication parsing in the reviewed code. PCBWay's CC BY-SA page is separately attributed and does not determine the license of every repository file, storefront claim, or product image.

The catalogue links public code and fabrication material without claiming a secure updater, complete deauthentication detector, supported release, final feature set, universal license scope, or permission to republish every artifact image.

Source note: Penzz-HM GigaGeiger repository, GG_OTA_061025.ino, and GigaGeiger PCBWay project.

Portal Badge (DEF CON 34) note

firmware binary, compatibility, and update-scope boundary · public source and commit history · no tagged release identified

The latest public firmware commit is titled “final code checks,” but the reviewed project provides no tagged release, signed/final binary, flash procedure, source revision declaration for event units, test/CI result, media-image provisioning method, rollback/recovery plan, hardware-variant compatibility matrix, or support lifecycle.

Source-level game and interface behavior remains discoverable without labeling the branch as a final, universally flashable, supported event firmware package.

Source note: `ch32fun-portal-badge` PlatformIO configuration, source tree, and commit history.

FrogStar Badge (DEF CON 33) note

firmware binary, source, license, and recovery gap · maker page links a UF2 binary · binary linked; development and release context unpublished

The project page links a Firmware v1.0 UF2 and gives a copy-to-flash instruction, but no reviewed source provides code, repository, license, changelog, checksums, signing, build toolchain, supported host procedure, bootloader instructions, hardware configuration, rollback, recovery, update policy, or security review.

Readers can locate the declared binary release without assuming it is open source, reproducible, authenticated, safe to flash on every variant, or supportable after failure.

Source note: BigTaro FrogStar 2025 project page and linked FrogStarFirmware1.0.uf2.

Ekoparty 2024 Official Badge note

firmware configuration caveat · primary repository snapshot · documented

The current public Badge Link module snapshot calls the DragonJAR Badge Connect type while the Ekoparty setter is visible but commented, so the catalogue does not claim the final deployed badge-type constant without a release artifact.

The record can document Badge Connect behavior and cross-event lineage while keeping firmware-configuration claims conservative.

Source note: badge-EKOParty-2024 firmware Badge Link and Badge Connect sources.

BSides Fort Wayne 2026 Optional E-Badge note

firmware deployment and release gap · public repository and GitHub metadata · source visible; final deployed image unrecovered

The current repository exposes MicroPython source, apps, custom-firmware documentation, and June revisions, but has no GitHub tag or release. No reviewed source maps a versioned binary or source commit to a physically delivered 2026 e-badge, provides post-event recovery/support scope, or records CTF deployment and results.

The record treats the code as a valuable public archive without asserting a final official firmware release, production flash state, challenge outcome, or supported owner-update path.

Source note: BSidesFW2026Badge repository tree, firmware README, source commit history, and empty tag/release endpoints.

Hackers Teaching Hackers 2026 Eagle 5 Badge note

firmware license and photo-provenance boundary · repository README and root-license review · GPLv3 firmware source recorded; image provenance incomplete

The README declares GPLv3 for the firmware and the root contains GNU GPLv3 text, but the embedded Eagle 5 photo does not identify a photographer, an image-specific attribution requirement, or complete processing provenance. This pass does not assume that a firmware license alone resolves all facts needed to republish a selected documentary image.

GPLv3 source information is recorded for research, while any local photo asset remains blocked until its individual source, reuse basis, attribution, and processing record are complete.

Source note: Eagle 5 README, repository LICENSE, and badge.gallery image policy.

C1B3RTR4CKS 2026 CH32V003 Badge note

firmware release and challenge boundary · public source-tree review · source available but release parity unknown

The organizer-linked repository exposes source and user documentation, but no tagged event release, signed image, installation ledger, or complete post-event challenge archive was recovered. The catalogue intentionally withholds operational use instructions and any claim about exact source-to-unit parity.

Public code remains an important preservation resource without being presented as a verified reproduction image or complete challenge solution set.

Source note: SEIF-UAM C1B3RTR4CKS 2026 badge repository and commit metadata.

RISC-V Summit Europe 2026 FPGA Badge note

firmware release and deployed-build gap · README and repository-state review · public references visible; event build unrecovered

The README links firmware-related repositories and team posts name custom firmware plus a default RV32I core, but the project repository has no tag or GitHub release and reviewed sources do not map a versioned build to physical summit boards, provide a final binary, define a support owner, or establish a recovery/update lifecycle.

The record describes public firmware context at a high level without presenting any current source checkout as deployed, supported, verified, or suitable for operation.

Source note: RISC-V FPGA Badge README, repository metadata, and SemiTO-V Developer Zone post.

Open Sauce 2026 Badge note

firmware release and deployed-build gap · public source and independent attendee archive · source/context public; canonical deployed build unrecovered

The designer repository contains Bop It firmware and examples, and a separate attendee repository contains a replacement firmware project, but neither reviewed source tags a final production release, maps a versioned build to a particular event badge, defines a support owner, or publishes a complete recovery/update lifecycle. The attendee project is intentionally not treated as the organizer's or designer's canonical event firmware.

The catalogue reports the valuable source and community-hacking trail without calling any checkout a final, authenticated, supported, or universally deployed badge image.

Source note: calebmarting Bop It source and README; putnam custom-firmware README; repository tag/release review.

Hackers Teaching Hackers 2026 Eagle 5 Badge note

firmware release and deployed-image gap · GitHub repository state · post-event initial source release visible; final device state unrecovered

The public repository has a single July 15 initial-release commit and no GitHub tag or release. It exposes firmware source and documentation, but reviewed sources do not map a versioned build to actual event units, establish a final signed/validated production image, state CTF deployment/results, or define an owner recovery/support lifecycle.

The dossier treats it as valuable code evidence without claiming the current checkout is the final deployed badge firmware or a supported update/recovery path.

Source note: Eagle 5 repository metadata, commit history, README, and tag/release endpoints.

Shitty Kitty V2 (DEF CON 34) note

firmware release and licensing gap · primary maker storefront and profile sources · awaiting announced firmware release

The product says new firmware with graphics and puzzles will be released and describes SkittyOS features, but it links no source repository, binary, versioned release, flashing workflow, build instructions, puzzle material, protocol documentation, or software/hardware/documentation license.

The record can describe the maker's announced feature surface without claiming a released, reproducible, inspectable, or reusable firmware archive.

Source note: Uberflux Shitty Kitty V2 product listing and lipo maker profile.

BSides Cheltenham 2023 Delorean Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and public development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating or reconfiguration procedure. No flashing, configuration, connection, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification or operation workflow.

Source note: bsides-cheltenham-2023-badge repository and firmware sketch.

BSides Cheltenham 2024 UFO Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and public development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating or reconfiguration procedure. No flashing, configuration, connection, activity, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification or operation workflow.

Source note: bsides-cheltenham-2024-badge repository and firmware sketch.

BSides Newcastle 2024 Plant Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and public development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user sensing, operating, or reconfiguration procedure. No flashing, configuration, connection, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification or operation workflow.

Source note: bsides-newcastle-2024-badge repository and firmware sketch.

BSides Newcastle 2025 Space Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and external development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating or reconfiguration procedure. No flashing or configuration directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification workflow.

Source note: bsides-newcastle-2025-badge repository and firmware sketch.

CyberNorth CyberFest 2025 Compass Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and external development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating, calibration, or reconfiguration procedure. No flashing, configuration, or connection directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification workflow.

Source note: cyberfest-2025-badge repository and firmware sketch.

CSIDES 2025 Crab Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and code-lineage references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, authorized-use policy, or safe end-user operating or reconfiguration procedure. No payload, connection, flashing, configuration, target-selection, or modification directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, authorized, or safe modification workflow.

Source note: csides-2025-badge repository and firmware sketch.

BSides Bournemouth 2025 Skull Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The source tree includes a firmware sketch and external development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating or reconfiguration procedure. No flashing, configuration, connection, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification workflow.

Source note: bsides-bournemouth-2025-badge repository and firmware sketch.

BSides Exeter 2025 Pirate Ship Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketches published; final deployment/support record unrecovered

The source tree includes separate badge and companion firmware sketches and external development references, but reviewed sources do not establish tagged final releases, signed binaries, source-to-unit mapping, build lockfiles, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating, connection, docking, or reconfiguration procedure. No code, flashing, configuration, connection, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification or deployment workflow.

Source note: bsides-exeter-2025-badge repository and badge/companion firmware sketches.

MNSEC 2025 Electronic Badge Collection note

firmware release and operational-configuration boundary · public firmware directory and README · binary, sketch, and examples available; final deployment record unrecovered

The repository provides a firmware binary, a named sketch, and examples, but it does not document a signed or reconciled final release, source-to-unit mapping, dependency lockfile, update/support policy, final connectivity configuration, service availability, data practice, or privacy policy. No credentials or operational configuration details are reproduced in this record.

Public source material remains linkable without claiming a reproducible, supported, secure, current, or uniform operational setup for delivered badges.

Source note: MNSEC2025BADGE firmware directory and README.

OzSec 2025 CRASHANDBURN Badge note

firmware release and validation gap · primary source repository · prototype source visible; production release unrecovered

The repository includes current MicroPython source and ESP32-S3/Pico 2 target files, but the README describes breadboard development and work in progress. No tagged final firmware, reproducible production build, test result, challenge outcome, or evidence that this source ran on conference units was recovered.

The game and flashing material remains valuable development evidence, but not a claim about production behavior or a supported owner-update path.

Source note: OzSecICT badge-crashandburn README, firmware directory, and main source.

DC-34 Countdown to Singularity Badge note

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 README describes an Arduino firmware directory and an initial AVR bootloader path, while the reviewed repository exposes no explicit root license, release/tag, final binary, version-to-board mapping, build/dependency lock, verified programmer/fuse package, update/recovery image, security review, vulnerability policy, support channel, warranty, or cleared badge artwork/photo. The board-art area is not treated as image-reuse permission.

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.

Source note: eggsactly/DC-34-Countdown-To-Singularity repository, README, and public trees.

MidWestCoast Badge (DEF CON 34) note

firmware release, code license, network, and data boundary · public source snapshot and MVP note · current source exists; release, deployment, and operational terms unverified

The project publishes source and describes it as current implementation, but the reviewed snapshot does not establish a tagged final release, compiled attendee image, device-specific configuration, reproducible build result, flashing/recovery path, dependency inventory, source license, security review, operational deployment, account/data handling, privacy notice, retention policy, update policy, or support commitment.

The catalogue links public project material without treating source visibility as a completed firmware release, security guarantee, network/data practice, or reusable code grant.

Source note: MidWestCoastBadge repository snapshot and MVP note.

Darknet-NG SMAO (DEF CON 34) note

firmware release, configuration, and licensing boundary · commit-pinned maker firmware and license documentation · versioned maker release published; delivered-unit state unverified

The repository supplies a versioned UF2, build notes, configuration delta, provisioning tools, tests, and MIT license text for its original hardware/documentation/tools while identifying the included Meshtastic firmware image as GPL-3.0-derived. It does not establish that every offered or collected unit has that exact image/PIN/configuration, provide an independent build audit, guarantee future upstream compatibility, or provide a post-event support, rollback, or recovery commitment.

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.

Source note: dcbokonon/darknet-smao v1.4 firmware BUILD.md, repository tree, and top-level LICENSE.

Celestial Wayfinder Badge (DEF CON 34) note

firmware release, dependency, and update-scope boundary · MIT repository and v4.0.0 release · public source and partial binary coverage

The MIT application repository depends on a side-by-side local `esp32-utilities` checkout, and its README's stated version-config value differs from the later public v4.0.0 release. That release publishes v3 and v2 binaries only. The reviewed sources do not establish a final shipped firmware hash, v1 v4 binary, rollback/recovery process, production provisioning, upgrade support guarantee, or compatibility of release assets with every offered unit.

The catalogue can link the MIT source and named binaries without treating them as a universal, final, supported field-update package.

Source note: Celestial-Wayfinder README and v4.0.0 GitHub release.

The Beer SAO / BCCC Temperature Badge (DEF CON 34) note

firmware release, deployed-revision, and support boundary · repository and license · public source exists; delivered-unit scope unverified

The repository documents source, a `thermometer-v1.1.0.uf2` file, and manufacturing tools under WTFPL v2, but does not provide a signed/hash-verified marketplace release, exact build provenance for every event unit, dependency-license audit, release/support policy, changelog-to-hardware mapping, security review, recovery guarantee, or field-test result. Its note that firmware was developed with Claude is source provenance, not an independent quality or authorship assessment.

The record links the public workflow without representing it as a final reproducible, supported, audited, or universally deployed firmware release.

Source note: BCCC Temperature SAO repository and LICENSE.

BSides Vancouver 2025 Electronic Badge note

firmware release, deployment, and support gap · first-party bundle and public source archive · binary and later source visible; canonical deployed release unrecovered

The official repository contains binary programming material, while the public archive has no GitHub release and calls v2.4.0 its first public refactored firmware release. Reviewed sources do not publish a versioned production release, secure update/recovery policy, official support owner, firmware signature status, or direct mapping between a physical 2025 unit and a source revision.

The catalogue links valuable source and binary evidence without asserting a current, authenticated, supported, or universally deployed firmware image.

Source note: bsidesvancouver/Bsides2025badge; maltchev releases page, README, commit history, and CHANGELOG.md.

OWASP SAO (DEF CON 34) note

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 repository exposes a README, `main.ino`, and a front-image asset, but no root license file or GitHub-detected repository license was recovered. The reviewed source does not establish a tag or release, binary, complete toolchain/configuration, reproducible build, source-to-unit mapping, signed update, safe UPDI workflow, recovery package, security review, privacy statement, support policy, warranty, or final installed effect set.

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.

Source note: DC34-OWASP-SAO repository metadata, root contents, commit-pinned README, and main.ino.

Pwnterrey 2026 Official ESP32-C5 Badge note

firmware release, production parity, and source-history gap · public companion firmware repository · needs provenance and release confirmation

The companion repository contains ESP32-C5 headless Marauder-derived source, documentation, and build material and calls itself official Pwnterrey firmware, but this pass did not establish a reviewed final release tag, signed binary, reproducible event build, contribution history for every change, full dependency inventory, or parity with any distributed badge.

The catalogue records public software provenance without representing a visible build artifact as the final event firmware, an audited release, a complete source history, or an authorized deployment.

Source note: ElectronicCats/pwnterrey-2026_Firmware repository and ESP32-C5 guide.

MalO SAO (DEF CON 34) note

firmware release, toolchain, dependencies, and software-license gap · repository and diary describe evolving work · implementation materials exist; final user release not identified

The sources discuss a compiled C library, Arduino IDE material, an evolving Python/C++ split, graphics/file-system/sensor work, games, puzzles, and USB-C modification, but do not provide a tagged final firmware release, stable installation guide, complete build environment, dependency inventory, update/recovery path, release integrity, formal test result, final game content, or a separate software license. The repository's CC BY-SA statement is not treated as a resolved license for every code dependency.

The dossier links the public work without presenting it as a finished end-user firmware or support package.

Source note: MalO_SAO repository and MalO SAO developer diary.

NilbinSec DC34 Main Badge Fuzzer SAO note

firmware release, update, support, and licence gap · public source-tree review · source and compiled artifacts visible; explicit release/licence/support terms absent

The repository exposes C source plus tracked hex/ELF files and describes a possible convention reflash, but the reviewed root has no explicit LICENSE/COPYING file, release/tag, checksum, version-to-board mapping, fuse map, programmer package, update image, recovery path, dependency lock, security review, vulnerability policy, support policy, or warranty. The README's build outline does not itself grant reuse rights or establish a supported update path.

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.

Source note: NilbinSec repository root, README, Firmware/Makefile, and tracked firmware artifacts.

ROOTCON 20 Electronic Badge note

firmware source and licence gap · official media-server listing and local binary inspection · binary-only release

ROOTCON published only the compiled rc20-human-fw.bin image, built from a dirty 5b987d4 tree, with no source repository, licence, flashing guide, schematic, PCB, or BOM. Meshtastic itself is GPL-3.0 licensed, but no corresponding source for this build has been located.

Hardware and feature claims are limited to what the ESP32-S3 image header and embedded strings declare, and the record does not describe the board layout or unpublished variants.

Source note: ROOTCON media server ROOTCON 20/Badge listing and rc20-human-fw.bin, checked 2026-09-30.

ICS Village DEF CON 34 Badge note

firmware source and licensing gap · official specification page · needs public archive or terms

The page names Porpoise Purpose Firmware, OneWili, and supported client languages but does not link firmware source, binaries, flashing instructions, protocol documentation, API reference, or a software license.

The catalogue does not claim a released firmware archive, update path, reproducible build, API implementation details, or redistribution rights.

Source note: FREE-WILi ICS Village DEF CON 34 Badge page.

Hackaday Supercon 2025 Communicator Badge note

firmware timing caveat · primary-source backed · documented

The reveal article said software was still being worked on while badges were being produced, with final behavior expected to settle at the event.

The record treats the repository and firmware documentation as living event artifacts rather than claiming a frozen pre-event production firmware state.

Source note: Hackaday Communicator Badge reveal and 2025 Communicator Badge firmware repository.

Hackaday Europe 2026 Communicator Badge note

firmware variant caveat · current public source trail · needs deeper archive recovery

The public sources describe Europe use, MicroPython apps, LoRa experimentation, and Meshtastic reflash framing, but this pass did not recover a distinct Lecco-specific firmware release archive.

Software claims stay tied to the public Europe articles and upstream Communicator Badge firmware repository rather than a separate Europe firmware tag.

Source note: Hackaday Europe 2026 CFP article and 2025 Communicator Badge firmware README.

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

firmware, CTF, game, and source-license gap · programmable/CTF/game wording · features named; implementation and release context unpublished

The sources call the combo fully programmable and name CTF, bling modes, laser tag, TV control, and Drinking Roulette, but no reviewed source provides firmware, binary, code, repository, license, build/flash instructions, configuration, game rules, solution/reset path, scoring, data handling, update policy, or security testing.

Readers can understand the advertised feature set without assuming it is open source, reproducible, supported, safe, or available in every unit/configuration.

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

RTV D20 Badge (DEF CON 34) note

firmware, CTF, gameplay, source, and licensing gap · no artifact-level technical source recovered · no implementation or interaction documentation located

No reviewed source says RTV D20 has firmware, software, a repository, binary, website, CTF challenge, game mechanic, D20 interaction, workshop use, update/recovery path, source code, license, security review, user-data behavior, or accessibility information. The Village's broader CTF/program descriptions are not attributed to this badge.

Readers are not led to assume that the D20 name denotes an electronic game, an access pass, a CTF device, or any documented implementation.

Source note: Red Team Village event page and DEFCON 34 Badgelife Form response.