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
2166 matching issue record(s)
HackThePlanet SAO (DEF CON 34) note

analog hardware, power, and GPIO electrical gap · maker-described component-level summary · needs circuit and host testing documentation

The source names a 555 timer, ten-bit counter, LEDs, trimmer, and a host-GPIO button but does not publish a schematic, parts values, power/current limits, header orientation, pin map, shorting path, isolation/protection, debounce behavior, LED electrical characteristics, thermal data, host test matrix, safety guidance, or compliance evidence.

The record does not treat the product description as a circuit design, electrical integration guide, or safe compatibility guarantee.

Source note: SAO HackThePlanet product page.

Flutter & Friends 2025 E-Paper Conference Badge note

app deployment, firmware, and source-rights boundary · public organizer-app and MIT package sources · companion source public; device deployment unresolved

Public app and package code establishes a companion workflow but not the precise store build attendees used, a preinstalled app, a badge firmware image, a flashing/update path, original firmware ownership, a post-event support commitment, or a license for event branding and media. The MIT package license applies to its source code only.

The entry keeps open-source companion software separate from physical-badge firmware, event deployment, trademark/media rights, and any implied image-reuse permission.

Source note: Flutter & Friends conference-app commit, friends_badge repository, package commit history, and MIT license.

Ruxcon 2015 HHV Badge note

archive-boundary caveat · source-backed but incomplete · needs deeper event archive

This pass recovered the HHV badge repository, build PDF, and programming writeup, but not an official Ruxcon badge-distribution page or attendee-count source for the badge run.

The catalogue ties the badge to the Hardware Hacking Village public archive and avoids claiming exact distribution volume or universal attendee issuance.

Source note: Ruxcon 2015 event page, InfoconDB, RuxconBadge2015 repository, and programming writeup.

DEF CON 20 Badge note

archive-depth caveat · source-backed but incomplete · needs deeper artifact inventory

This pass records the public firmware/material release paths but does not unpack, mirror, or inventory every firmware object, EEPROM dump, conference DVD file, or badge-contest writeup.

The record preserves the verified hardware and software surfaces while leaving deeper artifact archaeology for a later pass.

Source note: DEF CON event archive, Parallax forum attachments, and InfoconDB talk metadata.

AND!XOR DC28 Badge note

archive-depth caveat · source-backed but incomplete · needs deeper artifact inventory

The public repository preserves firmware, Gerbers, SPI tools, troubleshooting, and a flash image, while this pass does not audit every firmware commit, CTF flag, Slack hint, scoreboard state, patch, land-mine flag, or physical drop artifact.

The record captures the verified hardware/software surfaces without claiming complete CTF reconstruction or complete production logistics.

Source note: AND!XOR DC28 RTFM, CTF walkthrough logs, and GitHub repository.

BSides Agra 2025 IOTSRG Badge note

archive-source caveat · current live site replaced by hosting default page · archived source used

The live BSides Agra site currently serves a hosting/default page, so this record relies on Internet Archive snapshots for the official event context and official LinkedIn posts for the badge and soldering-village evidence.

Future maintenance should prefer a restored official page, badge-team repository, or post-event writeup if one appears, and should not weaken the record to the current default-page response.

Source note: Internet Archive CDX snapshots and current bsidesagra.com live-page check.

ToorCamp 2024 Shadybucks Wristband note

artifact classification · official wiki sources · modeled conservatively

The public sources prove a Shadybucks wristband, Shady Tag identity workflow, and badge CTF entry path, but not a recovered universal electronic PCB badge archive.

The record is classified as an identity/payment and CTF artifact instead of inventing electronics, components, firmware, or distribution details beyond the official wiki.

Source note: Shadybucks and Euphoria CTF wiki pages.

Ekoparty 2021 Badge Artwork Set note

artifact classification · primary official media attachments · documented narrowly

The recovered sources prove official 2021 badge-art variants, but not a physical badge, lanyard credential, electronic badge, PCB, firmware, badge challenge, or production/distribution quantity.

The entry is modeled as official role and competition badge artwork instead of being upgraded into an unsupported hardware badge.

Source note: Ekoparty attachment titles for attendee, speaker, workshop, ACFT, ICFT player, and Lado B variants.

BSides Cape Town 2025 Badge Sponsor Slot note

artifact detail boundary · official sponsorship source but narrow · classified as badge-sponsor inventory

The recovered public source trail proves a Badge Sponsor slot for the 2025 event, but does not prove an electronic badge, final printed credential design, lanyard artwork, sponsor imprint, attendee distribution count, schematic, PCB, firmware, challenge behavior, or production files.

