Pwnterrey

Pwnterrey 2026

The May 29, 2026 Pwnterrey cybersecurity conference in Monterrey, described by its official site as a free event. Electronic Cats' public repository identifies an official Pwnterrey 2026 ESP32-C5 badge and publishes its native KiCad project, while a companion repository identifies official firmware. These post-event public sources establish the event-linked artifact and source trail but not allocation, final production configuration, recipient handoff, final signed firmware, or image-reuse rights.

Rincón Tostitos By Jardín 85, Monterrey, Nuevo León, Mexico · Mexico · 2026

Pwnterrey 2026 Official ESP32-C5 Badge

Electronic Cats' public badge-pwnterrey-2026 repository describes itself as the official Pwnterrey 2026 badge and publishes a native KiCad hardware project plus a CERN Open Hardware Licence v1.2 file. Pwnterrey's official site places the free cybersecurity conference in Monterrey on May 29, 2026; Bishop Fox separately corroborates the date and Rincón Tostitos By Jardín 85 venue. The source documents a portable headless ESP32-C5 RISC-V badge with USB-C serial context, NFC tag-emulation circuitry, and GPS material. Electronic Cats' companion repository calls itself official Pwnterrey 2026 firmware and preserves an ESP32-C5 Marauder-derived source and build trail. These sources establish a real official event badge and public design and firmware references, but not a production quantity, registration-tier allocation, final assembled configuration, completed recipient handoff, final signed release, safe operational use, or reusable badge-image right.

Lifecycle

Add-ons & Upgrades

Pwnterrey 2026 Official ESP32-C5 Badge public repository documentation

companion firmware provenance

C5 Marauder-derived firmware and public build-material boundary

Electronic Cats' companion repository calls itself official Pwnterrey 2026 firmware and retains ESP32-C5 headless Marauder-derived source, documentation, and build material. Its root MIT text credits Just Call Me Koko; this record does not equate that upstream text or visible build artifacts with a final signed event binary, production configuration, safety review, or generalized authorization to operate wireless functions.

Compatibility: Pwnterrey 2026 Official ESP32-C5 Badge

Pwnterrey 2026 Official ESP32-C5 Badge published hardware license

hardware license boundary

CERN OHL v1.2 hardware-documentation scope

The repository provides CERN Open Hardware Licence v1.2 text for the hardware documentation. The licence file is treated as a hardware-documentation basis only, not an automatic licence for firmware, photos, readme graphics, logos, event branding, or trademarks.

Compatibility: Pwnterrey 2026 Official ESP32-C5 Badge

Pwnterrey 2026 Official ESP32-C5 Badge explicit repository description

official repository and event association

Official 2026 Pwnterrey badge and event-context boundary

Electronic Cats describes its public hardware repository as the official Pwnterrey 2026 badge, while Pwnterrey's official site documents the free May 29 Monterrey cybersecurity-event context. Neither reviewed source confirms admission inclusion, recipient eligibility, quantity, price, pickup, delivery, completed handoff, or a credential function.

Compatibility: Pwnterrey 2026 Official ESP32-C5 Badge

Pwnterrey 2026 Official ESP32-C5 Badge public repository documentation

open hardware design archive

Public native KiCad schematic, PCB, and project files

The hardware repository exposes native KiCad schematic, PCB, project, footprint, and related automation material. Public source availability does not by itself establish a complete BOM, fabrication readiness, tested manufacturing output, production run, firmware parity, or reuse rights for every non-hardware asset.

Compatibility: Pwnterrey 2026 Official ESP32-C5 Badge

Pwnterrey 2026 Official ESP32-C5 Badge public KiCad documentation

published hardware feature surface

NT3H2111 NFC tag-emulation and GPS source surface

The published KiCad source identifies an NT3H2111W0FHK NFC tag chip and GPS footprints and labels. This preserves the design-level evidence without asserting a fitted GPS receiver, a particular NFC configuration, field performance, data practice, authorized use case, or final assembled configuration.

Compatibility: Pwnterrey 2026 Official ESP32-C5 Badge

Pwnterrey 2026 Official ESP32-C5 Badge public hardware documentation

source-documented controller and interface

ESP32-C5 headless USB-C serial platform

The badge README describes a portable headless ESP32-C5 RISC-V device with USB-C and serial CLI context, while the KiCad source identifies the ESP32-C5-WROOM-1-N4 module value. The sources do not establish a final production revision, exact USB behavior, antenna, radio configuration, test result, or operation of every assembled unit.

Compatibility: Pwnterrey 2026 Official ESP32-C5 Badge

Operational history

Issues & Camp Impact

event allocation, production, and fulfillment gap · primary event and repository sources · post-event public evidence remains incomplete

The official site establishes Pwnterrey's May 29, 2026 event and Electronic Cats labels the public hardware repository official, but reviewed sources do not state a badge quantity, admission inclusion, registration tier, price, order record, recipient ledger, pickup, delivery, completed handoff, final production count, or post-event distribution outcome.

The catalogue preserves the official design and event association without presenting the badge as universally issued, sold, delivered, accepted, or used as an admission credential.

firmware release, production parity, and source-history gap · public companion firmware repository · needs provenance and release confirmation

The companion repository contains ESP32-C5 headless Marauder-derived source, documentation, and build material and calls itself official Pwnterrey firmware, but this pass did not establish a reviewed final release tag, signed binary, reproducible event build, contribution history for every change, full dependency inventory, or parity with any distributed badge.

The catalogue records public software provenance without representing a visible build artifact as the final event firmware, an audited release, a complete source history, or an authorized deployment.

hardware build, power, RF, and safety documentation gap · public KiCad repository and README · design-level evidence only

The public KiCad project identifies controller, NFC, USB-C, and GPS design material, but the reviewed sources do not supply a complete BOM, fitted-part list, PCBA record, battery or charging design, power budget, antenna/final RF implementation, measurements, certification, thermal or fault behavior, safe-modification guidance, or a verified finished configuration.

Published design references are not treated as a build recipe, electrical-safety endorsement, radio-performance claim, certification claim, or proof that every public component was fitted to every event unit.

hardware, firmware, media, and trademark license boundary · published license files and repository review · documented with scope separation

The hardware repository publishes CERN Open Hardware Licence v1.2 text for hardware documentation, while the companion firmware repository's root MIT text credits Just Call Me Koko. These findings do not automatically license all later firmware modifications, repository graphics, readme images, event media, logos, names, or trademarks.

The record links source and license material while leaving media publication, firmware-modification scope, branding, and trademark reuse outside the stated hardware-documentation basis.

missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original

No Pwnterrey 2026 badge image is published because the official event pages, hardware and firmware repositories, and readme graphics do not pair a selected factual artifact image with a reusable license or explicit permission basis, attribution, source URL, and processing provenance for local publication.

The record remains source-backed and image-free rather than copying repository graphics, event visuals, screenshots, social-media images, placeholders, or generated approximations.

wireless, NFC, GPS, privacy, and lawful-use boundary · public README and companion firmware documentation · source-described capabilities need authorized context

The public materials describe Wi-Fi, Bluetooth Low Energy, NFC, GPS, and Marauder-derived security-testing context, but do not provide a complete event-use policy, operator authorization record, data-handling terms, final RF configuration, range/interference testing, regulatory documentation, or a general-purpose safe-use guide.

The dossier contains no operational instructions and does not treat source-described wireless, NFC, or GPS capabilities as permission to test third-party systems, collect data, evade privacy expectations, or operate outside lawful owner-authorized work.

Resources

Sources