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
1262 matching issue record(s)

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

identity-artifact classification · official source · documented

The recovered CrikeyCon IX sources prove badge pickup and custom accessibility badge/pin artifacts but do not prove an electronic conference badge.

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

Source note: CrikeyCon IX schedule, archive page, and Humanitix ticketing.

identity-artifact classification · official source · documented

The official CHCon 2018 source proves identification tags/badges and badge challenges but does not prove that the attendee credential was an electronic PCB badge.

The record is modeled as an identity and challenge artifact so the CHCon lineage expands without unsupported microcontroller, firmware, display, radio, NFC, or CTF-on-badge claims.

Source note: CHCon 2018 event and sponsorship page.

identity-artifact classification · official source but no technical archive · documented

The recovered public trail proves a conference badge and lanyard sponsor context plus visible volunteer-badge requirement, but it does not prove an electronic badge, PCB, firmware, badge challenge, component list, schematic, production count, or final artwork.

The catalogue models the 2018 item as a conference identity/admission artifact and avoids upgrading sponsor and volunteer evidence into unsupported electronics claims.

Source note: Nullcon Goa 2018 sponsors page, volunteer page, schedule, venue page, and archive.

identity-artifact classification · primary writeups · documented

The sources prove a custom CR80 Hacker ID Card / reusable name-tag artifact and on-site card-printing workflow, but not a PCB, firmware project, badge challenge, or electronic conference badge.

The entry is modeled as an identity-card badge artifact and avoids unsupported electronics claims.

Source note: Security-Bits Hacker ID Card page, H2HC custom-card production post, and Need a New ID? follow-up.

identity-artifact evidence boundary · primary source but sparse post-date page · needs post-event artifact source

The current public page proves an official lanyard plus badge in the free conference pass, but still does not prove the final shipped artifact design, electronic hardware, firmware, or badge challenge.

The compendium can list the source-backed identity artifact while avoiding unsupported hardware claims until post-event photos, guide material, or organizer documentation appears.

Source note: UnknownCon 2026 event page and sponsor deck.

image provenance · Wikimedia Commons license metadata and visible DEF CON I Human badge text · licensed original replacement applied

The DEF CON 1 image uses a WebP crop from Sephiroth storm's CC BY-SA 4.0 Wikimedia Commons documentary photo `HackerCon Badges.jpg`.

The entry now has a real rights-cleared documentary-photo derivative while avoiding generated art, placeholder imagery, and reuse of the rights-limited official DEF CON media-server badge photo.

Source note: Wikimedia Commons File:HackerCon Badges.jpg, DEF CON 1 source trail, and badge.gallery image policy.

image provenance · source-backed · licensed original replacement applied

The DEF CON 17 visual uses Nate Grigg / nateOne's Flickr documentary photo `HUMAN` under CC BY 2.0, cropped to the visible Human attendee badge area.

The entry now has a rights-cleared original documentary photo while preserving the rule against copying Grand Idea Studio all-rights-reserved project-page images, press imagery, generated art, placeholders, or social-media scrapes.

Source note: Flickr photo 3793067350 structured metadata, Creative Commons Attribution 2.0 license page, and badge.gallery image policy.