The dossier preserves the real public badge-sponsor evidence while avoiding unsupported hardware or final-artifact claims.

Source note: BSides Cape Town 2025 sponsor page and Quicket event page.

NilbinSec PAC-MAN Ghost SAO (DEF CON 34) note

artifact form, hardware, connector, and electrical-safety documentation gap · maker names SAO but publishes no specifications · physical companion status documented; technical form unreported

The sources call the object an SAO and mention one of four colors, but do not disclose whether it contains electronics, a microcontroller, LEDs, sensors, a battery, passive circuitry, a standard or non-standard connector, voltage/current requirements, pinout, dimensions, materials, PCB, schematic, BOM, Gerbers, assembly, test data, host compatibility, ESD protection, or safety guidance.

The record preserves a real announced companion artifact without upgrading it into a programmable, electrically safe, standard-compliant, or universally compatible electronic badge.

Source note: NilbinSec roster response, Bluesky post, Spectre Sniffer listing, and maker profile.

RTV D20 Badge (DEF CON 34) note

artifact form, hardware, power, and safety documentation gap · public badge label only · technical and material form undisclosed

The reviewed sources call RTV D20 a Badge but do not identify whether it is electronic, a PCB, a physical credential, a token, a kit, or another identity artifact. They provide no components, board, power/battery/charging path, radio, display, inputs, connectors, dimensions, materials, schematic, BOM, Gerbers, assembly, test data, safety guidance, or compliance evidence.

The catalogue models a real planned named artifact without inventing its physical or electronic form, operating characteristics, safety profile, or engineering completeness.

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

BSides Roanoke 2026 Participant Badge Challenge note

artifact specification gap · organizer ticketing source · needs artifact-level documentation

Public sources establish that General Admission included a badge, but do not identify its material, artwork, dimensions, lanyard, QR/RFID/NFC behavior, electronic status, components, or production/distribution detail.

The record is modeled as a participant admission/identity artifact and does not infer a paper badge, electronic badge, or technical design.

Source note: Roanoke InfoSec Exchange Inc / Zeffy General Admission w/Badge listing and BSides Roanoke official site.

BSidesPDX 2020 Presenter LED Mask note

artifact-classification caveat · repository description and source comments · documented

The public repository describes the item as a talking LED mask for BSides 2020 presenters, and the firmware comments call it a BSides PDX speaker gift; no source recovered here says it was the attendee badge.

The catalogue models the object as a presenter wearable/event artifact rather than a general admission badge or attendee-wide distribution claim.

Source note: pdxbadgers/2020-mask repository description, README, and firmware comments.

Queercon 16 Q Badge note

artifact-depth caveat · source-backed but incomplete · needs deeper archive recovery

This pass relies on contemporary Hackaday technical coverage and DEF CON host-event context but does not recover an official Queercon 16 badge repository, firmware archive, full ARG ruleset, or production photo set.

The catalogue records verified hardware and social-game behavior while leaving firmware, challenge, and complete variant archaeology for a later pass.

Source note: Hackaday Queercon 16 article and DEF CON 27 host archive.

BSidesKC 2026 Admission Badge note

artifact-form and technology gap · official admission wording only · needs artifact documentation

The official source says attendees must present a BSidesKC badge at the afterparty but does not state the artifact's material, artwork, lanyard or wristband form, paper/card status, QR/barcode, RFID/NFC, electronics, maker, allocation, pickup, or access-control implementation.

The catalogue can preserve a real admission-artifact claim without upgrading it into an electronic conference badge or credential technology claim.

Source note: BSidesKC 2026 activities page.

DC503 5ohBEE Pager note

artwork-license boundary · README credit plus repository license · documented

The README credits the bee art to Ivycraft and the repository is Apache-2.0, but this pass does not treat that as a complete image-publication provenance record for the catalogue hero slot.

The catalogue preserves the artwork credit as source context while leaving the visual empty until a specific image can be cleared under the project image rules.

Source note: 5ohBEE README, 50bee.png repository asset, LICENSE, and badge.gallery image policy.

Hackover 2013 Badge note

assembled-for-beginners design choice · primary development post · historical

Hackover explicitly changed from the previous year's optional assembled Invader-style board toward giving every attendee an assembled and flashed PCB.

This is useful lore for European badge culture: the organizers optimized for immediate on-site play and beginners, not only for people already comfortable with microcontroller programming.

