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)
Greycademy 2026 Hackbadge warning

coin-cell brownout and field-repair history · first-person maker account · maker-reported repair applied; affected scope and final validation unverified

The maker reports that the original coin-cell setup could brown out after roughly two minutes, then says more than 200 already programmed badges were reprogrammed before distribution and informally appeared to have substantially improved battery life. The source does not provide a controlled test, exact firmware change, affected-unit count, serial/revision mapping, battery characterization, follow-up failure rate, or confirmation that every distributed unit received the repair.

The record keeps an attributable production/reliability history visible without offering repair instructions, declaring the hardware safe, or generalizing a maker observation into a verified universal outcome.

Source note: Terence Chan Zun Mun's public Greycademy Hackbadge account.

SAINTCON 2021 MiniBadge Collection note

collection-boundary caveat · official MiniBadges page · documented

The 2021 archived page documents many MiniBadges with distinct status, community, contest, booth, personal, and unofficial acquisition paths, so this record is a collection entry rather than a single universal attendee-issued main badge.

The catalogue preserves the MiniBadge ecosystem while keeping per-board authorship, distribution, electronics, and official/unofficial status boundaries separate.

Source note: SAINTCON 2021 Content - MiniBadges page.

SAINTCON 2022 MiniBadge Collection note

collection-boundary caveat · official guide category definitions · documented

The 2022 assembly guide covers official, sponsor, and personal MiniBadges, so this record is a documented collection entry rather than a claim that every listed PCB was a universal conference-issued attendee badge.

The catalogue preserves the MiniBadge ecosystem while keeping acquisition routes, creator roles, and support boundaries separate from main-badge distribution claims.

Source note: MiniBadges-of-2022 assembly guide official, sponsor, and personal category definitions.

SAINTCON 2023 MiniBadge Collection note

collection-boundary caveat · official FAQ plus community data export · documented

The 2023 public evidence supports a MiniBadge ecosystem with official, community, contest, and personal entries, not a single uniform attendee-issued main badge or a claim that every listed board was organizer-built.

The catalogue preserves the verified trading and collection surface while keeping per-board authorship, acquisition, electronics, and support boundaries narrow.

Source note: SAINTCON 2023 FAQ and MiniBadge Wiki 2023 data export.

SAINTCON 2024 MiniBadge Trading Collection note

collection-boundary caveat · official trading page plus standards trail · documented

The official 2024 page describes submitted and official MiniBadges brought to the conference, so this record models a collection/trading ecosystem rather than a single uniform attendee-issued main badge.

The catalogue preserves the verified BadgeLife surface while avoiding unsupported claims about universal distribution, per-MiniBadge electronics, or official status for every submitted design.

Source note: SAINTCON 2024 MiniBadge trading page and 2024 build-guide link.

DEFCON Furs 2026 Badge note

community-event access-rule and final-event-outcome boundary · official DEFCON Furs event-space and meetup schedules · badge-required event-space wording published; implementation and outcome unrecovered

The official Furry Village schedule says DEFCON Furs badge required and lists badge pickup, and the meetup schedule lists pickup sessions. Neither page identifies credential material, visual design, barcode, QR, RFID/NFC access use, account linkage, reader, venue verification process, staff discretion, revocation, personal-data practice, actual operation, or every attendee's completed pickup or entry result.

The catalogue records the published DEFCON Furs event-space boundary without inventing a technical access-control system or a record of individual access.

Source note: DEFCON Furs 2026 Furry Village and meetup schedules.

BadgeLife Village Badge (DEF CON 34) note

companion SAO documentation and image-provenance boundary · official BadgeLife companion page and badge guide · companion page is WIP; no cleared badge image selected

Badge.Life's companion DC34 SAO page contains WIP placeholders rather than named final add-ons or a technical compatibility list. Its badge guide shows a front-image link, but no reviewed image is paired with a reusable license or explicit permission basis, attribution, source URL, and processing notes. GhostGlitch's name on the companion WIP page is not treated as a main-badge or final-SAO authorship assignment.

No unverified SAO is added and no Badge.Life image is copied into the public catalogue; the record remains source-useful while awaiting completed add-on and image-rights evidence.

Source note: Badge.Life DC34 Village SAO page and Village Badge guide.

CPEC DC34 MechBattle Badge note

companion SAO scope, interface, fabrication, and compatibility boundary · commit-pinned CPEC companion source · design archive published; interface and physical result unverified

