Hacker Con Badges

Not just specs

Issues & Camp Impact

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

Reset
2209 matching issue record(s)
BSides Brisbane 2025 Cool Badge note

prospectus-to-shipped caveat · mixed ticketing and prospectus evidence · documented caveat

The sponsorship pack describes electronic badge design/build for 500 delegates, but the ticketing page only says cool badge and does not confirm final electronic hardware details.

The catalogue treats the electronic-badge wording as planning/prospectus evidence unless a final organizer post, repository, or attendee technical writeup is recovered.

Source note: BSides Brisbane 2025 Humanitix ticketing and 2025 BNE prospectus PDF.

MalO SAO (DEF CON 34) note

prototype, component, power, and final-revision gap · first-hand project diary and repository · ongoing project; final unit not established

The diary documents prototype r1 testing, a discovered IMU power-pin error/high-draw investigation, screen mechanical interference, and expected changes; the repository describes later processor revisions and broad component plans. No reviewed source proves the exact final PCB/population, LED count, assembly quality, power profile, thermal behavior, sensor calibration, durability, production test result, or compliance record for sold units.

Readers can see substantive development evidence without mistaking a working or revised prototype trail for a finished, safety-qualified production specification.

Source note: MalO SAO developer diary and MalO_SAO repository.

LayerOne 2017 CAN Bus Badge note

prototype-to-final caveat · badge-team logs · documented with caution

The public Hackaday.io material is a development log with prototype revisions and feature planning, while the official HHV page establishes the year as an electronic badge without publishing a final production source package.

The catalogue records the source-backed architecture and car-hacking direction while avoiding unsupported claims about every final shipped component, firmware image, or quantity.

Source note: LayerOne HHV archive, Hackaday.io project details, and project logs.

LayerOne 2015 Dual Electronic Badges note

prototype-to-production caveat · badge-team logs · documented with caution

The public Hackaday.io material mixes prototypes, late board changes, USB mirroring, level-shifter selection, build pressure, and final assembly notes rather than a single audited final production package.

The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, firmware image, quantity, or attendee role.

Source note: LayerOne 2015 Badge details and Building badges log.

LayerOne 2016 Conference Badge note

prototype-to-production caveat · badge-team logs · documented with caution

The public Hackaday.io material is a late build diary with PCB bring-up, component substitutions, Wi-Fi power debugging, hand-built early units, and pick-and-place preparation rather than a complete final manufacturing package.

The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, production quantity, or assembled variant.

Source note: LayerOne 2016 Conference Badge project and May 2016 project logs.

Carolina Code Conference 2026 Circuit Board Badge note

public technical reference and final-unit parity boundary · commit-pinned partner source archive · technical reference public; production parity unaudited

The public README identifies an ESP32-S3-WROOM-1-N8, ST7735S LCD, WS2812 LEDs, three buttons, Micro-USB, GPIO pads, and CR123A/USB power, but it does not provide schematics, PCB layout, BOM, fabrication package, assembly/test records, component substitutions, manufacturing quantity, compliance evidence, or an independent inspection of distributed units.

The entry is a traceable public platform reference, not a reproducible manufacturing record, safety assessment, interoperability guarantee, or proof that every event unit matched the README.

Source note: Circuit Board Medics commit-pinned Carolina Code Conference 2026 Badge README.

THOTCON 0xD Badge note

public-demo firmware boundary · source-backed but scoped · documented

The public repository is a cleaned-up demo firmware collection with examples and removed event-specific/proprietary material, while the Hackaday.io project describes a richer original badge firmware with menus, audio games, visual effects, timers, hidden screens, and challenge hooks.

The software description separates the recovered demo archive from the full shipped event firmware so the record does not overstate public source completeness.

Source note: Hackaday.io THOTCON 0xD project and `thotcon-examples` README.

Payment Village DEF CON 34 Volunteer Village Badge note

