Issues & Camp Impact · Hacker Con Badges

DEF CON 34 Shitty Add-On (narengogi) note

unnamed source, firmware, license, and publishing boundary · repository metadata, root-tree, and one-commit review · repository description and initial source files only; documentation/release/license unrecovered

The repository has no README, formal product title, firmware, build or programming instructions, tag/release, binary, source-to-board map, recovery path, support policy, warranty, root license, or detailed design explanation. GitHub reports no detected repository license. A public handle and an initial commit do not establish a real-world identity, sole authorship, design correctness, permission to reuse code/art/media, or availability of a completed product.

The entry uses a handle-qualified index title and links the raw source while avoiding invented technical behavior, a formal release, a legal reuse grant, or a stronger creator claim than the evidence supports.

Source note: narengogi repository metadata, root contents, and initial commit.

Clip-Boy: The Unofficial DEF CON 34 Electronic Badge note

unofficial DEF CON affiliation and credential boundary · primary official maker wording · independent DEF CON 34 badge

The official maker page explicitly calls Clip-Boy the unofficial DEF CON 34 electronic badge and offers a DEF CON pickup option. It does not identify the maker as a DEF CON organizer, say Clip-Boy is included with registration, provide access to DEF CON, replace a DEF CON Human badge, or establish official support/endorsement.

The catalogue classifies Clip-Boy as an independent BadgeLife artifact associated with DEF CON 34 rather than an official conference credential or admission substitute.

Source note: Clip-Boy official shop and product framing.

FrogStar Badge (DEF CON 33) note

unofficial DEF CON association and credential boundary · maker's express disclaimer and event schedule · independent electronic badge with scheduled DC33 creator activity

The maker page expressly calls FrogStar unofficial and says it will not get someone into the con. The creator-event schedule names a FrogStar Badge drop, but neither source says DEF CON issued it, included it with registration, made it a Human-badge replacement, granted access, or endorsed it as an official credential.

The catalogue classifies FrogStar as an independent BadgeLife artifact associated with DEF CON 33, not as an organizer-issued conference credential or admission item.

Source note: BigTaro FrogStar 2025 project page and DEF CON 33 Creator Events List.

35C3 Labitat Indie Badge note

unofficial badge classification · primary project page · documented

The project page says there was not an official DEF CON-style electronic badge tradition at Congress and frames this as an indie badge made for Labitat.

The catalogue treats the badge as Congress hallway badgelife, not as an official CCC admission badge.

Source note: Thomas Flummer 35C3 badge project page.

Unofficial 36C3 Badge note

unofficial badge classification · primary project-owner sources · documented

The badge announcement and project page identify the artifact as unofficial and distributed informally as kits at Congress.

The catalogue keeps it separate from official CCC event identity and models it as independent Congress badgelife.

Source note: Thomas Flummer 36C3 announcement and project page.

DEF CON 12 Forum Badge note

unofficial badge classification · primary forum evidence · documented

The DEF CON 12 Forum Badge is modeled as a community extra badge, not the official attendee credential.

The compendium can preserve the source-backed forum artifact without claiming it represents the main DEF CON 12 badge.

Source note: DEF CON forum thread where highwizard clarifies that the forum badge was a separate badge entirely.

NilbinSec DC33 Hack 'Em Crack 'Em Robots note

unofficial badge classification · first-hand forum plus product and schedule sources · documented

Hack 'Em Crack 'Em Robots is a NilbinSec badgelife release connected to DEF CON 33, not the official DEF CON 33 attendee badge.

The catalogue includes it as an unofficial community badge artifact while keeping the official Mar Williams DEF CON 33 badge as a separate record.

Source note: DEF CON #Badge Life forum announcement, RENXCHANGE product page, and DC33 schedule mirror.

Rabbit-Labs The Pirates' Plunder Badge note

unofficial badge classification · vendor product page plus public firmware · documented

