Country dossier
Canada
Worldwide badge coverage for Canada, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.
16 badge(s) · 16 event(s) · 5 series · 2015-2026
Back to countries
NorthSec · Bonsecours, Montreal · 2015 · 1 badge(s)
The Bonsecours NorthSec 2015 CTF edition whose official past-editions page documents 54 teams, team-of-eight competition structure, and hardware badges used for network, IPv6, RF-monitoring, smartcard, and related challenge paths.
NorthSec · Montreal · 2016 · 1 badge(s)
The Montreal NorthSec 2016 edition whose public badge repository documents an nRF51822 and STM32F072 electronic badge with OLED, BLE, touch buttons, USB, battery management, LEDs, and SWD/DFU programming paths.
NorthSec · Montreal · 2017 · 1 badge(s)
The Montreal NorthSec 2017 edition whose public badge repository documents the refreshed nRF51822 and STM32F072 electronic badge, OLED/BLE behavior, touch buttons, USB, batteries, firmware images, and schematic release.
NorthSec · Montreal · 2018 · 1 badge(s)
The Montreal NorthSec 2018 edition whose public badge repository documents an nRF52832 and STM32F070 electronic badge with OLED, BLE, NeoPixel RGB LEDs, buttons, rechargeable Li-ion battery support, USB charging, and schematics.
BSides Vancouver · Vancouver, British Columbia · 2019 · 1 badge(s)
The 2019 BSides Vancouver edition represented here by TwinkleTwinkie's public DEF CON 27 Hardware Hacking Village bio, which lists the BSides Vancouver 2019 Badge among notable artistic PCB badge work.
Hackfest · Plaza, Quebec City · 2019 · 1 badge(s)
The October 31-November 2, 2019 Hackfest 11 / Upside Down edition in Quebec City, where the official Hackfest history says the CTF introduced an electronic badge that was an immediate hit with participants.
NorthSec · Montreal · 2019 · 1 badge(s)
The Montreal NorthSec 2019 edition whose public badge repository documents an nRF52832 and STM32F070 electronic badge with OLED, BLE, NeoPixel RGB LEDs, USB, Li-ion battery support, hardware files, firmware, games, challenges, and schedule code.
NorthSec · Remote / online · 2021 · 1 badge(s)
The remote NorthSec 2021 edition whose official badge page and public repository document a North Sectoria ESP32 electronic badge with 240x240 LCD, Wi-Fi, BLE, NeoPixels, buttons, buzzer, game flags, and ESP-IDF firmware.
NorthSec · Marche Bonsecours, Montreal · 2022 · 1 badge(s)
The return-to-in-person NorthSec edition at Marche Bonsecours whose public repository archive preserves a 2022 ESP32 badge hardware tree, production files, BOM material, challenge assets, and SAO hardware directories.
NorthSec · Bonsecours Market, Montreal · 2023 · 1 badge(s)
The Montreal NorthSec 2023 anniversary edition whose public badge repository and first-hand technical writeup document an attendee electronic badge with badge-chain interaction, optional OLED, RGB LEDs, AVR firmware behavior, and hardware-source context.
NorthSec · Bonsecours Market, Montreal · 2024 · 1 badge(s)
The Montreal NorthSec 2024 edition whose public badge repository documents an ESP32-S3-WROOM-1 badge with NeoPixel LEDs, buttons, pairing connectors, four SAO connectors, USB-C or AAA battery power, and PlatformIO firmware targets.
BSides Vancouver · SFU Vancouver Campus, 515 W Hastings Street, Vancouver, British Columbia · 2025 · 1 badge(s)
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.
NorthSec · Bonsecours Market, Montreal · 2025 · 1 badge(s)
The Montreal NorthSec 2025 edition whose public badge repository documents an ESP32-C3 electronic badge with RGB LEDs, buttons, IR pairing, dual SAO connectors, USB-C/AAA power, and PlatformIO firmware workflows.
NorthSec · Bonsecours Market, Montreal · 2026 · 1 badge(s)
The May 9-17, 2026 Montreal NorthSec edition whose official registration page offered a new social electronic badge while supplies lasted and whose villages material documented badge soldering, badge-enhancement activity, and a badge museum. Post-event first-hand and third-party firmware sources document an observed ESP32-S3/NFC/NeoPixel badge configuration, while NorthSec's public archive still lacks an official 2026 hardware or firmware release.
REcon · Hilton Double Tree Montreal, Montreal · 2026 · 1 badge(s)
The June 19-21, 2026 Montreal reverse-engineering conference whose official sponsors page names Electronic Cats as the electronic badge sponsor and whose public badge-recon-2026 repository documents a CH32V203 and RP2040 badge with LoRa, NFC, and magspoof challenges.
Software You Can Love · Coquitlam and Port Moody, Metro Vancouver, British Columbia · 2026 · 1 badge(s)
The planned October 3-6, 2026 Software You Can Love developer conference in Metro Vancouver. Official conference updates place its Sunday Tables Day at Site B in Port Moody and say those attendees will receive a SYCL Badge V2, while the wider event includes Coquitlam talk days. Public material documents the planned badge and selected high-level revision claims, not final manufacture, exact unit configuration, delivery, or image rights.
CTF artifact
NorthSec's official archive says 2015 CTF participants were grouped into teams of eight and each had a hardware badge tied to the competition environment.
CTF category
The CTF page lists Electronic among the 2019 challenge categories, alongside Cloud, SDR, Web, and other challenge types.
add-on hardware
The 2022 hardware tree includes multiple SAO directories, including Ubisoft, numbered SAO revisions, BOMs, Gerbers, assembly exports, and board-source material.
artifact naming
TwinkleTwinkie's DEF CON 27 Hardware Hacking Village bio explicitly names BSides Vancouver 2019 Badge among notable produced works.
badge challenge
The PN7150 NFC daughterboard supports tag and reader detection, Mifare Classic read and write, and a flag-hunt where tapping a tag unlocks a flag and broadcasts it to every nearby badge.
badge challenge and game
The badge emulates magnetic stripe cards over USB serial and includes a solo Simon Says memory game triggered by holding button 4.
badge display surface
The production BOM lists twenty-four WS2811/5050 RGB LED parts plus additional red 0805 status LEDs on the badge hardware.
badge distribution
The registration page lists a new social electronic badge as an included item for multiple NorthSec 2026 ticket classes while supplies lasted.
badge game
The official badge page documents ten badge flags hidden across trivia, reverse engineering, and badge interfaces, submitted through FLAGBOT.
badge interface
A USB serial console enumerating as RECON2026 exposes commands for ping, mode, LEDs, LoRa transmit, chat, stats, beacon, scan, lock, Simon, reset, and test injectors.
badge networking
The release notes document a 915 MHz badge-to-badge LoRa social layer with Radar discovery, Chat, and Flags sharing over the SX1262 radio.
badge pickup workflow
The 2019 schedule lists badge pickup across opening night and both conference days, placing badges in attendee logistics.
badge pickup workflow
The villages schedule told attendees to retrieve goodies such as their t-shirt and badge using the QR code in their nSec order email.
badge software
The repository tag preserves firmware apps, games, challenge material, schedule code, BLE control, and LED control utilities.
challenge artifact
The public hardware tree preserves a badge challenge directory with bitmap, JPEG, PNG, and PSD assets tied to the 2022 badge archive.
challenge device
The official controller-screen repository documents an ESP32 screen interface that controlled 2023 badge LEDs over BLE mesh, exposed debug/admin menu behavior, sent messages/popups, and used secure boot on competition boards.
challenge surface
The same official note connects the badge context to network challenges, simulated IPv6 workstations, an RF monitoring station, and a provided smartcard.
conference context
The `Understanding & Making Pcb Art` session placed TwinkleTwinkie's PCB-art practice in the DEF CON 27 Hardware Hacking Village programme.
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.
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.
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.
event context
Hackfest's official history describes 2019 as the pre-pandemic record edition with 1600 participants at the Plaza.
firmware analysis
The writeup documents avrdude dumping, EEPROM fields, inverted serial signaling, 38400 8N1 framing, and a 0xAF 0xFA packet prefix.
firmware archive
The 2017 tree preserves event firmware images and website material alongside schematic and source references.
firmware archive
The official badge-conf-2023 repository preserves ATmega328PB firmware with PlatformIO/MiniCore build instructions, AVR fuse/upload workflow, and a `binary/firmware.hex` conference image.
firmware lifecycle
The repository documents separate PlatformIO build/upload environments for conference and CTF firmware on top of Espressif IDF.
firmware lifecycle
The repository documents PlatformIO/ESP-IDF environments for conference, CTF, and addon firmware plus USB serial monitoring and DTR reset behavior.
firmware reverse engineering
Jean Privat's 2025 writeup documents USB-C/esptool firmware dumping, ESP32-C3 detection, partition extraction, factory-app identification, firmware strings for badge-network and persistence components, and attempts to patch the original firmware.
firmware workflow
The README documents SWD programming for both MCUs and USB DFU flashing for the STM32 side.
firmware workflow
The README documents USB serial monitoring at 115200 baud plus reset-through-DTR guidance for firmware development and debugging.
hardware architecture
The 2016 badge paired nRF51822 OLED/BLE/battery/LED control with an STM32F072 USB and touch-button controller.
hardware architecture
The 2021 badge combined ESP32, 240x240 LCD, Wi-Fi, NeoPixels, six buttons, buzzer, and USB or external battery power.
hardware architecture
The V3j BOM identifies the badge core as ESP32_WROOM32_SKINNY with CH340C USB serial, AP2112 regulation, MCP73831 charging, power switching, and USB connector hardware.
hardware architecture
The README documents an ESP32-C3-WROOM-02-N4 badge core with eighteen NeoPixel RGB LEDs and five attendee-facing buttons.
hardware architecture
The README documents ESP32-S3-WROOM-1-N8R8, sixteen NeoPixels, six buttons, two pairing connectors, and four SAO v1.69bis connectors.
hardware architecture
The 2017 repository documents the continued nRF51822/STM32F072 badge platform with OLED, BLE, battery management, touch buttons, USB, and AAA/USB power.
hardware architecture
The 2018 badge moved to nRF52832 with OLED, BLE, NeoPixel RGB LEDs, buttons, battery management, and STM32 USB handling.
hardware architecture
The 2019 badge kept the nRF52832/STM32F070 split with OLED, BLE, NeoPixel RGB LEDs, buttons, and Li-ion/USB power.
hardware expansion and interaction
The badge exposes two Shitty Add-On V1.69bis connectors and an IR pairing connector, giving attendees both add-on and badge-to-badge interaction surfaces.
hardware source
The official hardware tree supplies KiCad board/schematic files plus JLCPCB BOM, CPL, and Gerber material, with dock and SAO design directories. It documents the released project design without proving that every recipient board was populated or flashed identically.
interaction hardware
The 2023 writeup documents side connectors for badge chaining, optional OLED feedback, buttons, RGB LEDs, and point-scoring badge-to-badge interaction.
lineage exhibit
The official villages page describes a Badge Museum documenting NorthSec's long-running electronic-badge history and open-hardware culture.
lineage milestone
Hackfest's official history says the 2019 CTF introduced an electronic badge and that participants immediately appreciated it.
maker attribution
The DEF CON 27 bio describes TwinkleTwinkie as an independent PCB artist who has manufactured artistic PCB badges and indie badge add-ons.
official CTF challenge surface
The official competition page's retained 2026 Solarpunk section says the hackable electronic badge was fully integrated into the CTF and that solving badge challenges earned points; it separately names badge-firmware tampering among on-site physical tracks.
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.
official firmware source
NorthSec's C++/Arduino PlatformIO tree includes shared NFC, e-paper, LED, and button modules alongside conference/CTF partition material. The public snapshot does not identify a tagged release, factory binary, or event-unit deployment revision.
planned attendee badge allocation
Software You Can Love's official 2026 update says attendees of Sunday Tables Day will receive a SYCL Badge V2.
planned hardware revision
The official update says the V2 moves from the earlier ATSAMD51J19 to an RP2350 and from LiPo power to three AAA batteries.
planned software experience
The official update describes an operating layer capable of supporting multiple Cart applications on the planned V2 badge.
post-event hardware observation
Marx314's post-event attendee account identifies an observed NorthSec 2026 badge with ESP32-S3-WROOM-1, 16 MB flash, ST25R3916 NFC, a six-button D-pad, an 18-pixel NeoPixel ring, and an e-ink display path. NorthSec's later official map corroborates the common controller/peripheral shape but not the reported module capacity or every production variant.
post-event official source release
NorthSec publicly released the separate nsec/badge-2026 source tree after the event, including hardware, firmware, animations, CTF content, dock material, and source artwork. Its historical commit timestamps are retained project chronology, not proof of public availability before the event.
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.
power system
The README documents Li-ion battery or USB power and USB charging when the power switch is on.
series context
The current official B|Sides Vancouver site anchors the Vancouver Security BSides lineage and location while this 2019 badge record remains constrained to recovered badge-specific evidence.
soldering challenge
The 2025 soldering-village writeup documents an add-on challenge with eight LEDs, polarity/defect debugging, VCC and pin behavior, SAO table context, scrambled code recovery, and final flag submission.
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.
third-party firmware
Marx314's public post-event source implements custom NFC-to-webhook behavior with Wi-Fi setup and display/no-display builds. It is replacement firmware for an observed badge configuration, not NorthSec's factory firmware or Apache-2.0 source release.
workshop add-on
The villages material describes enhancing the NorthSec badge with blinking electronic parts during soldering-village activity.
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.
OLED variant and distribution gap · repository but incomplete · needs final-population confirmation
The catalogue records the full hardware and challenge surface without asserting the exact populated OLED variant or the physical distribution scope.
archive scope caveat · source-backed but compact · documented
The visible page stays concise while preserving the key source trail for deeper later archaeology.
distribution scope caveat · official source wording · documented
The badge is classified as a CTF team hardware artifact rather than a confirmed all-attendee admission badge.
field-writeup scope caveat · first-hand writeup · documented
The catalogue uses them to enrich firmware and challenge behavior while keeping authoritative hardware-source claims tied to the official NorthSec repository.
final hardware and software release boundary · official pre-event badge update and repository review · limited planned revision surface public; final unit and release unrecovered
The record preserves the published V2 direction without presenting it as a finished specification, operating guide, safe configuration, or final hardware/software release.
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.
firmware-source caveat · source-backed but incomplete · documented; monitor newly surfaced 2022 badge archives
The record documents verified hardware and archive surfaces while avoiding unsupported badge-game or firmware-behavior claims.
hardware detail caveat · official source with limited technical detail · documented
The catalogue records the badge's existence and challenge context without inventing electronics.
hardware-source caveat · official post-event source plus first-hand observation · official design source documented; event-unit deployment scope remains open
The catalogue can document the official technical surface and CTF integration without presenting the published design snapshot or any third-party observation as a universal recipient-unit configuration.
hardware-source caveat · official source but technically shallow · needs primary badge archive
The record preserves the electronic-badge milestone while avoiding invented component or firmware claims.
hardware-source scope caveat · source-backed but incomplete · needs deeper post-event artifact inventory
The catalogue records verified hardware and firmware surfaces while leaving deeper NorthSec 2025 artifact archaeology for later work.
image provenance · project image provenance and repository license · licensed original replacement applied
The public badge page, image archive, and API point at a real repository photo with source URL, license, attribution, and processing notes preserved.
image provenance · project image provenance and repository license · licensed original replacement applied
The public badge page, image archive, and API point at a real official repository raster with source URL, license, attribution, and processing notes preserved.
image provenance · project image provenance and repository license · licensed original replacement applied
The public badge page, image archive, and API point at a real repository photo with source URL, license, attribution, and processing notes preserved.
image provenance · project image provenance and repository license · licensed original replacement applied
The public badge page, image archive, and API point at a real repository photo with source URL, license, attribution, and processing notes preserved.
image-rights boundary · local project policy · needs licensed original replacement
The entry remains image-free rather than copying event media, Flickr photos, screenshots, social images, or generated placeholder art.
image-rights boundary · local project policy · needs licensed original replacement
The entry remains image-free rather than copying event media, maker photos, social images, screenshots, or generated placeholder art.
large archive scope caveat · source-backed but compact · documented
The record is accurate at the badge level and leaves per-game or per-challenge archaeology for later expansion.
license dependency caveat · primary README · documented
The catalogue records the public badge workflow without overclaiming dependency licensing.
license dependency caveat · primary README · documented
The catalogue treats the hardware and source trail as public but does not imply that every upstream dependency is freely redistributable.
missing rights-cleared image · policy decision · open
The record favors source-backed text over uncleared visual material.
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.
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.
missing rights-cleared image · policy decision · open
The record is source-backed by the hardware archive while staying image-free under the no-generated/no-placeholder image policy.
missing rights-cleared image · policy decision · open
The record remains text-source complete while avoiding generated, placeholder, social-media, or uncleared imagery.
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.
missing rights-cleared image · local project policy · needs licensed original replacement
The Canadian record remains source-backed and image-free rather than copying repository diagrams, screenshots, social media, placeholders, or generated approximations.
missing rights-cleared image · policy decision · open
The badge remains source-backed without violating the no-generated/no-placeholder image policy.
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.
missing rights-cleared image · policy decision · open
The record remains text-source complete while avoiding generated, placeholder, or uncleared imagery.
mixed-source classification · primary plus first-hand secondary · documented
Claims are kept specific to what each source proves, and the record does not overstate official documentation beyond the public repositories and first-hand writeup.
official render caveat · repository audit · documented
The record has a rights-cleared visual without implying that the image is conference-floor photography.
official-source publication and deployment boundary · commit-pinned official GitHub publication · documented; public source release is post-event
Readers can inspect a real official source release while the catalogue avoids backdating its publication, claiming a particular factory image, or treating one source revision as proof for every badge handed out.
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.
pre-event production, allocation, and fulfilment boundary · official 2026 conference update · Tables Day inclusion announced; manufacture and handoff unverified
The catalogue records the source-backed planned day-specific allocation without treating it as an event-wide entitlement, an admission credential, or completed fulfilment.
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.
public-source scope caveat · source-backed but compact · documented
The catalogue records verified badge surfaces and leaves deeper event-specific artifact inventory for future work.
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.
remote-edition context · official source · documented
The record focuses on the public electronic badge, game flags, and development-board behavior rather than unsupported hallway-distribution details.
repository-to-event-unit and licence boundary · public repository metadata and unlinked official event material · public project context retained; October unit mapping and reuse rights unresolved
The repository is cited as source context without asserting event-unit parity or copying code, hardware files, artwork, branding, or images as reusable material.
retrospective archive caveat · repository archive backed · documented
The catalogue can seed the badge without implying that every file was published during the original 2022 event window.
source-depth caveat · speaker-bio backed but technically shallow · needs primary badge archive
The record preserves the Canadian PCB-art badge lineage while avoiding unsupported electronics, variant, firmware, dimension, or manufacturing claims.
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.
third-party firmware license caveat · repository metadata audit · source visible; license unspecified
Readers can inspect the custom firmware trail, but the catalogue does not imply permission to redistribute, modify, or reuse it and keeps it distinct from NorthSec's separately published Apache-2.0 source archive.