Issue dossier

The public bsidesbrisbane/badge-2026 archive now identifies the actual Clock Module hardware and provides Gerbers, BOM/CPL data, a case STL, and a detailed 555/74LS README. The repository was published six days after the event, has no tag or release, and does not establish a production total, source-to-unit mapping, individual configuration, or whether every event badge matched the photographed board.

A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.

Back to issues index

official hardware source and deployment boundary · post-event repository plus official event sources · source and production files documented; event-unit deployment scope remains open

The catalogue can document the verified discrete clock module while avoiding claims about universal deployment, event-day source availability, firmware, radio, or an exact recipient ledger.

Badge
BSides Brisbane 2026 Clock Module Badge
Category
official hardware source and deployment boundary
Severity
note
Confidence
post-event repository plus official event sources
Status
source and production files documented; event-unit deployment scope remains open
Timeframe
repository published 2026-07-10; reviewed 2026-08-04
Source note
bsidesbrisbane/badge-2026 commit 58a7d9b2e9502cb689f52f1f6826bfcaa90e214c, BSides Brisbane 2026 prospectus, Humanitix ticketing, and event-day updates.

Evidence

Related Resources

Source trail

Evidence Sources

BSides Brisbane / GitHub · retrieved 2026-05-15

bsidesbrisbane/badge-2026

Public source archive named `Repo for the BSides Brisbane 2026 Badge`, created on 2026-07-10 after the July 4 event. The pinned snapshot carries no tag or GitHub release, so it documents the project source rather than a release-bound deployed build.

Badge: BSides Brisbane 2026 Clock Module Badge