The CPEC companion source labels itself as SAO plug-in modules for the CPEC DC 34 badge and contains native design files, but does not identify an SAO version, pinout, voltage/current envelope, connector/power behavior, address/protocol, host-detection method, mechanical dimensions/fit, controller population, component substitutions, validation process, fabricated quantity, assembly status, or an actual compatible host badge. Its BOM and placement files are preparation artifacts, not proof of an order or completed build.

The catalogue keeps the files attached to the MechBattle record as a source-published companion design trail without representing them as a plug-and-play accessory, a safe wiring or flashing guide, a completed add-on lineup, or a distributed DEF CON artifact.

Source note: CPEC DC-34-Mech-SAO README and commit-pinned source tree.

CyberNorth CyberFest 2025 Compass Badge note

compass calibration, accuracy, and field-result boundary · maker repository description · feature and broad limitation documented; calibrated outcome unrecovered

The maker archive describes a magnetic compass feature, ambient-interference limits, and an intentionally coarse bearing display. It does not publish a calibrated reference, test conditions, accuracy/error figures, per-unit calibration record, participant-use result, field-reliability report, or a claim that every supplied unit produced the same outcome.

The catalogue records a source-described interactive feature without turning it into navigation guidance, an accuracy assurance, or a universal user-experience claim.

Source note: cyberfest-2025-badge README.

Fri3d Camp 2026 Badge note

completed-camp handout state · official 2026 camp and hardware repositories · camp completed; handout and production outcome unverified

The organizer event index lists Fri3d Camp 2026 among past events. The hardware README says Revision 02 was the version intended for handout during the camp, but neither source establishes individual attendee distribution, final allocation, physical-unit parity, or field reliability.

The catalogue can mark the event complete without converting a planned handout statement into a completed attendee-distribution or production claim.

Source note: Fri3d Camp event archive and Fri3dCamp/badge_2026_hw README.

EMF 2026 Spaceagon Badge note

completed-event allocation and fulfillment boundary · official completed-event and badge-listing sources · event complete; individual pickup records unavailable

EMF confirms that the July 2026 event is complete, and the official listing says all badges and components required on-site pickup and now displays the products as sold out. Neither source establishes production quantity, order count, individual collection, no-show handling, delivery, replacement, repair support, or a universal attendee allocation.

The catalogue records a completed event and a documented acquisition route without turning a sold-out post-event listing into a claim that every offered kit was manufactured, collected, or issued to all attendees.

Source note: Electromagnetic Field 2026 home page and official badge order listing.

Nullcon Goa 2014 Hardware Badge note

component-detail caveat · source-backed but incomplete · needs slide or video audit

Current sources prove the Nullcon 2014 hardware badge, the talk, the presenters, and Amey Gat's creator credit, but this pass does not rely on unverified component-level summaries for chip, firmware, schematic, or BOM claims.

The record keeps the hardware description conservative until the original presentation or video is audited for exact technical detail.

Source note: Nullcon schedule, official speaker page, Nullcon 2015 speaker bio, and Hackers of India archive.

CyberNorth CyberFest 2025 Compass Badge note

conference allocation, recipient, and handoff boundary · official CyberNorth event sources and maker repository · completed conference and maker distribution statement documented; recipient details unrecovered

CyberNorth establishes the October 7 Community Conference and Punk Security's source archive says the Compass Badge was given out to all attendees. The reviewed sources do not give an attendee count, production quantity, ticket-tier scope, named recipient list, pickup/handoff record, replacement policy, or proof of final physical-unit equality.

The catalogue preserves a completed conference-associated electronic badge without turning a maker's broad distribution statement into a recipient ledger or guaranteed universal entitlement.

Source note: CyberNorth CyberFest 2025 official page, Community Conference materials, and Punk Security Compass Badge repository.

leHACK 2026 Badge Hackropole note

conference credential separation · official leHACK practical information · workshop device and general badge pickup documented as distinct contexts

leHACK's practical-information page says reception staff issued a general conference badge when a QR code was presented. Badge Hackropole appears separately in the leLAB workshop schedule and hardware repository; no reviewed source says it was the admission badge, QR credential, access-control token, attendee-wide inclusion, or replacement for the general conference badge.

The record remains a workshop-made electronic artifact rather than an unsupported claim about leHACK admission, identity, access control, or universal badge allocation.

Source note: leHACK practical information and 2026 workshop schedule.

BSides SP 2026 Garoa Badge REV. 0 note

conference deployment and allocation boundary · Garoa organization demo archive with official event corroboration · documented caveat

