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
2208 matching issue record(s)
HRV SSTV Badge (DEF CON 34) note

independent DEF CON/HRV association, availability, and credential boundary · maker repository description and official Ham Radio Village event page · maker-associated planned project; official relationship and handoff unverified

The maker repository description says it is building an SSTV #badgelife badge for HRV at DEFCON 34, while Ham Radio Village's official page confirms its DEF CON 34 programme. The official event page does not mention the repository or badge. No reviewed source establishes HRV or DEF CON commissioning, sponsorship, organizer authorization, booth/pickup, price, quantity, sale/giveaway, recipient criteria, allocation, completed handoff, admission role, or access-control function.

The catalogue classifies this as an independent planned project associated with the event context, not an HRV-issued or DEF CON-issued badge, a guaranteed attendee benefit, a venue-authorized activation, a Human badge, an access credential, or proof that anyone received a physical unit.

Source note: livitup/hrv-sstv-badge repository description and Ham Radio Village DEF CON 34 event page.

EFF "Electric Fist" BadgeLife (DEF CON 34) note

independent EFF relationship and donation-accounting boundary · primary organizer event listing · limited to published organizer statement

The FAQ says the project is EFF-affiliated but independently organized by H4r0ld and V3rbaal, and the listing says proceeds support EFF's mission. It does not publish the product's ownership, payment processing, donation percentage or timing, beneficiary receipt, accounting, or EFF product-management terms.

The catalogue records the organizer's exact public relationship and benefit statements without presenting independent organizers as EFF staff, claiming an EFF retail product, or inferring unannounced donation details.

Source note: Eventbrite Electric Fist FAQ and event description.

Cult of Cthulhu Indie DEF CON 34 Badge note

independent badge and role-allocation classification · primary maker storefront source · documented pre-event

The storefront markets an independent badge with Acolyte, Glyph, Elder God, and redacted Cthulhu roles, while official DEF CON Human-badge registration is separate. It does not establish role counts, all distribution sites, final participant availability, or official DEF CON credential status.

The record is connected to DEF CON 34 for BadgeLife discovery while remaining distinct from the official Human badge and from unverified role/allocation claims.

Source note: Pfarrside Creations badge-only product listing and official DEF CON 34 badge context.

AND!XOR DC34 5N4CK3Y Badge note

independent badge classification · official project page and DEF CON context · documented pre-event

AND!XOR describes a separate badge project participating in DEF CON Contests & Events and a philanthropy/giveaway route. It is not the official DEF CON 34 Human badge or a general admission credential.

The record can sit under the DEF CON 34 event without confusing the independent BadgeLife project with the official conference-access badge.

Source note: AND!XOR DC34 official product page and DEF CON 34 event context.

Puzzled Hackers LED Badge (DEF CON 34) note

independent meetup and DEF CON credential boundary · first-hand Team announcement and official checkout · independent community meetup artifact

The Team says its meetup is free, badges are optional, and an actual DEF CON badge is not needed for the first Wednesday gathering. The checkout labels the item for DEF CON 34 and offers a possible arranged DEF CON handoff, but neither source makes Puzzled Hackers a DEF CON organizer, says the LED badge is included with registration, grants conference access, replaces a Human badge, or proves conference/venue authorization.

The catalogue models a real Puzzled Hackers community badge associated with DEF CON 34 while keeping it distinct from official admission, organizer issuance, and verified event access.

Source note: Puzzled Hackers CTF badge checkout and Team meetup announcement.

Monorail Con Badge (DEF CON 34) note

independent monorail, DEF CON, and credential boundary · primary maker storefront and first-person announcement · independent DEF CON 34-associated maker product

The maker explicitly says the project is not affiliated with the Las Vegas Monorail, and its sources frame pickup at DEF CON as a community handoff. No reviewed source says it includes a monorail ticket, transit discount, transit-company approval, DEF CON organizer affiliation, conference registration, event access, a substitute for a Human badge, or organizer support.

The catalogue treats this as an independent themed badge, not a transit artifact, fare instrument, official DEF CON credential, admission item, or sponsored product.

Source note: Zach's Hacks product page and first-person r/Defcon announcement.

BSides Fort Wayne 2026 Optional E-Badge note

individual design and fulfillment-credit gap · public organizer and commit evidence · organization and scoped source contributors credited

