DEF CON 34 · United States · 2026
Maker-published planned SSTV badge project for HRV/DEF CON 34; physical unit unverified
The public `livitup/hrv-sstv-badge` repository describes itself as building an SSTV #badgelife badge for HRV at DEFCON 34. Its commit-pinned source contains a project README, native KiCad board files, and a status document dated March 22, 2026 that still records design and prototype milestones rather than a shipped unit. Ham Radio Village's own page independently confirms its DEF CON 34 event in Las Vegas on August 6-9, 2026, but does not identify or endorse this project. The sources therefore support a publicly documented planned independent electronic-badge project associated with HRV/DEF CON 34, not an HRV- or DEF CON-issued artifact, ticket benefit, access credential, completed unit, allocation, delivery, or rights-cleared image.
People
The project is published from the livitup GitHub account. This credits a source-publisher role only; it does not identify a real-world person, establish hardware, firmware, art, manufacturing, or distribution authorship, or infer Ham Radio Village, DEF CON, or image-rights authority.
SourceThis record preserves a detailed current hardware-design trail without converting KiCad files, a README, or planning-status text into evidence of a fabricated, field-tested, or distributed radio badge. It deliberately records only high-level documented capabilities and does not reproduce installation, configuration, connection, or radio-operation directions.
The commit-pinned README describes a proposed RP2350B-based wearable with a camera, 2.4-inch TFT display, microSD storage, addressable LEDs, USB-C rechargeable LiPo power, two SAO headers, and separate SA818 radio-carrier boards. The public hardware tree contains main-board and carrier KiCad projects. These are maker-published design claims, not proof of a prototype, final component selection, completed board revision, production run, battery or power-path validation, radio characterization, electrical safety, compliance, or parity with any event unit.
The repository exposes CMake material, firmware documentation, and a C source file, while its dated status document still marks firmware development and a firmware MVP as not started. No reviewed source establishes a tagged firmware release, independently reproducible build, final binary, source-to-device mapping, update/recovery outcome, data practice, security review, or support commitment. The catalogue links the source trail but does not repeat its build, flashing, debugging, configuration, or radio-operation procedures.
The maker frames the planned artifact as a retro television-style badge for social image exchange in the DEF CON BadgeLife / Ham Radio Village context. The official Ham Radio Village page establishes that HRV is returning to DEF CON 34, not that it commissioned, approved, distributed, or operated this project. The claimed event association remains independent and pre-event.
Source-backed hardware metadata
Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.
The maker repository describes a planned SSTV #badgelife badge for HRV at DEFCON 34. Native design files exist, but no reviewed source confirms a prototype, delivery, or final event unit.
Signal sourceThe commit-pinned README names an RP2350B. This records the proposed MCU family, not final board population, firmware deployment, or physical-unit parity.
Signal sourceThe commit-pinned README proposes two SAO connectors but does not establish a final standard/version, pinout, electrical limits, host compatibility, or safe connection outcome.
Signal sourceThe commit-pinned README names USB-C. It does not establish connector protection, input limits, data behavior, charging implementation, or safe-use outcome.
Signal sourceThe commit-pinned README proposes a 2.4-inch TFT display. It does not establish a final display model, electrical behavior, physical assembly, or final event unit.
Signal sourceThe commit-pinned README proposes addressable LEDs. This does not establish a final population, power budget, animation behavior, safety, or physical-unit parity.
Signal sourceThe commit-pinned README proposes rechargeable lithium-polymer power. It does not establish a cell, charging/protection design, runtime, fault behavior, safety validation, or a delivered unit.
Signal sourceThe commit-pinned README proposes USB-C charging. It does not establish charger design, electrical compliance, power-delivery behavior, or safe service procedures.
Signal sourceRepair, preservation, and legal lab context
Parts, tools, and supplies that match this badge's documented hardware, protocols, or preservation needs. These are category-level recommendations, not compatibility guarantees.
Headers and connector supplies for SAO repair, add-on testing, and preservation.
This badge has a documented SAO connector. Matched technical signals: SAO.
Vendor link · selected for technical relevance
Display modules and related parts for repair and preservation planning.
This badge has a documented display signal. Matched technical signals: LCD.
Vendor link · selected for technical relevance
I2C adapter supplies for badge add-ons, sensors, and lab documentation.
SAO workflows often use I2C-compatible add-on testing and bench documentation. Matched technical signals: SAO.
Vendor link · selected for technical relevance
Extension wiring and jumper supplies for testing or displaying SAO add-ons away from the main badge.
Extension wiring is useful for testing and displaying SAO add-ons. Matched technical signals: SAO.
Vendor link · selected for technical relevance
Headers, sockets, and connector supplies for display repair or replacement work.
Display headers and connectors are useful for repair and preservation planning. Matched technical signals: LCD.
Vendor link · selected for technical relevance
Lifecycle
The README describes a camera, display, and microSD-based image surface within the planned badge. It establishes the intended project concept, not functioning capture, encoding, storage, display, interoperability, data handling, privacy, final firmware, event operation, or a delivered-unit result.
SourceThe README describes separate carrier boards for a radio module as part of the planned SSTV concept. The catalogue records that high-level design claim without reproducing setup, configuration, frequency, transmission, or radio-operation procedures, and without asserting a tested assembly, authorization, license status, performance, safety, or compliance outcome.
SourceThe maker's commit-pinned hardware tree contains native KiCad project files for a main badge board and separate carrier boards. This is a source-availability record only; it does not confirm a final design revision, Gerbers, component sourcing, fabrication, assembly, testing, safe behavior, production quantity, or DEF CON handoff.
SourceOperational history
The catalogue links the public source archive without treating it as an audited or finished firmware release, authorizing users to follow its procedures, or treating the root license as broad hardware/media/image permission.
The record retains high-level source-backed design claims without treating them as an electrical specification, a battery-safety statement, a radio-compliance claim, a universally compatible SAO result, or operational advice.
The catalogue classifies this as an independent planned project associated with the event context, not an HRV-issued or DEF CON-issued badge, a guaranteed attendee benefit, a venue-authorized activation, a Human badge, an access credential, or proof that anyone received a physical unit.
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.
Public design files are preserved as evidence of a planned artifact without being presented as proof of a fabricated, functioning, final, distributed, or event-deployed badge.