Garoa’s demo README says the REV. 0 badge was distributed at BSides SP 2026, but the reviewed public sources do not provide a recipient ledger, allocation criteria, production quantity, hardware-variant inventory, event-day firmware image, or source-to-unit mapping.

The catalogue records the source-backed event association without implying that every attendee received an identical unit or that the current demo archive was installed on conference hardware.

Source note: Garoa Badge — BSides SP 2026 Demo README, Garoa BSidesSP page, and Security BSides SP V21 page.

BSides Cheltenham 2026 Challenge Coin note

conference-token classification and physical-specification gap · official Early Bird package wording · challenge coin named; final object details unrecovered

The official package calls the item a Limited Edition Challenge Coin but does not identify its material, dimensions, weight, artwork, finish, edge, serialisation, manufacturer, manufacturing method, final quantity, physical configuration, or electronic capabilities.

The record is modeled as a planned conference token rather than as an electronic badge, a generic admission credential, or a specific finished coin unsupported by the organizer's page.

Source note: BSides Cheltenham 2026 official event and Early Bird package page.

HackerHotel 2027 Badge note

conflicting design direction · two Badge.Team sources · unresolved

Badge.Team's homepage still promises LoRa, a keyboard, a big screen, and an ESP32-P4, while the official hardware repository's active design is a CH643 LED-matrix starfish with infrared and no screen, keyboard, or radio. The starfish reached a prototype-1 fabrication package on October 22, 2026, but neither source says whether it replaces the ESP32-P4 plan, is a second board, or is an interim prototype.

The record lists both descriptions with attribution and makes no claim about which hardware attendees will receive.

Source note: Badge.Team homepage and badgeteam/hackerhotel2027-hardware, checked 2026-10-23.

DEF CON 15 Badge note

contest-archive scope · primary project page plus linked archives · needs deeper archive review

The project page names seven official contest entries and links several archives, but this pass records the main winner/runner-up facts rather than unpacking and modeling every submitted ZIP as separate source material.

The badge page preserves the contest lineage while leaving full per-entry reconstruction for a later archive pass.

Source note: Grand Idea Studio DEFCON 15 badge project page and linked contest-entry archives.

DEF CON 17 Badge note

contest-archive scope · official results plus primary project page · needs deeper archive review

The official results list 32 badge-hacking contest entries and the project page links selected ZIP archives, but this pass records the top entries and selected linked archives rather than unpacking every contest artifact.

The badge page preserves the contest lineage while leaving full per-entry reconstruction and media review for a later archive pass.

Source note: DEF CON 17 contest results and Grand Idea Studio DEFCON 17 badge project page.

44CON 2025 RF Detector Badge note

controller-mode caveat · repository README · source published

The README says at least one of the two control paths must be soldered: shield-only operation gives OLED mini-game behavior, while the recommended fuller experience uses the ESP32 Wemos D1 module and related support parts.

The record separates the minimal shield/display experience from the ESP32 and RF-detector build path instead of treating every configuration as identical.

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

METROPOLIS AI SAO (DEF CON 34) note

creative reference, rights, and image-provenance boundary · maker names a film inspiration · specific artifact and per-asset rights not established

The listing names Maria from Fritz Lang's 1927 Metropolis as inspiration but does not publish the art source, design license, film/reference rights analysis, per-asset attribution trail, or a selected reusable badge image. This record does not attempt to resolve the legal status of the film or rely on it as an image-reuse basis.

The catalogue preserves the maker's stated creative reference without republishing related art or inferring a license for the product image, board art, or source material.

Source note: METROPOLIS AI SAO product page.

C1B3RTR4CKS 2026 CH32V003 Badge note

credential allocation and recipient boundary · contemporaneous attendee report plus official event and repository sources · partially documented

A contemporaneous report describes the physical badge as the event credential and says badges were limited, but recovered sources do not state a final quantity, ticket entitlement, recipient ledger, variant allocation, access-control technology, or completed handoff record.

The dossier documents a real badge at the event without turning an attendee observation into an unsupported universal issuance or credential-system claim.

Source note: ARAINTEL attendee report, official C1B3RTR4CKS page, and SEIF-UAM badge repository.

Payment Village DEF CON 34 Volunteer Village Badge note

credential form, technology, and data-practice gap · official volunteer notice · past-date access benefit named; implementation and use unrecovered

