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)
BSides NOLA 2026 Rougarou Circuit Board Badge note

allocation and provenance boundary · event listing and attendee account · needs final organizer recap

The event listing advertises a guaranteed PCB badge in its pre-sale package, while the reviewed post-event public trail does not publish a final allocation count, recipient roster, variant inventory, production run, board-designer statement, or delivery report.

The catalogue records a pre-sale package and observed attendee artifact without claiming universal distribution, exact production scope, or a named board designer beyond the event listing's Fox Pick attribution.

Source note: BSides Global event listing and post-event BSidesNOLA / attendee public sources.

BSides Orlando 2026 Electronic Badge note

allocation and quantity boundary · organizer repository and official build page · on-site programming documented; badge count and ticket inclusion unpublished

The organizer README says the programmer SAOs programmed all of the attendees' badges in the Soldering Village, and the September 29 commit documents a JLCPCB order on a 3x5 panel, but no source gives the number of boards ordered or handed out, a ticket-tier rule, leftover stock, or failures. The 2026-badge repository was not publicly reachable from September 25 through September 29, and the official event page still had no wrap-up on October 1.

The record treats attendee programming at the event as organizer-stated, without asserting a count or that every registrant received a badge.

Source note: 2026-badge README and EasyEDA order commit; BSides Orlando official event and Build Your Badge pages; September 25 to October 1, 2026 rechecks.

Carolina Code Conference 2026 Circuit Board Badge note

allocation, color-variant, and availability boundary · official pre-event recipient wording · announced variants documented; quantities and outcome unrecovered

The organizer announced green attendee badges and purple sponsor/speaker versions, and said there would be no additional circuit-board badges after the initial event order. It does not provide counts, ticket-tier mapping, eligibility rules, order quantity, final color/render confirmation, lost-badge policy, transfer policy, scarcity outcome, or completed allocation evidence.

The record preserves the organizer's announced recipient distinction without claiming that all attendees, sponsors, or speakers obtained a particular final unit or color variant.

Source note: Carolina Code Conference 2026 Circuit Board Badge announcement and event-week guide.

Telecom Village DEF CON 34 Badge note

allocation, handoff, and credential boundary · official organizer and event sources · scheduled dates elapsed; artifact outcome unconfirmed

The organizer revealed an all-new badge and lanyard and previously said the badge package was received, but the scheduled conference dates have elapsed without a reviewed post-event organizer record. The sources do not identify recipient eligibility, ticket inclusion, price, stock, variant count, production count, pickup point, shipment, registration process, credential use, replacement policy, individual receipt, or a completed distribution ledger.

The catalogue records a real event-specific artifact announcement without presenting it as an official DEF CON Human badge, a universal attendee benefit, a credential with known access behavior, or a completed handoff.

Source note: Telecom Village official site, DEF CON 34 event page, organizer-account updates, and DEF CON 34 official registration page, rechecked 2026-09-15.

IEEE RFID 2026 Active BLE Badge note

allocation, handoff, and final device-state boundary · official conference and post-event programme sources · 100-badge availability statement; individual receipt unverified

The organizer's conference page says 100 complimentary BLE badges were available, and the programme chairs confirm the conference occurred. The official sources do not provide a recipient list, final quantity produced or accepted, inventory accounting, handoff report, serial allocation, activation result, replacement policy, device-health record, or post-event owner report.

The dossier records a documented conference artifact without translating an availability statement into universal receipt, final distribution, continuous operation, or a complete fulfillment account.

Source note: IEEE RFID 2026 official conference page, RFID Badges page, and Technical Program Chairs' welcome.

Payment Village DC33 Vulnerable ATM Badge note

allocation, ownership, and credential boundary · source-conservative public record · event object documented; recipient and access role unrecovered

The recovered sources do not state who could receive, buy, borrow, use, or keep the Vulnerable ATM Badge; whether it was a conference credential; whether it was a shared village installation; how many units existed; whether it was completed or handed out; or whether it could provide access to DEF CON or any village activity.

The record does not describe the item as an attendee entitlement, a DEF CON-issued Human badge, a volunteer badge, a personal device, or a completed distribution run.

Source note: Payment Village DEF CON 33 page, preserved DEF CON 33 programme copy, and Payment Village DEF CON 34 programme.

IEEE RFID 2026 Passive RAIN RFID Badge note

allocation, physical form, and credential boundary · official badge and post-event programme sources · passive artifact documented; handoff and format unresolved

The official badge page says attendees could choose whether to accept and carry conference RFID badges, while the programme chairs confirm the conference occurred. Neither source provides passive-tag quantity, recipient list, serial allocation, physical-tag dimensions or medium, final artwork, handoff record, replacement policy, photo evidence, or a statement that the tag granted admission or access.

The record remains a documented passive conference artifact rather than an unsupported claim about every attendee, a specific physical format, identity credential, venue access, or completed fulfillment.

Source note: IEEE RFID 2026 RFID Badges page and Technical Program Chairs' welcome.

HITCON 2026 NTAG215 NFC Attendee Badge note

allocation, physical-form, and credential boundary · official event, organizer-account, and ticketing sources · event and activity completed; final allocation and form unreleased

The official event and KKTIX pages establish HITCON 2026, published attendee-badge ticket conditions, the venue, and the ended onsite-sales window; the official organizer's closing update confirms that the gathering and NFC Battle ran. They do not provide a complete ticket-tier/recipient ledger, collection workflow, final quantity, card dimensions, material, lanyard, printed design, access-control behavior, revocation policy, participant receipt, or post-event fulfillment evidence.

The catalogue records a completed event-specific attendee artifact without claiming that every registrant received it, that every ticket tier includes it, or that it functions as an admission/access credential.

Source note: HITCON 2026 official event page, Association of Hackers in Taiwan KKTIX ticketing page, and HITCON / @HacksInTaiwan closing update.

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.

Aerospace Village DC34 SR-71 CTF Badge note

artifact, host association, and credential boundary · public team self-submission plus official Aerospace Village event page · independent CTF badge listing in public roster; scheduled dates elapsed without a post-event record

A publicly named ACR team submits SR-71 to the BadgeLife roster and states an Aerospace Village booth/Discord CTF plan, while Aerospace Village independently establishes the DEF CON 34 event. Neither source says that Aerospace Village designed, issued, endorsed, or distributed SR-71; nor do they say it is a DEF CON Human badge, a registration entitlement, an admission credential, or a completed event artifact. The roster team name alone is not treated as proof of corporate authorization.

The catalogue preserves a concrete event-associated BadgeLife listing without converting public self-description into organizer issuance, corporate endorsement, credential authority, or a completed distribution claim.

Source note: Aerospace Village DEF CON 34 event page and the public DEF CON 34 BadgeLife roster SR-71 self-submission, rechecked 2026-09-23.

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.

BSides Joburg 2026 Badge note

attendee-source badge boundary · first-hand attendee archive plus official event page · organizer hardware statement outstanding

The badge record rests on first-hand attendee reversing and firmware evidence; the official BSides Joburg site never mentions the badge, and no organizer statement, schematic, BOM, production count, or allocation ledger was recovered.

The catalogue documents a real shipped electronic attendee badge without claiming organizer design intent beyond the write-up's designer credit, quantities, or which ticket classes received one.

Source note: BSides Joburg official site, taffy210 repository, and zero-entry.co.za write-up, checked 2026-09-26.