Source note: Hackover badge development post on hackover.de/page/9/.

NYC Badge (DEF CON 34) note

assembly and electrical specification gap · primary storefront source · needs assembly and engineering documentation

The listing explains only the broad beginner soldering boundary and says three AAA cells are required. It does not publish the assembly order, header/component placement, connector pinout, rail voltage, battery wiring, current limits, charging behavior, test procedure, safety guidance, or final as-built configuration.

The catalogue does not turn a retail component list into a complete construction, operating, or electrical-safety guide.

Source note: Uberflux NYC Badge product listing.

44CON 2025 RF Detector Badge warning

assembly and voltage safety caveat · repository README · source published

The RF-detector path depends on configuring the MT3608 boost converter to 9 V before installing the RF module, and the README says JP1 is disconnected to prevent damage until voltage is confirmed.

The badge page preserves the original power-safety context for the AD8317 RF detector instead of presenting the module as a no-risk plug-in.

Source note: ElectronicCats/badge-44con-2025 README.

Security Fest 2024 Feskekôrka Piano Badge note

assembly production caveat · primary writeup · historical

Assembly was disrupted when the reflow oven conveyor stopped working; the team externally drove the conveyor motor and tuned the supply around 8.5 to 9 volts to keep production moving.

The record captures the real operational work behind the polished attendee artifact and preserves a useful production failure mode for future badge teams.

Source note: Hackster.io Feskekôrka Piano Badge writeup.

39C3 Critical Decentralization Cluster Badge note

assembly scope, official-credential, and allocation boundary · official 39C3 assembly and talk pages · assembly artifact documented; allocation unrecovered

The official Congress sources call the CDC Badge an electronic conference badge and development board presented by the Critical Decentralization Cluster, but reviewed sources do not identify it as the official CCC Human badge, a general Congress admission credential, a ticket entitlement, a conference-wide handout, an event price, an allocation count, or a recipient ledger.

The record preserves the concrete 39C3 assembly artifact while not conflating a cluster badge with CCC's main credential or assuming every attendee received one.

Source note: 39C3 Critical Decentralization Cluster assembly page, CDC Badge assembly event page, and Critical Decentralization Cluster 39C3 retrospective.

IEEE Rising Stars 2026 Conference Badge Project note

attendee allocation and configuration boundary · official post-event report · bare-PCB attendee allocation and limited advanced prototypes documented

The official page explicitly says all attendees received bare PCBs with no components and that only about five advanced badges were manually assembled. It does not publish an attendee count, recipient list, exact prototype count, handoff record, populated-board inventory, substitute-kit record, or proof that every participant received or operated a finished electronic device.

The catalogue keeps the universal bare PCB and limited populated-prototype claims separate instead of presenting the five advanced units as the standard attendee badge.

Source note: IEEE Rising Stars 2026 Badge Project page.

Onion DAO 2026 Hardware Badge note

attendee allocation and handoff caveat · official event page · accepted-attendee badge and soldering workflow announced; final outcome unverified

The official festival page says every accepted attendee gets a hardware badge at registration and finishes a small soldering step, but the reviewed public sources do not provide an attendee list, unit count, on-site registration ledger, completed distribution report, assembly completion rate, final kit contents, replacement policy, or post-event fulfillment record.

The catalogue preserves the organizer's explicit attendee-badge statement without presenting it as a verified universal handoff or a completed configuration for every individual participant.

Source note: Onion DAO 2026 festival and badge page.

MNSEC 2025 Electronic Badge Collection note

attendee allocation, recipient, and handoff boundary · manufacturer project page and public source archive · completed quantity reported; recipient outcome unrecovered

Beelog reports that 418 electronic badges were delivered to MNCERT CC as a custom order, and the archive says the MNSEC 2025 badge work was completed. The reviewed public sources do not publish ticket eligibility, role allocation, recipient identities, registration linkage, pickup location, handoff report, returns, replacements, or evidence that every conference attendee received a badge.

The catalogue records a completed event-associated badge collection without making an attendee-wide allocation or individual delivery claim.

Source note: Beelog MNCERT CC Electronic Badge Project and MNSEC2025BADGE repository.

NodeConf EU 2019 NodeWatch note

attendee-distribution evidence boundary · attendee report plus badge-site trail · documented with limits

An attendee report says the open-source smartwatch was handed to conference participants, while NodeWatch.dev and NearForm document the badge platform; this pass did not recover official registration or fulfillment terms proving exact distribution scope.