The Pirates' Plunder badge is modeled as a Rabbit-Labs vendor/community badgelife release for DEF CON 33, not the official DEF CON 33 attendee badge.

The catalogue keeps it separate from the official Mar Williams DEF CON 33 badge while preserving its vendor-booth debut and public firmware evidence.

Source note: Rabbit-Labs product page and RocketGod firmware repository.

AND!XOR DC24 Bender Badge note

unofficial badge classification · source-backed · documented

The AND!XOR Bender Badge was not the official DEF CON 24 admission badge and did not grant conference entry; it is modeled as an unofficial DEF CON-adjacent badgelife artifact.

Country, event, and series pages can show the badge's historical importance without confusing it with the official 1o57 skull badge.

Source note: Hackaday hands-on article and Hackaday.io project context.

AND!XOR DC25 Badge note

unofficial badge classification · primary project source · documented

The AND!XOR DC25 badge is modeled as an unofficial DEF CON-adjacent badgelife artifact and not as the official DEF CON 25 admission badge.

The compendium preserves the community hardware lineage without confusing it with the official DEF CON 25 rubber/plastic identity badge.

Source note: AND!XOR Hackaday.io project page and DEF CON 25 event context.

AND!XOR DC26 Badge note

unofficial badge classification · primary project source · documented

The AND!XOR DC26 badge is modeled as an unofficial DEF CON-adjacent badgelife artifact and not as the official DEF CON 26 Tymkrs/Toymakers admission badge.

The compendium preserves the community hardware lineage without confusing it with the official DEF CON 26 text-adventure badge.

Source note: AND!XOR DC26 Hackaday.io project page, Hackaday hands-on review, and DEF CON 26 event context.

AND!XOR DC27 Badge note

unofficial badge classification · primary project source · documented

The AND!XOR DC27 badge is modeled as an unofficial DEF CON-adjacent badgelife artifact and not as the official Grand Idea Studio DEF CON 27 crystal badge.

The compendium can show both the official DEF CON 27 badge and the community AND!XOR hardware without merging their lineages.

Source note: AND!XOR DC27 project page, Hackaday hands-on review, and DEF CON 27 event context.

Hackaday Remoticon 2020 Unofficial Badge note

unofficial badge classification · primary-source discussion and README · documented

The Hackaday.io Remoticon discussion and repository README state that there was no official badge and identify the board as an unofficial community badge.

The compendium treats the artifact as a source-backed community badge template, not as the official event credential or a universal attendee handout.

Source note: 2020 Remoticon Hackaday.io discussion and flummer/remoticon2020-badge README.

DEF CON Singapore 2026 HFSDR Badge note

unofficial badge classification · official event page plus community preorder · documented

The official DEF CON Singapore page establishes the conference, while the HFSDR sources are community/repository sources. No reviewed official DEF CON page identifies HFSDR as the official event admission badge.

The record is included as a source-backed community badgelife artifact connected to DEF CON Singapore, not as an official DEF CON badge claim.

Source note: DEF CON Singapore event page, r/Defcon preorder post, and rhgndf/hfsdr repository.

Hackbat DEF CON 32 Badge note

unofficial distribution scope · source-backed but incomplete · classification caveat

Hackbat was designed specially for DEF CON 32 and source text references people who received it at DEF CON, but the public sources do not make it the official DEF CON 32 attendee badge or state a complete distribution quantity.

The catalogue keeps Hackbat as an unofficial DEF CON 32 badgelife record separate from the official RP2350 DEF CON 32 Badge.

Source note: Hackaday.io Hackbat project page and thehackbat/defcon32_badge README.

GrrCON 2024 BadgeBuddy note

unofficial distribution scope · first-hand source · documented

BadgeBuddy was built for roughly thirty friends attending GrrCON rather than issued as an official event-wide admission badge.

The compendium records it as unofficial badgelife and avoids implying GrrCON organizer publication, attendee-wide distribution, or admission-credential status.

