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.
privacy-sensitive ticketing · official ticketing page · documented
This is useful lore for an identity-artifact dossier because the access marker deliberately minimized personal-data handling while satisfying campsite logistics.
Source note: Camp++ 2024 tickets page.
production crunch · event retrospective · historical
This preserves the operational reality behind the badge, not just the attendee-facing utility.
Source note: BruCON retrospective.
production firmware caveat · source-backed · documented
The record treats the badge as a living event platform and avoids implying that every public firmware artifact represented a fully settled pre-production state.
Source note: Hackaday production article and build article.
production issue · project-owner logs · documented
The entry preserves real production and firmware bring-up caveats that matter for surviving badges and reproduction attempts.
Source note: AND!XOR DEFCON 24 Badge Hackaday.io production and radio/LED logs.
production rework caveat · primary assembly guide · historical
The record preserves production reality and warns future builders that surviving boards may differ from repository files.
Source note: Thomas Flummer 35C3 badge assembly instructions.
production scramble · attendee-reported · documented
The record preserves manufacturing and logistics context as part of the badge's historical importance rather than presenting it as a frictionless production run.
Source note: MaxVT ShmooCon 2018 conference notes.
production scramble and repair caveat · badge-team source · documented
The record preserves the practical production history and avoids presenting the badge as a fully polished commercial batch.
Source note: TechMaker NoNameBadge 2019 making-of post.
production supply-chain caveat · badge-maker writeup · historical
The record preserves production reality without overstating it into a failure or delivery controversy.
Source note: Badge Pirates CactusCon 11 Badge writeup.
production throughput caveat · primary project log · historical
Fri3d 2018 belongs in the operational history of camp badges: even a strong design still had small-run manufacturing throughput constraints.
Source note: Ph0xx Hackaday.io mass-production project log.
production triage caveat · primary production log · documented
The record preserves the badge as a real distributed artifact with documented production yield and rework constraints rather than treating the design as frictionless reference hardware.
Source note: AND!XOR DC27 production log.
production-depth caveat · source-backed but historical · needs board-revision audit
The dossier records verified hardware/software behavior and image provenance while avoiding unsupported production-run or board-revision claims.
Source note: CCHS Melbourne LoliBot repository, Freetronics product page, and MicroPython tutorial.
programming prerequisite · primary docs · documented
The badge taught more than soldering, but the software path depended on a working microcontroller-programming toolchain.
Source note: BSides PR 2019 Badge Documentation programming section.
programming-access caveat · repository README · documented
The catalogue presents the badge as reflashable while preserving the practical recovery boundary for surviving units.
Source note: LayerOne2023 README DFU and optional programmer sections.
programming-access caveat · repository README · documented
The catalogue presents the badge as hackable and source-backed while preserving the practical hardware access needed to modify surviving units.
Source note: LayerOne_2024 README programming and flashing sections.
programming-station fallback · project-owner writeup · documented
Badge updates were handled manually at the event with a Bluetooth barcode scanner, local script, CC Debugger, and programming jig.
Source note: Official PN26 Electronic Badge writeup.
prospectus-to-artifact boundary · source-backed but incomplete · documented caveat
The entry keeps component-level fields empty until official post-event or repository evidence supports them.
Source note: BSides Brisbane 2026 prospectus, ticketing page, and LinkedIn updates.
prospectus-to-shipped caveat · mixed ticketing and prospectus evidence · documented caveat
The catalogue treats the electronic-badge wording as planning/prospectus evidence unless a final organizer post, repository, or attendee technical writeup is recovered.
Source note: BSides Brisbane 2025 Humanitix ticketing and 2025 BNE prospectus PDF.
prototype software maturity · official badge guide · historical
The record treats 0.7 as a real event badge and prototype board while separating Digispark-compatible operation from later HIDIOT 1.0 behavior.
Source note: 44CON Getting Started With Your HIDIOT Badge.
prototype-photo caveat · secondary press source · documented
The catalogue avoids binding the record to a specific public preview photo until an exact production-badge image is cleared.
Source note: Wired DEF CON 16 preview.
prototype-run caveat · primary author source · documented
The record does not imply universal attendee distribution or a polished PCB production batch.
Source note: CKN AfricaHackOn 2017 badge writeup.
prototype-to-final caveat · badge-team logs · documented with caution
The catalogue records the source-backed architecture and car-hacking direction while avoiding unsupported claims about every final shipped component, firmware image, or quantity.
Source note: LayerOne HHV archive, Hackaday.io project details, and project logs.
prototype-to-production caveat · badge-team logs · documented with caution
The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, firmware image, quantity, or attendee role.
Source note: LayerOne 2015 Badge details and Building badges log.
prototype-to-production caveat · badge-team logs · documented with caution
The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, production quantity, or assembled variant.
Source note: LayerOne 2016 Conference Badge project and May 2016 project logs.
public-demo firmware boundary · source-backed but scoped · documented
The software description separates the recovered demo archive from the full shipped event firmware so the record does not overstate public source completeness.
Source note: Hackaday.io THOTCON 0xD project and `thotcon-examples` README.
public-source scope caveat · source-backed but compact · documented
The catalogue records verified badge surfaces and leaves deeper event-specific artifact inventory for future work.
Source note: NorthSec 2024 badge README and repository tree.
radio configuration · primary docs · documented caveat
The platform needs region-aware documentation and defaults for legal and reliable LoRa use.
Source note: Konsool LoRa settings docs.
radio/cellular · primary wiki and talk · historical
Useful reminder that badge RF/cellular features can be field-sensitive.
Source note: TiLDA MK4 wiki and The making of TiLDA Mk4 talk.
recovered-wrap-up availability · public search/archive recovery · monitor for stable mirror
Future maintainers should preserve a stable archive citation or replacement official mirror before adding richer details.
Source note: Security BSides Athens 2024 Recap / Wrap-Up public search and BSides community file path.
recovery workflow · primary docs · documented
Good recovery docs reduce the risk that app or firmware experiments permanently strand an attendee's badge.
Source note: Fri3d 2024 badge documentation.
regional compliance · manufacturer update · in progress
This is useful operational context for an open badge-derived platform becoming a purchasable handheld.
Source note: Nicolai Electronics Tanmatsu March 2025 update.
registration and capacity context · primary FAQ · documented
Badge pickup and identity workflow should be read alongside the event's registration and capacity-control model.
Source note: GPN23 FAQ.
release and source inventory · repository documentation · needs deeper artifact inventory
Software and production claims stay tied to README, release names, public hardware trees, and the named SDK branch rather than treating the repository as a fully inventoried production archive.
Source note: ElectronicCats/badge-bugcon-2025 README, releases page, hardware trees, and SDK branch.
remaining hardware caveat · source-backed but intentionally narrow · BOM and production notes recovered; still needs shipped-count and image provenance
The dossier records the verified interaction, production, and technical-archive surface while avoiding unsupported production-scale and image-provenance claims.
Source note: HITCON 2025 PCB Badge guide, HITCON agenda page, john0312/hitcon-pcb-badge repository, JLCPCB BOM, and production notes.
remote-edition context · official source · documented
The record focuses on the public electronic badge, game flags, and development-board behavior rather than unsupported hallway-distribution details.
Source note: NorthSec past editions and 2021 badge page.
remote-event classification · official event page · documented
The record models it as a remote-event input badge and avoids ordinary attendee-distribution assumptions.
Source note: KernelCon 2021 Hack Live page and Hacker HotKey README.
render scope caveat · manual image review · documented
The record still prefers a future licensed original documentary photo if one appears, but the current image is source-backed upstream material rather than generated, approximate, social-media, or placeholder art.
Source note: Manual review of ElectronicCats badge-EKOParty-2024 repository images and badge.gallery image policy.
repairability · primary docs · ongoing
The maintenance record matters because reusable camp badges only stay useful if spare-part and repair workflows survive after the event.
Source note: Tildagon Replacing Components documentation.
replay hardware boundary · repository documentation · documented
The record distinguishes the conference CTF BADge from compatible at-home replay boards and preserves the hardware-debugging requirement without overstating universal compatibility.
Source note: therealdreg/hcon2026hwctf README.
repository and image license caveat · GitLab metadata and repository pass · no visible reusable image basis
Repository files and article photos are cited as evidence only; no badge image is copied locally without explicit image rights, attribution, and processing provenance.
Source note: TechMaker NoNameBadge 2019 article, GitLab project metadata, and badge.gallery image policy.
repository and image license caveat · GitLab metadata and source pass · no visible reusable image basis
The record stays image-free until a rights-cleared original photo or official upstream raster render is recovered.
Source note: TechMaker NoNameBadge 2020 article, GitLab project metadata, and badge.gallery image policy.
repository archive gap · current source trail · partial software hub recovered
The record can document the software hub without overstating it as a full production archive.
Source note: ConfiBadge 2026 Badge Hub and Bhub package hub.
repository archive status · GitHub repository metadata · documented
Primary claims come from the repository and README rather than relying on the expired-certificate homepage for evidence or images.
Source note: GitHub repository metadata and local TLS check on nodeconfeubadge.org.
repository license caveat · GitHub API review · documented
Repository photos and renders are retained as evidence only unless a separate explicit image license or permission basis is recovered.
Source note: GitHub API metadata for Hack-a-Day/2024-Supercon-8-Add-On-Badge.
repository license caveat · GitHub API recheck · no detected license
Repository files are cited as public evidence, but local reuse is limited: no repository images, artwork, hardware files, firmware, or slides are copied into the catalogue as licensed assets.
Source note: NUSGreyhats/greybadge25 GitHub API metadata and repository tree recheck.
repository license caveat · GitHub API recheck · no detected repository license
The record stays image-free and avoids publishing repository badge images or firmware assets locally without explicit reuse rights.
Source note: GitHub API metadata for HackRVA/badge2026 and badge.gallery image policy.
repository license caveat · current repository audit · needs license clarification
The catalogue cites repository facts as public evidence but does not reuse repository images, hardware files, or code assets as licensed local content.
Source note: rhgndf/hfsdr GitHub API repository metadata and contents listing, rechecked 2026-05-21.
repository license caveat · GitHub API and repository audit · needs explicit license
The catalogue can document firmware behavior while avoiding unsupported reuse claims for source or media.
Source note: lanrat/PacketHackVillageHitBBadge2021 repository and GitHub metadata.
repository license caveat · repository audit · needs explicit project license
The catalogue can cite the repository as evidence while keeping image publication and license-sensitive reuse conservative.
Source note: pjranki/bpod repository file tree and badge.gallery image policy.
repository license caveat · public repository but incomplete licensing · needs explicit project license
The catalogue can cite the repository as evidence while avoiding image or source reuse beyond attribution and linking.
Source note: BSidesPerth/Badge-2017 repository and badge.gallery image policy.
repository license caveat · repository README · needs component-level review
Firmware and hardware facts can be sourced from the repository, but code-reuse and asset-reuse claims should not be collapsed into one blanket license statement.
Source note: disobey-badge-2025-game-firmware README.