Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
The Wi-Fi and pick-and-place log documents CR123A cells and holders, diode validation, stencil-holder work, eight early hand-built badges, and pick-and-place setup six days before the conference.
SourceThe H2HC card-printing posts document CR80 85.6 x 53.98 mm card sizing, a DASCOM DC-7600 600 DPI full-duplex re-transfer printer, front/back artwork preparation, on-site pickup workflow, and optional UV-ribbon capability rather than electronic badge firmware.
SourceThe official post documents panelized boards, solder-paste stencil work, reflow, inspection, through-hole soldering, and testing.
SourceThe building-badges log says kits were made, speaker and staff badges were built, and LED badges were being assembled with a TM-220A pick-and-place shortly before the conference.
SourceThe first-hand writeup names Xometry as the injection-molding partner and describes design-for-manufacturing tradeoffs around wall thickness, sink marks, lens geometry, and schedule pressure.
SourceThe preserved DEF CON 33 programme calls the Vulnerable ATM Badge the largest badge at the conference that year and says it simulates ATM attack surfaces in a physical form factor that can be carried with two hands. It does not provide an operating procedure, board or module inventory, safety assessment, or proof of a final attendee-owned unit.
SourceThe badge-team notes describe USB device support, USB host, HID or CDC behavior, and ST-Link V2/SWD programming expectations.
SourceThe official page identifies the ATTINY85 pin mapping for SAO data pins and names the Amphenol programming-port and male-connector parts with 1.27 mm pitch.
SourceThe README documents Microchip Studio or avr-gcc build paths, `L12024POV.hex`, avrdude flashing to `t4313`, and Kraken or Arduino ISP programmer options for attendees.
SourceThe hardware-hacking guide documents AVRISP wiring and commands for initialization, target identification, flash reads/programming, and fuse access.
SourceThe badge could be programmed through an FTDI header, giving attendees a direct Arduino-style code-loading path.
SourceThe project is publicly shown in staged progress from idea collection through prototyping, electronic design, firmware, and delivery, with budget fit called out as the next challenge.
SourceThe repository publishes public design/source directories, names HotGlewd for PCB/sticker/promotional artwork, BitAssembly for pixel artwork, and declares the work CC BY-SA 3.0. The marketplace separately credits the SCP-1471 source. These statements provide traceable project provenance but do not clear a particular product image, confirm every dependency's licensing, or prove that every third-party lore asset may be republished.
SourceThe repository BadUSB notes document HID report framing, script loading, command bytes, and custom-HID interface context for writing scripts to the badge.
SourceJake Walker's Protoboard Hexpansion gives badge owners a small general-purpose prototyping surface in the official connector shape.
SourceThe public `bunnie/dc34-image` README identifies a Python utility for uploading a black-and-white 128×128 image to a DC34 badge over USB serial. It documents a customization path, not physical display technology, a selected shipped image, a final embedded firmware build, or event-unit parity.
SourceThe public `bunnie/dc34-bio` README identifies a Python utility for loading a BIO program to a DC34 badge over USB serial, with documented SAO-I/O selection and clock configuration. It documents a user-side tooling path, not complete embedded firmware, final connector mapping, safe settings, a supported end-user workflow, or event-unit parity.
SourceThe source tree documents a versioned `thermometer-v1.1.0.uf2`, USB BOOTSEL flashing, `flash_and_test.py` serial verification, and soak-log/report scripts for batch programming. Those tools demonstrate a public intended workflow, not a signed release, independently audited production test, all-unit pass record, final factory process, repair policy, or guaranteed recovery path.
SourceCPEC's companion repository says it contains design files for SAO plug-in modules for the CPEC DC 34 badge. Its commit-pinned source tree contains KiCad project, PCB, and schematic paths for fist, gatling, laser, missile, panel, and sword-named variants, an Arduino source file, and BOM/placement artifacts. The catalogue records that scoped design-source availability without inferring a populated board, hardware behavior, wiring, pinout, firmware result, safe electrical envelope, standard/version match, or working connection to a CPEC badge.
SourceThe maker-linked Penzz-HM repository includes the Arduino sketch, ESP32-S3 build outputs, a Gerber archive, enclosure STL files, and a root MIT license. It supplies a practical preservation and modification trail, but does not establish a complete schematic/BOM, reproducible production build, release-to-device mapping, every-dependency license, image-reuse selection, support commitment, or warranty.
SourceThe product links an Ouroboros How It Works PDF and a GitHub repository. The repository describes a distinct AVR-assembly ATmega328P authentication framework and GitHub marks its license field Other; it is not a released CH32V003 badge firmware, board, build package, or clear license grant. The linked PDF similarly does not establish a reusable media or source license.
SourceThe published ESP32 sketch enables promiscuous mode, sets a selected Wi-Fi channel, and increments a packet counter that it displays through the dial-style interface. It does not document capture filtering, persistence, encryption handling, packet content storage, channel coverage, sampling accuracy, traffic authorization, privacy handling, lawful-use context, test results, or RF performance.
SourceThe sketch scans nearby Wi-Fi networks, lets the user lock a selected access point by BSSID or SSID, and periodically displays the matching access point's RSSI. This documents a source-level tracking surface, not a validated locating tool, a guarantee that a BSSID belongs to the intended device, permission to scan or follow third-party equipment, a precise distance measurement, or a privacy-safe deployment.
SourceThe repository says core 0 samples DS18B20 temperature about every second and updates the display buffer, while core 1 multiplexes three digits at about 333 Hz; revision 1.3 or later cycles four brightness levels. It does not establish the exact binary deployed to every sold unit, final timing/accuracy under load, error handling, field behavior, update cadence, or supported configuration matrix.
SourceThe README documents Arduino-compatible firmware and PlatformIO profiles for normal, demo, and factory-test builds, including tests for LED order, orientation, and shake sensing. The code and documentation do not establish a public tagged event release, production test log, safe user modification path, support obligation, or actual configuration in an assembled badge.
SourceThe public PFC161 source defines a four-entry color buffer, blue/orange/off state values, touch initialization, a 470 pF touch-capacitor note, thresholded button logic, and timer-driven LED updates. This is source-level evidence for touch-controlled animated-color behavior, not a claim about the physical LED model/count/order, touch sensitivity, final modes, brightness, latency, power draw, safety, accessibility, or behavior of every produced unit.
SourceThe public C source includes PFC161 headers, configures active-low PA4/PA5 LED outputs, keeps separate LFSR state per channel, derives individual delay targets, and flashes channels from its main loop. This is source-level evidence for a two-channel randomized-light implementation, not proof of the exact final illuminated words, distribution of outcomes, timing, brightness, physical LED population, or behavior of every produced unit.
SourceThe public firmware declares ten LED modes, button-driven cycling, per-pixel color output, and pins labelled for minibadge clock control. This documents a possible firmware interaction surface without claiming that all current units expose the same button, pins, timing, modes, firmware revision, programming path, accessibility behavior, or support.
SourceThe public firmware declares ten LED modes, button-driven cycling, per-pixel color output, and pins labelled for minibadge clock control. This documents a possible firmware interaction surface without claiming that all current units expose the same button, pins, timing, modes, firmware revision, programming path, accessibility behavior, or support.
SourceThe source initializes touch ADC support, reads PD2 through `ReadTouchPin`, starts audio after a threshold, and updates the source-declared D/F/I/U and display LED outputs from timer-driven code. This is source-level evidence of the intended interaction, not a claim that every physical unit behaves identically or that its touch sensitivity, sound volume, audio content, LED population, timing, accessibility, or reliability has been independently tested.
SourceThe public documentation names exposed UART pins for an XMODEM bootloader and describes a rapidly developed codebase with some unresolved bugs, while the repository exposes current source/firmware material. It documents an implementation and update trail without reproducing flashing steps or claiming a tagged/reproducible firmware release, verified binary-to-board mapping, secure update, rollback/recovery package, support policy, or safe owner modification.
SourceThe maker and README describe roughly five or six lighting programs, a favourite-colour setting, motion enable/disable, random or sequential program selection, a handle program button, and rear setup button. The README describes a star touch sensor but says it might not work by DC34, and describes the SC7A20H accelerometer while separately documenting a REV1 motion-interrupt limitation. This preserves high-level source claims without promising final program count, touch behavior, motion reliability, or user experience.
SourceCall Center Village's public source calls this a phone-booth-shaped, power-only SAO v2: one 1206 LED and one 330 ohm current-limiting resistor are wired in series from VCC to GND, with no microcontroller or I2C and the SDA, SCL, GPIO1, and GPIO2 pins left unconnected. The repository includes KiCad project, schematic, PCB, connector symbol, BOM, placement, netlist, Gerber packages, and a CC BY-SA 4.0 license. It does not prove final kit or pre-soldered population, per-unit quality, current draw under an actual host, final production revision, DC34 electrical test result, user assembly outcome, or general host safety.
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.
SourceThe electronics repository publishes the PCB design in KiCad with schematic PDF and BOM exports, and its companion case repository publishes case/button/acrylic design files; both state CERN-OHL-S-2.0 for design files. Those releases document modifiable design sources, not a promise that every commercial unit matches them, a safe build recommendation, source-code license scope, or image-reuse permission.
SourceThe project's MVP note identifies the Arduino/C++ tree as the live implementation and describes visual/interactions work. This establishes accessible current project source, not a tagged release, reproducible build, compiled attendee image, device configuration, flashing/support workflow, final feature set, or proof that it ran on a distributed badge.
SourceThe repository identifies an RP2350B, 16 MB flash, USB-C, and a 1.5-inch 128 by 128 grayscale SSD1327 OLED. The listing says over fifty LEDs, while the diary describes two 24-device red-green LED banks. This creates a useful documented surface but not a final populated-unit specification, current budget, assembly record, or universal performance guarantee.
SourceThe post says only 100 would be available at a Sneakreaper Industries booth. In replies, its author gives $150 and Hall W4. The source does not document a checkout page, seller identity, order count, stock ledger, payment, refund/replacement terms, exact booth authorization, completed manufacture, handoff, delivery, remaining stock, or post-event outcome.
SourceCircuit Board Medics' MIT archive documents CircuitPython 10.2.1, editable `code.py`, a preloaded launcher, tutorials, a serial-console guide, and samples. It does not establish a signed or immutable factory image, deployment record, security review, or support commitment.
SourceThe FirstBuild repository publishes a schematic PDF, firmware tree, and MIT license for software and associated documentation. These sources establish a valuable design and software trail, but do not automatically cover credited artwork, photographs, trademarks, every third-party dependency, a final hardware manufacturing package, or a selected reusable badge image.
SourceThe repository specifies an RP2350A QFN-60, W25Q16 2 MB flash, USB-C for programming and serial debug, RUN/BOOTSEL/brightness buttons, and a three-pin SWD header. The marketplace adds 3.0 V tolerance and says non-power SAO pins are routed to the RP2350. These sources do not establish a final board revision, voltage/current budget, level shifting, overload protection, SAO standard conformance, electrical testing, or universal host compatibility.
SourceThe source tree names a DS18B20 one-wire sensor on GPIO 16 and three common-anode seven-segment displays multiplexed through a 74HC595, while the listing describes a waterproof probe and triple display. The firmware source says a missing DS18B20 produces a display fallback and logs die temperature to USB serial. No reviewed source provides temperature calibration, traceability, environmental limits, response time, error bounds, food-contact certification, or a suitable-use guarantee.
SourceThe README points to an Arduino 1.8.5 firmware directory and says stock AVR chips need a one-time bootloader step before normal Arduino flashing. This preserves an implementation trail without reproducing programming commands or claiming a safe procedure, final fuse/programmer configuration, reproducible build, tagged firmware, deployed badge binary, recovery path, support, or warranty.
SourceThe published KiCad source identifies an NT3H2111W0FHK NFC tag chip and GPS footprints and labels. This preserves the design-level evidence without asserting a fitted GPS receiver, a particular NFC configuration, field performance, data practice, authorized use case, or final assembled configuration.
SourceThe README names an STM32G031F8P6 Cortex-M0+ controller, MXC6655XA I2C accelerometer, and eight SK6805SIDE-G-003 side-emitting RGB LEDs as the current production target. It is source-backed design intent, not proof that this exact hardware was manufactured, placed on every board, tested, or distributed.
SourceThe README's BOM names an ATmega328P-PU, PCF8523T real-time clock, three pushbuttons, seven 2×3 SAO connectors, a 9 V jack/battery path, regulator parts, LEDs, display components, and an ISP port. It identifies a design inventory, not a verified final board, complete/electrically accurate BOM, component availability, safe power path, SAO pinout/current budget, host compatibility, or tested build.
SourceThe public repository calls the project a MidWestCoast Badge for a MidWestCoast Party and its firmware README labels the code DEF CON 34 badge firmware. These labels establish a publisher-supplied pre-event association, not party operation, organizer affiliation, date or venue, DEF CON endorsement, on-floor authorization, allocation, sale, pickup, attendee entitlement, or access control.
SourceHackaday reports BLE and NFC alongside the low-power badge design, while the hardware archive identifies the nRF52832-based MDBT42Q module.
Source