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)
LayerOne 2018 ESP32 Alexa Badge note

hardware-media rights caveat · local project policy · documented

Visible official, Hackaday, and Hackaday.io media prove the badge and add-on context, but no specific LayerOne 2018 badge photo or full upstream raster has been paired with complete reusable image license or permission, attribution, source URL, and processing notes.

The entry remains source-backed and image-free rather than copying article photos, event media, repository screenshots, or project images without full provenance.

Source note: badge.gallery image policy, LayerOne HHV page, Hackaday article media, GitHub repository, and mmca Hackaday.io project media.

LayerOne 2019 Voight-Kampff Badge note

hardware-media rights caveat · local project policy · documented

Visible Hackaday, official, and repository-linked media prove the badge and add-on context, but no specific LayerOne 2019 badge photo or full upstream raster has been paired with complete reusable image license or permission, attribution, source URL, and processing notes.

The entry remains source-backed and image-free rather than copying article photos, event media, repository screenshots, or project images without full provenance.

Source note: badge.gallery image policy, LayerOne HHV page, Hackaday article media, and charlie-x/layerOne2019 repository media.

44CON 2017 HIDIOT 1.0 Badge note

hardware-repository license boundary · public repository review · needs explicit license clarification

The public HIDIOT hardware repository exposes board, schematic, and PNG files but no repository license metadata, and its README includes trademark and documentation-use constraints.

The catalogue links the hardware archive for evidence but does not copy media or imply broad reuse rights beyond what the source states.

Source note: rawhex/hidiot_hardware README and GitHub metadata.

Helgatchi Badge (DEF CON 34) note

hardware-source and production-revision boundary · published directory structure only · source-tree scope not reconciled with manufactured units

The Hardware tree visibly includes drawings, spacer, front PCB, back PCB, and test-jig directories, but this pass did not reconcile schematic, BOM, Gerber, fabrication, enclosure, test-jig, or revision files against the live store's product configuration. The sources do not identify final board revision, quantities, assembly operator, test coverage, serialisation, materials, or unit-to-unit variance.

The directory structure is recorded as a useful maker trail without treating it as a complete released hardware package or confirmation that all sales share one documented revision.

Source note: Pips801/Helgatchi Hardware tree and DC801 Helgatchi Badge product page.

Wild West Hackin' Fest Deadwood 2025 E-Badge note

hardware-source boundary · official challenge page plus attendee teardown · needs deeper archive recovery

The official WWHF page proves an electronic badge and badge CTF but does not publish a component list, schematic, BOM, firmware release, PCB files, or challenge-source archive; component-level details currently come from a post-event attendee teardown.

The catalogue records ESP32-S3, OLED, charger, LED, BLE, serial, and firmware-analysis details as teardown-backed rather than official board documentation.

Source note: WWHF e-badge page and AlrikRr NetRunSecurity badge-hacking writeup.

DC503 Wagon Party Badge note

hardware-source caveat · source-backed but incomplete · needs deeper production archive

The repository preserves firmware and programming instructions, but this pass did not recover schematics, board files, BOM, final production quantity, handout list, or a photographed final badge set.

Hardware claims stay limited to the README programming workflow, nRF52832 target, SSD1306 display setup, I2C pin mapping, and firmware-observed inputs.

Source note: pdxbadgers/wagonparty README and firmware source.

Biohacking Village DC33 Distiller BHV Badge note

hardware-source caveat · source-backed but incomplete · needs final design-file recovery

Public sources document the CM5 platform, custom PCB functions, enclosure, software branches, and user operation, but this pass did not recover a final public schematic, PCB/Gerber release, full bill of materials, or production count.

The catalogue keeps hardware claims to verified public documentation and avoids inventing component identifiers or manufacturing details.

Source note: PamirAI BHV user guide, Distiller CM5 SDK/Python branches, and Raspberry Pi article.

Lonely Hackers Club DC33 Meshtastic Badge note

hardware-source caveat · official product specs but incomplete archive · needs schematic or firmware archive

The public page gives concrete module/specification details, but this pass did not recover a custom schematic, case source, firmware patch repository, manufacturing files, or bill of materials beyond the listed hardware platform.

The catalogue records verified hardware and firmware configuration while avoiding unsupported custom-board or source-release claims.

Source note: LHC Meshtastic Badge 2025 page and LHC Meshtastic guide.

BSides Tampa 2018 Badge note

hardware-source caveat · source-backed but incomplete · needs badge-team archive

