OzSec 2025 · United States · 2025

OzSec 2025 CRASHANDBURN Badge

Work-in-progress MicroPython game-badge archive

A source-conservative OzSec 2025 badge record: the organizer-linked repository calls itself the code and supporting-document archive for the CRASHANDBURN badge, while retaining work-in-progress hardware alternatives and MicroPython game source.

OzSec Wichita Kansas United States MicroPython Badge Games Hardware Variants Documentation Archive North America

EventOzSec 2025

SeriesOzSec

LocationHyatt Regency Wichita, Wichita, Kansas

CountryUnited States

People

Authors & Credits

CRASHANDBURN badge archive publisher

OzSecICT

GitHub organization linked by the official OzSec site and publishing the CRASHANDBURN source, firmware, hardware, and support-document archive.

Source

event archive and badge-context publisher

OzSec

Organizer-hosted source for the OzSec 2025 event context, badge USB-data-cable instruction, and Badge President/Honorary Chair listing.

Source

Why It Mattered

It records a distinct Wichita security-conference badge line with real development material while keeping planned design choices separate from evidence of a final manufactured or issued artifact.

Hardware

The public work-in-progress BOM lists USB-C, charging and power components, display alternatives, an RP2350 section, and an ESP32-S3-WROOM-1-N8R8 option. A separate pinout explicitly says it is for an ESP32 version. These sources document competing development directions, not a final controller, display, board, battery, or production configuration.

Software & Apps

The repository README describes MicroPython development for an RP2040 or RP2350 and multiple minigames, while the current main source implements a selectable HiLo, DTMF, Kode, and Rock-Paper-Scissors game set with LED and button behavior. The firmware directory contains ESP32-S3 and Raspberry Pi Pico 2 MicroPython target files, but no tagged final badge release is documented.

Lore

OzSec's archived 2025 event page identifies the Hyatt Regency Wichita venue and tells attendees to bring a laptop and USB data cable to connect to their badge. It also names a Badge President/Honorary Chair, but the page's conflicting date fragments and the repository's work-in-progress wording prevent a claim about final delivery or exact event-date linkage.

Lifecycle

Add-ons & Upgrades

development workflow source-backed work in progress

Host flashing and upload 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

Source

firmware prototype source-backed work in progress

MicroPython selectable game set

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

Source

hardware planning planned reference design

USB-C, charging, and power-path 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

Source

hardware planning planned alternatives

Work-in-progress controller and display alternatives

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

Source

Operational history

Issues & Camp Impact

event-date archive inconsistency note

The current OzSec 2025 archive contains October 23-24 wording in its headline and FAQ but October 10-11 wording in its schedule, indicating that the retained page mixes date fragments. This record therefore associates the badge archive with OzSec 2025 and the Hyatt Regency Wichita venue without asserting an exact event date.

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.

Confidence: primary organizer-hosted archive
Status: needs dated archive recovery
Timeframe: 2025 archive review
Source note: OzSec 2025 event archive.

final delivery and distribution gap note

The current repository describes the badge as work in progress and says it will be built, while the event archive identifies OzSec 2025. The reviewed public sources do not confirm a final manufacturing run, ticket or attendee allocation, pickup, shipment, firmware deployed at the event, or individual receipt.

The catalogue preserves the real design/archive trail without treating a planning repository as proof of a final issued conference badge.

Confidence: organizer-linked repository and historical event archive
Status: event record and design archive not reconciled
Timeframe: post-event archive review on 2026-08-04
Source note: OzSec 2025 event archive and OzSecICT badge-crashandburn README.

firmware release and validation gap note

The repository includes current MicroPython source and ESP32-S3/Pico 2 target files, but the README describes breadboard development and work in progress. No tagged final firmware, reproducible production build, test result, challenge outcome, or evidence that this source ran on conference units was recovered.

The game and flashing material remains valuable development evidence, but not a claim about production behavior or a supported owner-update path.

Confidence: primary source repository
Status: prototype source visible; production release unrecovered
Timeframe: current archive review
Source note: OzSecICT badge-crashandburn README, firmware directory, and main source.

