BSides Fort Wayne
The June 7, 2025 Indiana Security BSides edition whose first-hand badge-team writeup documents an attendee badge, badge talk, and CTF challenge path while the public organization repository preserves the badge hardware and firmware archive.
Fort Wayne, Indiana · United States · 2025
BSides Fort Wayne 2025 had an electronic conference badge documented by a first-hand badge-team writeup and a public organization repository, with ESP32-WROVER hardware, dual SPI display headers, seven WS2812B LEDs, accelerometer, buzzer, LiPo charging, MicroPython firmware, and badge CTF challenge apps.
Lifecycle
The repository includes multiple `badgechal` application files and firmware documentation stating that the custom C modules are required for CTF challenges.
The board exposes seven WS2812B RGB LEDs and a button set using IO0 plus a PCA9535 I2C expander for six additional controls.
The public app tree includes menu, settings, schedule, Tetris, analog clock, battery monitor, system monitor, and other badge applications.
The hardware specification identifies the ESP32-WROVER-E-N8R8 as the badge controller with 240 MHz dual-core CPU, 8 MB flash, and 8 MB SPI RAM.
The hardware documentation maps two SPI screen headers with separate DC, reset, chip-select, and display-enable control signals.
The firmware README documents a custom MicroPython 1.26.0 image with compiled badge-challenge modules and a Russ Hughes GC9A01 C display driver.
The specification documents a LIS3DHTR accelerometer, LiPo voltage monitoring, DW01A protection, TP4056 charging, TPS63060 buck-boost conversion, and a PWM buzzer.
Operational history
Keep the source note explicit and prefer archive/search snapshots or future official archive pages if a dedicated 2025 official page becomes available.
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.
The record remains source-backed and image-free rather than copying blog media, logos, screenshots, schematic snippets, generated art, or approximate badge imagery.
Hardware claims use the current hardware specification text and repository tree instead of relying on the stale embedded link alone.