BSides Fort Wayne 2026 · United States · 2026
Optional organizer e-badge ticket add-on paired with a distinct 2026 source archive
BSides Fort Wayne's organizer ticket page offered a $30 optional e-badge add-on for the June 6, 2026 conference. The public BSidesFW2026Badge repository has distinct June 2026 activity, including a dedicated STLs/2026 enclosure set and default badge data changed to 2026, together with MicroPython source and inherited V4 technical documentation. The evidence links a real optional e-badge offer to a 2026 source archive without claiming a confirmed sale, physical receipt, firmware deployment, or exact final hardware configuration.
People
The June 6 commit under luke-gilsinger changes the source default badge data to 2026. This is a scoped public repository contribution credit, not a claim of hardware design, deployed firmware ownership, production, or distribution authority.
SourceThe June 4 commit under David Prows adds the STLs/2026 mechanical-source set. The repository root MIT LICENSE also names Copyright (c) 2025 David Prows. This credit is limited to public commit and license evidence, not a claim of full badge-design, manufacture, or fulfillment ownership.
SourceThe BSidesFortWayne organization profile identifies the yearly Fort Wayne information-security conference, links the official site, and owns the public BSidesFW2026Badge repository. This is an organizer/source-publisher credit, not a claim of individual design, manufacture, fulfillment, or image-reuse authority.
SourceIt keeps the Indiana Security BSides lineage current while separating a documented 2026 ticket offer and public source archive from the older 2025 documentation preserved in the same repository, rather than silently re-labelling inherited specifications as a confirmed 2026 production device.
The current 2026 repository includes a V4 technical document inherited from the 2025 lineage. That document describes an ESP32-WROVER-E-N8R8 system with USB-C and CH340C programming hardware, seven WS2812B LEDs, PCA9535-backed buttons, LIS3DHTR accelerometer, LiPo monitoring/charging/protection, a 3.3 V buck-boost stage, display headers, buzzer, and expansion pads. The 2026 source archive does not separately prove that this exact board revision, component population, power configuration, or safety/production validation applied to a ticketed 2026 unit.
The public 2026 repository includes MicroPython source, applications, custom-firmware documentation, and badge-challenge material. A June 6 source commit changes the default badge identity data to 2026. The repository has no GitHub tag or release, and the reviewed sources do not establish that the current tree or custom firmware binary was the final deployed image on any 2026 e-badge.
The official BSides Fort Wayne home identifies a June 6, 2026 yearly information-security conference, while its organizer ticket listing advertised the e-badge as a separate $30 add-on. The public BSidesFW2026Badge repository was created in March 2026 and has June source activity: David Prows added a STLs/2026 mechanical set on June 4, and luke-gilsinger changed default badge data to 2026 on June 6. Its root README nevertheless retains BSidesFW2025Badge and 2025 wording, so this record preserves a deliberate revision boundary instead of implying that every inherited guide describes the final 2026 artifact.
Lifecycle
A June 6 commit changes the default badge identity title in the repository source to 2026. It is direct evidence of a 2026 software revision, not evidence that the current tree was flashed or run on a particular physical e-badge.
SourceThe organizer ticket listing advertises a $30 optional BSidesFW 2026 e-badge add-on for the June 6 event. This establishes the offer and price snapshot, not order count, payment, manufacture, inventory, pickup, shipping, physical receipt, replacement, or attendee-wide distribution.
SourceThe repository provides MicroPython application source and firmware documentation that describes compiled C modules and CTF challenge support. No reviewed release, tag, post-event guide, or device record verifies the production image or an owner-support path for 2026 units.
SourceThe current repository includes V4 documentation for an ESP32-WROVER platform with LEDs, buttons, accelerometer, LiPo/power circuitry, display headers, buzzer, and expansion pads. Its 2025 wording and old schematic link keep this as context rather than a claim about every optional 2026 e-badge unit.
SourceA June 4 commit adds a 2026 3MF badge file plus screen-cover and rounded/squared battery-case STL files under STLs/2026. The files establish published mechanical-source material, not a fabrication run, final print settings, assembly result, or image-reuse clearance.
SourceThe root LICENSE is MIT and names David Prows with a 2025 copyright. The catalogue records that source license while keeping the separate requirement for a selected image's source URL, reuse basis, attribution, and processing notes before publishing a badge hero image.
SourceOperational history
2026-specific source changes are recorded precisely, while older hardware and guide material remains labelled inherited context rather than silently upgraded into a production claim.
Readers can inspect inherited technical context without treating it as a safety validation, complete specification, compatibility guarantee, or reproducible final device.
The record treats the code as a valuable public archive without asserting a final official firmware release, production flash state, challenge outcome, or supported owner-update path.
The dossier credits only the named organization and narrowly evidenced source contributions without inferring authorship, manufacturing responsibility, distribution control, or image permission.
The catalogue may link the source archive and license while maintaining the separate image-rights threshold for any future local badge asset.
The record remains source-backed and image-free rather than copying Eventbrite media, GitHub previews, repository logos, README assets, STL screenshots, schematics, generated art, or approximate badge imagery.
The catalogue can document the real e-badge offer without saying anyone purchased, received, used, or was universally issued the artifact.