The official notice calls the volunteer benefit a village badge that provides conference access, but does not identify a physical or digital form, lanyard, artwork, barcode, QR code, RFID, NFC, serialisation, electronics, reader/scanner, access-control system, account linkage, data handling, privacy policy, support process, replacement procedure, or actual use.

The entry models the disclosed identity/access artifact without turning a generic access statement into an electronic-badge, tracking, authentication, privacy, or completed-access claim.

Source note: Payment Village DEF CON 34 volunteer notice, rechecked 2026-09-15.

Adversary Village DEF CON 34 Volunteer Badge note

credential form, technology, and data-practice gap · official volunteer notice · past-date volunteer artifact named; implementation and use unrecovered

The official notice calls the benefit Adversary Village badges but gives no physical or digital form, lanyard, artwork, barcode, QR code, RFID, NFC, serialisation, electronics, reader/scanner, access-control system, account linkage, data handling, privacy policy, support process, replacement procedure, or actual-use record.

The record preserves the named volunteer artifact without turning a generic badge statement into an electronic badge, tracking system, authentication method, privacy claim, confirmed physical handoff, or completed access record.

Source note: Adversary Village DEF CON 34 call for volunteers, rechecked 2026-09-15.

HackerOne BUG HUNT 2026 Access Pro Badge note

credential form, technology, and data-practice gap · official Access Pro package wording · ticket-tier badge named; implementation unreleased

The official Access Pro listing names a Unique access Badge embracing #BadgeLife, but does not identify a physical or digital form, lanyard, artwork, barcode, QR code, RFID, NFC, serialisation, electronics, reader/scanner, access-control system, account linkage, data handling, privacy policy, support process, or replacement procedure.

The catalogue records the disclosed ticket-tier identity artifact without turning a marketing label into an electronic badge, tracking system, authentication method, privacy claim, or confirmed physical handoff.

Source note: BUG HUNT 2026 official Access Pro package listing.

Original Series Tricorder Badge (DEF CON 34) note

current badge and historical Tricorder SAO identity boundary · same-maker but separately named product sources · related maker lineage documented; hardware and distribution parity unconfirmed

The roster names an approximately $125 Original Series Tricorder badge featuring various sensors, while current MakeItHackin public product materials describe a separate $30 Tricorder SAO with rechargeable-battery and badge-powered forms. No reviewed source publishes a common revision, bill of materials, board layout, sensor suite, controller, behavior, packaging, price, allocation, or explicit statement that the current badge contains or derives from that historical SAO.

Readers can follow the useful same-maker historical context without treating it as an undocumented specification for the new DEF CON 34 badge.

Source note: MakeItHackin DEF CON 34 roster response, Tricorder SAO repository/README, Tindie listing, and tutorial.

Badge Crown SAO (DEF CON 34) note

current marketplace availability, BadgeLife drop, and credential boundary · live maker listing and current BadgeLife schedule · $10 / 10-remaining / 20-sold snapshot and August 7 4 PM drop published

The listing showed $10, 10 remaining, 20 sold, PRE/DROP labels, and an August 7 BadgeLife Village drop; Badge.Life schedules Brookes Bytes Badge and SAOs at Friday 4 PM. Neither source establishes payment records, final inventory, run size, exact Badge Crown allocation, completed manufacture, pickup, shipment, delivery, refund, replacement, or post-event availability. Nor does either source say DEF CON designed, issued, sponsors, or will distribute it; that it is included with registration; or that it grants admission, replaces a Human badge, or is a universal attendee benefit.

The catalogue retains a time-specific independent maker offer and village context without treating it as an official credential, guaranteed handoff, or completed transaction.

Source note: Brooke's Bytes Badge Crown SAO Uberflux listing and Badge.Life current DC34 village schedule, reviewed 2026-08-05.

Hacker Boba Badge Kit (DEF CON 34) note

current marketplace availability, BadgeLife drop, and credential boundary · live maker listing and current BadgeLife schedule · $10 / 17-remaining / 33-sold snapshot and August 7 4 PM drop published

The listing showed $10, 17 remaining, 33 sold, PRE/DROP labels, and an August 7 BadgeLife Village drop; Badge.Life schedules Brookes Bytes Badge and SAOs at Friday 4 PM. Neither source establishes payment records, final inventory, run size, exact Hacker Boba allocation, completed manufacture, pickup, shipment, delivery, refund, replacement, or post-event availability. Nor does either source say DEF CON designed, issued, sponsors, or will distribute it; that it is included with registration; or that it grants admission, replaces a Human badge, or is a universal attendee benefit.

