BSides Ballarat

BSides Ballarat 2026

The February 28-March 1, 2026 regional Victorian BSides edition whose public event page documents the Underground interactive ESP32 conference badge, SAO support, and limited BSides SAO add-on.

Emerging Technologies Hub, Central Ballarat, Victoria · Australia · 2026

BSides Ballarat 2026 Underground Badge

BSides Ballarat 2026's public event page documents an Underground interactive conference badge designed and produced by Firnsy at Ballarat Hackerspace, with ESP32 processing, a screen, controls, badge-to-badge communication, SAO support, and a limited BSides SAO add-on; a public maker writeup also documents a third-party WS2812B Simple Add-On for the badge. In a March 2026 post-event update, an organizer reported that the conference badge contained 20 puzzles and that its full source code had been released.

Lifecycle

Add-ons & Upgrades

post-event badge challenge

20 badge puzzles and stated source release

A March 24 post-event update by Dr Paul Black says the conference badge had 20 puzzles to solve and that full source code was released. The post directs readers through a short link whose final archive target was not independently recovered in this pass.

Compatibility: BSides Ballarat 2026 Underground Badge

third-party SAO add-on

WS2812B pass-through SAO

A maker writeup documents a simple BSides Ballarat 2026 SAO board with a six-pin pass-through connector and a WS2812B addressable RGB LED driven from pin 5.

Compatibility: BSides Ballarat 2026 Underground Badge

Operational history

Issues & Camp Impact

source-code archive gap · organizer-reported release but archive unrecovered · needs public canonical source-archive link

The official event page documents the Underground badge's ESP32, screen, controls, badge-to-badge communication, SAO support, and CTF framing, and a maker writeup documents a WS2812B SAO board. A March 24 organizer post says the 20-puzzle conference badge received a full source-code release, but it routes through an unresolved LinkedIn short link; this pass therefore did not independently recover or inspect firmware, schematic, PCB, BOM, radio protocol, or production files for the main badge.

The record captures the post-event challenge and stated-release evidence while avoiding unsupported chip pinout, firmware, radio, protocol, software-license, or shipped-behavior claims until the canonical archive is retrieved.

Resources

Sources