BSides CDMX

BSides CDMX 2025

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.

Ex Fabrica MX, Mexico City · Mexico · 2025

BSides CDMX 2025 Badge badge image

BSides CDMX 2025 Badge

BSides CDMX 2025's Electronic Cats repository documents a Security BSides CDMX badge built around a Puya PY32F030F28U6TR, NeoPixels, OLED display, two AAA battery holder, Shitty Addon connector, role-specific KiCad hardware variants, a Metro add-on, public firmware, release HEX files, and BOM assets.

Lifecycle

Add-ons & Upgrades

BSides CDMX 2025 Badge archived source

badge add-on

Metro 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.

Compatibility: BSides CDMX 2025 Badge

BSides CDMX 2025 Badge source-backed

badge controller

Puya PY32F030 badge core

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.

Compatibility: BSides CDMX 2025 Badge

firmware and production lifecycle

Release HEX and BOM archive

The releases page preserves `app.hex`, `Metro.hex`, and BOM CSVs for Community, Guest, Speaker, Staff, and Metro add-on outputs.

Compatibility: BSides CDMX 2025 Badge

firmware workflow

Puya template firmware build path

The firmware README documents GNU Arm Embedded Toolchain setup, J-Link or PyOCD programming, Makefile configuration, and make/flash commands for PY32F0 targets.

Compatibility: BSides CDMX 2025 Badge

Operational history

Issues & Camp Impact

image provenance upgrade · repository README license statement and exact raster source · licensed official upstream raster render applied

The BSides CDMX 2025 visual uses Electronic Cats' official `BADGE-BSIDES-CDMX-2025-03.png` community-badge raster from the public hardware tree.

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 scope caveat · repository README and license files · documented

The repository is GitHub-detected as GPL-3.0 and the README separately states the hardware is released under CERN Open Hardware Licence v1.2. This record treats software, firmware, hardware documentation, and the selected hardware-tree raster according to their documented scopes rather than assuming one license covers every asset.

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.

source inventory caveat · repository tree and releases · needs deeper artifact inventory

The public tree preserves many firmware library files, role-specific hardware variants, backup archives, release HEX files, BOM CSVs, and Metro add-on material, but this pass did not audit every generated backup zip, dependency license, or manufacturing output.

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.

Resources

Sources