The catalogue retains a time-specific independent maker offer and village context without treating it as an official credential, guaranteed handoff, or completed transaction.

Source note: Brooke's Bytes Hacker Boba Uberflux listing and Badge.Life current DC34 village schedule, reviewed 2026-08-05.

Agency Wand (DEF CON 34) note

current marketplace availability, BadgeLife drop, and fulfillment boundary · live maker listing and current BadgeLife schedule · $60 / 19-remaining / 11-sold snapshot and August 7 4 PM drop published

The live listing showed $60, 19 remaining, 11 sold, PRE/DROP labels, and a DEF CON 34 BadgeLife Village August 7 4 PM drop; Badge.Life lists Brookes Bytes Badge and SAOs in the Friday 4 PM village schedule. Neither source establishes payment records, final inventory, run size, exact product allocation at the schedule slot, event authorization, completed manufacture, pickup, shipment, delivery, refund, replacement, or post-event availability.

The catalogue preserves a time-specific independent-maker listing and schedule association without turning it into a fulfillment report, guaranteed handoff, or completed transaction.

Source note: Brooke's Bytes Agency Wand Uberflux listing and Badge.Life current DC34 village schedule, reviewed 2026-08-05.

Breadbadge (DEF CON 34) note

current marketplace availability, DC34 drop, and fulfillment boundary · live maker listing and current BadgeLife schedule · $80 / five-remaining / four-sold snapshot and planned schedule published

The live listing showed $80, five remaining, four sold, and a Defcon34 drop, while Badge.Life schedules Bread Badge by Tw0nkus in a Friday 1:30 PM slot. Neither source establishes payment records, final inventory, run size, exact location, event authorization, expected handoff mechanics, completed manufacture, pickup, shipment, delivery, refund, replacement, or post-event availability.

The catalogue preserves a time-specific maker listing and schedule association without turning it into a fulfillment report or guaranteed handoff.

Source note: Tw0nkus Breadbadge Uberflux listing and Badge.Life current DC34 village schedule.

Star Trek SAO Phaser v2.2 (DEF CON 34) note

current-event and historical-revision identity boundary · same-name sources with no formal 2026 mapping · same title and maker/product linkage; exact 2026 parity unconfirmed

The roster and 2026 maker video use the exact Star Trek SAO Phaser v2.2 name, while the live product listing says v2.2 was made for DC31 and follows a 2019 v1. No reviewed source publishes a 2026 BOM, board revision, production label, serial range, change log, component/finish/packaging comparison, or explicit statement that the planned DEF CON 34 units are identical to the older product listing.

Readers can trace the useful v1/DC31 history without assuming the current planned sale is a newly engineered board, an unchanged old run, or a fully mapped revision.

Source note: Hak4Kidz DEF CON 34 roster response, H4K-Dave video, and Hak4Kidz Lab Tindie listing.

BSides Fort Wayne 2025 Badge note

current-site rollover caveat · source freshness check · documented

The live BSides Fort Wayne site has rolled forward to 2026, while the first-hand 2025 badge-team writeup and public 2025 badge repository preserve the 2025 evidence trail.

Keep the source note explicit and prefer archive/search snapshots or future official archive pages if a dedicated 2025 official page becomes available.

Source note: May 22, 2026 source check of bsidesfortwayne.org, Thad Turner writeup, and public GitHub repository metadata.

BSidesPDX 2016 ATTiny85 Badge note

date-source inconsistency · conflicting public sources · documented

The official 2016 schedule and speaker page place the Friday program and keynote on October 14, 2016, and Calagator records October 14-15, 2016, while the current official past-events index lists October 19-20, 2016 even though those weekdays do not match the printed Friday/Saturday wording.

The event page uses the schedule/Calagator October 14-15 dates and preserves the mismatch as a provenance caveat instead of silently normalizing it.

Source note: BSidesPDX 2016 schedule, BSidesPDX 2016 speakers page, BSidesPDX past-events page, and Calagator event record.

GrrCON 2026 15th Anniversary Badge low

decoy RECHARGE port · attendee hardware inspection · design caveat

The micro-USB port marked RECHARGE is connected to nothing, so plugging in USB neither charges nor powers the badge; the attendee firmware archive also warns against powering the badge from a 3.3 V adapter against the coin-cell rail or wiring the badge TX to the adapter TX.

Owners should replace the coin cells rather than expect USB charging and follow the archive's wiring notes when exploring the console.

Source note: Redline Cyber Security writeup and securekomodo firmware archive README.