DEF CON 34 · United States · 2026
Independent planned ESP32-S3 battle-game badge project for DEF CON 34
Cyber Professionals Enthusiast Club's public `DC34-Mech-Badge` repository calls the work the DC 34 MechBattle Badge, describes it as the second iteration of menu and game logic for a CPEC DC34 badge offering, and says it is not final; its GitHub description explicitly calls it a DEFCON 34 Mech Badge by CPEC. A second CPEC repository publishes an in-progress PlatformIO/Arduino game codebase targeted at an Adafruit Feather ESP32-S3 no-PSRAM board, with source-level display, Bluetooth Low Energy, QR, and sound surfaces. A third CPEC repository says it contains design files for SAO plug-in modules for the CPEC DC 34 badge; its commit-pinned source tree includes native KiCad project, PCB, and schematic paths with fist, gatling, laser, missile, panel, and sword filenames, an Arduino source file, and BOM/placement artifacts. The linked game-mechanics document is also a draft. These primary sources establish a real independent planned badge and companion-add-on design trail, not final physical hardware, manufactured units, electrical compatibility, availability, event authorization, DEF CON organizer affiliation, admission, deployed radio behavior, or reusable-image rights.
People
CPEC's public repositories name the DC 34 MechBattle Badge and the related game source. This is a source-publisher credit only, not a statement of individual hardware, firmware, art, manufacturing, distribution, DEF CON organizer, or image-reuse ownership.
SourceThis record preserves a current independent BadgeLife-style project at the point where its authors have published enough code to establish an artifact and a specifically scoped companion add-on design trail, but not enough evidence to turn source targets into finished devices. It distinguishes an explicit project name, draft code, and native companion files from the things a repository cannot prove: an assembled board, a safe power/radio design, a working host interface, a completed game, a distribution plan, or an official conference role.
The in-progress game repository's PlatformIO configuration targets `adafruit_feather_esp32s3_nopsram`; its display source initializes a 240 by 320 ST77xx-class screen, and its sound source is written around a buzzer output. Those source targets support a narrow intended ESP32-S3/display/sound platform statement. Separately, the companion SAO repository contains native KiCad project, PCB, and schematic paths for fist, gatling, laser, missile, panel, and sword-named variants, plus BOM and placement artifacts. That is source-file evidence for a scoped companion design only, not proof that the main badge or any companion variant was fabricated, assembled, electrically compatible, functional, safe, final, or present in a physical event unit. No reviewed source establishes a complete main-badge schematic/BOM/Gerber archive, a final component population, battery or power design, radio antenna, enclosure, connector limits, test data, certification, or host-compatibility matrix.
CPEC's in-progress game source uses Arduino/C++, display and JSON libraries, NimBLE, QR-code support, and named menu, pilot-record, game-state, sound, and Bluetooth modules. The companion SAO tree also contains an Arduino source file, while the separate earlier repository calls its menu/game logic a second iteration and not final. None of the reviewed repositories releases a tagged final firmware image, build provenance, hardware-matched configuration, documented player-data/privacy behavior, stable radio or add-on protocol, user update/recovery path, test report, completed game rules, or explicit repository license. The catalogue therefore records public in-progress source surfaces, not a deployment guide, production firmware, interoperability guarantee, or security claim.
The first repository links a draft document titled M.E.C.H. Fighters / Modular Environmental Combat Hardware as game-design material. The companion repository calls its scope SAO plug-in modules for the CPEC DC 34 badge and its description refers to plug-in weapon and power-up designs. Those source labels establish a creative and companion framing only; they do not establish final playable content, mechanical/electrical behavior, any event programme, intended audience, third-party affiliation, distribution, prize, or a DEF CON activity. The project's DC34 naming and repository descriptions provide an independent DEF CON 34 association, not proof that the conference issued, funded, endorsed, or authorized it.
Lifecycle
The game repository references ST77xx display libraries, NimBLE, QR-code support, and a buzzer-oriented sound module. It does not publish a stable radio protocol, user-consent model, player-data practice, safe electrical design, final UI, host compatibility matrix, or proof that these modules ship together in a DEF CON artifact.
SourceCPEC's companion repository says it contains design files for SAO plug-in modules for the CPEC DC 34 badge. Its commit-pinned source tree contains KiCad project, PCB, and schematic paths for fist, gatling, laser, missile, panel, and sword-named variants, an Arduino source file, and BOM/placement artifacts. The catalogue records that scoped design-source availability without inferring a populated board, hardware behavior, wiring, pinout, firmware result, safe electrical envelope, standard/version match, or working connection to a CPEC badge.
SourceThe CPEC repositories publish menu, pilot-record, game-state, display, sound, and game modules, and the earlier repository calls its code a non-final second iteration. Those sources establish an in-progress planned interaction surface, not final gameplay, player outcomes, a completed CTF, physical controls, accessibility behavior, or a deployed event experience.
SourceThe game repository's PlatformIO configuration targets an Adafruit Feather ESP32-S3 no-PSRAM board with Arduino and a LittleFS configuration. This records an intended development target only; it does not identify a final badge PCB, assembly, controller population, storage, boot flow, power design, or a manufactured event unit.
SourceOperational history
The catalogue keeps the files attached to the MechBattle record as a source-published companion design trail without representing them as a plug-and-play accessory, a safe wiring or flashing guide, a completed add-on lineup, or a distributed DEF CON artifact.
The catalogue records a real named planned badge project and a source-published companion design trail, but does not turn source files into proof of physical, safe, completed, or distributed hardware artifacts.
The record remains image-free and does not reproduce draft lore, repository previews, screenshots, logos, board renders, or any generated/approximate badge image.
The badge is classified as an independent planned project associated with DEF CON 34, not an official conference badge, registration benefit, access credential, organizer-endorsed product, or confirmed distribution.
The record does not offer configuration or operating instructions, claim secure or private interaction, assert a released firmware, or treat public code as a license grant.
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.