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

BSides Vancouver 2025 Electronic Badge

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.

Lifecycle

Add-ons & Upgrades

BSides Vancouver 2025 Electronic Badge public refactored-source documentation

documented firmware capability

NFC and activity-progress source surface

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

BSides Vancouver 2025 Electronic Badge public source documentation

documented hardware platform

REV 2 ESP32-C3/NFC production-board documentation

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

BSides Vancouver 2025 Electronic Badge public facilitator/source materials

education and community context

Badge-workshop materials

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

2025 first-party binary programming bundle

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

BSides Vancouver 2025 Electronic Badge public source committed after event

post-event software lifecycle

2026 public v2.4.x source publication

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

BSides Vancouver 2025 Electronic Badge MIT software and documentation license

source license

MIT-licensed public source archive

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

Operational history

Issues & Camp Impact

2025 production versus 2026 source-revision boundary · public commit chronology and dated hardware documentation · dated artifact and later source distinguished

The hardware reference calls the board REV 2 dated 2025-05-05, while the public refactored firmware and workshop documentation were committed in May-June 2026. The archive itself labels a prebuilt directory as 2025 production, but no reviewed release or hash maps the later source tree to the original 2025 binary or proves a 2026 electronic-badge reissue.

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 official repository contains binary programming material, while the public archive has no GitHub release and calls v2.4.0 its first public refactored firmware release. Reviewed sources do not publish a versioned production release, secure update/recovery policy, official support owner, firmware signature status, or direct mapping between a physical 2025 unit and a source revision.

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

No BSides Vancouver 2025 Electronic Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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

The hardware reference describes USB and parallel CR2032 power paths and warns that coin cells cannot sustain NFC-reader startup without a lower-power firmware setting; it also says the Wi-Fi portal is intended for USB power. Reviewed sources do not provide battery characterization, current measurements, charging behavior, thermal testing, protection validation, electrical limits, assembly inspection, or compliance results.

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

The public hardware reference names the 2025-05-05 REV 2 board and its component outline, but reviewed sources do not establish a reconciled manufacturing BOM, component substitutions, production test result, fabrication count, final assembled photographs, board-revision distribution, or complete physical-unit configuration.

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 organizer page calls the item an electronic badge and supplies programming materials, but reviewed sources do not establish ticket inclusion, optional price, production quantity, recipient count, check-in handoff, workshop enrollment, inventory, replacement terms, shipment, or a completed delivery ledger.

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 public archive's MIT license covers software and associated documentation under BSides Vancouver Society copyright, but reviewed sources do not separately allocate reusable rights for all badge photographs, physical-board art, logos, event names/marks, embedded media, third-party components, or individual source contributions.

The record may link the software and documentation license while keeping visual, branding, physical-artifact, and local-image reuse claims deliberately scoped.

Resources

Sources