Source note: CynicalSignals BadgeBuddy writeup and GrrCON official site.

Ninja Networks DC17 Party Badge note

unofficial party scope · primary forum narrative · documented

The badge is modeled as a Ninja Networks party invitation for DEF CON 17 weekend, not as the official DEF CON 17 admission badge.

The compendium keeps the unofficial party-badge lineage separate from the official DEF CON badge series while preserving its badgelife significance.

Source note: DEF CON forum thread and unsynchronized.org Ninja Networks party badge archive.

DC503 DEF CON 26 VIP Banglet note

unofficial party-badge classification · repository title and official talk page · documented

The public sources describe the item as the DC503 VIP Banglet and as the DC503 badge discussed at BSidesPDX, not as the official DEF CON 26 admission badge or a BSidesPDX attendee badge.

The catalogue keeps the DC503 wrist badge separate from the official DEF CON 26 Tymkrs badge, the AND!XOR DC26 badge, and BSidesPDX 2018's conference-badge archive.

Source note: pdxbadgers/2018-banglet README and BSidesPDX 2018 Making of the Banglet speaker page.

DEF CON 15 Badge note

unpopulated expansion caveat · primary designer source · documented

Accelerometer and 2.4 GHz RF support was fully designed but unpopulated on the badge circuit board.

The catalogue records the expansion footprints as a design surface without implying that every attendee badge shipped with populated motion or RF hardware.

Source note: Grand Idea Studio DEFCON 15 badge project page.

OzSec 2026 Conagotchi Badge note

unsigned OTA updates · stock updater source comment · documented limitation

The stock updater's own comment says updates are integrity-checked with SHA-256 but not signed, so a malicious server on an adversarial network could serve matching hashes for malicious files. It names a signed ed25519 manifest as the future fix. The site's publish workflow still sets a plain-HTTP host with a note to switch once a certificate is issued, although the dev manifest was served over HTTPS on October 27, 2026.

The record treats OTA as a user-started convenience with a known trust gap, not as a secured update channel. Whether attendee badges point at the prod channel or have OTA configured is not shown.

Source note: rufflabs/ota.conagotchi.com dev/ota.py and .github/workflows/sync-ota.yml, checked 2026-10-27.

IFLFU SAO (DEF CON 34) note

update lineage and prior-edition boundary · public roster update label and v2 repository name · current update evidenced; prior lineage not reconstructed

The roster calls IFLFU SAO an update to an existing item and the public code repository is named `iflfu-v2-pfc161`, but this pass did not recover a source-backed earlier event edition, older product listing, release date, technical delta, production record, attribution, recipient scope, or compatibility statement. The maker card calls an unlabeled item its original/first OffensiveSAO, but does not print IFLFU.

The record preserves the visible update/v2 trail without inventing a previous event, assigning an exact earlier version, merging unknown revisions, or treating the seller card as standalone proof of historical IFLFU distribution.

Source note: DEFCON 34 Badgelife Form response, BigFuckingBadge DEF CON 34 page, and iflfu-v2-pfc161 repository.

Day of the Dead Turkey v1 (DEF CON 34) note

v1/v2, form-factor, and Saintcon-lineage boundary · separate product titles and roster wording · separate v1 listing documented; technical distinction and historical link unreported

The maker has separately titled v1 and v2 product pages, but the reviewed product descriptions provide no engineering, physical, or revision explanation distinguishing them. The storefront calls v1 an oversize minibadge or standalone badge, while the roster calls the pair a standalone small badge or Saintcon minibadge. This pass did not recover an exact variant mapping, changelog, SAINTCON event distribution, final configuration, or evidence that all described terms refer to the same production run.

The catalogue keeps v1 distinct because its own listing is distinct while avoiding an invented hardware revision, size, Saintcon history, or universal compatibility claim.

Source note: Day of the Dead Turkey v1/v2 product listings and DEFCON 34 Badgelife Form response.