The organizer and dated commits name BSides Fort Wayne, David Prows, and luke-gilsinger, but reviewed sources do not assign an individual 2026 badge designer, PCB engineer, artist, firmware release owner, manufacturer, assembler, ticket seller, fulfillment owner, or image-rights authority.

The dossier credits only the named organization and narrowly evidenced source contributions without inferring authorship, manufacturing responsibility, distribution control, or image permission.

Source note: BSidesFortWayne organization profile; BSidesFW2026Badge commit history; root license.

Hackers Teaching Hackers 2026 Eagle 5 Badge note

individual design and fulfillment-credit gap · named publisher and attendee sources · scoped publisher/attendee credits only

Zack Nagaich is named by the GitHub account and initial release, and Paul Danis is named by the attendee account, but reviewed sources do not identify the 2026 Eagle 5 PCB designer, visual artist, hardware reviewer, firmware coauthors, event badge lead, manufacturer, assembler, seller, fulfilment owner, or image-rights authority.

The catalogue credits only the named event organization, source publisher, and attendee report without inferring individual design, production, distribution, branding, or image-use roles.

Source note: HTH official sources; syn-ack-zack profile and Eagle 5 commit; Paul Danis public account.

Open Sauce 2026 Badge note

individual design, manufacturing, and fulfilment-role boundary · named designer and attendee collaboration sources · scoped named credits only

Caleb Marting is named by the root license and an attendee as the badge designer, and the attendee archive names putnam and Gerard Hudson for custom-firmware work. Reviewed sources do not allocate individual mechanical, electrical, firmware, artwork, fabrication, assembly, test, procurement, sales, handoff, support, or image-rights roles beyond those narrow facts.

The catalogue credits only named, source-supported roles without inferring sole authorship, production responsibility, distribution control, trademark authority, or image permission.

Source note: calebmarting/os2026-badge LICENSE and README; putnam custom-firmware README.

RISC-V Summit Europe 2026 FPGA Badge note

individual manufacturing and delivery-role boundary · named design and production-context sources · team/design credits and named production partner recorded; role allocation incomplete

The README names five designers and team sources name SemiTO-V and NextPCB, but reviewed sources do not allocate individual PCB, firmware, FPGA, artwork, review, procurement, assembly, quality-control, logistics, handoff, support, or image-rights roles among the named people or organizations.

The dossier credits named contributors and the stated production partner without inferring sole authorship, manufacture responsibility, fulfilment ownership, product-support duty, or image authority.

Source note: RISC-V FPGA Badge README; SemiTO-V Developer Zone and production updates.

CSIDES 2025 Crab Badge note

infrared feature, authorization, and field-result boundary · Punk Security sponsor listing and maker repository · high-level feature documented; operating outcome and authorization unrecovered

The public sources describe an infrared-capable badge and preserve related source material, but do not establish final emitter configuration, output, range, target compatibility, actual device-interaction results, attendee use, venue authorization, legal or regulatory compliance, safety review, support policy, or final-unit parity. No use, configuration, targeting, payload, timing, or device-interaction directions are reproduced here.

The catalogue makes the event-artifact feature auditable while declining to provide operational guidance or to infer authorized, safe, reliable, or successful use.

Source note: Punk Security CSIDES event listing and csides-2025-badge repository.

ScapyCon 2026 Badge note

issuance and completion gap · official event page plus participant archives · organizer wrap-up and handoff unverified

The official ScapyCon page still carries pre-event ticketing wording after the elapsed September 15-16 dates, and the public archives do not identify the badge's designer, manufacturer, production count, or attendee handout scope.

The edition is not marked completed on official wrap-up evidence, and the badge record documents the public hardware and firmware trail without asserting organizer issuance or universal attendee allocation.

Source note: ScapyCon 2026 event page, dissecto GmbH firmware archive, and breachlabz flash kit, checked 2026-09-26 and rechecked 2026-09-27.

MNSEC 2026 Event Badge note

issuance and completion gap · official site plus builder documentation · organizer wrap-up and handoff unverified

The official MNSEC site still read pre-event on September 29, 2026, five days after the September 24 date, and the badge repository publishes a pre-event user guide and renders without a production count, attendee allocation, or distribution statement.

The edition is not marked completed and the record does not assert that every attendee received the badge.

Source note: MNSEC 2026 official site and MNSEC2026BADGE repository, checked 2026-09-29.

JawnCon 0x3 Calculator Badge note

