Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
The 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 official 2026 documentation says the main badge runs a customized MicroPythonOS build with pre-installed apps, an App Store, custom MicroPython development, and local or camp-assisted firmware restoration paths.
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 project tree contains a firmware binary, a named sketch, and component-oriented examples. This establishes a public software trail without reproducing connectivity, configuration, update, or operating instructions or claiming a final deployed image for every delivered unit.
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.
SourceThe badge incorporated an SMD soldering challenge circuit credited to MakersBox, turning part of the board into a small assembly exercise.
SourceThe 2025 soldering-village writeup documents an add-on challenge with eight LEDs, polarity/defect debugging, VCC and pin behavior, SAO table context, scrambled code recovery, and final flag submission.
SourceThe badge became an electronic cocktail rendition after attendees soldered RGB flashing LEDs and coin-cell power onto the custom PCB.
SourceNolaCon's badge page says the badge had been a conference Learn to Solder centerpiece for the past three years and presents Patches as the 2025 continuation.
SourceTony Goacher's TGSTL app turns a SparkFun sound detector into a Tildagon sound-to-light path, tying the app store to a physical sensor hexpansion.
SourceThe hardware archive publishes native KiCad material with CERN Open Hardware Licence v1.2 text for hardware documentation, and GitHub marks the separate firmware archive GPL-3.0. These source and license findings do not automatically cover firmware deployment, repository graphics, event media, logos, trademarks, or local image publication.
SourceThe main Badge.Team page links Codeberg homes for Cyber Ægg hardware and firmware, with hardware docs identifying KiCad files and software summary pages pointing at Rust/Embassy firmware work.
SourceThe public repository includes native KiCad schematic, PCB, project, and production-data files plus MicroPython-oriented configuration, main application, e-ink driver, and bitmap assets. The archive does not expose an explicit root repository licence, release, or proof that it matches every produced or participant-configured unit.
SourceThe repository's visible history has an event-period README before the October 25 conference, while the main Arduino source appears in a November 21 post-event commit. The chronology preserves public evidence without equating the later checkout with a dated event binary or documented final artifact.
SourceThe public archive declares an MIT license for software and associated documentation under BSides Vancouver Society copyright. This is a source-license record, not an automatic reuse clearance for every photograph, board-art layer, logo, physical artifact, or event mark that may appear around the project.
SourceThe public repository preserves firmware, Gerbers, SPI tooling, troubleshooting notes, a flash-image archive, and Apache-2.0 license metadata after the CTF window.
SourceThe 2024 badge released KiCad, firmware, web configuration, production data, and a programming-jig model, with CERN-OHL-P-2.0 hardware and MIT firmware licensing.
SourceThe Hackover archive preserved firmware and schematic git clone commands after the event, including a note that KiCad-free users could find schematic PDFs under plots/schematics.
SourceThe report says the electronic badge was hackable, had already been hacked by at least three people during the CTF, and contained hidden Easter eggs and challenges integral to that competition. It does not describe the challenge design, interfaces, exploitation path, firmware, scoring, data handling, or any completed participant outcome.
SourceThe listing says Science Dog is now Coder Dog and calls its keyboard-lighting behavior AI magic. It does not name a model, inference, application, network, controller, firmware, sensor, or programmable feature. This retains the maker's wording without converting it into an artificial-intelligence or software claim.
Source