Day of the Dead Turkey v2 (DEF CON 34) note

v1/v2, form-factor, and Saintcon-lineage boundary · separate product titles and roster wording · separate v2 listing documented; technical distinction and historical link unreported

The maker has separately titled v1 and v2 product pages, but the reviewed product descriptions provide no engineering, physical, or revision explanation distinguishing them. The storefront calls v2 an oversize minibadge or standalone badge, while the roster calls the pair a standalone small badge or Saintcon minibadge. This pass did not recover an exact variant mapping, changelog, SAINTCON event distribution, final configuration, or evidence that all described terms refer to the same production run.

The catalogue keeps v2 distinct because its own listing is distinct while avoiding an invented hardware revision, size, Saintcon history, or universal compatibility claim.

Source note: Day of the Dead Turkey v1/v2 product listings and DEFCON 34 Badgelife Form response.

DEF CON 19 Badge note

variant inventory gap · official program source · needs deeper artifact inventory

The official program says the number of badge designs was intentionally not released and was much larger than the standard role set, but this pass does not reconstruct every physical variant.

The record preserves the existence of hidden variants without overclaiming a complete catalog of DEF CON 19 badge shapes.

Source note: DEF CON 19 program badge section.

BSides Goa 2024 SecOps Hackable Badge note

vendor-booth classification · source-backed but scoped · documented

The SecOps page proves a Hackable BCPen/CPen badge challenge tied to the SecOps booth at BSides Goa 2024, but does not prove the artifact was the official all-attendee BSides Goa admission badge.

The catalogue classifies this as a vendor-booth challenge badge artifact and avoids overstating event-wide distribution.

Source note: SecOps Hack the Badge page and BSides Goa 2024 event site.

HackerHotel 2027 Badge note

venue discrepancy · official event site versus Badge.Team homepage · event site preferred

The official Hacker Hotel site lists Hotel Zuiderduin in Egmond aan Zee for February 19-21, 2027, while Badge.Team's homepage still describes the event at hotel de Werelt on the Veluwe.

The edition uses the official event site's venue; the Badge.Team text is kept only as attributed context.

Source note: hackerhotel.nl and badge.team, checked 2026-10-17.

ICS Village DEF CON 34 Badge note

village badge classification · official availability and event pages · documented listing; post-date village operation unconfirmed

The source frames this as a hardware badge available at ICS Village or Vendor Village, while the DEF CON 34 event has separate official Human-badge context. The sources do not identify the ICS badge as an official DEF CON admission credential.

The record remains attached to the ICS Village event edition without confusing a village hardware project with a general conference-access badge.

Source note: FREE-WILi ICS Village DEF CON 34 Badge page and official ICS Village DEF CON 34 page.

SEC Youth Challenge 2023 Flux Decoder Badge note

village badge classification · source-backed classification · documented

The artifact belongs to the Social Engineering Community Youth Challenge at DEF CON 31 and is not the official DEF CON 31 admission badge.

The compendium keeps the record under its own Social Engineering Community series while cross-linking the DEF CON context.

Source note: FluxDecoder repository description and DEF CON forum Youth Challenge listing.

BTV Camera Badge (DEF CON 34 Fundraiser) note

village fundraiser and DEF CON credential boundary · primary organizer listing · documented independent village offering

The Eventbrite page describes a Blue Team Village fundraiser and in-village pickup. It does not say the artifact is DEF CON's official Human badge, is included with DEF CON registration, grants access, is an admission credential, or has a convention-wide production/allocation status.

The catalogue classifies it as a source-backed Blue Team Village fundraiser artifact rather than a substitute for conference registration or the official DEF CON badge.

Source note: BTV Camera Badge DEF CON 34 fundraiser listing.

Car Hacking Village DC32 Main Badge note

village-badge classification · official and repository source trail · documented

