B|Sides Vancouver
The official B|Sides Vancouver 2025 badge page identifies the electronic badge and links the programming resources. This event-context credit does not assign individual board, firmware, manufacturing, or image-rights roles.
SourceBSides Vancouver 2025 · Canada · 2025
ESP32-C3/NFC electronic badge with first-party binaries and later public source
BSides Vancouver's official 2025 badge page calls the artifact an electronic badge, links its first-party programming bundle, and directs firmware information to a public project archive. That archive documents a 2025 REV 2 board and a public firmware refactor committed in 2026, so this record separates the completed 2025 artifact from the later source-tree revision.
People
The official B|Sides Vancouver 2025 badge page identifies the electronic badge and links the programming resources. This event-context credit does not assign individual board, firmware, manufacturing, or image-rights roles.
SourceThe public archive's MIT license names Copyright 2025-2026 BSides Vancouver Society. This is a scoped software/documentation copyright credit, not a claim of ownership for every physical board, image, logo, or event asset.
SourceThe named GitHub account owns the public archive and authored the visible May-June 2026 source and workshop commits. This credit is limited to that source-publication trail and does not assert original 2025 badge design, manufacture, deployment, or media authority.
SourceIt turns a previously shallow Canadian series into a traceable electronic-badge record: the organizer's archive, a first-party binary bundle, dated hardware documentation, and later source publication all converge without requiring an unsupported claim about 2026 distribution or the exact deployed 2025 build.
The public hardware reference describes a 100 mm × 100 mm single-sided FR-4 board with an ESP32-C3FH4, ST25R3911B NFC reader, five SK6812MINI-HS RGB LEDs, six charlieplexed indicator LEDs, Hall and ambient-light sensors, two buttons, USB Type-A edge power/serial, and two parallel CR2032 holders. It calls this the production REV 2 PCB dated 2025-05-05; it is technical documentation, not an independently audited production, allocation, or safety record.
The organizer's first-party repository preserves a bootloader, partition table, badge binary, and macOS-oriented flashing helper for the 2025 electronic badge. A separate public source archive labels v2.4.0 its first public refactored firmware release and documents NFC, LED, sensor, Wi-Fi portal, and mini-CTF behavior. The source commits are from May-June 2026, have no tagged release, and do not prove exact parity with the 2025 production binary, so no checkout is presented as the canonical deployed firmware.
The official archive places workshops on May 25 and the conference schedule on May 26. The 2025 badge page frames the hardware around programming, LEDs, puzzles, sensors, and secrets; the later source archive says it was prepared for badge-workshop sessions. The catalogue preserves that maker and workshop context without copying operating or modification instructions.
Lifecycle
The later source archive documents NFC tag interactions, LED progress indicators, sensors, optional Wi-Fi control-panel behavior, and a mini-CTF. The catalogue preserves that high-level feature surface while refusing to call it the exact factory image or reproduce programming and challenge instructions.
SourceThe public hardware reference describes a 100 mm × 100 mm board, ESP32-C3FH4, ST25R3911B NFC reader, RGB and charlieplex LEDs, sensors, buttons, USB edge connector, and CR2032 holders, and calls the PCB REV 2 dated 2025-05-05. This is linked as a technical documentation trail rather than a production audit or safety certification.
SourceThe repository README and workshop guide describe a hands-on badge-workshop package with a starter template and source material. The record keeps this as source-published workshop context; no reviewed organizer source proves every session date, participant count, or completed workshop outcome.
SourceThe organizer's own repository describes files for programming the BSides Vancouver 2025 Electronic Badge and lists a bootloader, partition table, badge binary, and helper script. It establishes an official programming bundle without exposing a versioned source release, deployment ledger, or individual recipient record.
SourceThe archive's history places the initial public refactored v2.4.0 source and workshop docs on May 29, 2026, with related v2.4.1 and deck updates through June 1. It increases transparency around the 2025 board but does not establish a 2026 badge reissue or production-firmware parity.
SourceThe public archive declares an MIT license for software and associated documentation under BSides Vancouver Society copyright. This is a source-license record, not an automatic reuse clearance for every photograph, board-art layer, logo, physical artifact, or event mark that may appear around the project.
SourceOperational history
The record does not backdate later source improvements into the delivered 2025 image or treat public 2026 commits as evidence of a separate 2026 conference badge.
The catalogue links valuable source and binary evidence without asserting a current, authenticated, supported, or universally deployed firmware image.
The Canada record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
No safety, battery-life, interoperability, or reliable wireless-operation claim is inferred from the visible board documentation.
Source-backed board details remain useful without becoming a claim of every produced badge's exact bill of materials, layout, quality, or final physical state.
The catalogue records a real 2025 electronic badge without asserting that every ticket holder received one or that a particular source bundle was flashed onto every physical unit.
The record may link the software and documentation license while keeping visual, branding, physical-artifact, and local-image reuse claims deliberately scoped.