published commitment-schedule wording discrepancy · two official Payment Village pages · source wording preserved; commitment schedule unresolved

The volunteer page asks volunteers to commit to all three days while naming a Friday August 6 through Sunday August 9 span, whereas the official event page says Payment Village will be on site all four days from August 6 to 9. The public pages do not explain whether this is wording drift, day-count shorthand, a shift requirement, or a substantive volunteer-schedule distinction.

The catalogue retains the exact published uncertainty instead of deriving a final volunteer commitment from inconsistent wording.

Source note: Payment Village DEF CON 34 volunteer notice and official event programme.

BTV Camera Badge (DEF CON 34 Fundraiser) note

radio monitoring, false-positive, privacy, and regulatory boundary · current listing and reviewed source code · feature family documented with operational limits unknown

The listing describes display cues for deauthentication activity and nearby Flipper Zeros. The older source uses Wi-Fi promiscuous filtering/channel hopping and BLE prefix matching, but the sources do not establish a final 2026 scan configuration, detection accuracy, false-positive/false-negative rate, nearby-device identity proof, RF performance, user notice/consent model, data retention behavior, venue policy, certification, or jurisdiction-wide legality.

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.

Source note: BTV Eventbrite fundraiser listing and `camera_badge_rev01` source review.

Hackers Teaching Hackers 2026 Eagle 5 Badge note

radio scope, lawful-use, and field-operation boundary · source-backed capability but incomplete operational record · technical context documented; field use unverified

The source identifies an SX1262 and RNode/Reticulum-oriented firmware context but does not establish radio band/region configuration, antenna characteristics, authorization, venue coordination, permitted use conditions, actual over-the-air deployment, range, interference testing, privacy handling, or safety outcome at HTH 2026.

The catalogue records high-level communications capability only and deliberately omits operating instructions, frequency/configuration guidance, challenge tactics, and claims about lawful or safe field operation.

Source note: Eagle 5 README, CHANGES.md, and HTH 2026 source-review boundary.

Darknet-NG SMAO (DEF CON 34) note

radio, BLE privacy, and regulatory-use boundary · maker product and technical documentation · requires operator, regional, and event-context assessment

The sources describe US 915 MHz LoRa, BLE companion-app pairing, a unique per-unit BLE PIN, source-published RF sweeps, and a low-transmit configuration. They do not provide radio-compliance evidence, region-specific operating/support terms, mesh-service or data-handling terms, privacy/security review, PIN recovery policy, threat model, event radio policy, or a claim that mesh traffic is private.

The catalogue does not expose individual credentials or turn maker radio/network statements into legal, privacy, security, compliance, or operational advice.

Source note: Darknet-NG SMAO Uberflux product page/payload and dcbokonon/darknet-smao v1.4 documentation.

Onion DAO 2026 Hardware Badge note

radio, expansion, and secure-element use caveat · official module and hardware documentation · capabilities documented; operational use remains user-specific

The optional CC1101 design names region-dependent Sub-GHz bands and the module guide gives scanning and ASK/OOK replay as examples only with authorization. The secure element and exposed side-port GPIO make the hardware capable of identity and external-hardware experiments, but the reviewed sources do not establish frequency legality, authorization, emissions compliance, antenna safety, third-party-module electrical compatibility, credentials/provisioning, privacy controls, or appropriate use for a particular user or venue.

The record documents the available hardware surfaces without endorsing RF transmission, replay, credential use, or unreviewed expansion hardware.

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

Unknown Security Conference 2026 Pwn Llama Badge note

radio, power, and data-use boundary · primary public documentation · needs independent operational assessment

The source documents BLE behavior, USB-C and battery/LiPo power options, and persistent device state, but it is not an electrical-safety certification, privacy notice, radio compliance record, or independent security assessment.

The catalogue records the documented capabilities without making safety, privacy, security, or regulatory claims.

Source note: ElectronicCats Badge-UnknownSecurity-Conference-2026 README.

