Hacker Con Badges

Laser* Tag Badge

Laser* Tag Badge DS at DEF CON 34

The independent 2026 Laser* Tag Badge DS BadgeLife release for DEF CON 34, whose maker page documents the electronic game platform and whose public late-July update says boards are in hand and final assembly/flashing is underway. Pickup and play are announced for DEF CON week, but the badge remains a pre-event independent project rather than an official DEF CON admission credential.

Las Vegas Convention Center and independent DEF CON BadgeLife pickup points, Las Vegas, Nevada · United States · 2026

Laser* Tag Badge DS (DEF CON 34)

Laser* Tag Badge DS is an independent BadgeLife project planned for DEF CON 34. Its maker page describes an RP2350-based infrared tag game with a 915 MHz LoRa score-sync option and QR fallback, while a public late-July update says the boards have arrived and final assembly and flashing are in progress. The record is pre-event and independent; it is not an official DEF CON admission badge.

Lifecycle

Add-ons & Upgrades

Laser* Tag Badge DS (DEF CON 34) publicly documented

infrared compatibility protocol

OpenLASIR interoperability

The MIT-licensed OpenLASIR repository defines a NEC-inspired 38 kHz, 32-bit infrared interoperability protocol and identifies the 2026 Laser* Tag Badge DS as a first-party supporting badge.

Compatibility: Laser* Tag Badge DS (DEF CON 34)

Laser* Tag Badge DS (DEF CON 34) planned with stated fallback

leaderboard synchronization

LoRa and QR score sync

The maker page describes online leaderboard score syncing over LoRa if RF conditions permit, with QR-code encoding of game data as the documented fallback.

Compatibility: Laser* Tag Badge DS (DEF CON 34)

Operational history

Issues & Camp Impact

Laser* Tag Badge DS (DEF CON 34) note

LoRa score-sync reliability caveat · official maker documentation · conditional design

The maker page says LoRa leaderboard syncing depends on RF conditions and may fail to reach planned base stations in a crowded ISM-band environment, with QR codes as the stated fallback. It also describes IR-play limitations from venue lighting and reflections.

The record does not present LoRa connectivity, leaderboard coverage, or all-vs-all IR play as guaranteed DEF CON 34 behavior.

Laser* Tag Badge DS (DEF CON 34) note

badge firmware and design archive gap · official maker page and public protocol repository · needs final badge archive

OpenLASIR is a public MIT-licensed compatibility protocol with examples, but reviewed sources do not publish complete final DS firmware, a badge-specific flashing workflow, schematic, PCB files, Gerbers, BOM, electrical design details, or a complete badge firmware license.

The catalogue can distinguish documented interoperability and game intentions from unverified full-badge implementation or reproducible-build claims.

Laser* Tag Badge DS (DEF CON 34) note

missing rights-cleared image · local project policy · needs licensed original replacement

No Laser* Tag Badge DS image is published because the maker page, public pre-event update, and protocol repository do not pair a specific badge image with source URL, reusable license or explicit permission basis, attribution, and processing notes.

The current United States record remains source-backed and image-free rather than copying maker-site images, Reddit images, repository previews, screenshots, placeholders, or generated approximations.

Laser* Tag Badge DS (DEF CON 34) note

pre-event assembly and fulfillment boundary · maker page and public assembly update · awaiting DEF CON 34 outcome

The maker page calls the project a 2026 DEF CON 34 version and warns that production might not finish in time. A public late-July update says boards are in hand and final assembly/flashing is more than halfway complete, but no completed run, attendee delivery, quantity, or final fulfillment report is public.

The catalogue records a currently evidenced independent project and announced pickup path, not a confirmed delivered run, attendance-wide issue, final recipient count, or post-event game outcome.

Resources

Laser* Tag Badge DS official maker page official maker page · Dani Weidman's project page for the 2026 DEF CON 34 Laser* Tag Badge DS. It documents the planned hardware, IR game, conditional LoRa/QR scoring model, pickup context, production caveats, and named project help. Its images are evidence only, not a reuse license. OpenLASIR repository public interoperability protocol repository · Dani Weidman's MIT-licensed public OpenLASIR repository for a NEC-inspired 38 kHz IR protocol with 32-bit frames plus MicroPython and Arduino/C++ examples. It identifies Laser* Tag Badge DS as a first-party supporting 2026 badge, but is not a complete DS firmware or hardware-design archive. Laser* Tag Badge public assembly update public pre-event assembly update · Public late-July DEF CON community update saying boards are in hand and final assembly/flashing is underway, with announced DEF CON-week pickup points and a LoRa-or-QR scoring fallback. The post image does not establish reusable image rights.

Sources

Dani Weidman: Laser* Tag Badge DS Retrieved 2026-05-15 · Primary maker source for the 2026 DEF CON 34 DS project, including the RP2350-Zero platform, IR components, conditional 915 MHz LoRa radio, displays, LEDs, controls, 18650 battery, SAO-port limitation, game rules, pickup plans, and production/RF caveats. It does not provide reusable image permission. GitHub / danielweidman: OpenLASIR Retrieved 2026-05-15 · Primary public protocol source with an MIT license, NEC-inspired 38 kHz carrier and 32-bit framing documentation, MicroPython and Arduino/C++ examples, and a first-party reference to the 2026 Laser* Tag Badge DS. It does not establish a complete badge firmware, badge PCB archive, or final production build. Reddit / r/Defcon public post: Laser* Tag Badge updates / final preorders Retrieved 2026-05-15 · Public late-July pre-event update corroborating that boards had arrived and final assembly and flashing were underway, plus announced pickup and LoRa/QR-score-sync context. It is used conservatively as a production-status update, not as a final fulfillment report or reusable-image license.