BSides Peoria 2025 · United States · 2025
Maker-published one-off ESP32 badge-challenge device
A source-bounded independent BSides Peoria 2025 challenge-badge dossier. Technet8394's event-period public HackTheBadge README calls the work "My ESP32 code for the BSides Peoria Badge Challenge 2025." Its later source release documents an ESP32, a 240×320 ILI9341 TFT panel, two batteries, and wiring. BSides Peoria's official 2025 announcement establishes the October 25 Bradley University event, and its 2026 organizer retrospective says the prior edition drew nearly 350 people and had electronic badges. No reviewed organizer source links this specific maker project to a main attendee badge, official issuance, or completed handoff, so the catalogue keeps it as an independent event-associated challenge device.
People
The organizer's official pages establish the 2025 event setting and later retrospective electronic-badge context. This credit does not assign HackTheBadge design, manufacture, allocation, approval, or image-rights authority to the organizer.
SourceThe public account owns the HackTheBadge repository and commits. This limited source-publisher credit does not infer a legal name, organizer position, sole hardware/firmware authorship, manufacture, distribution, conference authorization, or image-rights ownership.
SourceIt preserves a public, time-bounded maker archive for a real local security-conference badge challenge while keeping its source-declared event relationship separate from an unproven official attendee-badge, access-credential, or distribution claim.
The maker's event-period README identifies an off-the-shelf ESP32, a 240×320 ILI9341 TFT panel, wiring, and two batteries. The later public Arduino source uses the ILI9341 display library and SPI pins. Neither source establishes a custom PCB, enclosure, wearable form, exact ESP32 module, battery chemistry/capacity/protection, charger, power budget, final component substitutions, assembled-unit count, or the hardware configuration used at the conference.
A public Arduino-style source file contains a Wi-Fi and local web-server/display challenge surface. The maker describes the archive as a one-off challenge project and does not publish a compiled binary. The catalogue records source-level context only: it does not provide connection details, credentials, endpoints, challenge answers, operating steps, deployment instructions, or claim that the visible source matches an event device.
The repository was created before the October event and its public code was added after it. BSides Peoria's later organizer retrospective says that the previous year's electronic badges were still being discussed, but it does not name HackTheBadge, its author, its form, its recipient group, or a badge challenge. The project therefore remains a maker-declared event-associated artifact rather than a confirmed official conference badge.
Source-backed hardware metadata
Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.
Technet8394's event-period public README calls HackTheBadge ESP32 code for the BSides Peoria Badge Challenge 2025. The organizer does not directly link the independent source to an official attendee or main badge.
Signal sourceThe event-period maker README identifies an off-the-shelf ESP32. It does not establish a final module, board revision, or conference-unit population.
Signal sourceThe post-event Arduino source includes Wi-Fi and a local web-server surface. This does not establish live event deployment, network parameters, credentials, user-data practice, or support.
Signal sourceThe maker README names a 240×320 ILI9341 TFT panel. It does not establish a particular panel revision, final wiring, display behavior, or device parity.
Signal sourceThe post-event main.ino archive provides an Arduino-style source surface. It does not establish a tagged event image, reproducible build, source-to-device mapping, or safe reconfiguration workflow.
Signal sourceRepair, preservation, and legal lab context
Parts, tools, and supplies that match this badge's documented hardware, protocols, or preservation needs. These are category-level recommendations, not compatibility guarantees.
Display modules and related parts for repair and preservation planning.
This badge has a documented display signal. Matched technical signals: TFT.
Vendor link · selected for technical relevance
Headers, sockets, and connector supplies for display repair or replacement work.
Display headers and connectors are useful for repair and preservation planning. Matched technical signals: TFT.
Vendor link · selected for technical relevance
Debug probes for ARM/RISC-V badge development, recovery, and documentation.
Debug probes can support authorized recovery, firmware work, and documentation for microcontroller badges. Matched technical signals: ESP32.
Vendor link · selected for technical relevance
USB serial adapters for logs, recovery, and firmware documentation workflows.
This badge has a documented microcontroller platform where serial logs or flashing workflows may be relevant. Matched technical signals: ESP32.
Vendor link · selected for technical relevance
Anti-static bags and storage supplies for preserving loose badge PCBs and sensitive components.
This is documented as an electronic or hardware artifact where anti-static storage can support preservation. Matched technical signals: Electronic badge.
Vendor link · selected for technical relevance
Lifecycle
The pre-event README names an off-the-shelf ESP32, a 240×320 ILI9341 TFT panel, wiring, and two batteries. This establishes a maker-stated parts surface only; it does not prove a PCB, enclosure, wearable form, final board/module, battery chemistry/capacity/protection, power budget, or an event-unit configuration.
SourceThe post-event Arduino-style source contains Wi-Fi, local web-server, SPI, preferences, and ILI9341 display code. The catalogue records this high-level source context without publishing connection details, credentials, URLs, endpoints, challenge answers, access steps, or a claim that the visible code was deployed at the event.
SourceThe repository's visible history has an event-period README before the October 25 conference, while the main Arduino source appears in a November 21 post-event commit. The chronology preserves public evidence without equating the later checkout with a dated event binary or documented final artifact.
SourceOperational history
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The catalogue models a real maker-declared event-associated challenge artifact rather than presenting it as organizer-issued, attendee-wide, admission-bearing, or independently confirmed electronic hardware.
The entry records a narrow source-backed electronic challenge-device outline without treating it as a reproducible build, a safe assembly guide, a uniform physical badge, or a completed production run.
The catalogue does not expose connection or challenge details, claim a current working service, offer configuration guidance, infer a released event firmware, or treat public source visibility as a broad license or support commitment.