Issue dossier
The maker documents three XIAO ESP32-S3 boards, patch antennas, display, lithium-ion cell, Gerbers, a battery cage, and real build caveats including reversed battery connector polarity, button-footprint mismatch, and fit variation. Reviewed sources do not establish a full final BOM or substitutions, unit inspection, battery cell provenance, charge/protection settings, current or thermal measurements, enclosure safety, RF exposure, emissions/regulatory compliance, ESD/short/reverse protection, test results, or safe assembly/service instructions.
A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.
Back to issues index
hardware, battery, radio, electrical-safety, and compliance boundary · maker README and hardware guide · component and build caveats published; broad validation unrecovered
Public fabrication material and candid build notes remain discoverable without becoming a universal build, battery-service, radio-operation, or electrical-safety recommendation.
- Badge
- Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
- Category
- hardware, battery, radio, electrical-safety, and compliance boundary
- Severity
- note
- Confidence
- maker README and hardware guide
- Status
- component and build caveats published; broad validation unrecovered
- Timeframe
- post-event source pass
- Source note
- Friend or Foe README and hardware/badge README.
maker-published fabrication and mechanical documentation
Primary source for the Gerber/fabrication, component, battery-polarity, button-fit, display-fit, antenna, and 45-unit DEF CON-run statements. It does not establish final unit equality, safe construction, regulatory compliance, or participant allocation.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
maker-published hardware and firmware archive
Public maker archive for the Friend or Foe badge's high-level hardware, firmware, Android, backend, and documentation trail. It establishes a publisher-described independent project, not DEF CON or Packet Hacking Village issuance, event-wide allocation, a security review, or a reusable image grant.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
maker-published post-event Android release
The September 16, 2026 release publishes an Android APK and checksum for the companion's nearby-aircraft ordering, 15-mile aircraft-alert distance gate, location-refresh handling, and Bluetooth/Privacy-list stability changes. Its publisher-reported emulator and test results do not establish physical-phone, badge, Bluetooth-radio, location, RF, privacy, security, or field-operation validation.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
maker-published project documentation
Primary maker documentation for the three-board ESP32-S3 badge architecture, passive RF-awareness framing, display/Android surface, published version labels, and stated 45-badge DEF CON run cost context. It is not an independent manufacturing, allocation, safety, or performance audit.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
official village programme
Primary official programme source for the completed Friend or Foe presentation, its Packet Hacking Village association, and the source-named Will Hatzer / Charles Grow roles. It does not establish badge allocation, recipient handoff, RF performance, or image rights.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
official village programme
Primary Packet Hacking Village page for the completed August 7-9, 2026 DEF CON 34 village setting and its scheduled Friend or Foe presentation. It does not say the village or DEF CON issued, sold, funded, or distributed the badge.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
repository license
The repository publishes an MIT license. It makes source-license provenance visible but does not by itself identify a documentary badge image with attribution and processing notes for gallery publication.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
Packet Hacking Village / Wall of Sheep · retrieved 2026-09-06
Primary official village programme establishing the completed Packet Hacking Village DEF CON 34 setting, dates, and the Friend or Foe talk listing. It supplies event context only, not badge ownership, issuance, funding, allocation, handoff, or technical validation.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
Packet Hacking Village / Wall of Sheep · retrieved 2026-09-06
Primary official talk page identifying the completed Friend or Foe presentation and naming Charles Grow as hardware designer. It does not establish a DEF CON, village, or attendee-wide badge distribution.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
lnxgod / GitHub · retrieved 2026-09-06
Primary maker description for the three-board ESP32-S3 wearable badge, passive RF-awareness framing, Android-over-USB-C surface, listed components, and maker-reported 45-badge DEF CON run. It is not a third-party audit or recipient ledger.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
lnxgod / GitHub · retrieved 2026-09-06
Primary maker hardware source for fabrication files, three-XIAO-ESP32-S3 build, antenna and board details, build caveats, and the historical 45-badge DEF CON run statement. It does not prove all final units, a safe fabrication process, certification, or public image reuse.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
lnxgod / GitHub · retrieved 2026-09-06
Primary source-license record for the public repository. No specific repository or programme photo is selected for this gallery because the required source, attribution, and processing provenance have not been assembled.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
lnxgod / GitHub · retrieved 2026-09-16
Primary maker-published post-event Android companion release. It names nearby-aircraft sorting, a 15-mile valid-distance gate for helicopter and ADS-B-drone alerts, refreshed phone location handling, and stable Bluetooth/Privacy result ordering. The publisher reports automated and emulator checks, while explicitly retaining the need for physical-phone Bluetooth and field-location testing; it does not establish physical badge compatibility, RF/detection accuracy, location accuracy, privacy/security outcomes, or field safety.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)
lnxgod / GitHub · retrieved 2026-09-06
Primary maker-published archive for the independent Friend or Foe badge/platform, its ESP32 source tree, current published-version labels, and root MIT license. It does not establish organizer authorization, final event units, allocation, RF efficacy, privacy/security outcomes, or cleared gallery-image rights.
Badge: Friend or Foe Badge (DEF CON 34 Packet Hacking Village)