HackRVA
RVAsec credited HackRVA for the 2016 badge line.
SourceRVA5sec 2016 · United States · 2016
Hand-built badge with USB reflashing and CTF challenge hooks
The RVA5sec 2016 badge is documented by HackRVA's official interview as a hand-built custom-firmware electronic badge with reused/improved hardware, standard USB reflashing, low-frequency serial-transmission experimentation, and CTF challenge hooks.
People
RVAsec credited HackRVA for the 2016 badge line.
SourceThe 2016 interview identifies Morgan Stuart in the badge-team context.
SourceRVAsec provided the conference context for the 2016 badge.
SourceThe 2016 interview is attributed to Paul Bruggeman.
SourceIt records the fifth-year RVAsec/HackRVA badge line as an iterative community hardware project, with explicit production numbers, team credits, firmware goals, and challenge behavior rather than just a photo of a conference object.
The interview says the hardware was mostly reused from the prior two years with improvements based on attendee feedback, and that more than 350 boards had been quality checked before the conference. The team built the badges by hand and emphasized reusable hardware after the event.
HackRVA describes mostly custom firmware, standard USB reflashing, a shifted focus toward CTF challenges, and experimentation with low-frequency serial transmissions through the speaker and badge LED sensors.
The badge-team interview explicitly names the project as a learning process for the local hackerspace, with more volunteers joining, production getting easier, and attendees encouraged to modify and reuse the badge after RVAsec.
Lifecycle
The 2016 interview says the badge focus shifted toward CTF challenges.
SourceHackRVA described standard USB as a way to make post-event reflashing easier.
SourceHackRVA discussed low-frequency serial transmissions from the speaker to nearby badge LED sensors.
SourceOperational history
The record remains image-free rather than copying article media.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The record avoids claiming a recovered schematic, BOM, final firmware tree, or complete CTF source.