BSidesTLV
Official publisher of the 2026 Hardware Village, event, and FAQ sources used for this planned electronic badge record.
SourceBSidesTLV 2026 · Israel · 2026
Planned Israeli hardware CTF badge
A planned BSidesTLV 2026 electronic badge record from the official Hardware Village page: the June 25, 2026 conference centers its hardware CTF on an electronic badge and schedules Badge Talk plus Badge Hacking sessions.
People
Official publisher of the 2026 Hardware Village, event, and FAQ sources used for this planned electronic badge record.
SourceIt extends the Israeli BSidesTLV badge lineage beyond the 2025 Infinity Glove record while keeping the 2026 entry pre-event and source-limited until final hardware, firmware, challenge, and image evidence is public.
The official Hardware Village page proves an electronic badge is part of the 2026 hardware CTF, but this pass does not recover component names, PCB files, power details, board photos, schematics, BOM, firmware, or production notes.
The source trail documents hardware CTF activity around the badge and separate Badge Talk / Badge Hacking sessions. No firmware repository, challenge binaries, writeups, app framework, or protocol documentation has been recovered yet.
The 2026 Hardware Village page frames the badge as the center of the hardware CTF, with attendees expected to solder, probe, debug, and interact with badge challenges during the event. The public record stays pre-event until the June 25, 2026 edition has shipped-badge evidence.
Lifecycle
The official Hardware Village page says the hardware CTF centers around the electronic badge and asks attendees to solder, probe, debug, and solve it.
SourceThe Hardware Village page lists Badge Talk and Badge Hacking sessions as part of the 2026 badge workflow.
SourceOperational history
The record preserves badge existence and planned CTF framing while avoiding unsupported component-level claims.
The Israeli 2026 record remains source-backed and image-free rather than copying page media, screenshots, or generated artwork.
The record should not claim shipped hardware, final challenge behavior, attendee distribution scope, or post-event outcomes until the event happens and artifact-level sources appear.