DEF CON 34 · United States · 2026
Pre-event independent ESP32-C3 touchscreen badge project for DEF CON 34
Aask42's public MidWestCoastBadge repository identifies an independent MidWestCoast Badge project, labels its firmware as DEF CON 34 badge firmware, and frames it around a MidWestCoast Party / IoT-hacking context. Its commit-pinned firmware README names an ESP32-C3 driving a 240×320 ST7789 IPS panel plus a capacitive touch controller at I2C address 0x15, with swipe-and-tap controls and no buttons. A project MVP note identifies the Arduino/C++ tree as the current implementation. DEF CON's own registration page independently establishes the August 6-9, 2026 Las Vegas conference context. These sources support a real pre-event independent electronic-badge project associated by its publisher with DEF CON 34, not proof of final physical units, party or event authorization, DEF CON issuance or endorsement, allocation, price, delivery, attendance, admission, deployed firmware, or reusable-image rights.
People
The public GitHub namespace publishes the reviewed MidWestCoastBadge source. This is source attribution only; it does not establish a real-world identity, party or DEF CON affiliation, design/manufacturing role, event authorization, delivery responsibility, or image-rights authority.
SourceThis record retains a current public maker source that exposes a specific MCU, display family, touch interface, and intentionally buttonless interaction model before the event. It preserves that narrow evidence without turning an in-progress source tree into a confirmed physical run, event program, party authorization, field-tested device, or official credential. The resulting entry is more useful than a vague teaser and more accurate than an inferred hardware teardown.
The public firmware README identifies an ESP32-C3, a 240×320 ST7789 IPS panel, and a capacitive touch controller at I2C address 0x15. It says swipes and taps drive the interface and that the badge has no buttons. The reviewed source snapshot does not establish the exact ESP32-C3 module, panel or touch-controller part number, PCB, antenna, battery, charging or USB path, power budget, connectors, dimensions, enclosure, schematic, BOM, Gerbers, assembly method, production revision, electrical limits, safety guidance, compliance evidence, or a final physical-unit configuration.
The repository publishes an Arduino/C++ implementation and its MVP note describes that tree as the current source. The reviewed material does not establish a tagged attendee release, final compiled image, reproducible build result, device-specific configuration, flashing/recovery guide, final interaction behavior, companion-app release, deployment status, support policy, software dependency inventory, security review, privacy notice, or a completed distribution build. The source tree is recorded as source evidence, not as proof that a particular firmware image ran on event hardware.
The repository calls the artifact a badge for the MidWestCoast Party and describes an IoT-hacking setting, while its firmware documentation calls it DEF CON 34 badge firmware. Those are publisher-supplied project labels. Neither the repository nor DEF CON registration establishes a party organizer relationship, a planned party date or venue, DEF CON organizer affiliation, authorization to operate or distribute at the event, an attendee entitlement, a registration benefit, access control, or a completed on-floor handoff.
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.
Aask42's public README identifies the MidWestCoast Badge as DEF CON 34 badge firmware driving a display and touch interface; this signals a source-documented electronic badge project, not a confirmed final physical run.
Signal sourceThe commit-pinned firmware README specifically names an ESP32-C3. It does not identify a final module, board, or shipped hardware configuration.
Signal sourceThe commit-pinned firmware README identifies a 240×320 ST7789 IPS panel. It does not identify a panel variant, board integration, calibration, or final unit.
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: ST7789 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: ST7789 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-C3.
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-C3.
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 README says the firmware targets an ESP32-C3 driving a 240×320 ST7789 IPS panel with a capacitive touch controller at I2C 0x15, controlled by swipes and taps with no buttons. It does not identify exact modules, panel/controller variants, PCB integration, power path, touch calibration, gesture thresholds, final unit behavior, or hardware test results.
SourceThe project's MVP note identifies the Arduino/C++ tree as the live implementation and describes visual/interactions work. This establishes accessible current project source, not a tagged release, reproducible build, compiled attendee image, device configuration, flashing/support workflow, final feature set, or proof that it ran on a distributed badge.
SourceThe public repository calls the project a MidWestCoast Badge for a MidWestCoast Party and its firmware README labels the code DEF CON 34 badge firmware. These labels establish a publisher-supplied pre-event association, not party operation, organizer affiliation, date or venue, DEF CON endorsement, on-floor authorization, allocation, sale, pickup, attendee entitlement, or access control.
SourceOperational history
The record remains an independently published pre-event project associated by its source with DEF CON 34, not an official conference badge, party credential, organizer program, or access item.
The catalogue links public project material without treating source visibility as a completed firmware release, security guarantee, network/data practice, or reusable code grant.
The entry reports the named firmware target and interaction surface without inferring a complete electrical design, reliable touch behavior, safe power path, or compatibility with external hardware.
The record remains image-free rather than copying repository media, code screenshots, event graphics, social posts, renders, placeholders, or generated approximations.
The catalogue preserves a real source-documented electronic-badge project without presenting it as a delivered product, attendee issue, or verified physical run.