hardware configuration and BOM gap note

The public BOM identifies alternative displays, an RP2350 section, an ESP32-S3 option, and an ESP32-specific pinout, while its own header calls the BOM work in progress. It does not establish the controller, display, PCB revision, battery, enclosure, component population, or electrical behavior of a final artifact.

The record can show the documented development directions without collapsing alternatives into an invented production specification.

Confidence: primary work-in-progress repository
Status: final configuration unconfirmed
Timeframe: current archive review
Source note: OzSecICT badge-crashandburn component BOM and ESP32 pinout.

missing rights-cleared image note

No OzSec 2025 CRASHANDBURN badge image is published because the organizer event archive and public repository do not pair a specific badge image with a reusable license or explicit permission basis, attribution, and processing notes.

The record remains source-backed and image-free rather than copying event media, repository previews, social-media images, screenshots, placeholders, or generated approximations.

Confidence: local project policy
Status: needs licensed original replacement
Timeframe: current archive review
Source note: badge.gallery image policy, OzSec event archive, and OzSecICT badge-crashandburn repository.

repository licensing gap note

The reviewed public repository root lists source, hardware, scripts, firmware, and documentation but no explicit LICENSE file or license declaration was identified. Public visibility is not treated as permission to redistribute hardware, firmware, documents, or embedded visual material.

The catalogue links the source trail for research while preserving the separate requirement for explicit reuse terms, especially for any future local image asset.

Confidence: public repository root review
Status: no explicit root license identified
Timeframe: current archive review
Source note: OzSecICT badge-crashandburn public repository root and badge.gallery image policy.

Resources

CRASHANDBURN ESP32 pinout work-in-progress pinout · Current pinout explicitly labeled for an ESP32 version, including game-completion LEDs and button inputs; it is not asserted as the final production board. CRASHANDBURN MicroPython main source firmware source · Current MicroPython entry point implementing selectable HiLo, DTMF, Kode, and Rock-Paper-Scissors games with LED and button behavior. CRASHANDBURN component BOM work-in-progress hardware BOM · Current planned component list for display alternatives, USB-C, charge and power path parts, RP2350 section, and an ESP32-S3 option; it does not prove a final built configuration. OzSec 2025 CRASHANDBURN repository source and design repository · Organizer-linked public repository whose README identifies it as code and supporting documents for the OzSec 2025 CRASHANDBURN badge, explicitly work in progress. OzSec 2025 event archive official event archive · Organizer-hosted OzSec 2025 archive for Wichita context, Hyatt Regency venue, badge USB-data-cable wording, and Badge President/Honorary Chair attribution. Its conflicting date fragments are tracked as an archive caveat.

Sources

OzSec: OzSec 2025 event archive Retrieved 2026-05-15 · Primary organizer-hosted source for the 2025 Wichita conference context, Hyatt Regency venue, instruction to bring a USB data cable for the badge, and Badge President/Honorary Chair wording. It has conflicting date fragments, so no exact date is asserted. OzSecICT / GitHub: OzSecICT/badge-crashandburn Retrieved 2026-05-15 · Primary organizer-linked badge archive whose README names the OzSec 2025 CRASHANDBURN badge and says it will be built in MicroPython for an RP2040 or RP2350 with multiple minigames, while retaining work-in-progress status. OzSecICT / GitHub: CRASHANDBURN component BOM Retrieved 2026-05-15 · Primary planned-hardware source for the selectable display, USB-C, charging, power, RP2350, and ESP32-S3 component paths, not a final production BOM. OzSecICT / GitHub: CRASHANDBURN ESP32 pinout Retrieved 2026-05-15 · Primary pinout source for the ESP32-version game LEDs and buttons; its explicit version qualifier prevents a claim that it matches a final shipped unit. OzSecICT / GitHub: CRASHANDBURN main MicroPython source Retrieved 2026-05-15 · Primary current source for the game selector, HiLo, DTMF, Kode, and Rock-Paper-Scissors game hooks, LED updates, button callbacks, and idle blink behavior.