kit and assembled form discrepancy · official badge page versus media preview · unresolved

The official build notes have attendees solder the kit from parts drawers at the JawnCon soldering station, while Hackaday says the badge comes in assembled or kit form and is distributed as a bare PCB.

Both statements are kept with attribution until post-event sources show which forms were actually offered.

Source note: JawnCon badge page and Hackaday preview, checked 2026-10-15.

ToorCon 13 Spectrum Analyzer Badge note

kit-completion caveat · primary source · documented

The base badge worked as a spectrum analyzer, while full Ubertooth-capable behavior required a larger hacking kit and additional firmware installation on both microcontrollers.

The catalogue separates shipped badge behavior from optional kit upgrades and does not imply that every attendee badge was fully populated as an Ubertooth.

Source note: Great Scott Gadgets ToorCon 13 badge page and Project Ubertooth source tree.

Hack the North 2026 Hacker Badge low

late screens and wearability · first-hand designer writeup · documented

On August 10, 2026, 25 screens from a bad supplier batch failed testing, leaving 1,725 boards ready; the designer told JLCPCB that around 1,600 working boards on time mattered more than 1,750 perfect boards late. In the post-event survey of 115 hackers, the top complaint (24 people) was that the badge, two AA cells on a bare board, was heavy and clunky to wear.

The record does not claim that all 1,750 badges reached hackers working on day one; the writeup does not say how the 25 late boards were handled.

Source note: va3ndf.com Making 1,750 programmable PCB badges, checked 2026-10-21.

Agency SAO Badge V2 (DEF CON 34) note

license and image-provenance boundary · GitHub repository metadata and source-tree review · no detected repository license or rights-cleared image trail

GitHub reports no detected repository license, and the reviewed repository provides no root license, release, explicit artifact-image permission, selected factual unit image, image attribution, or processing provenance. Code visibility, a GitHub handle, or any repository media would not independently grant image reuse.

The badge remains image-free and the code is linked as evidence rather than treated as a license grant, image-reuse permission, or complete open-hardware release.

Source note: MadmanTimmy3241/Defcon-badge-V2-RP2040 repository metadata and commit-pinned source-tree review.

Hackaday Remoticon.2 DIY Badge note

license and media caveat · source-limited audit · needs deeper license audit

This pass did not identify a clear project-wide license on the Hackaday.io Remoticon.2 files that would support local reuse of project photos, renders, or artwork as catalogue images.

The project is cited for artifact facts and fabrication context, but image and artwork reuse is withheld pending explicit license or permission evidence.

Source note: Remoticon 2 badge Hackaday.io project, files page, Hackaday article media, OSH Park previews, and badge.gallery image policy.

HackGDL 2026 Camera Badge note

license and repository-media boundary · GitHub API metadata and repository tree · documented with caution

GitHub metadata reports `license: null` for ElectronicCats/badge_hackgdl_2026, and the reviewed recursive tree exposes no top-level LICENSE or COPYING file. Public source and hardware files do not by themselves grant reuse rights for product photos, README imagery, logos, trademarks, social media, or other repository media.

The catalogue cites the source trail but publishes no image and makes no broad code, hardware, artwork, or trademark reuse claim.

Source note: GitHub API repository metadata and recursive tree for ElectronicCats/badge_hackgdl_2026, Electronic Cats product page, and badge.gallery image policy.

BSides Fort Wayne 2026 Optional E-Badge note

license and visual-material scope boundary · repository root license review · MIT source license documented; image use remains unqualified

The repository root publishes an MIT LICENSE for Software and associated documentation, but this pass did not identify a selected factual badge photo or official raster with complete image-specific source, license or explicit permission basis, attribution, and processing provenance. Public repository visibility or a generic source license is not used to copy media by default.

The catalogue may link the source archive and license while maintaining the separate image-rights threshold for any future local badge asset.

Source note: BSidesFW2026Badge LICENSE, repository tree, and badge.gallery image policy.

BSidesPDX 2015 Badger Badge note

license boundary · repository files · documented

The PCB repository includes CC BY-SA 3.0 licensing, while the firmware file carries a permissive source-header notice and the repositories do not provide a single unified image/documentation rights statement for publishable badge media.

The record cites code and hardware sources but does not reuse repository artwork or social/event imagery as a hero image.

Source note: pdxbadgers/pcb-2015 COPYING.TXT and pdxbadgers/fw-2015 badger.ino.

