Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
CampZone 2020 exposed a broad set of Badge.Team Python modules for input, display, audio, WiFi, HID, MIDI, MQTT, touchpads, and app configuration.
SourceThe SDK branch documents hardware, audio, camera, e-ink, SAM LED, ASR/VAD, TTS, optional Whisper, native display, package, and Debian installation modules for the CM5 platform.
SourceThe app library and USB copy workflow let attendees add their own MicroPython apps to the badge.
SourceSHA2017 sits in the early Badge.Team lineage where apps, contributed code, documentation, and post-event platform work became central.
SourceThe CampZone 2019 docs explain app packaging, metadata, icons, state persistence, Hatchery submission, and post-install behavior.
SourceMCH2022 used Hatchery for app loading and publishing, making post-distribution applications part of the badge experience.
Sourcecard10's wearable hardware was extended through Hatchery-hosted applications and firmware workflows.
SourceDisobey 2019 could download MicroPython applications from Hatchery once configured for WiFi.
SourceDisobey 2020 exposed app installation and publishing through Hatchery and the badge's installer application.
SourceSoftwareHub is documented as the app source for browsing and installing Konsool software.
SourceDeveloper docs and community writeups show TiDAL apps and experiments such as a custom Doom port while preserving MicroPython functionality.
Sourceflow3r's app directory and MicroPython docs support post-event applications, instruments, utilities, and experiments.
SourceHITCON said badge holders could use the device after the event as an offline physical wallet for Bitcoin or Ethereum, but this catalogue pass does not independently verify wallet security or firmware implementation.
SourceThe badge page documents a ROM store and an official GulaschPushNotifier ROM, making app-like software swapping part of the GPN17 experience.
SourceThe badge artifact was implemented as a custom GB Studio game that guides players through a virtual Sao Paulo, hotel, conference, and Brazil-themed environment.
Sourcebl00mbox lets multiple flow3r applications make sound together, with foreground/background audio behavior documented for app authors.
SourceThe badge home page invites attendees to explore firmware, write code, use onboard peripherals, and discover hidden features and challenges.
SourceThe repository includes apps and examples such as menu, REPL, Asteroids, Flappy Bird, Snake, Mario, T-Rex, sketch, and image-display code.
SourceThe upstream repository preserves user-app examples and firmware docs for writing MicroPython applications on the Communicator Badge platform.
SourceThe repository preserves user-app directories for games, screensavers, spectrum analysis, text adventure, air-quality, hardware-monitor, app-manager, and other MicroPython examples.
SourceThe README documents interpreter commands for IR, LEDs, note output, buttons, D-pad, framebuffer drawing, flash read/write, and source-buffer execution.
SourceHackRVA's later interview describes audio from USB through the badge speaker path.
SourceOfficial docs describe FREE-WILi GUI support, ESP32 WebSocket interface, USB serial console API, WASM scripting examples, host Python API, FAT filesystem, and WASM control of device features.
SourceThe official Badge Hub page says ConfiBadge 2026 software, MicroPython libraries, example apps, and community-contributed mods live in the hub.
SourceNodeWatch documents the Espruino embedded JavaScript interpreter and Bangle.js programming path as the watch's attendee-facing software platform.
SourceThe public source trail ties the badge to the Espruino/Puck.js JavaScript runtime lineage for attendee-programmable behavior.
SourceThe README says the badge is based on Pixl.js and uses Espruino IDE, CLI, and Pixl.js firmware-update workflows.
SourceThe event wiki links appfs as the way applications were stored and loaded on the badge, making installable apps part of the platform instead of just firmware demos.
SourceThe repository stores emulator, tutorial, examples, manuals, and firmware paths so the badge can be studied or programmed beyond the original event floor.
SourceThe public tools repository preserves Python assembler and disassembler scripts plus pseudo-op support for writing Voja4 programs outside direct binary entry.
SourceFri3d 2024 docs expose BadgeLink, MicroPython, Arduino, USB, WiFi, update, and reset workflows as first-class extension paths.
SourceKonsool documents browser-based firmware flashing plus OTA and USB update workflows.
SourceTiLDA MKe was designed around event schedule updates, talk alerts, online registration, torch mode, and camp utility behavior.
SourceThe BCD firmware article documents an ESP32-S3 firmware flashing path and a continuing software surface.
SourceThe ESP32 badge is documented as MicroPython-capable, making the recycled phone shell a programmable badge platform rather than a static prop.
SourceMicroPython apps and OS work continue after the event through the documented app publishing and simulator workflow.
SourceThe 2016 badge could act as a USB HID keyboard for generated passwords and random-number output.
SourceThe README documents 3.3 V TTL UART2 debug serial at 115200 baud, root credentials, terminal access, Python 3.11.6, and a simple Python hello-world path.
SourceThe 2023 status table marks audio output working on both badge hardware and simulator while audio/jack input remains not implemented.
SourceThe HackRVA recap documents two-channel audio behavior on the 2018 badge.
SourceThe original TiLDA wiki grouped wireless experiments, game mechanics, contributed code, hardware plans, and bug fixes as a shared camp hacking surface.
SourceThe badge records preserve Tetris, moving messages, accelerometer readouts, and a planned demoscene contest as first-class badge activity.
SourceThe README links Badge.Team firmware, a flasher, Rust examples, workshop firmware, and a 3D printed case branch.
SourceThe 2016 badge documented 9600 baud optical serial communication and IR terminal messaging between badges and from a universal remote.
SourceThe attendee report says the badge was simple enough for beginners to get going and was soldered during the conference with shared attendee setup help.
SourceAttendees could build a bonus track with standoffs, headers, jumper wires, and a detect-pad bridge, then insert it into the badge for racing.
SourceThe official activity guide documents a small PCB kit that lets attendees harness the badge crank output to charge devices through USB-A.
SourceThe builder log says the ToorCon badge incorporated an SMD Challenge with eight LEDs, including one smaller 0201 LED.
Source