BruCON

BruCON 0x0A

The 10th BruCON edition, with an electronic badge documented through the event retrospective and public GitHub repository.

Belgium · Belgium · 2018

BruCON 0x0A Badge

BruCON's 10th-edition electronic badge, documented as a schedule, venue-map, reminder, alcohol-sensor, and public ESP-IDF/KiCad badge project.

Lifecycle

Add-ons & Upgrades

BruCON 0x0A Badge archived source

backend lifecycle

Server schedule and enrollment backend

The server tree records the PHP/MySQL workflow around badge enrollment, nicknames, alcohol-sensor data, and schedule JSON generated from BruCON's Sched export.

Compatibility: BruCON 0x0A Badge

BruCON 0x0A Badge archived con build

firmware lifecycle

Con firmware release

The repository README links the BruCON0xA release as the firmware version installed on the conference badge, preserving the shipped build rather than only source head.

Compatibility: BruCON 0x0A Badge

BruCON 0x0A Badge archived source

hardware manufacturing source

KiCad and Gerber production package

The repository preserves the KiCad project, board files, schematic, generated Gerbers, and position files needed to study or reproduce the badge PCB.

Compatibility: BruCON 0x0A Badge

Operational history

Issues & Camp Impact

missing rights-cleared image · local project policy · needs licensed original replacement

No BruCON 0x0A Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The Belgium record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

source-depth caveat · event retrospective and repository review · schematic-backed review still useful

The repository review confirms the source tree, firmware release, KiCad/Gerber package, LCD, ADC, Wi-Fi, URL, menu, map, schedule, and server-side workflow, but the page still avoids unsourced chip-level claims that require careful schematic/BOM extraction.

The dossier is now stronger than a first-pass retrospective record while still keeping component lists tied to inspectable files.

Resources

Sources