Hacker Con Badges

BSides Exeter

BSides Exeter 2025

The completed April 26, 2025 Security BSides conference at The Forum, University of Exeter. The organizer's ticketing page and Security BSides listing establish the passed date and venue; Punk Security's own event listing identifies it as badge sponsor, and its post-event source archive says the Pirate Ship Badge was given out at the event with a venue treasure-chest interaction. The sources do not establish a production count, recipient list, individual handoff, final unit configuration, chest count or deployment, safety validation, player outcome, or reusable image rights.

The Forum, University of Exeter, Exeter, England, United Kingdom · United Kingdom · 2025

BSides Exeter 2025 Pirate Ship Badge

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.

Lifecycle

Add-ons & Upgrades

BSides Exeter 2025 Pirate Ship Badge maker-documented event interaction

event badge game

Venue treasure-chest interaction

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.

Compatibility: BSides Exeter 2025 Pirate Ship Badge event context only; no current interaction, hardware, or support claim

BSides Exeter 2025 Pirate Ship Badge official sponsor listing and public source archive

event sponsor and maker relationship

Punk Security badge-sponsor event association

Punk 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.

Compatibility: BSides Exeter 2025 Pirate Ship Badge only; not a general Security BSides credential or admission entitlement

BSides Exeter 2025 Pirate Ship Badge maker-documented source archive

physical badge design

Pirate-ship PCB form and printed-art context

The 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.

Compatibility: BSides Exeter 2025 Pirate Ship Badge source-design context; no generic hardware or art-reuse claim

BSides Exeter 2025 Pirate Ship Badge maker-published after event

source-material archive

Public badge and companion source archive

Punk 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.

Compatibility: Punk Security source archive only; licence, final-release, companion-deployment, and all-unit parity remain unresolved

Operational history

Issues & Camp Impact

BSides Exeter 2025 Pirate Ship Badge note

badge-sponsor relationship, allocation, and handoff boundary · official event sources, Punk sponsor listing, and maker archive · completed event and sponsor badge documented; recipient scope unrecovered

The organizer sources establish the completed April 26 conference, Punk Security identifies itself as badge sponsor, and its archive says the Pirate Ship Badge was given out at BSides Exeter. The reviewed sources do not give a production count, ticket-tier eligibility, role allocation, recipient list, pickup/handoff record, replacement policy, or proof that all attendees received the badge.

The catalogue records a completed event-associated electronic badge without turning sponsorship or a broad maker distribution statement into a universal allocation claim.

BSides Exeter 2025 Pirate Ship Badge note

final hardware, companion, power, and electrical-safety gap · public repository review · design outline and source files public; production/safety result unrecovered

The repository names an ATtiny402, button, CR2032 clip, and 5050 NeoPixel for the badge and preserves separately named companion source/model material, but reviewed sources do not establish final component substitutions, battery brand/capacity, power budget, electrical limits, production revision, chest count, companion configuration, field placement, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

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.

BSides Exeter 2025 Pirate Ship Badge note

firmware release and operating-procedure boundary · public repository review · firmware sketches published; final deployment/support record unrecovered

The source tree includes separate badge and companion firmware sketches and external development references, but reviewed sources do not establish tagged final releases, signed binaries, source-to-unit mapping, build lockfiles, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating, connection, docking, or reconfiguration procedure. No code, flashing, configuration, connection, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification or deployment workflow.

BSides Exeter 2025 Pirate Ship Badge note

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

No BSides Exeter 2025 Pirate Ship Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

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.

BSides Exeter 2025 Pirate Ship Badge note

source-license, visual-material, and branding scope boundary · GitHub API metadata and repository-tree review · no detected repository license; image rights unresolved

GitHub metadata reports a null detected license for the repository, and no root LICENSE or COPYING file was recovered in the public tree. The public repo contains board images, artwork, and companion assets, but neither it nor event/sponsor pages pair a selected factual badge photo or official render with an image-specific reuse basis, named attribution, source URL, and processing provenance.

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.

BSides Exeter 2025 Pirate Ship Badge note

treasure-chest interaction, participant, and outcome boundary · maker repository description · venue interaction documented; configuration and player outcome unrecovered

The maker archive says attendees used venue treasure chests to unlock additional LED modes and preserves related source/model material. It does not publish a chest count, placement/deployment record, final companion configuration, connection details, challenge values, player count, participation data, score or completion data, participant identities, prize policy, official result, or ongoing service status. No interaction procedure is reproduced here.

The catalogue records the documented badge game without claiming universal participation, a completed CTF, any individual outcome, or a safe/reproducible operating procedure.

Resources

Security BSides BSides Exeter 2025 listing Security BSides event listing · The Security BSides Global listing records the passed April 26, 2025 Exeter event. It corroborates event timing, not the sponsor badge's technical design, recipient allocation, or image rights. Punk Security BSides Exeter badge-sponsor listing badge sponsor event listing · Punk Security's public event listing identifies BSides Exeter on April 26, 2025 and says it was badge sponsor. It supports the sponsor/event relationship, not a universal attendee entitlement, final production count, or delivery outcome. Pirate Ship Badge EAGLE source archive native PCB source · Public EAGLE source directory for the Pirate Ship Badge. It makes design material available without proving final manufacture, component substitutions, safe modification, chest deployment, or complete physical-unit parity. BSides Exeter 2025 organizer ticket page official organizer ticket page · BSides Exeter's organizer ticket page identifies the completed Saturday April 26, 2025 information-security conference at The Forum, University of Exeter. It establishes passed event date/venue context, not badge allocation, production, technical design, or image rights. BSides Exeter 2025 Pirate Ship Badge repository public badge source archive · Punk Security's public repository identifies the Pirate Ship Badge for BSides Exeter 2025, says it was given out at the event, and preserves board, schematic, EasyEDA, Gerber, badge/chest firmware, and companion-model material. It is a maker source archive, not a per-unit production, safety, chest-deployment, or delivery ledger. Pirate Ship Badge firmware sketch public firmware source · Public firmware sketch for the badge's source-described event interaction. It is linked as evidence without reproducing code, connection, flashing, configuration, docking, modification, or hardware-assembly instructions. Pirate Ship Badge GitHub repository metadata repository metadata · GitHub API metadata reports a public Punk Security repository created after the event and a null detected license field. It supports timing and licence-boundary review, not a grant of code, hardware, artwork, media, or brand reuse rights.

Sources

BSides Exeter / Ti.to: BSides Exeter 2025 Retrieved 2026-05-15 · Primary organizer ticket page for the passed April 26, 2025 information-security conference at The Forum, University of Exeter. It does not identify the technical badge or distribution details. GitHub API: bsides-exeter-2025-badge repository metadata Retrieved 2026-05-15 · Primary metadata source for the public repository's post-event creation timing and null detected license field. It is not itself a copyright grant or evidence of final event production. Punk Security: Punk Security BSides Exeter listing Retrieved 2026-05-15 · Primary sponsor source identifying Punk Security as BSides Exeter's 2025 badge sponsor. It supports the badge sponsor relationship, not recipient allocation or final handoff. Punk Security / GitHub: bsides-exeter-2025-badge Retrieved 2026-05-15 · Primary public badge archive for the Pirate Ship Badge, its at-event distribution statement, ATtiny402/button/CR2032/5050-NeoPixel parts statement, source files, and treasure-chest interaction account. It does not establish a final production run, recipient ledger, companion-deployment record, or selected image licence. Security BSides Global: BSidesExeter Retrieved 2026-05-15 · Security BSides network listing corroborating the passed April 26, 2025 event in Exeter, United Kingdom. It does not establish a badge allocation or technical implementation.