The record treats NodeWatch as the NodeConf EU 2019 attendee badge without claiming exact batch size, every-ticket entitlement, or post-event availability limits.

Source note: Nordcloud attendee report, NodeWatch.dev, and NearForm source trail.

DEF CON 28 Safe Mode Badge note

audio-artifact caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document the cassette, liner, lanyard, and media-server availability, but this pass does not mirror or audit every audio file, transcript, tape variant, or final puzzle solution branch.

The catalogue records the verified analog badge surfaces and leaves complete audio forensics for a later artifact-level pass.

Source note: DEF CON forum challenge post, Hackaday hands-on article, and CIRCUITS TO KERNEL writeup.

CypherCon 2026 Extreme Badge note

availability, fulfillment, and benefit boundary · official registration, FAQ, and ticket category · recovered sold-out listing; completed recipient outcome unavailable

The recovered official listing labels the Extreme Badge sold out and its premium copy lists event experience benefits, but the sources do not establish quantity, purchaser count, payment, allocation, final price, eligibility, collection, shipment, replacement, receipt, benefit delivery, badge inventory, or whether every Extreme purchaser received an electronic artifact. The event's completion does not resolve any of those outcomes.

The catalogue records the organizer's availability and premium-tier wording, not a fulfilled VIP benefit, a guaranteed badge allocation, a final stock ledger, or an admission/access entitlement beyond the source's high-level ticket description.

Source note: CypherCon 2026 registration, ticket category, FAQ, and public organizer-account timeline mirror.

BSides Lisbon 2026 Electronic Badge note

badge and CTF relationship boundary · official current About page · both programme items announced; linkage unproven

The About page lists an electronic badge and a CTF in the same programme sentence, but does not say the CTF is physical, badge-based, or implemented by the badge. No challenge mechanics, source, scores, data flow, prizes, or results are public.

The catalogue records both official programme elements without incorrectly presenting the badge as a CTF device or asserting a physical challenge path.

Source note: BSidesLisbon 2026 About page.

Laser* Tag Badge DS (DEF CON 34) note

badge firmware and design archive gap · official maker page and public protocol repository · needs final badge archive

OpenLASIR is a public MIT-licensed compatibility protocol with examples, but reviewed sources do not publish complete final DS firmware, a badge-specific flashing workflow, schematic, PCB files, Gerbers, BOM, electrical design details, or a complete badge firmware license.

The catalogue can distinguish documented interoperability and game intentions from unverified full-badge implementation or reproducible-build claims.

Source note: OpenLASIR repository and Dani Weidman official maker page.

BSides Greenville 2023 Wi-Fi Analyzer Badge note

badge form, distribution, and credential boundary · event-programme wording and attendee report · event-linked badge documented; form and allocation unresolved

The source material calls the starting item a conference badge and says it could be transformed, but does not establish whether it was electronic before conversion, whether it was a PCB, whether an add-on was supplied, who could participate, ticket-tier eligibility, badge quantity, component-kit count, completed build count, replacement policy, or whether it operated as an admission credential.

The record remains a source-backed event artifact rather than an unsupported universal-attendee, access-control, or electronic-hardware claim.

Source note: CyberSC's BSides Greenville 2023 listing and Mike Holcomb's contemporaneous BSidesGVL announcement.

Carolina Code Conference 2026 Circuit Board Badge note

badge rendering and visual-rights boundary · official announcement image review · official renders visible; local reuse not cleared

The organizer's badge announcement displays renderings of the planned green and purple circuit-board badges, but the page does not provide an image-specific reusable license or explicit local-publication permission, photographer/render author attribution, processing basis, or final physical-artifact identity. It also depicts a planned rather than confirmed delivered object.

No local badge image is published; the record remains source-backed and image-free pending a factual artifact image or official upstream raster with complete reuse basis, attribution, and processing provenance.

Source note: Carolina Code Conference 2026 Circuit Board Badge announcement and badge.gallery image policy.

Hack Glasgow 2026 Attendee Name Badge note

badge technology, access-control, and data boundary · official FAQ review · no technical or badge-linked data behavior published

The official FAQ says a valid QR code is scanned on entry and separately says a handle or name may be written on a badge. It does not connect those statements or publish a badge barcode/QR, RFID/NFC, chip, firmware, app, protocol, identity system, data collection, privacy notice, retention, account linkage, CTF behavior, repository, or security review.

The entry does not turn the event's admission procedure into a technical feature, access-control claim, or data-handling claim about the attendee name badge.

Source note: Hack Glasgow official 2026 FAQ and event page.