BugCON · Mexico City (CDMX) · 2022 · 1 badge(s)
The BugCON 2022 CDMX edition whose Electronic Cats badge repository and README document an RP2040 electronic badge with USB serial use, LEDs, microphone, buzzer or speaker, EdgeImpulse audio-classification context, Arduino Mbed programming notes, KiCad hardware files, and firmware examples.
BugCON · Mexico · 2023 · 1 badge(s)
The BugCON 2023 edition whose Electronic Cats badge repository and README document a resistance-themed official badge, ESP32S3 or RP2040 feature statement, UART, Bluetooth and Wi-Fi on ESP32S3, AA battery support, GPL firmware, CERN-OHL hardware files, KiCad hardware trees, and Arduino developer workflow.
BugCON · Mexico City · 2024 · 1 badge(s)
The Mexico City BugCON security conference edition whose official Electronic Cats badge repository documents community and VIP ESP32-C6 hardware variants, firmware paths, and CERN-OHL hardware release.
BSides CDMX · Ex Fabrica MX, Mexico City · 2025 · 1 badge(s)
The July 18, 2025 Mexico City Security BSides edition whose official event page documents the Ex Fabrica MX venue and whose Electronic Cats repository preserves a PY32F030 badge, role variants, Metro add-on, firmware, BOMs, and hardware renders.
BugCON · Fronton Bucareli, Mexico City · 2025 · 1 badge(s)
The November 20-21, 2025 Mexico City BugCON edition whose official event pages and Electronic Cats repository document a Linux-capable RV1106 badge with open hardware source, add-on board, and release-image flashing path.
HackGDL · Jardin Americana, Guadalajara, Jalisco · 2025 · 1 badge(s)
The March 1, 2025 Guadalajara HackGDL edition whose official pages and Electronic Cats repository document a HackGDL event badge based on the ESP32-S3 Minino platform.
HackGDL · Jardín Americana, Guadalajara, Jalisco · 2026 · 1 badge(s)
The completed March 14, 2026 Guadalajara HackGDL edition whose official page, sponsor deck, organizer feed, and Electronic Cats sources document an event-associated RV1106G3 camera badge artifact without proving attendee inclusion or credential allocation.
Pwnterrey · Rincón Tostitos By Jardín 85, Monterrey, Nuevo León, Mexico · 2026 · 1 badge(s)
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.
TROPICON · Cozumel, Mexico · 2026 · 1 badge(s)
The completed April 17-18, 2026 cybersecurity event in Cozumel. The official TROPICON home establishes the event's date and location, while Electronic Cats' public hardware repository describes its project as the official TROPICON 2026 badge and a companion firmware archive names the same edition. The reviewed event page does not itself link or independently confirm those technical archives, allocation, credential role, final production, recipient handoff, or image-reuse rights.
WomenCon · IQSEC offices, Mexico City, Mexico · 2026 · 1 badge(s)
The completed July 25, 2026 first WomenCon edition at IQSEC in Mexico City. Official WomenCon ticket posts advertised an included Electronic Cats Digital Morpher Badge, and an IQSEC-host-linked public trail records attendee-supplied AAA batteries for badge screens, registration kit handoff, and a post-event source statement that Electronic Cats badges supported live hardware hacking. No technical or rights-cleared-image archive is public.
badge add-on
The hardware tree and release assets preserve a Metro add-on with silkscreen/edge SVGs, source artwork, `Metro.hex`, and a Metro add-on BOM CSV.
badge add-on
The repository preserves a separate Add_On_Bugcon_2025 tree with PY32F002AA15M footprint/source material, KiCad files, decorative artwork, and firmware/libraries.
badge applications
The repository and store page say the badge ships with BLE apps, Wi-Fi apps, and a digital-pet app as ready-to-use examples for the event.
badge camera interface
The product documentation names a 3 MP SC3336 camera and MIPI CSI connection as part of the 2026 camera-badge surface.
badge computer
Electronic Cats describes the Camera Badge HackGDL 2026 around the RV1106G3 Linux platform with ARM Cortex-A7, RISC-V, NPU, and ISP context.
badge controller
The README and store page document HackGDL 2025 as an ESP32-S3 badge based on the Minino platform.
badge controller
The README identifies the BugCON 2023 badge as an ESP32S3 or RP2040 design with UART, ESP32S3 Bluetooth/Wi-Fi, and AA battery support.
badge controller
The README lists the Puya PY32F030F28U6TR microcontroller as the badge core, and the firmware README documents the PY32F0 MCU family and Cortex-M0+ build path.
badge controller
The README lists RP2040, USB, LEDs, microphone, buzzer or speaker, and EdgeImpulse-backed machine-learning context for the BugCON 2022 badge.
badge controller
The README documents an RV1106G3 platform with ARM Cortex-A7, RISC-V MCU, NPU, ISP, and Linux operating-system support.
badge hardware
Public documentation lists 18650 battery support, buck conversion, WS2812E NeoPixels, and Python spidev examples for LED control from Linux.
badge interface
Public documentation lists NeoPixels, OLED display, two AAA battery holder, and Shitty Addon connector as badge technology.
badge interface
Public badge documentation lists an integrated OLED screen, four physical buttons, three NeoPixels, buzzer, three-AAA battery holder, USB-C, and Shitty Addon connector.
badge interface and power surface
Electronic Cats lists WS2812E NeoPixels, buttons, a USB hub, GPIO/UART, 18650 battery support, and a buck-converter power path; this does not establish final production configuration or safety validation.
badge interfaces
The README documents broad RV1106 interfaces including GPIO, camera/sensor MIPI CSI, UART, SPI, I2C, USB hub support, and GPIO-based Ethernet path.
badge variant
The community variant used ESP32-C6 hardware with USB, two AA batteries, LEDs, and a 128x32 0.91-inch I2C SSD1306 OLED.
badge variant
The VIP variant used ESP32-C6 hardware with USB, two AA batteries, LEDs, and a 1.28-inch GC9A01 circular TFT LCD.
badge variants
The hardware tree preserves separate KiCad directories and board rasters for Community, Guest, Speaker, Sponsor, and Staff role variants.
commit-pinned hardware documentation
The hardware README names an ESP32-C6, a 2.79-inch 142×428 colour IPS NV3007 display, LoRa hardware, and AHT30; the archive contains native KiCad project, schematic, and PCB material. This retains a high-level documented design surface without asserting a final BOM, populated revision, power path, antenna, test result, safety assessment, or final unit configuration.
companion firmware provenance
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.
developer workflow
The README points Arduino developers to the project wiki and links the Arduino Mbed RP2040 core as the programming route for the badge.
developer workflow
The firmware developer guide documents required Arduino libraries, RP2040 and ESP32-S3 pin edits, production pin changes, and compile/flash commands for both board targets.
firmware and production lifecycle
The releases page preserves `app.hex`, `Metro.hex`, and BOM CSVs for Community, Guest, Speaker, Staff, and Metro add-on outputs.
firmware development
The badge README points developers to the Minino firmware guide for ESP-IDF setup, modular app structure, compile, flash, and monitor workflows.
firmware examples
Separate firmware directories preserve an SSD1306 OLED DinoGame sketch and a BLE advertising Spoof sketch modified for ESP32-S3.
firmware lifecycle
The firmware tree preserves an AudioWAV sketch with USB mass-storage and PWM audio behavior plus an EdgeImpulse note linking audio-classification tutorial material.
firmware lifecycle
The Badge firmware tree preserves menu, terminal, Wi-Fi server, generated web assets, AirTag, UART, hardware-pin, and NeoPixel control source files.
firmware lifecycle
The firmware tree preserves separate Community and VIP directories, with Community firmware build guidance and VIP development framed around CircuitPython and Thonny.
firmware lifecycle
The README and releases document Rockchip/Luckfox upgrade_tool flashing for Bugcon-Badge-2025 image tarballs and the v1.0/v1.1 release path.
firmware workflow
The repository startup path tells attendees to connect the badge over USB and open the serial port at 115200 baud to see badge text.
firmware workflow
The README tells attendees to connect over USB, select the correct serial port at 115200 baud, observe terminal startup, and type `help` for additional commands.
firmware workflow
The README documents bootloader mode, ESP Tool web flashing at address 0x0, and an esptool.py console command for `HackGDL_2025.bin` on ESP32-S3.
firmware workflow
The firmware README documents GNU Arm Embedded Toolchain setup, J-Link or PyOCD programming, Makefile configuration, and make/flash commands for PY32F0 targets.
hardware archive
The ESP32-S3 schematic backs ESP32-S3-WROOM, USB-C, SSD1306 OLED, WS2812B Mini LEDs, buttons, slide switch, I2C, and battery-rail claims; the repository's SAMD11-named tree contains an RP2040 schematic with USB-C, W25Q flash, battery, OLED, WS2812B Mini LEDs, and switches.
hardware archive
The hardware tree preserves KiCad schematic and board files whose schematic names RP2040, SPH0641LM4H microphone, PAM8302AAD amplifier, W25Q16JV flash, MCP1700 regulator, battery, buzzer, LEDs, micro-USB, BOOT, and RESET elements.
hardware archive
The public hardware tree preserves KiCad board, schematic, project, footprint, camera, MCU, USB, power, and mechanical-source files for the named 2026 artifact.
hardware license boundary
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.
host-linked pre-event power and collection statement
A WomenCon update preserved through an IQSEC-linked public profile says attendees needed to bring their own AAA batteries to turn on the badge screens and that registration distribution of shirts and kits started at 08:30. It names neither battery count or specification nor display technology, kit inventory, pickup verification, assembly, electrical safety, replacement, or individual handoff result.
maker repository and event context
Electronic Cats calls its public hardware project Badge Oficial Tropicon 2026, while TROPICON's official home establishes the completed Cozumel event. The event page does not itself link or independently confirm the repository, and neither source establishes ticket inclusion, quantity, price, pickup, delivery, admission use, or recipient handoff.
official organizer-described intended use
WomenCon calls the Digital Morpher an interactive electronic and collectible badge designed or developed by Electronic Cats, explicitly intended to be connected for hardware hacking. The sources do not identify the connection type, interfaces, hardware-hacking activities, safety rules, firmware behavior, challenge, access-control role, or supported workflow.
official repository and event association
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.
official ticket-package and availability statement
WomenCon's early-ticket post says the $550 MXN first phase had 20 tickets and included the Digital Morpher Badge. A later Fase 2 post says the $850 MXN ticket included it and frames the event at 100 people maximum. These public snapshots do not prove final ticket price, sales count, registration completion, attendee eligibility, comp/speaker allocation, refund, recipient identity, kit contents, or per-attendee delivery.
open hardware design archive
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.
published hardware feature 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.
software workflow
The README documents 3.3 V TTL UART2 debug serial at 115200 baud, root credentials, terminal access, Python 3.11.6, and a simple Python hello-world path.
source and license boundary
The hardware archive publishes native KiCad material with CERN Open Hardware Licence v1.2 text for hardware documentation, and GitHub marks the separate firmware archive GPL-3.0. These source and license findings do not automatically cover firmware deployment, repository graphics, event media, logos, trademarks, or local image publication.
source-documented controller and interface
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.
source-stated completed-event operating claim
A post-event WomenCon text reproduced through the IQSEC-linked public trail says Electronic Cats electronic badges were functioning at 100 percent with hardware hacking in real time. That supports completed-event use at a high level, but does not document test methods, affected units, functionality, defects, user outcomes, firmware version, repairs, security controls, or an independently reproducible result.
AHT30/AHT10 sensor discrepancy and final-unit parity gap · commit-pinned hardware and firmware documentation · source discrepancy unresolved
The entry preserves both source statements and does not select a sensor, claim a final component list, or represent public design files as a verified production configuration.
Electronic Cats role, hardware-license, and authorship boundary · organization-level source statements · designer/developer organization named; scope and license unpublished
Credits stay at the named organization level and do not infer an open-hardware release, named-person authorship, production responsibility, ownership, or reusable-image permission.
event allocation, production, and fulfillment gap · primary event and repository sources · post-event public evidence remains incomplete
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.
event and firmware inventory caveat · repository metadata and decoded source files · needs archive/event-page recovery
Event and software claims stay bounded to the repository, README, developer guide, visible source tree, and decoded representative files instead of inventing event logistics or treating the repository as a fully inventoried production archive.
event association and allocation boundary · official event page, organizer feed, product page, and repository · documented event association only
The catalogue treats this as a real event-associated camera-badge artifact without representing it as a universal attendee credential or completed fulfillment record.
event-context depth caveat · repository metadata and README · needs archive/event-page recovery
Event claims stay bounded to BugCON 2022 CDMX and the public badge repository instead of inventing dates, venue, ticket tier, or distribution scope.
firmware release, production parity, and source-history gap · public companion firmware repository · needs provenance and release confirmation
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.
firmware, camera, and deployment boundary · public project and product documentation · not fully documented
The record avoids setup, login, and interface-command instructions and does not infer security, privacy, operational, or final firmware properties beyond the documented high-level platform.
firmware, wireless, data, and operational-policy gap · public companion firmware archive · source archive public; final deployment and policy evidence unrecovered
The catalogue links public source material at a high level without treating it as a final deployment, safety/compliance result, operating policy, privacy practice, or authorization to use any communications capability.
firmware-release scope · repository documentation · needs deeper artifact inventory
Software claims stay tied to the README, release path, and Minino documentation rather than treating the repository as a fully inventoried final production archive.
firmware-source caveat · repository tree and decoded sketches · needs deeper firmware inventory
Software claims stay tied to the README instructions, visible firmware tree, and decoded example sketches rather than treating the repository as a complete final production firmware archive.
hardware build, power, RF, and safety documentation gap · public KiCad repository and README · design-level evidence only
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 variant evidence caveat · README and repository tree · documented with caution
Hardware claims stay tied to visible source files rather than inferring which variant shipped, how many boards were produced, or whether every tree name matches the final production board identity.
hardware, firmware, and build archive gap · official high-level board and usage statements · no public technical release recovered
The compendium records the source-described artifact and usage context without inventing a component-level architecture, reproducible hack path, implementation assurance, or open-source status.
hardware, firmware, media, and trademark license boundary · published license files and repository review · documented with scope separation
The record links source and license material while leaving media publication, firmware-modification scope, branding, and trademark reuse outside the stated hardware-documentation basis.
hardware, power, and production archive gap · product page and public KiCad tree · needs deeper production evidence
Hardware claims remain limited to the documented high-level surface and visible source tree rather than being treated as an audited final production specification.
image provenance upgrade · repository README license statement and exact raster source · licensed official upstream raster render applied
The record has a rights-cleared official upstream raster with source URL, license basis, attribution, local source preservation, and optimized WebP delivery while avoiding generated, placeholder, screenshot, social-media, or conference-gallery imagery.
license and repository-media boundary · GitHub API metadata and repository tree · documented with caution
The catalogue cites the source trail but publishes no image and makes no broad code, hardware, artwork, or trademark reuse claim.
license scope caveat · GitHub API, repository tree, and README · documented with caution
The catalogue can cite the open-hardware claim and public source while avoiding assumptions that firmware, SDK material, readme images, KiCad renders, logos, or event graphics are reusable publication assets.
license scope caveat · repository README and license files · documented
The catalogue can cite and publish the selected hardware render while keeping firmware/source licensing and event trademarks separate from the hardware-documentation reuse basis.
license scope caveat · repository README and store page · documented with caution
The catalogue can cite the source and hardware release while keeping image publication and trademark reuse separate from code and hardware licensing.
license scope caveat · GitHub API, repository README, and license files · documented
The catalogue can cite GPL software and CERN-OHL hardware documentation while avoiding assumptions that firmware, photos, logos, screenshots, KiCad renders, trademarks, or other media all share one reuse scope.
license scope caveat · primary repository · documented
The compendium can cite the open-hardware release while avoiding assumptions that all firmware, screenshots, photos, or repository media share the same reuse terms.
license-file caveat · GitHub API and repository README · documented with caution
The catalogue can cite the README's open-hardware claim and public source while avoiding assumptions that firmware, photos, readme images, logos, KiCad renders, or other repository media are reusable publication assets.
missing rights-cleared image · local project policy · needs licensed original replacement
The Mexico record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying diagrams, screenshots, event artwork, GitHub assets, logos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying repository graphics, event visuals, screenshots, social-media images, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying product photos, repository screenshots, GitHub attachments, logos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying event logos, README images, GitHub assets, KiCad screenshots, social photos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying LinkedIn media, social posts, screenshots, event graphics, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying logos, screenshots, GitHub assets, KiCad outputs, event graphics, social photos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy and source review · needs selected, attributable, cleared original
The record remains source-backed and image-free rather than copying repository media, event graphics, social posts, screenshots, placeholders, or generated approximations.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying repository or web imagery without complete provenance.
organizer association, allocation, and credential boundary · official event home and maker-published repository · event and maker archive documented; organizer linkage and distribution unrecovered
The catalogue records a real source-documented event artifact without converting a maker description into organizer confirmation, universal issuance, a credential claim, or a completed fulfilment record.
release and source inventory · repository documentation · needs deeper artifact inventory
Software and production claims stay tied to README, release names, public hardware trees, and the named SDK branch rather than treating the repository as a fully inventoried production archive.
screen, AAA battery, and power-safety gap · host-linked pre-event battery statement · AAA requirement and screens named; electrical details unpublished
The entry does not turn a bring-your-own-battery reminder into an electrical specification or a safety recommendation.
source inventory caveat · repository tree and releases · needs deeper artifact inventory
Software and production claims stay tied to README, releases, firmware README, visible hardware tree, and named release assets rather than treating the repository as a fully inventoried manufacturing archive.
ticket, allocation, and distribution scope gap · official ticket posts and completed-event source trail · included-ticket intent and event completion documented; unit allocation unknown
The record does not present limited-capacity sales language, a registration announcement, or a high-level functional post as a complete distribution, entitlement, or support record.
wireless, NFC, GPS, privacy, and lawful-use boundary · public README and companion firmware documentation · source-described capabilities need authorized context
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.