BSides Exeter
BSides Exeter's organizer ticket page establishes the completed 2025 information-security conference. This preserves event context only, not badge design, manufacture, distribution, image-rights, or source-archive ownership.
SourceBSides Exeter 2025 · United Kingdom · 2025
ATtiny402 pirate-ship badge with venue treasure-chest interaction
A completed BSides Exeter 2025 electronic PCB badge created by the event's badge sponsor, Punk Security. Organizer ticketing and Security BSides sources establish the April 26 conference at The Forum, University of Exeter; Punk Security's own event listing identifies it as badge sponsor. Its post-event public repository identifies the pirate-ship badge, says it was given out at BSides Exeter, preserves EAGLE, EasyEDA, Gerber, badge/chest firmware, and chest-model material, and describes a venue treasure-chest interaction for unlocking additional LED modes. The archive names an ATtiny402, button, CR2032 clip, and 5050 NeoPixel for the badge. The sources do not establish a production quantity, attendee allocation, individual handoff, final unit-by-unit configuration, chest count or deployment, safety validation, player outcome, or reusable image provenance.
People
BSides Exeter's organizer ticket page establishes the completed 2025 information-security conference. This preserves event context only, not badge design, manufacture, distribution, image-rights, or source-archive ownership.
SourcePunk Security's event listing identifies it as the 2025 BSides Exeter badge sponsor, and its public repository identifies the Pirate Ship Badge and preserves source material. This credit reflects the publicly named sponsor/maker/archive roles without assigning attendee allocation, companion deployment, safety, event-organizer authority, or image rights.
SourceIt fills an unseeded completed United Kingdom Security BSides artifact with organizer event confirmation, sponsor/maker evidence, public hardware-and-firmware material, and a source-backed venue game. The record preserves the interaction’s existence without converting it into a technical procedure or assuming every attendee received, used, or completed the same badge/chest path.
The public maker archive describes the Pirate Ship Badge with an ATtiny402 microcontroller, one surface-mount button, CR2032 battery clip, and one 5050 NeoPixel addressable LED, plus EAGLE/EasyEDA/Gerber material. It also preserves a separately named ATtiny402 breakout-board source and 3D-model material for the venue treasure-chest context. The sources do not establish final component substitutions, battery brand/capacity, power budget, electrical limits, production revision, chest count, field deployment, assembly quality, or safety outcome for every physical badge or companion unit.
Punk Security's source archive preserves separate Arduino sketches for the badge and venue treasure-chest context. The record does not reproduce codes, connection, flashing, configuration, modification, docking, hardware-assembly, or interaction directions and does not claim a tagged release, signed binary, source-to-unit mapping, deployment inventory, support policy, or all-unit firmware parity.
BSides Exeter's organizer ticket page describes an information-security community conference at The Forum, University of Exeter on April 26, 2025. Punk Security's public archive calls the artifact a pirate-ship badge with treasure chests and says attendees could use the venue interaction to unlock new LED modes. That source-described game context is retained without publishing challenge values, treating it as a universal attendee experience, or asserting a final player or prize outcome.
Source-backed hardware metadata
Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.
Punk Security's public repository identifies the Pirate Ship Badge as the BSides Exeter 2025 electronic badge. It does not establish attendee-wide allocation, final unit parity, or image rights.
Signal sourceThe repository's parts list names one 5050 NeoPixel addressable LED. The signal does not establish package substitutions, current budget, brightness, power behavior, or final-unit parity.
Signal sourceThe repository's parts list names a CR2032 surface-mount battery clip. It does not establish battery brand, capacity, protection, power budget, runtime, electrical safety, or final-unit parity.
Signal sourceThe public badge and treasure-chest source trees use Arduino sketches with MegaTinyCore for the ATtiny4x2 family. This records source-bounded software lineage, not a supported or safe configuration, assembly, or reconfiguration procedure.
Signal sourceRepair, preservation, and legal lab context
Parts, tools, and supplies that match this badge's documented hardware, protocols, or preservation needs. These are category-level recommendations, not compatibility guarantees.
Battery holders, connectors, and safe replacement supplies for preservation work.
This badge has documented battery or rechargeable power hardware. Matched technical signals: CR2032.
Vendor link · selected for technical relevance
Anti-static bags and storage supplies for preserving loose badge PCBs and sensitive components.
This is documented as an electronic or hardware artifact where anti-static storage can support preservation. Matched technical signals: Electronic badge.
Vendor link · selected for technical relevance
Lifecycle
The maker archive says attendees could use venue treasure chests to unlock additional LED modes and preserves companion source/model material. It establishes the source-described event interaction, not a chest count, deployment record, device configuration, challenge value, participant result, prize outcome, or current playable service.
SourcePunk Security's own event listing says it was BSides Exeter's 2025 badge sponsor, and its public repository identifies the Pirate Ship Badge for the event. This establishes a maker/sponsor event association without claiming the event organizer owned the archive or that every attendee received a unit.
SourceThe repository calls the artifact a pirate-ship badge and preserves EAGLE, EasyEDA, Gerber, and printed-art material. This records documented physical/art context without claiming every delivered unit used an identical final board, art revision, assembly quality, or manufacturing finish.
SourcePunk Security's public repository preserves board, schematic, EasyEDA, Gerber, badge/chest firmware, and companion-model material. The archive is linked for provenance without presenting it as a licensed derivative-work, manufacturing, connection, flashing, deployment, or safety guide.
SourceOperational history
The catalogue records a completed event-associated electronic badge without turning sponsorship or a broad maker distribution statement into a universal allocation claim.
The record preserves source-backed badge and companion context without treating public project material as a fabrication, repair, deployment, electrical-safety, or universal final-unit specification.
The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification or deployment workflow.
The United Kingdom record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
Source files and public project material are cited as evidence, but no local image, artwork, source file, or brand asset is copied or treated as licensed for reuse.
The catalogue records the documented badge game without claiming universal participation, a completed CTF, any individual outcome, or a safe/reproducible operating procedure.