BSides Vancouver 2025 Electronic Badge note

recipient allocation and delivery gap · official archive and first-party bundle · artifact and programming bundle documented; allocation outcome unrecovered

The organizer page calls the item an electronic badge and supplies programming materials, but reviewed sources do not establish ticket inclusion, optional price, production quantity, recipient count, check-in handoff, workshop enrollment, inventory, replacement terms, shipment, or a completed delivery ledger.

The catalogue records a real 2025 electronic badge without asserting that every ticket holder received one or that a particular source bundle was flashed onto every physical unit.

Source note: BSides Vancouver 2025 badge programming page and bsidesvancouver/Bsides2025badge repository.

Robotic Hacking Community DEF CON 34 AI-Connected Badge note

recipient allocation and fulfillment boundary · primary official sources · post-event source release; recipient outcome unrecovered

RHC scheduled on-site physical-badge pickup for DEF CON 34 and later published firmware, but reviewed sources do not establish recipient eligibility, a distribution count, unit serial allocation, individual pickup, final firmware parity for every issued badge, or CTF participation/results.

The dossier records a released badge platform without converting event and source-release evidence into a completed attendee-delivery ledger.

Source note: Robotic Hacking Community home, CTF, badge documentation, and firmware repository.

BSides Maine 2026 Electronic Lighthouse Badge note

recipient, variant, and credit scope gap · official event posts and organizer recap · main attendee and planned VIP variant named; detailed fulfillment and individual roles unpublished

The organizer announced a main attendee badge and a special VIP edition, while the agenda documents generic registration pickup. None of the reviewed sources supplies a delivery ledger, variant inventory, recipient count, special-edition handoff, individual builder roster, or role-specific design/manufacturing/firmware attribution. The lead organizer's post-event thanks to Ryan Boutot supports only an organizer-recognized electronic-badge contributor credit.

The catalogue keeps main-attendee, VIP, event-logistics, and contributor statements distinct instead of treating an advertised variant or a thank-you as universal allocation or sole authorship.

Source note: BSides Maine badge reveal, VIP announcement, 2026 agenda, and Ben Strout organizer recap.

BSides Athens 2024 Electronic Circuit Badge note

recovered-wrap-up availability · public search/archive recovery · monitor for stable mirror

The badge-specific claims are preserved in recovered official wrap-up text, but the direct BSides-hosted file endpoint may require archive recovery if the live fetch path changes.

Future maintainers should preserve a stable archive citation or replacement official mirror before adding richer details.

Source note: Security BSides Athens 2024 Recap / Wrap-Up public search and BSides community file path.

DCZia MK9 Badge (DEF CON 34) note

release and fulfillment boundary · public project source and during-event build guide · maker-documented release; production count and recipient ledger absent

The August 7 build guide addresses purchasers and says badges ship pre-flashed, and the August 4 UF2 commit describes the image as released on badges, so the release is maker-documented. The reviewed sources still provide no production count, recipient list, sale-channel or giveaway record, or completed distribution report, and the planned add-on board's distribution remains unconfirmed.

The catalogue records a maker-documented independent badge release, not a verified run size, universal attendee issue, or official DEF CON distribution.

Source note: DCZia MK9 project repository, August 4 and 7, 2026 commits, and public August 2 announcement, rechecked 2026-09-25.

BugCON 2025 Linux Badge note

release and source inventory · repository documentation · needs deeper artifact inventory

The README and releases document v1.0/v1.1 image tarballs, add-on firmware hex, BOM asset names, and the Luckfox SDK branch, but this pass did not audit every large release image, generated SDK artifact, dependency license, or manufacturing output.

Software and production claims stay tied to README, release names, public hardware trees, and the named SDK branch rather than treating the repository as a fully inventoried production archive.

Source note: ElectronicCats/badge-bugcon-2025 README, releases page, hardware trees, and SDK branch.

BSides Perth 2025 ESP32 TFT Badge note

