Issues & Camp Impact · Hacker Con Badges

Easterhegg 2010 eHaserl note

workshop supply caveat · official wiki · historical

The wiki says the name-badge upgrade kit was already sold out and asks for a parts and supplier list, while also mentioning battery exchanges for people who did not receive the larger battery.

This records the logistical side of early badge workshops: kits, batteries, and replacement parts shaped the attendee experience.

Source note: EH2010 badge wiki Teileliste and Inbetriebnahme sections.

Hack&Roll 2026 Quack & Roll Badge note

workshop-firmware caveat · repository documentation · documented

The public code is a badge workshop/demo firmware that lights dice LEDs from button input, so it is not treated as proof of every firmware image or challenge shipped during Hack&Roll 2026.

The software section separates the recoverable ESP-IDF workshop code from any unrecovered event firmware or private production tooling.

Source note: firmware README and firmware/main/main.c.

Aerospace Village DC33 Aranya ESP32 Badge Board note

workshop-scope caveat · official workshop page · documented

The official schedule limited the SpiderOak Aranya workshop to 20 attendees because hardware was included for free.

The catalogue treats the board as a limited attendee-retained workshop artifact, not a village-wide or DEF CON-wide attendee badge.

Source note: Aerospace Village DEF CON 33 workshop schedule.

CampZer0 2013 Identity Artifacts note

wristband evidence boundary · official ticket-prices page · documented

The ticket-prices page lists event wristbands as an infrastructure cost, but the current source set does not document the physical wristband design or exact distribution workflow.

The record preserves the wristband planning signal while avoiding unsupported claims about a specific worn artifact.

Source note: CampZer0 ticket-prices page.

Hack Glasgow 2026 Attendee Name Badge note

write-in identity-artifact classification and physical-form gap · official 2026 FAQ and post-event statistics · event completed; attendee name/handle field documented; credential form unspecified

Hack Glasgow's FAQ says an attendee may write a handle or name on their badge, while its August 16 statistics update supports completion of the August 15 event. Neither source identifies paper, plastic, metal, lanyard, dimensions, printed design, barcode, QR code, RFID/NFC, display, PCB, components, battery, manufacture, quantity, or final physical form.

The record is deliberately modeled as a completed-event identity artifact rather than an electronic badge or a more specific physical credential unsupported by the organizer's public wording.

Source note: Hack Glasgow official 2026 FAQ, event page, and public statistics page.

RVAsec 2021 Badge note

year-specific source gap · source-limited · open

The public trail supports Badge Intro context and continuing HackRVA electronic-badge lineage, but this pass did not recover a 2021-specific public firmware repository, schematic, BOM, component list, production note, or final attendee guide.

The record avoids importing 2020 or 2022 technical details into 2021 without a year-specific source.

Source note: InfoconDB RVAsec 2021 and HackRVA badge overview.

Hak4Kidz Chicago 2026 Fun Badge note

youth-attendee allocation, event-outcome, and CTF-linkage boundary · official 2026 event page and flyer · past-date inclusion statement retained; issuance and delivery unrecovered

The flyer says youth attendees receive a fun badge, but supplies no recipient ledger, age or registration rules, adult or chaperone allocation, quantity, pickup or handoff details, delivery outcome, replacement process, or post-event confirmation. The home page's Time Travel: Capture the Flag wording is event context only and does not establish any badge-linked CTF function.

The record preserves a real organizer-published inclusion statement without turning it into proof that a particular youth attendee received an artifact or that it participated in the CTF.

Source note: Hak4Kidz Chicago 2026 official event page and flyer, reviewed 2026-08-05.

seeess DC33 Tipsy Badge warning

zap-mode operation caveat · primary README and firmware · documented

The public documentation says the first attempt should be seated and away from stairs or hard surfaces, the person wearing electrodes should control the zap button, and zap modes should run on batteries rather than USB power.

User-facing wording preserves the practical safety boundary around operating surviving badges or reproductions.

Source note: Tipsy Badge README Safe Use Conditions and Safety sections.

Overglade 2026 Zero-Power NFC E-Ink Badge note

zero-power, hardware, and firmware parity boundary · maker README and design journal · source design documented; final event-unit parity unverified

The maker's README and journal document a zero-power concept, RP2040, passive NFC, e-ink driver, USB-C, GPIO breakouts, and source trees, but do not identify a final attendee-unit revision, panel variant, assembled BOM, physical output, radio configuration, power behavior, active-NFC implementation, firmware image/release, provisioning record, participant configuration, or all-unit parity.

Hardware and software descriptions remain tied to the public design archive rather than promoted to a fully known, uniform, deployed event build.

Source note: Overglade-Badges README, JOURNAL.md, PCB tree, and firmware tree.