BSides Vancouver
BSides Vancouver 2025
The May 25-26, 2025 BSides Vancouver edition whose official 2025 badge archive identifies an electronic badge, links a first-party programming bundle, and directs badge information to a public source archive. The public hardware documentation calls the production board REV 2 dated 2025-05-05, while the visible refactor was committed in 2026 and is not treated as proof of a 2026 electronic-badge reissue.
SFU Vancouver Campus, 515 W Hastings Street, Vancouver, British Columbia · Canada · 2025
documented firmware capability
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.
Compatibility: Documented 2025 board and later public source archive
documented hardware platform
The 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.
Compatibility: BSides Vancouver 2025 Electronic Badge
education and community context
The 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.
Compatibility: BSides Vancouver Badge workshop context
official firmware handoff
The 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.
Compatibility: BSides Vancouver 2025 Electronic Badge
post-event software lifecycle
The 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.
Compatibility: BSides Vancouver 2025 Electronic Badge source trail
source license
The 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.
Compatibility: maltchev/bsides-vancouver-badge archive
2025 production versus 2026 source-revision boundary · public commit chronology and dated hardware documentation · dated artifact and later source distinguished
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.
firmware release, deployment, and support gap · first-party bundle and public source archive · binary and later source visible; canonical deployed release unrecovered
The catalogue links valuable source and binary evidence without asserting a current, authenticated, supported, or universally deployed firmware image.
missing rights-cleared image · local project policy · needs licensed original replacement
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.
power and electrical-safety documentation gap · public hardware reference · power outline and caveat documented; validation unrecovered
No safety, battery-life, interoperability, or reliable wireless-operation claim is inferred from the visible board documentation.
production-board and physical-configuration boundary · public hardware documentation · documented REV 2 outline; complete production record unrecovered
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.
recipient allocation and delivery gap · official archive and first-party bundle · artifact and programming bundle documented; allocation outcome unrecovered
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.
source-license, visual-asset, and event-mark scope boundary · MIT license review · software/documentation license recorded; separate rights unresolved
The record may link the software and documentation license while keeping visual, branding, physical-artifact, and local-image reuse claims deliberately scoped.