BSides Vancouver 2025 · Canada · 2025

BSides Vancouver 2025 Electronic Badge

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.

EventBSides Vancouver 2025
SeriesBSides Vancouver
LocationSFU Vancouver Campus, 515 W Hastings Street, Vancouver, British Columbia
CountryCanada

People

Authors & Credits

2025 event and badge-archive publisher

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.

Source

named public-source software and documentation copyright holder

BSides Vancouver Society

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

Source

public refactored firmware and workshop-archive publisher

maltchev

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

Source

Why It Mattered

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

Hardware

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.

Software & Apps

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.

Lore

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

Add-ons & Upgrades

documented firmware capability public refactored-source documentation

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

Source
documented hardware platform public source documentation

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

Source
education and community context public facilitator/source materials

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

Source
official firmware handoff public binary bundle

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

Source
post-event software lifecycle public source committed after event

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

Source
source license MIT software and documentation 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

Source

Operational history

Issues & Camp Impact

2025 production versus 2026 source-revision boundary note

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.

Confidence
public commit chronology and dated hardware documentation
Status
dated artifact and later source distinguished
Timeframe
May 2025 to June 2026
Source note
maltchev source commit history, README, HARDWARE.md, and CHANGELOG.md.
firmware release, deployment, and support gap note

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.

Confidence
first-party bundle and public source archive
Status
binary and later source visible; canonical deployed release unrecovered
Timeframe
2025-2026 source trail
Source note
bsidesvancouver/Bsides2025badge; maltchev releases page, README, commit history, and CHANGELOG.md.
missing rights-cleared image note

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.

Confidence
local project policy
Status
needs licensed original replacement
Timeframe
current catalogue build
Source note
badge.gallery image policy and official BSides Vancouver 2025 badge archive, first-party binary bundle, and later public firmware and hardware source archive.
power and electrical-safety documentation gap note

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.

Confidence
public hardware reference
Status
power outline and caveat documented; validation unrecovered
Timeframe
current source review
Source note
BSides Vancouver badge HARDWARE.md and CHANGELOG.md.
production-board and physical-configuration boundary note

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.

Confidence
public hardware documentation
Status
documented REV 2 outline; complete production record unrecovered
Timeframe
2025 board documentation
Source note
BSides Vancouver badge HARDWARE.md and first-party 2025 binary bundle.
recipient allocation and delivery gap note

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.

Confidence
official archive and first-party bundle
Status
artifact and programming bundle documented; allocation outcome unrecovered
Timeframe
BSides Vancouver 2025
Source note
BSides Vancouver 2025 badge programming page and bsidesvancouver/Bsides2025badge repository.
source-license, visual-asset, and event-mark scope boundary note

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.

Confidence
MIT license review
Status
software/documentation license recorded; separate rights unresolved
Timeframe
current catalogue build
Source note
BSides Vancouver public-source LICENSE and badge.gallery image policy.

Resources

Sources