Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
SHA2017 used the Badge.Team Hatchery path for discoverable badge applications, and the current Hatchery index still exposes SHA2017-compatible project records.
SourceThe MCH2022 Hatchery catalogue made app discovery and installation part of the camp badge workflow rather than a post-hoc source dump.
SourceThe EMF 2022 Hatchery API still lists TiDAL categories across event, game, graphics, hardware, utility, data, silly, unusable, and adult apps, preserving the badge as an app ecosystem rather than a one-off PCB.
SourceThe live app directory makes Tildagon a post-event software platform, with badge, background, game, media, music, pattern, hexpansion utility, schedule, WiFi, and sensor apps published by community authors.
SourceApps were submitted by adding a folder with main.py metadata headers to the Mk4-Apps GitHub repository, validating with tilda_tools, and opening a pull request; official rules banned malicious apps and code/image hot-loading without good reason.
SourceNew apps are published by adding a TOML pointer under the flow3r-apps index and opening a merge request; after merge the app appears in the public directory.
SourceThe app index treats a commit that increments metadata.version in flow3r.toml as a new release, making post-camp app maintenance part of the badge lifecycle.
SourceThe repository setup flow flashes a CircuitPython UF2, then copies the RP2350 filesystem to CIRCUITPYTHON for the badge runtime.
SourceThe official archive and sponsorship kit prove the electronic badge's event and sponsor context, but do not expose component-level hardware, firmware, artwork, or production files.
SourceJay Turla / @shipcod3's public post preserves the ROOTCON 12 Electronic Badge title, but this pass did not recover a public schematic, firmware archive, BOM, or rights-cleared image.
SourceThe OPCDE Kenya agenda preserved a dedicated session on making the AfricaHackOn 2018 Electronic Conference Badge, anchoring the badge's existence while leaving the technical archive open.
SourceLater writeups treated the 2019 badge as an ESP32-WROOM-32U board suitable for C# NanoFramework and ESP32 game/video experiments.
SourceThe official about page describes the merch bundle as a shirt, electronic badge, and sticker bundle, supporting an electronic-badge classification while leaving component details unknown.
SourceTwinkleTwinkie's DEF CON 27 Hardware Hacking Village bio explicitly names BSides Vancouver 2019 Badge among notable produced works.
SourceSOLDER LVL2, SOLDER LVL3, SOLDER LVL4, and Puzzle Badge entries document a tiered soldering and puzzle MiniBadge trail designed by Rushan.
SourceThe assembly documentation directs builders to consult a BSides Perth team member at assembly stations before soldering. It supports an on-site assembly context but does not establish how many badges were offered or who received one.
SourceThe project page describes an automated-assembly-oriented design and manual population using solder paste, a stencil, reflow, manual pick-and-place, and post-assembly rework, with exposed-pad and 0.5 mm fine-pitch assembly constraints.
SourceThe 2023 data includes through-hole and surface-mount difficulty notes, parts lists, LED/resistor builds, and acquisition guidance, while the official FAQ encourages newcomers to learn MiniBadge design.
SourceThe guide covers LED orientation, two-position headers, through-hole and SMD soldering, reverse-mount LEDs, RFID sticker placement, motor/fan parts, hot glue, cable-test behavior, and ATTiny programming for selected MiniBadges.
SourceThe official Build Your Badge page says the badge arrives with the microcontroller, reverse-mounted LEDs, and tiny parts pre-soldered, and that attendees solder four LEDs and the SAO connector on the front and the power switch and battery holder on the back before inserting an AAA battery, with help at the Soldering Village.
SourceHeatSync Labs brought acrylic backs, coin batteries, LEDs, resistors, and badge lanyards so attendees could solder a working LED badge at the booth.
SourceThe assembly guide says attendee conference bags contained the badge PCB, passives, fuses, headers, D1 Mini ESP8266 board, USB battery, and exchange token for HHV display parts.
SourceThe forum narrative says the team used solder paste, a hotplate, and manual display insertion to finish about 500 functional badges before the party.
SourceThe official badge section says each participant could design a custom configuration for their badge.
SourceLayerOne's Hardware Hacking Village page says both attendee and speaker badges were electronic and had to be assembled in the village.
SourceAttendees assembled their badges at soldering stations with peer help and minimal official guidance before staff flashed firmware.
SourceThe assembly guide steps through resistor, photocell, LED, switch, MOSFET, potentiometer, and battery-holder installation with orientation and test reminders.
SourceThe assembly manual documents the LiPo battery, PowerBoost 500C, cable routing, custom board mounting, acrylic shield, screws, standoffs, and lanyard hardware needed to complete the badge.
SourceHackaday describes attendees receiving a bag of components and assembling the badge in the Hardware Hacking Village soldering environment.
SourceThe documentation frames the badge as a DIY kit distributed to participants, with easy-to-mount DIP components and step-by-step resistor, LED, switch, and battery-holder assembly.
SourceThe infodesk page says arriving attendees received a goodie bag with a T-shirt and other items, while the ticket page documents day-ticket handling through the infodesk.
SourceThe infodesk and ticket pages document arrival goodie-bag pickup, T-shirt eligibility timing, day passes, and merch context around the non-electronic camp artifact bundle.
SourceThe infodesk page says arriving attendees received a goodie bag with a T-shirt and other items, making the non-electronic artifact bundle part of the camp identity record.
SourceA unique 3D-printed QR code on each case led attendees to a configurator for frame selection, name text, size, and position before firmware generation.
SourceThe designer records that an attendee cracked the game by extracting tag IDs from firmware and emulating them with a Flipper Zero, which was encouraged.
SourceThe official festival page says every accepted attendee gets a hardware badge at registration, with most components already on the board and a little soldering needed to bring it alive.
SourceThe attendee guide told delegates they could choose their own interaction protocols using a badge sticker, making the credential part of the event's interpersonal-boundary signalling.
SourceThe Humanitix page says TinkerInk brought a badge press so attendees could make custom pins signalling whether they wanted to be approached or left alone.
SourceThe official NFC Battle description asks attendees to tap a phone against another attendee's badge to complete an exchange, unlock collectible cards, and rank by cards collected. The organizer's August 22 closing update refers to NFC Battle in the past tense, confirming the activity ran. Neither source identifies the card payload, tag-memory configuration, app, backend, account linkage, privacy handling, or security model.
SourceThe CrikeyCon Connect section told attendees to look for the CrikeyCon Connect badge when seeking informal information-security career conversations.
SourceThe conduct/support section says Friendly Bear volunteers could be identified by the Friendly Bear text on their name badge.
SourceThe README links name-changing tools and explains how badge owners could make the badge connectable via menu item or button-held boot modes.
SourceHackerware documents sticking a mini speaker on the backside and soldering its leads at LS1 to play the piano.
SourceThe badge added a piezo buzzer for simple tones, including circus-themed and button-feedback jingles.
SourceThe public firmware archive includes ToneChaser examples for musical modes while the project writeup documents audio games and badge sound output.
SourceThe public archive includes a SoundBoard example mapping sounds to three capacitive touch pads through the XT_DAC_AUDIO library.
SourceThe README lists a MAX4466 microphone module, and the firmware samples A0 to choose mouth frames based on detected voice volume.
SourceThe event report documents I2S audio hardware, a 2-watt speaker amplifier, and a microphone pre-amplifier for the voice/audio experiment path.
Source