This record belongs to Car Hacking Village's DEF CON 32 hardware ecosystem and is not the official DEF CON 32 Human admission badge.

The compendium keeps the badge under its own village lineage while preserving DEF CON event context and avoiding an attendee-wide DEF CON main-badge claim.

Source note: Car Hacking Village official page, CHV repositories, and IOActive build-series context.

VULNCON 2025 Solder & Spark Badge note

village-scope boundary · official source but narrow · documented

The official source proves a Solder & Spark Badge Village kit and workshop activity, but does not prove the same electronic badge was issued to every attendee as a general admission credential.

The catalogue classifies this as a workshop/village badge artifact and avoids a universal conference-badge claim.

Source note: VULNCON 2025 schedule and Solder & Spark Badge Village page.

ROOTCON 15 Virtual Human Badge note

virtual artifact classification · source-backed but incomplete · classified as virtual identity artifact

The recovered public sources prove virtual-only Human Badge sponsorship allocations and official badge/lanyard artwork, but do not prove physical badge distribution, electronic hardware, firmware, a challenge platform, or attendee-wide badge variants.

The dossier keeps ROOTCON 15 in the lineage as a pandemic-era virtual badge/artwork artifact instead of implying a shipped electronic badge.

Source note: ROOTCON 15 archive, RC15 Sponsorship Overview, and ROOTCON 15 artwork directories.

ROOTCON 14 Survival Kit Badge note

virtual-edition scope · official guide · documented

ROOTCON 14 was a Recovery Mode virtual event because COVID-19 restrictions prevented mass gatherings, with conference access delivered through ROOTCON Discord.

The record should be read as a virtual-edition attendee-kit artifact, not an on-site conference credential used at a physical venue.

Source note: RC14 Quick Guide.

The Diana Initiative 2020 Off-the-Shelf Virtual Badge note

virtual-event artifact boundary · source-backed · documented

The recovered sources support an off-the-shelf Arduino Nano badge workshop artifact for remote participants, not a claim that every attendee received a centrally manufactured physical badge.

The catalogue models the badge as a virtual-conference workshop build and simulation artifact rather than upgrading it into an all-attendee production electronic badge.

Source note: The Diana Initiative 2020 Sched workshop page, TechGirlMN Maker Village archive, and TechGirlMN hardware guide.

Kernelcon 2020 Hack-Master Badge note

virtual-event behavior caveat · project-owner source · historical

The serial CTF mini game was removed when Kernelcon 2020 became virtual, so the record documents planned/offline capability without claiming that the mini game ran at the event.

The badge remains an electronic artifact, but its event-game behavior is kept narrower than the original hardware capability.

Source note: ZonkSec retrospective and kernelcon-2020-badge README.

Payment Village DEF CON 34 Volunteer Village Badge note

volunteer allocation and handoff boundary · official event and volunteer pages · scheduled dates elapsed; recipient outcome unconfirmed

The volunteer notice gives a June 1, 2026 application deadline and states a village-badge benefit, while the event page retains its August 6-9 programme. The sources do not publish an event-completion report, accepted-volunteer list, applicant count, confirmed staffing roster, badge quantity, cost, production, pickup point, shipment, delivery, actual access scope, completed issuance, replacement policy, or post-event outcome.

The record does not promise a badge to applicants, describe it as a universal DEF CON attendee benefit, or claim that any volunteer received or used one.

Source note: Payment Village DEF CON 34 event page and volunteer notice, rechecked 2026-09-15.

Adversary Village DEF CON 34 Volunteer Badge note

volunteer selection, allocation, and handoff boundary · official event and volunteer pages · scheduled dates elapsed; recipient outcome unconfirmed

The official notice says only a limited number of volunteers will be selected and says selected people will hear back by email or Discord; the event page retains an August 7-9 programme. The sources do not publish an event-completion report, accepted-volunteer list, applicant count, staffing roster, badge quantity, cost, production, pickup point, shipment, delivery, completed issuance, replacement policy, or post-event outcome.