release, allocation, and deployment boundary · event and archive timestamps · documented caveat

The public archive was created before the event but the reviewed final snapshot was pushed after it. The sources do not map that snapshot to an exact event-day firmware build, deployed virtual service, production quantity, ticket entitlement, recipient list, or uniform physical configuration.

The record preserves documented hardware and archive context without converting a public project tree into universal attendee distribution or a verified final release.

Source note: BSides Perth 2025 Humanitix listing and badges4dotcom/bsidesperth2025badge commit history/tree at 7a0f64862bcff660a81f9733475bb8ae91576f1e.

FirstBuild / GE Appliances Washer/Dryer Badge (DEF CON 34) note

release, installed-firmware, and production-parity gap · public release surface and distribution guide · tagged release required by project guide; none public when reviewed

The distribution guide says each physical-badge firmware batch should correspond to a permanent tagged GitHub release and archive. The visible FirstBuild release and tag surfaces had no public entry on this source pass, so no final firmware binary, source archive, hash, build-to-badge mapping, release note, or installed-firmware provenance was established.

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.

Source note: FirstBuild Open-Source Distribution Guide and GitHub releases/tag surfaces.

HITCON 2025 PCB Badge note

remaining hardware caveat · source-backed but intentionally narrow · BOM and production notes recovered; still needs shipped-count and image provenance

Recovered official sources now include the PCB Badge guide, public technical repository, production BOM, production notes, firmware, PCB files, base-station/backend/game/web/software trees, hardware revision notes, timer/DMA details, menu-flow notes, and BadUSB protocol notes, but this pass still does not assert a shipped count or rights-cleared badge image.

The dossier records the verified interaction, production, and technical-archive surface while avoiding unsupported production-scale and image-provenance claims.

Source note: HITCON 2025 PCB Badge guide, HITCON agenda page, john0312/hitcon-pcb-badge repository, JLCPCB BOM, and production notes.

Ekoparty 2024 Official Badge note

render scope caveat · manual image review · documented

The Ekoparty 2024 image is an official hardware-tree raster, not a documentary field photo of a populated physical badge.

The record still prefers a future licensed original documentary photo if one appears, but the current image is source-backed upstream material rather than generated, approximate, social-media, or placeholder art.

Source note: Manual review of ElectronicCats badge-EKOParty-2024 repository images and badge.gallery image policy.

h-c0n 2026 CTF BADge note

replay hardware boundary · repository documentation · documented

The repository says people replaying the CTF at home can flash a Raspberry Pi Pico 2, but boards different from the CTF PCB need an LED on GPIO 25 and one challenge may require a debug probe and cable.

The record distinguishes the conference CTF BADge from compatible at-home replay boards and preserves the hardware-debugging requirement without overstating universal compatibility.

Source note: therealdreg/hcon2026hwctf README.

NoNameCon 2019 NoNameBadge note

repository and image license caveat · GitLab metadata and repository pass · no visible reusable image basis

The public firmware project is useful evidence, but the GitLab project exposes no README URL in the project metadata and no top-level reusable image-license basis was recovered in this pass.

Repository files and article photos are cited as evidence only; no badge image is copied locally without explicit image rights, attribution, and processing provenance.

Source note: TechMaker NoNameBadge 2019 article, GitLab project metadata, and badge.gallery image policy.

NoNameCon 2020 Air Quality Badge note

repository and image license caveat · GitLab metadata and source pass · no visible reusable image basis

The public firmware project and TechMaker article are strong evidence, but no complete reusable image-license, attribution, source URL, and processing-provenance basis was recovered for publishing article photos or GitLab project imagery locally.

The record stays image-free until a rights-cleared original photo or official upstream raster render is recovered.

Source note: TechMaker NoNameBadge 2020 article, GitLab project metadata, and badge.gallery image policy.

NodeConf EU 2018 Badge note

repository archive status · GitHub repository metadata · documented