Public sources prove BSides Tampa 2018 event context, electronic badge assembly activity, and a visible badge/lanyard artifact, but this pass did not recover schematic, BOM, firmware, assembly instructions, controller part, battery details, or challenge-source material.

The record captures the source-backed artifact without inventing electronics or software behavior beyond the public evidence.

Source note: St. Petersburg College attendee report, Wikimedia Commons photo metadata, and badge.gallery inclusion policy.

BSidesSLC 2025 E-Badge note

hardware-source caveat · official source plus matching public archive · technical archive recovered; needs authoritative release mapping

The official page documents the custom ESP32-S3-WROOM / LoRa badge and its visible features. A commit-pinned archive titled 2025 Utahtastic BSides Badge mirrors that description and includes KiCad PCB/schematic files plus a Meshtastic-derived source tree, but BSidesSLC does not directly link it or name its author.

The catalogue can now record the public technical archive while withholding an audited final BOM, manufacturing package, event firmware image/configuration, app settings, challenge archive, production count, and proof that every delivered unit matched the public tree.

Source note: BSidesSLC official site and distinctm1nd/2025_utahtastic_bsides_badge at b0eb50f42125df564aef9f3beee962fa5024decf.

BSidesSF 2022 Hardware Village Badge note

hardware-source caveat · official source but incomplete · needs technical archive

The official source proves a pre-assembled Arduino-programmable badge, but this pass did not recover a schematic, BOM, controller part, firmware repository, payload archive, PCB files, production count, or official badge photo license.

The catalogue records the real village artifact while avoiding unsupported component or firmware claims.

Source note: BSidesSF 2022 Hardware Village schedule description.

NorthSec 2026 Badge note

hardware-source caveat · official post-event source plus first-hand observation · official design source documented; event-unit deployment scope remains open

NorthSec's separate Apache-2.0 nsec/badge-2026 repository now publishes KiCad, BOM/CPL/Gerbers, a pin map, and C++/PlatformIO source for the ESP32-S3/NFC/e-paper/NeoPixel design. It does not identify a source commit, binary, display state, component revision, or assembly/flash configuration for each distributed badge. Marx314's write-up remains useful first-hand context, including its observed 16 MB module report, but it is not an official production ledger.

The catalogue can document the official technical surface and CTF integration without presenting the published design snapshot or any third-party observation as a universal recipient-unit configuration.

Source note: nsec/badge-2026 commit 4dab9e6c4c0b8efc9a643ee646a49550453ea22c hardware tree, board_pins.h, platformio.ini, and LICENSE; NorthSec 2026 registration/competition/villages/schedule pages; NSEC26 Badge Shenanigans.

Hackfest 2019 Electronic Badge note

hardware-source caveat · official source but technically shallow · needs primary badge archive

The official sources prove an electronic badge was introduced for the 2019 CTF, but this pass did not recover a schematic, BOM, PCB repository, firmware, controller details, display, radio, battery, badge-team writeup, or production count.

The record preserves the electronic-badge milestone while avoiding invented component or firmware claims.

Source note: Hackfest history, Hackfest 2019 schedule, and Hackfest CTF 2019 page.

HackConRD 2026 eBadge note

hardware-source depth caveat · firmware/readme source but no CAD archive · needs hardware archive recovery

The recovered 2026 trail documents controller, display, radio, LEDs, buzzer, buttons, firmware, games, RF behavior, and ticket inclusion, but this pass did not recover schematic, PCB files, BOM, enclosure files, exact shipped quantity, or hardware errata.

The record keeps hardware claims to the official site and firmware repository without inventing a final circuit, board revision, manufacturing run, or image provenance.

Source note: HackConRD 2026 site, eBadge page, and Badge_HackConRD_2026 README.

RVAsec 2026 Badge note

hardware-source gap · post-event repository evidence · needs schematic and BOM recovery

The event has happened and a public firmware repository now exists, but no public schematic, BOM, PCB source, component list, production writeup, or manufacturing archive has been recovered for the final badge hardware.

The catalogue can document the firmware, simulator, and RP2040/Pico SDK workflow while keeping manufacturing-grade hardware claims open.

Source note: RVAsec pages and HackRVA/badge2026 repository.

NorthSec 2025 Badge note

hardware-source scope caveat · source-backed but incomplete · needs deeper post-event artifact inventory

The public repository preserves README, KiCad, BOM, schematic, and firmware material, but this pass does not mirror every CTF challenge artifact, post-event solve, manufactured-board photograph, or field report.

