Issue dossier
CPEC's first repository explicitly says its code is not final, while the second is an active in-progress game repository. The third, scoped companion repository provides KiCad, BOM, and placement source assets, but no reviewed source supplies a provenance-backed photograph of a completed MechBattle or companion unit, a physical prototype account, manufacturing/order evidence, serial/revision log, assembly/test record, final hardware population, or completed event-unit confirmation.
A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.
Back to issues index
draft code and physical-artifact boundary · primary CPEC repositories · planned project and companion design sources; physical artifacts unverified
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.
- Badge
- CPEC DC34 MechBattle Badge
- Category
- draft code and physical-artifact boundary
- Severity
- note
- Confidence
- primary CPEC repositories
- Status
- planned project and companion design sources; physical artifacts unverified
- Timeframe
- pre-event source pass as of 2026-08-05
- Source note
- CPEC DC34 MechBattle, DC34 Mech Badge Game, and DC-34-Mech-SAO repositories.
commit-pinned public companion add-on design archive
Commit-pinned CPEC source whose README says it contains design files for SAO plug-in modules for the CPEC DC 34 badge. The tree includes native KiCad project, PCB, and schematic files with fist, gatling, laser, missile, panel, and sword names, an Arduino source file, and BOM/placement artifacts. It establishes a scoped companion design-file trail, not fabrication, populated hardware, pinout/electrical compatibility, working firmware, final revision, distribution, event authorization, or image-reuse permission.
Badge: CPEC DC34 MechBattle Badge
official event context
Official DEF CON registration source for the August 6-9, 2026 Las Vegas event context. It does not identify CPEC's project, endorse it, prove maker presence, authorize distribution, or make it an admission credential.
Badge: CPEC DC34 MechBattle Badge
primary in-progress badge source
CPEC's public repository explicitly calls this the DC 34 MechBattle Badge and the second iteration of menu/game logic for a CPEC DC34 badge offering. Its README says the work is not final; the GitHub description calls it a DEFCON 34 Mech Badge by CPEC. It does not establish a physical board, allocation, final firmware, event authorization, or image-reuse basis.
Badge: CPEC DC34 MechBattle Badge
primary in-progress game source
CPEC's public in-progress PlatformIO game repository targets an Adafruit Feather ESP32-S3 no-PSRAM board and contains display, BLE, QR, sound, menu, and game modules. Source code is evidence of intended software work, not proof that it was deployed on a physical badge, used at DEF CON, secure, privacy-preserving, compatible, or licensed for reuse.
Badge: CPEC DC34 MechBattle Badge
public companion add-on design repository
CPEC's public repository identifies itself as design files for SAO plug-in modules for the CPEC DC 34 badge. Its current repository surface is linked separately from the immutable source snapshot below; neither source establishes a fabricated board, published interface specification, final firmware, compatible host, distribution, event authorization, or image-reuse permission.
Badge: CPEC DC34 MechBattle Badge
source-linked draft design document
The first CPEC repository links this document as game-play mechanics material. It supplies draft creative context only and does not establish final gameplay, technical implementation, event programming, distribution, or rights in any media.
Badge: CPEC DC34 MechBattle Badge
Cyber Professionals Enthusiast Club · retrieved 2026-05-15
Draft game-design material linked directly from CPEC's MechBattle README. It corroborates an authored game framing but is not a final product specification, event schedule, rules release, distribution plan, technical archive, or image license.
Badge: CPEC DC34 MechBattle Badge
Cyber Professionals Enthusiast Club / GitHub · retrieved 2026-05-15
Commit-pinned primary CPEC source. Its README calls the repository design files for CPEC SAO plug-in modules for the CPEC DC 34 badge. Native KiCad files and BOM/placement artifacts identify a public companion design archive, while the root exposes no reviewed explicit license or release. It does not establish a final schematic correctness, fabricated board, interface version/pinout, electrical safety, compatible host, firmware outcome, sale/giveaway, DEF CON authorization, or image-reuse basis.
Badge: CPEC DC34 MechBattle Badge
Cyber Professionals Enthusiast Club / GitHub · retrieved 2026-05-15
Primary team-published source. Its README names the DC 34 MechBattle Badge, calls the code the second menu/game-logic iteration for a CPEC DC34 badge offering, says it is not final, and links the draft game mechanics. GitHub's repository description explicitly says DEFCON 34 Mech Badge by CPEC. It does not publish hardware design, availability, final firmware, licensing, production, or image-rights evidence.
Badge: CPEC DC34 MechBattle Badge
Cyber Professionals Enthusiast Club / GitHub · retrieved 2026-05-15
Primary CPEC game-code repository. Its PlatformIO target and public source establish a source-level ESP32-S3/Arduino display, BLE, QR, sound, menu, and game surface. It contains no reviewed root license file, event allocation record, deployed-firmware release, hardware-production statement, or image-reuse permission.
Badge: CPEC DC34 MechBattle Badge
DEF CON · retrieved 2026-05-15
Official event-context source for DEF CON 34's August 6-9, 2026 Las Vegas setting. It does not identify CPEC's independent project as issued, included, venue-authorized, or an access credential.
Badge: CPEC DC34 MechBattle Badge