BSides Leeds 2026 Artie the Owl Badge note

license gap · repository inspection · no license file

The punk-security repository carries no LICENSE file, no license header in firmware.ino, and no license badge in the GitHub sidebar, so the firmware is treated as all-rights-reserved rather than redistributable.

The catalogue records the verified hardware and challenge surface without claiming redistribution rights over the firmware or any derivative.

Source note: punk-security/bsides-leeds-2026-badge repository file tree and firmware.ino.

Unknown Security Conference 2026 Pwn Llama Badge note

license scope boundary · repository README and LICENSE · hardware license documented; broader terms unverified

The README says the hardware is released under CERN Open Hardware Licence v1.2. That statement does not itself establish a separate license for firmware, documentation beyond the stated hardware scope, trademarks, or visual assets.

The record links the hardware source and license while avoiding overbroad reuse, firmware, trademark, or image-rights claims.

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

BugCON 2023 Badge note

license scope caveat · GitHub API, repository README, and license files · documented

GitHub detects GPL-3.0 for the repository, while the README and LICENSE_HARDWARE.md state that hardware documentation is under CERN Open Hardware Licence v1.2 and that Electronic Cats and BugCON trademarks are not granted for PCB sales.

The catalogue can cite GPL software and CERN-OHL hardware documentation while avoiding assumptions that firmware, photos, logos, screenshots, KiCad renders, trademarks, or other media all share one reuse scope.

Source note: ElectronicCats/Badge-BugCON2023 README, LICENSE, LICENSE_HARDWARE.md, and GitHub API metadata.

BugCON 2024 Badge note

license scope caveat · primary repository · documented

The repository README states the hardware is released under CERN Open Hardware Licence v1.2, while the license text itself says software and firmware are outside that license unless explicitly expressed.

The compendium can cite the open-hardware release while avoiding assumptions that all firmware, screenshots, photos, or repository media share the same reuse terms.

Source note: BugCON 2024 repository README and LICENSE_HARDWARE.md.

BugCON 2025 Linux Badge note

license scope caveat · GitHub API, repository tree, and README · documented with caution

GitHub reports no detected top-level license for `ElectronicCats/badge-bugcon-2025`, and the README says to consult license files without exposing a simple whole-repository license for hardware, firmware, photos, diagrams, or artwork.

The catalogue can cite the open-hardware claim and public source while avoiding assumptions that firmware, SDK material, readme images, KiCad renders, logos, or event graphics are reusable publication assets.

Source note: ElectronicCats/badge-bugcon-2025 repository metadata, README, and badge.gallery image policy.

BSides CDMX 2025 Badge note

license scope caveat · repository README and license files · documented

The repository is GitHub-detected as GPL-3.0 and the README separately states the hardware is released under CERN Open Hardware Licence v1.2. This record treats software, firmware, hardware documentation, and the selected hardware-tree raster according to their documented scopes rather than assuming one license covers every asset.

The catalogue can cite and publish the selected hardware render while keeping firmware/source licensing and event trademarks separate from the hardware-documentation reuse basis.

Source note: ElectronicCats/Badge-bsides-cdmx-2025 README, LICENSE, LICENSE_HARDWARE, and GitHub API metadata.

HackGDL 2025 Minino Badge note

license scope caveat · repository README and store page · documented with caution

The README says firmware is GNU AGPL v3.0 and hardware is CERN Open Hardware Licence v1.2, but this pass does not treat product photos, screenshots, GitHub attachments, logos, trademarks, or store media as reusable image assets.

The catalogue can cite the source and hardware release while keeping image publication and trademark reuse separate from code and hardware licensing.

Source note: HackGDL 2025 badge README, Electronic Cats product page, and badge.gallery image policy.

Div0 Tingkat eBadge (DEF CON Singapore 2026) note

license, artwork, and image-provenance boundary · repository metadata, root tree, and commit-pinned README review · source tree public; reuse license and rights-cleared badge image unrecovered

GitHub reports no detected repository license, and the reviewed root contains no visible license file. The archive includes artwork and image assets, but none is paired in the reviewed source trail with a badge-specific reusable license or explicit permission basis, attribution, processing notes, and a source-to-physical-artifact mapping. The spelling/artwork differences and event-label conflict make selecting a factual representative image even less defensible.

No repository art, PNG, screenshot, source graphic, social image, or generated approximation is copied into the public image directories; the record remains source-linked and image-free pending complete reusable-image provenance.

