OzSec
OzSec 2025
The OzSec 2025 Wichita information-security conference represented by the organizer's CRASHANDBURN badge-design archive. The current event archive identifies the venue and badge USB-data-cable context but contains conflicting date text, while the public repository remains explicitly work in progress and does not prove final production or distribution.
Hyatt Regency Wichita, Wichita, Kansas · United States · 2025
development workflow
The README calls for VS Code, Python, mpremote, and a boot-select flash procedure, using a Raspberry Pi Pico 2 on a breadboard for current firmware development rather than documenting a final deployed attendee workflow.
Compatibility: OzSec 2025 CRASHANDBURN development source snapshot
firmware prototype
The current main script selects HiLo, DTMF, Kode, and Rock-Paper-Scissors games, updates associated LEDs, registers buttons, and restores a random idle blink mode.
Compatibility: OzSec 2025 CRASHANDBURN firmware source snapshot
hardware planning
The work-in-progress BOM lists USB-C connector and protection parts, a charge-controller section, power switch, AA connectors, regulator parts, and charge/status LEDs without documenting the final board or battery assembly.
Compatibility: OzSec 2025 CRASHANDBURN Badge design archive only
hardware planning
The BOM documents alternative display modules, an RP2350 section, and an ESP32-S3-WROOM-1-N8R8 option, while the separate pinout is explicitly for an ESP32 version. These are development choices, not a confirmed final badge configuration.
Compatibility: OzSec 2025 CRASHANDBURN Badge design archive only
event-date archive inconsistency · primary organizer-hosted archive · needs dated archive recovery
The record avoids turning a stale or mixed archive page into an incorrect precise date claim and leaves the date open for a dated official programme, ticket, or post-event report.
final delivery and distribution gap · organizer-linked repository and historical event archive · event record and design archive not reconciled
The catalogue preserves the real design/archive trail without treating a planning repository as proof of a final issued conference badge.
firmware release and validation gap · primary source repository · prototype source visible; production release unrecovered
The game and flashing material remains valuable development evidence, but not a claim about production behavior or a supported owner-update path.
hardware configuration and BOM gap · primary work-in-progress repository · final configuration unconfirmed
The record can show the documented development directions without collapsing alternatives into an invented production specification.
missing rights-cleared image · local project policy · needs licensed original replacement
The record remains source-backed and image-free rather than copying event media, repository previews, social-media images, screenshots, placeholders, or generated approximations.
repository licensing gap · public repository root review · no explicit root license identified
The catalogue links the source trail for research while preserving the separate requirement for explicit reuse terms, especially for any future local image asset.