The record does not promise a badge to applicants or claim that any volunteer received, used, or retained one.

Source note: Adversary Village DEF CON 34 event page and call for volunteers, rechecked 2026-09-15.

GrrCON 2026 Staff Badge note

volunteer selection, credential-function, and delivery boundary · official 2026 volunteer terms and home review · selected-volunteer badge commitment published; operational terms unrecovered

The reviewed official sources establish a badge commitment only for people selected as volunteers. They do not publish the number or identity of selected volunteers, role-specific badge variants, attendee or speaker issuance, ticket-to-badge relationship, presentation requirements, admission or amenity mechanism, access-control technology, issuer, pickup, shipment, loss/replacement policy, receipt, or completed delivery ledger.

The catalogue records the organizer's explicit staff-badge commitment without treating it as a general-attendee badge, a verified access-control credential, proof of individual selection, or proof that any person has received a badge.

Source note: GrrCON official home and 2026 volunteer terms.

SHA2017 Badge note

web installer dependency · primary docs · historical

The WebUSB install path depended on browser USB support and a hosted installer, which made setup easier for supported environments but added platform and link-lifecycle dependencies.

The install workflow was accessible for many users, but the compendium records it as an ecosystem dependency rather than firmware alone.

Source note: SHA2017 wiki and Hack42 WebUSB installer.

Aerospace Village DC34 SR-71 CTF Badge note

winnable CTF, raffle, allocation, and fulfilment boundary · public team self-submission · acquisition and raffle concepts disclosed; elapsed-date outcome unreleased

The team says SR-71 is only winnable through its CTF and that a full card collection enters a raffle, but does not publish eligibility, entry conditions, required card set, winner count, badge quantity, cost, allocation, prize terms, odds, schedule, handoff, shipping, receipt, refund, replacement, or final fulfilment evidence, and the recheck found no post-event CTF or raffle result record.

No contest, lottery, acquisition, ownership, prize, or delivery outcome is implied beyond the narrowly stated CTF and raffle concepts.

Source note: Public DEF CON 34 BadgeLife roster SR-71 self-submission.

Gothcon 2026 Blinky Badge note

wireless behavior and default-firmware scope · public repository and organizer store · documented with scope boundary

The repository documents ESP-NOW pattern contagion and a user opt-out, while the store says Wi-Fi and BLE are not used in default firmware. The sources do not publish a production firmware hash, final RF configuration, range/interference testing, regulatory documentation, or a Bluetooth interaction protocol.

The record describes public ESP-NOW application behavior without claiming final radio performance, BLE functionality, a production firmware identity, or certification.

Source note: Gothcon 2026 Badge README and official store listing.

Pwnterrey 2026 Official ESP32-C5 Badge note

wireless, NFC, GPS, privacy, and lawful-use boundary · public README and companion firmware documentation · source-described capabilities need authorized context

The public materials describe Wi-Fi, Bluetooth Low Energy, NFC, GPS, and Marauder-derived security-testing context, but do not provide a complete event-use policy, operator authorization record, data-handling terms, final RF configuration, range/interference testing, regulatory documentation, or a general-purpose safe-use guide.

The dossier contains no operational instructions and does not treat source-described wireless, NFC, or GPS capabilities as permission to test third-party systems, collect data, evade privacy expectations, or operate outside lawful owner-authorized work.

Source note: ElectronicCats/badge-pwnterrey-2026 README and pwnterrey-2026_Firmware ESP32-C5 guide.

Sneakreaper Limited-Edition Badge (DEF CON 34) note

wireless, NFC, and lawful-use boundary · source-named Wi-Fi, Bluetooth, and NFC surface · no operational or compliance guidance identified

