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.
distribution scope caveat · official event page · documented source limitation
The catalogue records the badge as a CyberThreat 2024 challenge artifact without inventing a universal distribution count.
Source note: CyberThreat official event page.
distribution scope caveat · badge-maker writeup · documented
The catalogue avoids implying every BSidesKC attendee had a fully electronic badge while still recording the verified electronic badge ecosystem.
Source note: Badge Pirates BSidesKC 2019 badge writeup.
distribution scope caveat · official source wording · documented
The badge is classified as a CTF team hardware artifact rather than a confirmed all-attendee admission badge.
Source note: NorthSec past-editions page.
distribution scope caveat · primary source · documented
The record should not imply every 2017 attendee received this electronic badge.
Source note: HITCON CMT 2017 events and KKTIX ticketing pages.
distribution scope caveat · official source · documented
The record distinguishes registered-attendee distribution from the free CommSec Village visitor purchase path.
Source note: HITBSecConf2018 Amsterdam CommSec Village page.
distribution scope caveat · official source but incomplete · documented source limitation
The record avoids implying universal attendee distribution or a known production run.
Source note: HITBSecConf2019 Amsterdam archive.
distribution scope caveat · official source · documented
The record does not imply a universal public visitor badge or a known production run.
Source note: JD-HITBSecConf2018 Beijing CommSec Village page.
distribution scope caveat · artifact source but incomplete event logistics · documented source limitation
The record is treated as a Packet Hack Village / HITB+CyberWeek artifact rather than a universal admission credential.
Source note: Hackster Packet Hack Badge project and HITB+CyberWeek event sources.
distribution-count caveat · source-backed but incomplete · needs shipped-count recovery
The badge is included as a source-backed village badge without claiming attendee-wide DEF CON distribution or a final production quantity.
Source note: OSHWA certification and Differential Destroyer README.
distribution-count caveat · primary badge page · documented
The record preserves the limited-run status without overclaiming final distribution.
Source note: LHC Meshtastic Badge 2025 page.
distribution-depth caveat · badge-team source but no ticket archive · needs event archive recovery
The record states first official badge and technical archive details without claiming attendee-wide distribution mechanics or quantity.
Source note: Verpent HackConRD 2024 writeup and HHW_HackConRD2024 repository.
distribution-scope caveat · source-backed but incomplete · needs final handout record
The record avoids claiming universal DEF CON, DC503, or BSidesPDX distribution and treats the artifact as a VIP/party wrist badge.
Source note: pdxbadgers/2018-banglet repository and README.
distribution-scope caveat · source-backed but incomplete · needs final handout record
The record avoids claiming universal 503 Party, DC503, DEF CON, or RainSec distribution and limits itself to the public repository's party-pager scope.
Source note: pdxbadgers/5ohBEE-2019 repository metadata and commit history.
distribution-scope caveat · official page plus event summary · documented
The record preserves the verified distribution language without implying every DEF CON or BIC Village attendee received one.
Source note: BIC Pick badge page and B.I.C. Village Event 2025 @ DEF CON 33 PDF.
distribution-scope caveat · official source · documented
The catalogue records the electronic badge without implying that every attendee received a fully assembled programmed unit.
Source note: BSidesROC 2019 badge page.
distribution-scope caveat · official schedule plus repositories · documented
The catalogue models the artifact conservatively as a BSidesPDX 2015 badge-hacking board archive rather than a universal attendee badge claim.
Source note: BSidesPDX 2015 schedule, pdxbadgers/pcb-2015, and pdxbadgers/fw-2015.
distribution-scope caveat · secondary event listing plus repository · documented
The catalogue records the source-backed BSidesPDX 2016 PCB badge without claiming that every attendee received one.
Source note: Calagator Security BSides Portland listing and pdxbadgers/pcb-2016.
distribution-scope caveat · official schedule plus repository · documented
The catalogue records a source-backed BSidesPDX 2017 badge archive without overclaiming distribution scope.
Source note: BSidesPDX 2017 schedule, speakers page, and pdxbadgers/pcb-2017.
distribution-scope caveat · official schedule plus repository · documented
The catalogue records a source-backed BSidesPDX 2018 badge archive without overclaiming distribution scope.
Source note: BSidesPDX 2018 schedule, speakers page, and pdxbadgers/badge-2018.
distribution-scope caveat · official schedule plus repository · documented
The catalogue records a source-backed BSidesPDX 2019 badge archive without overclaiming distribution scope.
Source note: BSidesPDX 2019 schedule and pdxbadgers/badge-2019.
distribution-scope caveat · source-limited · open
The catalogue treats the artifact as a source-backed La Villa Hacker 2025 badge without implying every village attendee received one.
Source note: La Villa Hacker site, dynamic store surface, and Badge-Villa-Hacker repository.
distribution-scope caveat · project-owner writeup · documented
Claims are limited to a self-order/forkable hardware template and do not imply all Remoticon attendees received one.
Source note: Thomas Flummer blog, GitHub README, and OSH Park shared project.
distribution-scope caveat · official source but narrow · documented
The record preserves the public distribution statement while leaving final shipped-quantity confirmation for follow-up.
Source note: HW101 Seasides 2026 Hardware Hacking Village page.
distribution-source boundary · first-hand badge-team source · documented
The catalogue may state that the badge was given to attendees, but it does not claim final production quantity, ticket-tier mechanics, or exact replacement/spare counts.
Source note: Thad Turner BSides Fort Wayne 2025 writeup and BSidesFW2025Badge repository.
documentation completeness · primary writeup and archived repo · historical caveat
The dossier should stay conservative until photos, final attendee firmware notes, and any workshop pages are recovered.
Source note: Christophe VG Fri3d Badge writeup and Fri3dBadge2016 GitHub repository.
documentation fragmentation · primary docs · historical
The page should keep multiple source links instead of pretending there is one complete canonical source.
Source note: Badge.Team docs, SHA2017 wiki, GitHub, Hatchery, WebUSB, media.ccc.de, and retrospective sources.
documentation lifecycle · primary docs · historical/current archive
The compendium treats MCH2022 as a platform record with multiple source trails rather than a single static badge page.
Source note: Badge.Team MCH2022 docs, Hatchery, GitHub, and Tweakers.
documentation mutability caveat · primary documentation disclaimer · documented
Hardware and software claims stay tied to the current public documentation snapshot and should be revisited if FREE-WILi revises the page or publishes design files.
Source note: FREE-WILi ICS Village Badge documentation disclaimer and FreeWili_WebDocs markdown source.
documentation-depth caveat · repository tree inspection · documented
The record remains useful for source discovery while preserving the limits of the public documentation.
Source note: BadgePiratesLLC/CactusCon13 repository metadata and top-level tree.
documentation/lore · primary wiki · historical
The hidden-beacon mechanic is source-backed, while exact participant gameplay reconstruction remains partial.
Source note: EMF Badge Wiki SiNE page.
dual-badge consolidation caveat · official archive and project logs · documented with caution
Readers see the two-source-backed badge designs without treating one board's hardware, firmware, or production state as universal to the other.
Source note: LayerOne HHV 2015 Electronic Badge section and CharlieX Hackaday.io project.
dual-module assembly choice · designer writeup · historical
The record names both options so readers do not infer every badge had the same radio-module build.
Source note: OSHCamp23 Badge writeup.
e-paper app constraints · app writeup · historical
This is useful lore for app-store records: the badge could run surprising software, but display technology shaped what was practical.
Source note: SpritesMods e-ink Gameboy writeup.
earlier-lineage caveat · source-limited · documented; monitor newly surfaced archives
CactusCon 2012-2013 and 2015-2016 stay explicit negative coverage until primary event pages, ticket text, badge-team archives, photos with reuse rights, repositories, or other artifact-level public sources surface.
Source note: CactusCon 2019 registration update, Robot Ambassador CactusCon PCB Badges writeup, Ratil.life Hacking and Skydiving writeup, Arizona LoCo Team September 2018 notes, and current badge.gallery source standards.
early platform · primary wiki · historical
Useful context for how much of later badge culture grew from visible, community-maintained troubleshooting.
Source note: EMF 2012 badge wiki.
electronic badge not proven · official guide but intentionally narrow · classified as identity artifact
The dossier preserves the pandemic-era badge/lanyard artifact without upgrading it into unsupported electronics.
Source note: RC14 Quick Guide.
electronic badge not proven · source-backed but incomplete · classified as physical identity artifact
The dossier preserves ROOTCON 17 as an attendee identity artifact and avoids upgrading the record into unsupported electronics.
Source note: RC17 Conference Overview, RC17 Pocket Guide, and ROOTCON 17 Art directory.
electronic badge not proven · source-backed but incomplete · classified as 3D-printable artifact
The dossier is modeled as a 3D-printable badge artifact instead of upgrading the record into unsupported electronics.
Source note: ROOTCON 18 archive, media directory, Badge directory, and Badge/STL directory.
electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact
The dossier preserves Zer0Con 2024 as an admission-badge availability record without inventing electronics or a physical credential design.
Source note: Zer0Con 2024 archive and POC Security official update trail.
electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact
The dossier preserves Zer0Con 2025 as an admission-badge availability record without inventing electronics or a physical credential design.
Source note: Zer0Con 2025 archive and POC Security official update trail.
electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact
The dossier preserves Zer0Con 2026 as an admission-badge availability record without inventing electronics or a physical credential design.
Source note: Zer0Con 2026 official page and POC Security official update trail.
electronic-badge evidence gap · source-backed limitation · documented; monitor future updates
The catalogue classifies this as a conservative conference identity artifact instead of an electronic badge or badgelife project.
Source note: BSides Reykjavik sponsorship packages and 2026 event pages.
event and firmware inventory caveat · repository metadata and decoded source files · needs archive/event-page recovery
Event and software claims stay bounded to the repository, README, developer guide, visible source tree, and decoded representative files instead of inventing event logistics or treating the repository as a fully inventoried production archive.
Source note: ElectronicCats/Badge-BugCON2023 repository metadata, README, firmware/readme.md, firmware tree, and current BugCON site recheck.
event scope caveat · official summit page plus badge repository · documented
The event and badge are included, but distribution and admission-credential claims remain conservative.
Source note: GreyCTF Summit 2025 page and NUSGreyhats/greybadge25 README/release trail.
event-context caveat · corroborated public sources · documented
The event edition is named by year and kept source-scoped rather than assigning an unsupported CactusCon edition number.
Source note: Robot Ambassador writeup and Malware Analysis and Forensics CactusCon April 4 2014 slide page.
event-context depth caveat · repository metadata and README · needs archive/event-page recovery
Event claims stay bounded to BugCON 2022 CDMX and the public badge repository instead of inventing dates, venue, ticket tier, or distribution scope.
Source note: ElectronicCats/Badge-BugCON-2022 repository metadata, README, and current BugCON site recheck.
event-context gap · source-backed but incomplete · needs archive recovery
The record remains useful as a badge-art lineage entry while leaving event logistics and artifact distribution open for archive recovery.
Source note: Current Ekoparty site check and official media attachment pages.
event-network dependency · primary docs · historical
Post-event use depended on either successful event-time setup or manual reflashing.
Source note: Disobey 2019 Badge.Team docs.
event-network limitation · primary docs · historical
Hatchery/app workflows depended on network context, so event-time and post-event behavior should be documented separately.
Source note: Disobey 2020 Badge.Team docs.
event-software caveat · project-owner writeup · documented
The entry separates source-backed plans, public interpreter code, and final-event uncertainty.
Source note: HackRVA RVAsec 8 layout post.