The catalogue records verified hardware and firmware surfaces while leaving deeper NorthSec 2025 artifact archaeology for later work.

Source note: NorthSec 2025 badge repository, README, hardware tree, and schematic PDF.

Vibe Coder Dog SAO (DEF CON 33) note

historical DEF CON 33 provenance and distribution gap · maker-stated historical association in a current listing · historical origin stated; original event evidence not recovered

The current maker listing says the SAO was created for DEFCON 33, but this pass did not recover an original 2025 product page, dated announcement, schedule entry, drop record, production count, sales record, recipient list, or attendee report. The 2026 leftover listing does not by itself prove how, when, or whether units were originally distributed at DEF CON 33.

The record may preserve the maker-stated DEF CON 33 association while avoiding a stronger original-distribution, sale, allocation, or event-outcome claim.

Source note: Vibe Coder Dog SAO product listing, reviewed 2026-08-04.

BSides Peoria 2026 Planned Conference Badge note

historical electronic-badge reference boundary · official organizer wording · prior-year promotion retained separately from 2026 artifact evidence

The sponsor call says people were still talking about the previous year's electronic badges before describing what is new in 2026. It does not explicitly say that the planned 2026 badge is electronic or reuses a previous design, and no technical 2026 badge archive was recovered.

The entry does not turn a historical promotional sentence into a 2026 electronics, firmware, challenge, compatibility, or delivery claim.

Source note: Call For Sponsors: BSides Peoria 2026 official organizer post.

HAL2001 Simple Badge note

historical scope · public history page and event archive · needs primary artifact recovery

Public badge-history sources describe earlier Dutch camps such as HAL2001 as having very simple badges or none at all, and no sourceable public record currently supports an electronic HAL2001 badge specification.

The compendium includes HAL2001 as a lineage and identity-artifact entry while leaving electronics, credits, and images marked for primary-source recovery.

Source note: WHYcast history episode 41 and the official event archive.

OHM2013 Patch / Hat Identity note

historical scope · public history page and event archive · needs primary artifact recovery

OHM2013 sits immediately before SHA2017 in the Dutch camp lineage, but currently has stronger public memory as hat/patch identity culture than as a sourceable electronic badge.

The compendium models OHM2013 as a non-PCB identity artifact and leaves any electronic-badge claim open pending primary evidence.

Source note: WHYcast history episode 41 and the official event archive.

Payment Village DC33 Vulnerable ATM Badge note

historical versus current programme boundary · official 2026 schedule plus historical programme archive · 2025 artifact and 2026 teaching reference kept separate

Payment Village's official 2026 schedule includes an Introduction to the Vulnerable ATM Badge, while the historical DEF CON 33 programme describes the 2025 object. Neither source says the 2025 hardware remains unchanged, will return as a physical unit, is newly issued in 2026, or is the same as the separate volunteer village badge announced for DEF CON 34.

The catalogue preserves cross-year educational continuity without inventing a 2026 hardware revision, reissue, allocation, or relationship among distinct Payment Village artifacts.

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

Beelzebub Minibadge Holder (DEF CON 34) note

horror theme, authorship, and endorsement boundary · maker wording and source labels only · creative framing recorded; rights and affiliation unsubstantiated

The maker presents Beelzebub as a horror-themed minibadge holder, but reviewed sources do not identify the art, character, product, firmware, or hardware authorship chain; a rights/license basis for associated creative elements; or authorization, affiliation, sponsorship, or endorsement from DEF CON, SAINTCON, or another organization/person.

The dossier records source-described creative framing without asserting ownership, franchise/religious or cultural affiliation, sponsorship, endorsement, authorship, or media-reuse authority.

Source note: Beelzebub product page, public Badgelife response, and distinctm1nd repository.

Krampus Minibadge Holder (DEF CON 34) note

horror theme, authorship, and endorsement boundary · maker wording and source labels only · creative framing recorded; rights and affiliation unsubstantiated

The maker presents Krampus as a themed minibadge holder, but reviewed sources do not identify the art, character, product, firmware, or hardware authorship chain; a rights/license basis for associated creative elements; or authorization, affiliation, sponsorship, or endorsement from DEF CON, SAINTCON, or another organization/person.

The dossier records source-described creative framing without asserting ownership, franchise/religious or cultural affiliation, sponsorship, endorsement, authorship, or media-reuse authority.

