BSides Perth

BSides Perth 2025

The October 18-19, 2025 BSides Perth edition whose public event ticketing and commit-pinned badge archive document an attendee-assembled ESP32 DevKit / 1.8-inch TFT challenge badge without establishing attendee-wide allocation or a deployed final revision.

UWA Business School, Crawley, Perth · Australia · 2025

BSides Perth 2025 ESP32 TFT Badge

The public BSides Perth 2025 badge archive and its assembly documentation identify a physical, attendee-assembled custom-PCB artifact built around an ESP32 DOIT DevKit v1, 1.8-inch LCD TFT, four tactile buttons, headers, and Micro-USB power. The archive also documents a virtual companion and challenge context, but it was published in September-October 2025 and does not prove that every event attendee received the same physical configuration.

Lifecycle

Add-ons & Upgrades

assembly context

On-site physical badge assembly

The assembly documentation directs builders to consult a BSides Perth team member at assembly stations before soldering. It supports an on-site assembly context but does not establish how many badges were offered or who received one.

Compatibility: BSides Perth 2025 ESP32 TFT Badge

challenge companion

Virtual companion and challenge context

The project README documents a virtual companion and online-challenge context. The catalogue records that high-level relationship without reproducing service details, credentials, operational endpoints, or challenge solutions.

Compatibility: BSides Perth 2025 ESP32 TFT Badge

hardware and firmware archive

Commit-pinned PCB and firmware archive

The reviewed snapshot preserves KiCad PCB/schematic material and Arduino-style physical-badge source. Its post-event publication does not prove an exact deployed revision or source-to-device mapping.

Compatibility: BSides Perth 2025 ESP32 TFT Badge

Operational history

Issues & Camp Impact

missing rights-cleared image · local project policy · needs licensed original replacement

No local BSides Perth 2025 badge image is published because the reviewed repository has no stated license or explicit image reuse permission, and the event and archive media do not supply a complete image-specific license, attribution, source URL, and processing trail.

The physical badge remains source-backed and image-free rather than copying repository renders, build images, event media, screenshots, or a generated approximation.

release, allocation, and deployment boundary · event and archive timestamps · documented caveat

The public archive was created before the event but the reviewed final snapshot was pushed after it. The sources do not map that snapshot to an exact event-day firmware build, deployed virtual service, production quantity, ticket entitlement, recipient list, or uniform physical configuration.

The record preserves documented hardware and archive context without converting a public project tree into universal attendee distribution or a verified final release.

repository license and image-reuse caveat · repository metadata and reviewed root tree · needs explicit reuse permission or license

The checked commit-pinned archive has no top-level license and GitHub reports no detected repository license. That leaves code, documentation, source imagery, and CAD/render reuse scope unresolved.

The catalogue may link to the public technical archive as evidence but does not publish its imagery, copy source files, or infer a reusable license from public availability.

Resources

Sources