The `nearform/nceubadge2018` repository is archived and its GitHub metadata reports the homepage as `https://nodeconfeubadge.org/`, but that site currently presents an expired TLS certificate to curl.

Primary claims come from the repository and README rather than relying on the expired-certificate homepage for evidence or images.

Source note: GitHub repository metadata and local TLS check on nodeconfeubadge.org.

Gothcon 2026 Blinky Badge note

repository license and final-release boundary · public repository review · needs explicit license and release terms

The public repository contains source, KiCad, Gerber, and documentation material but the reviewed root has no explicit LICENSE file and no tagged final release was identified. Public visibility alone does not establish rights to reuse code, hardware, documents, embedded images, or final production firmware.

The catalogue can link the technical trail without representing it as licensed open hardware, free software, a released production artifact, or a valid source of reusable images.

Source note: claviger/gothcon-firmware repository root and hardware tree.

BSides Perth 2025 ESP32 TFT Badge note

repository license and image-reuse caveat · repository metadata and reviewed root tree · needs explicit reuse permission or license

The checked commit-pinned archive has no top-level license and GitHub reports no detected repository license. That leaves code, documentation, source imagery, and CAD/render reuse scope unresolved.

The catalogue may link to the public technical archive as evidence but does not publish its imagery, copy source files, or infer a reusable license from public availability.

Source note: badges4dotcom/bsidesperth2025badge archive at commit 7a0f64862bcff660a81f9733475bb8ae91576f1e and badge.gallery image policy.

BSides San Diego 2024 ESP32-C3 Badge note

repository license and reuse caveat · repository metadata and reviewed root tree · needs explicit reuse permission or license

The reviewed public badge tree has no detected repository license or top-level license file. That leaves reuse scope for code, documentation, CAD, and source imagery unresolved despite the archive's public availability.

The catalogue links to the technical archive as evidence but does not copy its source files or images or infer a reuse license from public access.

Source note: Somerset-Recon/bsides-badge-2024 commit-pinned archive at 74dfe2b79832817beb40c92fa1fe34609a8d132e and badge.gallery image policy.

GreyCTF Summit 2025 GreyBadge note

repository license caveat · GitHub API recheck · no detected license

GitHub reported `license: null` for NUSGreyhats/greybadge25 during this pass, and no visible top-level LICENSE file was used as a reuse basis.

Repository files are cited as public evidence, but local reuse is limited: no repository images, artwork, hardware files, firmware, or slides are copied into the catalogue as licensed assets.

Source note: NUSGreyhats/greybadge25 GitHub API metadata and repository tree recheck.

DEF CON Singapore 2026 HFSDR Badge note

repository license caveat · current repository audit · needs license clarification

A 2026-05-21 GitHub API and repository-contents recheck found `license: null` and still did not recover a LICENSE, LICENSE.md, or COPYING file in the public HFSDR repository.

The catalogue cites repository facts as public evidence but does not reuse repository images, hardware files, or code assets as licensed local content.

Source note: rhgndf/hfsdr GitHub API repository metadata and contents listing, rechecked 2026-05-21.

BSides Canberra 2023 bPod note

repository license caveat · repository audit · needs explicit project license

The bPod repository is public and contains exact hardware, firmware, updater, server, and manufacturing artifacts, but this pass did not find a top-level project license covering reuse of repository images or source material.

The catalogue can cite the repository as evidence while keeping image publication and license-sensitive reuse conservative.

Source note: pjranki/bpod repository file tree and badge.gallery image policy.

BSides Perth 2017 Wemos Badge note

repository license caveat · public repository but incomplete licensing · needs explicit project license

The public Badge-2017 repository preserves source files, but this pass did not recover a top-level license covering code, documentation, or any repository images.

The catalogue can cite the repository as evidence while avoiding image or source reuse beyond attribution and linking.

Source note: BSidesPerth/Badge-2017 repository and badge.gallery image policy.