Source note: RestiaAshdoll8 repository metadata, root tree, and commit-pinned README; badge.gallery image policy.

Retia DEF CON 32 Badge note

license, image, artwork, and branding boundary · GitHub metadata and immutable repository-tree review · no detected repository license; selected image reuse rights unresolved

GitHub metadata reports no detected license and the immutable source tree has no root LICENSE or COPYING file. The README includes a badge photograph, but the source does not pair it with a selected-image reuse basis, named attribution, processing provenance, or permission covering artwork, marks, event naming, or media.

The catalogue cites the source archive but does not copy its badge photo, board images, code, fabrication files, artwork, logos, trademarks, screenshots, or a generated approximation.

Source note: Retia repository metadata, immutable 2024-labelled source tree/README, and badge.gallery image policy.

RISC-V Summit Europe 2026 FPGA Badge note

license, sponsorship, and event-endorsement boundary · README and team-source statements · hardware-license and named-sponsor claims recorded narrowly

The project README states a CERN-OHL-W hardware license and names RISC-V International, NextPCB, GOWIN Semiconductor, and DeepComputing as sponsors, while team posts associate the badge with the summit. These claims do not by themselves show that event organizers owned the repository, issued the board as a standard credential, endorsed every current revision, or granted image-reuse permission.

The catalogue links the source-license and sponsorship context while keeping organizer ownership, attendee credential status, trademark/endorsement scope, physical-delivery responsibility, and image rights separate.

Source note: RISC-V FPGA Badge README; SemiTO-V project updates; official RISC-V Summit pages.

BugCON 2022 Badge note

license-file caveat · GitHub API and repository README · documented with caution

The README says hardware is released under CERN Open Hardware Licence v1.2 and says to consult a LICENSE_HARDWARE file, but this pass found no top-level `LICENSE_HARDWARE.md` through the GitHub contents API and GitHub reports no detected repository license.

The catalogue can cite the README's open-hardware claim and public source while avoiding assumptions that firmware, photos, readme images, logos, KiCad renders, or other repository media are reusable publication assets.

Source note: ElectronicCats/Badge-BugCON-2022 README, repository metadata, GitHub contents API 404 for LICENSE_HARDWARE.md, and badge.gallery image policy.

44CON 2025 RF Detector Badge note

license-scope caveat · repository metadata and README review · needs explicit license clarification

GitHub reports the repository license as MIT, while the README says the hardware is released under CERN Open Hardware Licence v1.2; the source pass did not recover the referenced LICENSE_HARDWARE file.

The catalogue links repository images, diagrams, and hardware files as evidence but does not copy media or collapse the software, hardware, documentation, and artwork license boundaries.

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

RISC-V Summit Europe 2026 FPGA Badge note

limited Developer Zone allocation and fulfilment gap · primary team event updates · 25 boards planned; logistics delay published; recipient outcome unrecovered

SemiTO-V said it planned to bring 25 boards to the Developer Zone workshop, then reported that a logistics issue prevented intended June 8 distribution and hoped for June 9 availability. Reviewed sources do not establish a final inventory, distribution date, ticket eligibility, recipient count, pickup process, shipment, replacement, refund, completed handoff, or a universal attendee allocation.

The catalogue does not turn a limited planned workshop allocation into proof that all 25 boards, all workshop participants, or all summit attendees received a badge.

Source note: SemiTO-V Developer Zone post and public team update feed.

Hackaday Berlin 2023 Voja4 Badge note

lineage and revision caveat · official article plus project notes · documented

Hackaday says the Berlin badge was re-skinned and included a couple hardware tweaks, but stayed 100% compatible with the 2022 Supercon badge.

The catalogue records the Berlin artifact as an event-specific revision while avoiding unsupported claims about exact PCB changes until a Berlin-specific hardware archive is recovered.

Source note: Hackaday Berlin badge preview and v0j4 project notes.

Hackaday Supercon 2016 LED Matrix Badge note

lineage reuse · source-backed · documented

The Supercon II badge intentionally reused the core Hackaday Belgrade badge concept while changing visual design, integrating the accelerometer, exposing expansion pads, and updating the bootloader.

The compendium keeps the US Pasadena record separate while preserving the Serbian Belgrade design lineage and shared firmware roots.

Source note: Hackaday.io Supercon II project and Design And Hacking Drilldown article.