Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
The miniconf workflow gathered training video from the car and analyzed it offline with TensorFlow before attendees tried self-driving runs.
SourceThe README says Mode 1 cycles GPIO1/GPIO2 on the left badge port. The current source drives four two-bit patterns, releases the lines, samples them, and then listens for edges. NilbinSec explicitly warns that this mode may harm a main badge depending on its GPIO configuration, so the source does not establish a safe, supported, or authorized use on any connected device.
SourceThe README describes Mode 2 as triggering the open-drain CPU wake-up interrupt on GPIO4 of the right SAO port. The source holds its configured GPIO line low while the Attack/Trigger switch is pressed, then releases it to high impedance. This documents the public implementation, not a safe/authorized use, final badge compatibility, or successful challenge result.
SourceThe README broadly says Mode 3 cycles 0x00–0x7F while listening as an I²C slave. The source instead documents passive bus observation over 0x08–0x77 and explicitly skips 0x19 and 0x3C. It says it does not drive SDA/SCL or ACK, but this is still not a guarantee of target compatibility, complete address coverage, bus safety, or authorized testing.
SourceOfficial docs preserve post-event recovery behavior: firmware v1.6.0+ can force hexpansion detection with button chords, and failed updates may require better WiFi or flashing.
SourceThe sources name an ATtiny1616, five reverse-mounted addressable LEDs, rear ambient-light LED, handle setup LEDs, two physical controls, CR2032 power with polarity protection, a more efficient 3.6 V boost converter, and external MOSFET gate. They do not establish final PCB/schematic/BOM, exact LED or power configuration, current draw, runtime, electrical limits, fabrication, test result, safety validation, or that all delivered units use the documented REV1 design.
SourceThe repository README calls Beelzebub a holder for five minibadges, while the store says the board is assembled except for minibadge headers and an optional battery holder, and excludes shown minibadges. Those statements do not establish the exact slot layout, header/pinout, MiniBadge standard, power/clock/data behavior, soldering skill or safety requirements, attachment force, mechanical fit, contents of every unit, or compatibility with a particular minibadge.
SourceThe repository README calls Krampus a holder for six minibadges, while the store says the board is assembled except for minibadge headers and an optional battery holder, and excludes shown minibadges. Those statements do not establish the exact slot layout, header/pinout, MiniBadge standard, power/clock/data behavior, soldering skill or safety requirements, attachment force, mechanical fit, contents of every unit, or compatibility with a particular minibadge.
SourceThe vendor list says CTF challenges unlock extra features and bling modes, names Drinking Roulette, and calls the product fully programmable. No source publishes game rules, age/access policy, challenge/solution path, reset path, player scope, score service, firmware, configuration, content rights, data handling, or security review.
SourceThe vendor PDF says the Sheriff SAO supports laser-tag play that makes friends' badges light up and that an IR blast can power down TVs. It does not identify transmitter/receiver parts, carrier/protocol/code set, range, target compatibility, consent/safety boundaries, power, regulatory context, tests, or a guarantee that any third-party badge or television will respond.
SourceThe Sheriff guide lists the Sheriff SAO, CR2032 or LIR2032 battery, magnet battery holder, sticky pad, soldering iron, and flush cutter; it describes soldering battery wires, using the holder's independent switch, selecting Sheriff batt mode, and magnet-mounting it through clothing. It says an LIR2032 may last longer but the badge does not charge it. The source does not replace battery-safety, charging, thermal, medical-device, magnetic-interference, or assembly-risk guidance.
SourceThe DEF CON 27 bio describes TwinkleTwinkie as an independent PCB artist who has manufactured artistic PCB badges and indie badge add-ons.
SourceThe source release includes a UF2, user-preferences delta, build notes, provisioning GUI/script, and hardware-independent tests. It names a Meshtastic `event/defcon34` relationship and documents its own source-published configuration boundary, but it is not treated as a post-event support commitment, exact delivered-unit inventory, or a general-purpose flashing procedure.
SourceThe v1.1 release says some pre-sale 1.0 or 1.01 badges should flash the update to fix an unspecified issue, and says `enable, sh ver` can check that the badge is on the 1.1 build. It does not identify the issue, affected count, unit identifiers, changelog, validation, rollback, installed population, or update outcome.
SourceElectronic Cats calls its public hardware project Badge Oficial Tropicon 2026, while TROPICON's official home establishes the completed Cozumel event. The event page does not itself link or independently confirm the repository, and neither source establishes ticket inclusion, quantity, price, pickup, delivery, admission use, or recipient handoff.
SourceThe reviewed maker release contains the v1.4 KiCad project, DRC/ERC reports, Gerber archive, BOM/placement/netlist production files, board documentation, populated-board media, and NanoVNA tuning material. The repository calls its production outputs the exact files from which its run was built; the catalogue preserves that as a maker statement rather than independent manufacture, quality-control, or field-performance proof.
SourceThe maker describes left, center, and right dial positions for 2.4 GHz channel monitoring, RSSI foxhunting, and local browser firmware flashing. The source uses a rotary input to choose operating paths, but does not establish mode reliability, range, scan completeness, update success, accessibility, safe use, or that every sold unit has identical configuration.
SourceThe Exploitee.rs announcement says a new Hacker Pager revision is being brought to DEF CON 34, describes online availability windows, BadgeLife Village pickup, and no on-site sales. It does not publish a final inventory, price, order ledger, vendor authorization, completed sale, pickup, delivery, refund, replacement, or post-event availability result.
Sourcecoryallegory says the unit is fully assembled, uses a standard 2 by 3 SAO header, and has cycling multicolor LEDs that light the keyboard. No source supplies an LED count/part/current, controller, voltage/current limits, pinout, orientation, power budget, circuit, schematic, BOM, PCB files, dimensions, safety guidance, or host test matrix.
SourceThe listing says the Sphere SAO works with upside-down SAO ports and the High Roller SAO has blinky lights. The source does not provide a pinout, electrical requirement, LED count/type, firmware, published design, host test matrix, or general compatibility guarantee.
SourceAoSC says a confirmed $100-or-greater donation to a youth-STEM-supporting charity may receive a 2026 eChallengeCoin by U.S. mail or DEF CON pickup, and says the first 20 recipients are intended to have brass blanks created by students from a local high-school engineering program. These statements do not establish charity status, tax treatment, donation validation, privacy/retention practice, quantity awarded, recipient eligibility, shipping, pickup, school identity, manufacturing quality, payment, or final delivery.
SourceHogFillet describes a 555 timer clocking a ten-bit ripple counter, eight counter outputs driving eight LEDs, and an onboard trimmer controlling the timing rate. The source does not name component variants or values, flash-rate range, LED current, supply limits, power draw, electrical protection, schematic, BOM, PCB files, or final unit test results.
SourceThe product page says the speaker SAO plays monorail-themed sounds and has a mini SD card for adding MP3 files. It does not identify audio hardware, controller, firmware, MP3 limits, file workflow, source audio, media license, volume/safety behavior, or final shipped implementation.
SourceThe maker says the badge has three pre-programmed sound effects with accompanying light shows, including a gong effect. It does not identify audio hardware, firmware version, sound files, copyright/recording rights, controls, runtime, accessibility, configuration, or final shipped behavior.
SourceThe listing says two analog inputs are tuned precisely to unlock a hidden LED pattern, and solving four puzzles unlocks the badge's full potential. It does not publish the inputs, sequence logic, calibration range, solutions, reset behavior, accessibility path, scoring, or outcome evidence.
SourceThe maker says the 2026 coin presents as a serial device when connected to a computer and hosts the Sara and the Missing Artifacts terminal text adventure. It also says new firmware can support other adventures. No public game source, binary, command reference, release/version mapping, host test matrix, reset/save guide, accessibility documentation, or support policy was recovered.
SourceThe project page describes a Game Boy-inspired top-down adventure with 30-plus CTF puzzles, while the live listing describes 35-plus CTF and puzzle challenges. Both frame the badge as a playable adventure with unlockable bling; no public challenge archive, final count, solution policy, ruleset, scoring system, accessibility review, or completed game behavior is published.
SourceThe project page says badges can link up to 50 units, while the live listing says participants can create more than 1,000 unique words and phrases with other badges. Neither source publishes the transport, pairing, range, privacy/security model, player-data handling, protocol, connectivity requirement, interoperability, or final event behavior.
SourceThe README says the badge lets users display an estimate for when the AI singularity will occur, with front buttons that shift that estimate, eight seven-segment displays, and a real-time clock. It documents a source-project interaction concept, not an assembled unit, final screen/readout behavior, calibrated clock, usability result, event challenge, prize, or completed distribution.
SourceThe maker says a frog-themed CTF unlocks GIFs, bling, and secret surprises, and that a frogger-like game is built into the badge. No source provides challenge rules, release dates, solution path, scoring/leaderboard, content source or license, offline/online behavior, telemetry, personal-data handling, security model, or preservation archive.
SourceThe seller describes an underwater world where CTF challenges deliver packages to DEF-SEA inhabitants, potentially with other players, plus pirate battles, underwater cults, and a hidden Atlantis. No source provides rules, release timing, solution path, challenge inventory, player count, score validation, server/network behavior, content provenance, archive, or accessibility information.
SourceThe Spectre Sniffer listing says one included Pac-Man Ghost SAO comes in one of four colors. It does not name those colors, explain random or selected allocation, provide variant photos with reuse rights, map colors to the 1,000-unit giveaway, or establish identical artwork, PCB, components, behavior, or mechanical compatibility across all artifacts.
SourceA direct NilbinSec Bluesky reply says a Spectre Sniffer purchase includes a PAC-MAN Ghost SAO and helps fund over 1,500 free SAOs for Vegas. This is a product-bundle statement, not proof that the included companion is the same board, color, quantity pool, or configuration as the separately announced 1,000-unit giveaway.
SourceThe roster says touching the gun's end changes animated colors and that it interacts with the PORTAL Badge; the maker page describes blue portal, orange/red portal, and off modes and calls it a companion to the year's Portal Badge. Those claims do not publish a final interaction protocol, connector/pinout, input/output voltage/current budget, compatibility matrix, required Portal Badge revision, test results, or guarantee that any two units interoperate.
SourceThe product page says configuration and messaging use the Meshtastic app over BLE and that each unit has its own BLE PIN printed on its bag. The catalogue does not store PINs, identify a pairing workflow, claim a privacy/security review, or describe shared mesh traffic as private.
SourceThe listing names an onboard ATtiny814 connected to two RGB LED eyes, with power from the SAO connector or an included CR2032 battery. It does not publish default firmware, LED electrical data, power budget, battery runtime, voltage limits, connector pinout, host matrix, or final behavior.
SourceThe listing says v1.0 changes labeling and swaps I2C and GPIO pins from v0.1. It explicitly says the SAO does not support SAOv3 ARP or hot-plugging features. This does not establish final firmware behavior, electrical hot-plug safety, backwards compatibility, host-specific behavior, completed testing, or a full SAOv3 implementation.
SourceThe maker lists an ESP32-C3 and 24 RGB LEDs. The source does not identify the exact module, board revision, LED package/layout, power budget, radio configuration, antenna, electrical characteristics, or test results.
SourceThe listing names an ATtiny1616-S, two-character fourteen-segment display driven through shift registers, RGB LED, timer-based non-hardware-PWM behavior, and reprogramming through a separate UPDI adapter. It does not publish final firmware, exact parts/configuration, code, flashing instructions, electrical design, display/LED behavior contract, or support policy.
SourceThe live listing names an RP2350 with 4 MB flash, 16 RGB addressable LEDs, and a 128x128 grayscale display; the maker project page calls the display a 128x128 OLED. The source does not identify exact part numbers, wiring, final layout, revision, component list, schematic, PCB, test data, or a complete screen/LED specification.
SourceThe listing names seven orange reverse-mounted LEDs, an ATtiny824, and reprogramming with a separately obtained UPDI adapter. It does not publish exact LED electrical data, power budget, controller configuration, final firmware, wiring, flashing instructions, or a board-revision test record.
SourceThe product and repository describe configurable matching against BLE and Wi-Fi identifiers such as MAC/OUI/manufacturer/device-name/service/SSID fields, with LED, vibration, screen-wake, and scan-setting choices. They do not publish detection range, radio state timing, false-positive/false-negative rates, rule precedence, actual target databases, data retention, export, device consent, security controls, or a universal detection guarantee.
SourceThe source tree documents USB-C, UF2, SWD pads, a rear 2x3 SAO header, and a claimed SAO v1.69bis fit. It does not establish a pinout or electrical limit for every host, a supported-host matrix, a safe user workflow, or a general compatibility guarantee.
SourceThe technical release documents a four-layer board, chip-antenna feed/match design, u.FL test points, SAO-or-USB-C power mux, no battery, and source-published tuning data. Its claimed measured and power-budget context remains maker evidence, not a blanket electrical-safety, host-compatibility, or performance guarantee.
SourceThe maker says the Crown is fully soldered and assembled, names one SAO connector, three flashing red LEDs, and three resistors, and says it needs no separate battery or programming. The listing says only to use a compatible badge; it does not identify the connector standard, pinout, supply range, current draw, flashing circuit, LED/resistor parts, polarity/protection, host matrix, or safe attachment result.
SourceThe maker describes twenty-four NeoPixel LEDs, an ATtiny 814, USB-or-battery power, and custom or pre-programmed themes. The public firmware defines four eye and twenty wing LED arrays plus color/mode code. The sources do not establish LED model/current, exact final color order, controller package/fuses, USB/power implementation, power budget, battery type, safety, or final production parity.
SourceThe maker describes five NeoPixel LEDs, an ATtiny 814, development-pin access, USB-or-battery power, and custom or pre-programmed themes. The public firmware defines a five-element LED array plus color/mode code. The sources do not establish LED model/current, exact final color order, controller package/fuses, development-pin or USB/power implementation, power budget, battery type, safety, or final production parity.
SourceThe maker names an ATtiny1616, two 10 kΩ potentiometers, eleven independently controlled LEDs, and a UPDI-compatible one-wire programming interface. It does not publish circuit or pinout documentation, LED electrical characteristics, controller configuration, programmer settings, firmware, or electrical-safety validation.
Source