Source note: Krampus product page, public Badgelife response, and distinctm1nd repository.

THOTCON 0xC Badge note

housing-design tradeoff · first-hand project writeup · documented

The badge housing changed from a two-piece ABS and clear-PC concept to a single clear-polycarbonate part after injection-molding review, timeline pressure, wall-thickness concerns, sink-mark risk, and lens-geometry iteration.

The record preserves the badge as a real production artifact with mechanical and optical compromises rather than treating the enclosure as a frictionless visual shell.

Source note: Rob Rehrig THOTCON 0xC project writeup.

Camp++ 2026 Identity Artifacts note

identity verification boundary · official how-to page · planned flow; outcome unconfirmed

The how-to page requires government-issued ID or passport at the location reception for legally required overnight-stay check-in, separate from the camp ticket-code and wristband flow. Its past-date text does not prove individual check-in or wristband issuance.

The dossier separates campsite legal check-in from the camp identity artifact and does not convert planned logistics into a confirmed access model.

Source note: Camp++ 2026 how-to page rechecked 2026-08-25.

BSides Adelaide 2026 Identity Lanyard Badge note

identity-artifact boundary · primary source · post-event verification complete

The 2026 Adelaide record is now treated as an identity/lanyard surface trail from CFP, sponsorship-page, Humanitix, and sponsor-brief sources, not a confirmed distributed badge implementation.

The catalogue tracks the attendee badge/lanyard surface while keeping hardware, firmware, artwork, challenge behavior, and distribution claims open until post-event technical recovery appears.

Source note: BSides Adelaide 2026 CFP, sponsorship page, Humanitix ticketing, and sponsor brief.

BSides Melbourne 2020 Lanyard and Registration Artifact note

identity-artifact classification · official source · documented

The recovered BSides Melbourne 2020 sources prove conference registration and lanyards, but do not prove an electronic badge or a separate printed badge artifact.

The entry is intentionally modeled as a lanyard and registration identity artifact so the Melbourne lineage expands without inventing PCB, firmware, RF, display, CTF, or programmable behavior.

Source note: BSides Melbourne 2020 schedule and sponsor page.

BSides Melbourne 2023 Identity Badge note

identity-artifact classification · official source · documented

The recovered BSides Melbourne source trail proves a badge and lanyard credential with consent and interaction-protocol signalling, but does not prove an electronic badge.

The entry is intentionally modeled as a conference identity artifact so the Melbourne lineage expands without inventing PCB, firmware, RF, display, CTF, or programmable behavior.

Source note: BSides Melbourne 2023 attendee communications and official archive.

BSides Melbourne 2024 Identity Badge note

identity-artifact classification · official source · documented

The recovered 2024 prospectus proves a badge/lanyard identity artifact with pronoun, photo-permission, and interaction-preference signalling, but does not prove an electronic badge.

The entry is intentionally modeled as a social-signal identity artifact so the Melbourne lineage expands without inventing PCB, firmware, RF, display, CTF, or programmable behavior.

Source note: BSides Melbourne 2024 sponsorship prospectus and sponsors page.

BSides Melbourne 2026 Lanyard Badge note

identity-artifact classification · primary sources · documented; post-event details still needed

The 2026 entry is source-backed as a participant badge/lanyard identity artifact, but no post-event artifact detail, final artwork record, field report, or reusable badge photo has been recovered yet.

The catalogue keeps the Melbourne lineage current while avoiding claims about final production, design, electronics, firmware, or attendee field use beyond the public badge/lanyard source trail.

Source note: BSides Melbourne 2026 home page, sponsor page, and sponsorship package.

CrikeyCon VI 2019 Identity and Support Badge note

identity-artifact classification · official source · documented

The recovered CrikeyCon VI source proves attendee badge pickup, staff badges, Friendly Bear name badges, and special speaker badges but does not prove an electronic conference badge.

The entry is intentionally modeled as conference identity, support, and speaker credentials so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

Source note: CrikeyCon VI official archive page.

CrikeyCon VII 2021 Identity and Connect Badge note

identity-artifact classification · official source · documented

The recovered CrikeyCon VII sources prove badge pickup and a CrikeyCon Connect badge marker but do not prove an electronic conference badge.

The entry is intentionally modeled as a conference identity and support-signal artifact so the CrikeyCon lineage expands without inventing PCB, firmware, RF, CTF, display, or programmable behavior.

Source note: CrikeyCon VII archive, schedule, and events pages.