The post names Wi-Fi, Bluetooth, and 13.56 MHz NFC but does not publish radio configuration, antenna characteristics, NFC interaction design, range, emissions, consent model, data handling, target authorization, access controls, user instructions, regulatory/compliance evidence, safety limits, or venue rules. Its high-level capability wording is not an authorization or instruction to interact with third-party systems or credentials.

Readers can identify the announced wireless/NFC surface without treating the record as a sanctioned operational guide, a privacy guarantee, a compliance claim, or permission to use the badge against systems or media they do not own or control.

Source note: Sneakreaper limited edition defcon badge!

BadgESC{21} Badge note

wireless, WLED, and privacy configuration boundary · public repository and maker-project context · software lineage documented; final deployment configuration unrecovered

The project sources establish an ESP32-C3 and WLED-related material, but do not provide a reviewed final deployment snapshot for every badge's radio settings, network/service configuration, access controls, telemetry, data retention, privacy practice, update policy, or post-event availability. No credentials or operational configuration details are reproduced here.

The entry records the source-backed software context without asserting a particular network behavior, service, privacy posture, security property, or current operational endpoint.

Source note: End Summer Camp badge-2025 firmware directory and Jacopo Franco's maker project.

AND!XOR DC25 Badge note

wireless-game caveat · primary game log · documented

The BOTNET log frames wireless activity as badge-only gameplay with custom packet structures and payloads interpreted only by AND!XOR badges, with activation and airplane-mode opt-out behavior.

The catalogue records the game mechanics without implying a real-world botnet or harmful network capability beyond the badge ecosystem described by the project owners.

Source note: AND!XOR BOTNET game log.

Clip-Boy: The Unofficial DEF CON 34 Electronic Badge note

wireless-security capability, legal, and authorized-use boundary · official seller disclaimer · high-level feature claims only

The seller frames Clip-Boy as lawful security-research/education hardware, says it ships passive/listen-only, and says users are responsible for applicable computer-misuse, wiretap/interception, and radio/spectrum rules. The source does not give jurisdiction-specific authorization, event/venue permission, operational procedure, testing scope, consent model, privacy/data-retention behavior, accuracy, RF performance, or a guarantee that optional research capabilities are lawful or appropriate in a particular setting.

The catalogue does not provide guidance for active testing, characterize any security feature as safe or legal everywhere, or turn a seller disclaimer into a compliance determination.

Source note: Clip-Boy official shop terms and AI/tooling disclosure.

ToorCon 20 Official Badge note

withheld puzzle files · source-backed · documented

The builder log explicitly says the author was sworn to secrecy and forced to burn Gerber files, so the public record intentionally withholds the art secrets and full board files.

Future archive work should seek official or creator permission before treating private Gerbers, puzzle art, or code meanings as publishable catalogue evidence.

Source note: Hackaday.io Official Toorcon Badge? log.

Ruxcon 2015 HHV Badge note

workshop errata · source-backed · documented

The build guide documents that the indicated I2C bus was not actually connected to an I2C peripheral and that the switch footprint could short contacts unless tabs were clipped.

The record preserves the badge as a real workshop artifact with teachable hardware mistakes rather than hiding production friction.

Source note: Building the Ruxcon 2015 Hardware Hacking Badge PDF.

Ruxcon 2016 HHV Badge note

workshop errata · source-backed · documented

The RuxBadge build sheet warns of design mistakes, reversed boot-jumper markings, and possible battery-holder contact shorts before battery insertion.

The catalogue records the badge as a real workshop artifact with documented assembly hazards rather than a frictionless production object.

Source note: RuxBadge instruction sheet.

OSHCamp 2023 Badge note

workshop kit dependency · official event page and designer writeup · historical

The OSHUG event page framed the badge session as a solder-paste and reflow workshop and told attendees to bring their own tools and accessories for programming and use.

The badge experience depended on workshop readiness instead of only passive distribution; that is useful context for anyone comparing camp-badge accessibility.

Source note: OSHCamp 2023 event page and OSHCamp23 Badge writeup.