Hacker Con Badges

Not just specs

Issues & Camp Impact

Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.

Reset
2204 matching issue record(s)
La Villa Hacker 2025 Badge note

distribution-scope caveat · source-limited · open

The official event site and Electronic Cats repository prove event and badge-project context, but this pass did not recover a static official product page proving attendee-wide distribution, final sales count, or exact pickup logistics.

The catalogue treats the artifact as a source-backed La Villa Hacker 2025 badge without implying every village attendee received one.

Source note: La Villa Hacker site, dynamic store surface, and Badge-Villa-Hacker repository.

BSides Fort Wayne 2025 Badge note

distribution-source boundary · first-hand badge-team source · documented

The attendee-wide badge statement comes from a first-hand badge-team writeup rather than a recovered 2025 official archive page or production-count document.

The catalogue may state that the badge was given to attendees, but it does not claim final production quantity, ticket-tier mechanics, or exact replacement/spare counts.

Source note: Thad Turner BSides Fort Wayne 2025 writeup and BSidesFW2025Badge repository.

Fri3d 2016 Badge note

documentation completeness · primary writeup and archived repo · historical caveat

The surviving public record is strong enough to seed the badge, but the archived repository and writeup do not provide the same polished end-user documentation depth as later Fri3d badge years.

The dossier should stay conservative until photos, final attendee firmware notes, and any workshop pages are recovered.

Source note: Christophe VG Fri3d Badge writeup and Fri3dBadge2016 GitHub repository.

ICS Village DC33 FREE-WILi Badge note

documentation mutability caveat · primary documentation disclaimer · documented

FREE-WILi documentation says it may be updated without notice and includes a liability disclaimer, so this record cites both the live docs and the GitHub markdown source for traceability.

Hardware and software claims stay tied to the current public documentation snapshot and should be revisited if FREE-WILi revises the page or publishes design files.

Source note: FREE-WILi ICS Village Badge documentation disclaimer and FreeWili_WebDocs markdown source.

HackThePlanet SAO (DEF CON 34) note

documentation, circuit archive, and licensing gap · reviewed first-party listing only · no technical archive identified

The maker intentionally says there is no firmware or I2C handshake, and the reviewed source does not provide a schematic, BOM, PCB/Gerbers, assembly guide, component datasheets, circuit license, documentation license, test procedure, host example, or final revision record.

The entry is a narrow source-backed analog-artifact record, not a reproducible open-hardware or software dossier.

Source note: SAO HackThePlanet product page.

Badge Crown SAO (DEF CON 34) note

documentation, source-license, and support boundary · live maker listing and current public-source review · product description published; design/source/support terms unrecovered

The listing says no programming is required and points to a website printed on the add-on, but the reviewed product trail does not publish a schematic, PCB/Gerber/BOM source, component specifications, effect-circuit explanation, software source, formal version history, source license, warranty, support process, repair path, or vulnerability/safety policy.

The catalogue retains the maker's concrete sales description without claiming a reproducible design, supported repair path, open-source release, or lifetime product maintenance.

Source note: Brooke's Bytes Badge Crown SAO Uberflux listing and current public product trail.

Agency Wand (DEF CON 34) warning

documented DC34 REV1 power, accelerometer, and hardware-revision warning · public TrueControl DC34 README · source labels critical REV1 issues; field-correction and event outcome unrecovered

The public DC34 REV1 section labels a Q1-related power problem critical: enabling the gate can pull the 3.0 V rail low enough to brown out or glitch the MCU. It separately labels LED-program-related voltage fluctuations critical for accelerometer interrupt accuracy and says motion-wake animations should be disabled; it also identifies a floating accelerometer SDO design-improvement concern. The source contains its own workaround discussion, but this catalogue neither reproduces modification directions nor asserts that any revision, retail unit, or participant resolved the stated problems.

Readers can see the source-published REV1 limitation without receiving an unsafe repair prescription or an unsupported claim about a later board revision, battery behavior, accelerometer reliability, or field fix.

Source note: trueControl/hsc25-dc34-wand README, DC34 REV1 Hardware Issues section.

2026 eChallengeCoin (DEF CON 34) note

donation proof, privacy, tax, and charity-verification scope · public form fields and organizer wording · collection flow published; policies not recovered

The form asks for contact information and an uploaded donation receipt/confirmation that can show amount, charity name/address, and identifying information, but reviewed sources do not publish a privacy notice, controller/contact policy, retention/deletion period, storage/security safeguards, data-sharing terms, age/minor policy, tax-deductibility statement, nonprofit-status standard, charitable solicitation registration, verification method, receipt policy, or dispute process.

Readers can distinguish the organizer's philanthropic request from financial, tax, legal, privacy, or data-security advice and should not assume a particular validation, deduction, confidentiality, retention, or delivery outcome.

Source note: Choose Your Own Charity eChallengeCoin Submission form and AoSC eChallengeCoin page.

BSides Kraków 2026 Exclusive Donator Badge note

donator-variant relationship, allocation, and pickup boundary · official 2026 ticket and agenda page · separately named donation-pass artifact documented; relationship and fulfillment unverified

The official page distinguishes an Exclusive donator badge on the 1 zł Donation pass from the Exclusive badge on the free general/student passes, but does not say whether the variants differ in material, artwork, technology, function, issuance quantity, value, or recipient treatment. It also does not publish a recipient ledger, pickup procedure, shipment, receipt, or completed delivery.

The catalogue preserves the documented ticket-tier naming distinction without inventing a physical/technical variant, exclusive benefit, allocation result, or completed handoff.

Source note: Security BSides Kraków official 2026 ticket and agenda page.

CPEC DC34 MechBattle Badge note

draft code and physical-artifact boundary · primary CPEC repositories · planned project and companion design sources; physical artifacts unverified

CPEC's first repository explicitly says its code is not final, while the second is an active in-progress game repository. The third, scoped companion repository provides KiCad, BOM, and placement source assets, but no reviewed source supplies a provenance-backed photograph of a completed MechBattle or companion unit, a physical prototype account, manufacturing/order evidence, serial/revision log, assembly/test record, final hardware population, or completed event-unit confirmation.

The catalogue records a real named planned badge project and a source-published companion design trail, but does not turn source files into proof of physical, safe, completed, or distributed hardware artifacts.

Source note: CPEC DC34 MechBattle, DC34 Mech Badge Game, and DC-34-Mech-SAO repositories.

CPEC DC34 MechBattle Badge note

draft game-design and media-rights boundary · source-linked draft document and local image-policy review · creative context only; no reusable media basis

The source-linked game document is a draft creative reference and the badge, game, and companion repositories contain code and media assets, but none pairs a selected factual physical-badge or companion image with a reusable license or explicit permission basis, named attribution, source URL, and processing notes. The sources also do not establish final game content or third-party rights.

The record remains image-free and does not reproduce draft lore, repository previews, screenshots, logos, board renders, or any generated/approximate badge image.

Source note: CPEC DC34 MechBattle, DC34 Mech Badge Game, and DC-34-Mech-SAO repositories, linked game-design document, and badge.gallery image policy.

LayerOne 2015 Dual Electronic Badges note

dual-badge consolidation caveat · official archive and project logs · documented with caution

The official HHV archive and Hackaday.io project describe two 2015 badges, so this catalogue keeps them in one LayerOne 2015 record while clearly separating the PSoC4/ESP8266 LED badge from the VoCore/OpenWRT network badge.

Readers see the two-source-backed badge designs without treating one board's hardware, firmware, or production state as universal to the other.

Source note: LayerOne HHV 2015 Electronic Badge section and CharlieX Hackaday.io project.

CactusCon 8 Electronic Badge note

earlier-lineage caveat · source-limited · documented; monitor newly surfaced archives

The CactusCon 8 registration update says electronic badges were available "as always", which hints at earlier CactusCon electronic-badge years, but the current early-lineage pass only recovered artifact-level evidence for the 2014 PCB badge, 2017 Wi-Fi/Bluetooth scanner badge, and 2018 paid badge option.

CactusCon 2012-2013 and 2015-2016 stay explicit negative coverage until primary event pages, ticket text, badge-team archives, photos with reuse rights, repositories, or other artifact-level public sources surface.

Source note: CactusCon 2019 registration update, Robot Ambassador CactusCon PCB Badges writeup, Ratil.life Hacking and Skydiving writeup, Arizona LoCo Team September 2018 notes, and current badge.gallery source standards.

LayerOne 2026 Three-Button Keyboard Badge note

electrical repair caveat · official post-event report · documented narrowly

The official wrap-up says riverside and Holly helped fix an electrical issue with all badges by hand, but does not describe the fault, failure rate, repair method, timing, participant impact, or final reliability.

The record preserves a real build and repair constraint without inferring a root cause, systemic hardware defect, or attendee-facing failure beyond the official statement.

Source note: LayerOne 2026 Wrap-up! official post-event report.

ROOTCON 14 Survival Kit Badge note

electronic badge not proven · official guide but intentionally narrow · classified as identity artifact

The official guide proves a paid-attendee Survival Kit with conference badge, lanyard, and sticker set, but does not prove an electronic badge, PCB, firmware, components, production run, shipped count, or challenge behavior.

The dossier preserves the pandemic-era badge/lanyard artifact without upgrading it into unsupported electronics.

Source note: RC14 Quick Guide.

ROOTCON 17 Badge and Lanyard note

electronic badge not proven · source-backed but incomplete · classified as physical identity artifact

The recovered public sources prove a Human/Human+ badge-and-lanyard inclusion and lanyard artwork, but do not prove an electronic badge, firmware, PCB, component stack, challenge behavior, or badge variant taxonomy.

The dossier preserves ROOTCON 17 as an attendee identity artifact and avoids upgrading the record into unsupported electronics.

Source note: RC17 Conference Overview, RC17 Pocket Guide, and ROOTCON 17 Art directory.

ROOTCON 18 3D-Printable Badge note

electronic badge not proven · source-backed but incomplete · classified as 3D-printable artifact

The recovered public sources prove a ROOTCON 18 badge artifact directory with STL model files, but do not prove an electronic badge, PCB, firmware, components, production run, distribution count, or final physical variants.

The dossier is modeled as a 3D-printable badge artifact instead of upgrading the record into unsupported electronics.

Source note: ROOTCON 18 archive, media directory, Badge directory, and Badge/STL directory.

Zer0Con 2024 Entry Badge note

electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact

The recovered public sources prove limited Entry badge availability and closed-conference registration context, but do not prove an electronic badge, PCB, firmware, component stack, challenge behavior, physical badge design, or lanyard artwork.

The dossier preserves Zer0Con 2024 as an admission-badge availability record without inventing electronics or a physical credential design.

Source note: Zer0Con 2024 archive and POC Security official update trail.

Zer0Con 2025 Entry Badge note

electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact

The recovered public sources prove limited Entry badge availability and closed-conference context, but do not prove an electronic badge, PCB, firmware, component stack, challenge behavior, physical badge design, or lanyard artwork.

The dossier preserves Zer0Con 2025 as an admission-badge availability record without inventing electronics or a physical credential design.

Source note: Zer0Con 2025 archive and POC Security official update trail.

Zer0Con 2026 Entry Badge note

electronic badge not proven · source-backed but intentionally narrow · classified as entry/admission artifact

The recovered public sources prove limited registration availability and closed-conference context, but do not prove an electronic badge, PCB, firmware, component stack, challenge behavior, physical badge design, or lanyard artwork.

The dossier preserves Zer0Con 2026 as an admission-badge availability record without inventing electronics or a physical credential design.

Source note: Zer0Con 2026 official page and POC Security official update trail.

BSides Nashville 2026 Challenge Coin note

electronic-badge evidence boundary · official prospectus and event-page comparison · no 2026 electronic attendee artifact established

The official sponsorship prospectus lists an Electronic Badge Sponsor option, while the completed-event information explicitly documents the attendee challenge coin. Neither source identifies an issued 2026 electronic badge, a PCB, electronics, firmware, recipient allocation, or a technical archive.

The commercial sponsorship label is preserved as context but does not turn this non-electronic coin record into an unsupported electronic-badge claim.

Source note: BSides Nashville 2026 Sponsorship Prospectus and What's New for BSides Nashville 2026.

BSides Reykjavik 2026 Conference Badge note

electronic-badge evidence gap · source-backed limitation · documented; monitor future updates

The recovered official sources prove badges as sponsorship/logo-placement artifacts, but they do not describe a PCB, firmware, soldering project, hardware challenge, QR workflow, lanyard design, production quantity, or exact physical badge design.

The catalogue classifies this as a conservative conference identity artifact instead of an electronic badge or badgelife project.

Source note: BSides Reykjavik sponsorship packages and 2026 event pages.

cackalackycon 2026 Student Paper Badge note

electronic-badge technical and delivery-detail gap · official organizer, CFP, and ticketing sources · needs badge-specific primary documentation

The organizer-provided CFP proves a separate speaker-colored electronic-badge allocation and paper-badge guest path, while Eventzilla markets an electronic badge and calls the student item a paper ticket. None of those sources identifies the electronic badge's board, maker, physical form, ticketed-recipient inventory, quantity, firmware, or source archive.

The paper record remains bounded to students, while the separately seeded speaker electronic-badge record captures only the allocation actually established by public sources rather than treating ticket marketing as a universal technical claim.

Source note: cackalackycon 2026 official event page, Cackalackycon 101, organizer-provided CFP, and organizer-linked Eventzilla ticketing page.

Black Hat Europe 2026 Student Pass Badge note

eligibility, credential-function, and pickup boundary · official 2026 pass-comparison page · Student Pass pickup date and day-specific scope published; allocation and fulfillment unverified

The reviewed pages limit the explicit badge-pickup statement to the Student Pass and say that pass provides select event access on Thursday, December 10. They do not state a student recipient count, registration qualification outcome, whether other pass classes receive a comparable badge, a presentation/access-control role for this artifact, an issuer, pickup workflow, shipment, loss/replacement terms, receipt, or a completed delivery ledger.

The catalogue preserves the narrow official Student Pass evidence without treating it as a general-attendee badge, technical access credential, proof of individual eligibility, or proof that any badge has been collected.

Source note: Black Hat Europe 2026 official registration and pass-comparison pages.

Black Hat USA 2026 Black Hat Badge with DEF CON Symbol note

eligibility, cross-event role, and fulfillment boundary · official 2026 DEF CON-registration page · eligible-pass workflow and scheduled pickup published; qualification and handoff unverified

The source limits the optional DEF CON ticket path to paid Black Hat Briefings, Summit, and/or Training-pass registrants and excludes Business Pass Only registrations. It does not publish a purchaser list, confirmation process beyond the stated symbol, recipient count, a badge-production or pickup ledger, loss/replacement terms for this marked variant, a physical-access role for it, or evidence that any individual completed the scheduled pickup.

The catalogue records the narrow cross-event verification protocol without treating the marked Black Hat badge as a general attendee entitlement, a DEF CON admission badge, a technical access credential, or proof of delivery.

Source note: Black Hat USA 2026 official DEF CON-registration page and attendee resources.

Shitty Kitty V2 (DEF CON 34) note

engineering archive, pinout, and compliance gap · primary maker storefront source · needs public engineering documentation

The listing presents detailed components and calls its SAO ports 1.69bis-compliant, but does not publish a schematic, BOM, Gerbers, board layout, connector pinout, display part identification, power-tree detail, rail/current test data, SAO test report, or standards-compliance evidence.

The catalogue retains precise maker-published components without treating a storefront specification as a fully reproducible design or universal SAO compatibility guarantee.

Source note: Uberflux Shitty Kitty V2 product listing.

Overglade 2026 Zero-Power NFC E-Ink Badge note

event allocation and physical-production boundary · official event sources and maker archive · event completed; badge allocation unverified

Hack Club's official pages establish a completed Singapore game jam, while Kai Pereira's maker archive explicitly identifies Overglade hackathon badges. Neither reviewed official page publishes a ticket-to-badge entitlement, recipient list, allocation rule, quantity, pickup/delivery record, organizer-issued credential role, manufacturing record, or final physical-production ledger.

The catalogue records a real event-specific maker artifact without treating it as a universal attendee benefit, official access credential, organizer-issued device, or complete production account.

Source note: Overglade official page, Hack Club Horizons Arcana retrospective, and Kai Pereira's Overglade-Badges archive.

Pwnterrey 2026 Official ESP32-C5 Badge note

event allocation, production, and fulfillment gap · primary event and repository sources · post-event public evidence remains incomplete

The official site establishes Pwnterrey's May 29, 2026 event and Electronic Cats labels the public hardware repository official, but reviewed sources do not state a badge quantity, admission inclusion, registration tier, price, order record, recipient ledger, pickup, delivery, completed handoff, final production count, or post-event distribution outcome.

The catalogue preserves the official design and event association without presenting the badge as universally issued, sold, delivered, accepted, or used as an admission credential.

Source note: Pwnterrey official site and ElectronicCats/badge-pwnterrey-2026 repository.

BugCON 2023 Badge note

event and firmware inventory caveat · repository metadata and decoded source files · needs archive/event-page recovery

The repository proves the official BugCON 2023 badge and preserves firmware examples, but this pass did not recover a stable official BugCON 2023 event page, venue/date source, distribution count, release binary, final flashed image, or complete audit of every generated web asset and sketch dependency.

Event and software claims stay bounded to the repository, README, developer guide, visible source tree, and decoded representative files instead of inventing event logistics or treating the repository as a fully inventoried production archive.

Source note: ElectronicCats/Badge-BugCON2023 repository metadata, README, firmware/readme.md, firmware tree, and current BugCON site recheck.

Security Fest 2026 RP2040 Badge note

event association and allocation boundary · official event source plus self-described official badge repository · partially documented

The event and repository establish a Security Fest 2026 conference-badge association, but recovered sources do not state ticket inclusion, number of units, recipient eligibility, on-site handoff, or whether every attendee received the artifact.

The record can document a real event artifact without converting the public source trail into unsupported issuance or credential claims.

Source note: Security Fest official event page and Security Fest 2026 Badge README.

HackGDL 2026 Camera Badge note

event association and allocation boundary · official event page, organizer feed, product page, and repository · documented event association only

HackGDL's official sources name Electronic Cats in the 2026 event context, the organizer feed later promotes a 2026 badge bundle, and Electronic Cats publishes a Camera Badge HackGDL 2026 product and repository. None of those sources proves inclusion with admission, attendee receipt, access-control role, recipient count, ticket tier, price at the event, pickup, shipment, or final distribution.

The catalogue treats this as a real event-associated camera-badge artifact without representing it as a universal attendee credential or completed fulfillment record.

Source note: HackGDL 2026 home and sponsor deck, HackGDL public organizer feed, Electronic Cats product page, and ElectronicCats/badge_hackgdl_2026 repository.

Avnet FAE Institute 2026 PCB Badge note

event association, allocation, and credential boundary · creator-published commission statement plus vendor event context · event-specific design documented; recipient scope unrecovered

Alex Glow's public project source identifies a commission for Avnet FAE Institute 2026, while vendor updates establish the Phoenix event and technical-training context. Reviewed sources do not identify the commissioning terms, Avnet ownership of the repository, attendee eligibility, ticket inclusion, quantity, price, pickup, shipping, access-control role, participant receipt, or a completed allocation ledger.

The catalogue records an event-specific hardware badge design without turning a creator's commission statement into proof that every attendee received it, that it was an official access credential, or that any particular physical unit was issued.

Source note: Alex Glow's 26-06-FAEIBadge repository and README; Nexperia and Toradex public event updates.

CPEC DC34 MechBattle Badge note

event association, availability, and credential boundary · CPEC repository wording and official DEF CON event context · independent association; allocation and authorization unconfirmed

CPEC's repository description uses DEFCON 34 and the source names a CPEC DC34 offering, but no reviewed CPEC or DEF CON source establishes a sales/giveaway plan, quantity, price, recipient eligibility, pickup, shipping, completed handoff, venue approval, sponsorship, organizer role, Human-badge status, or admission function.

The badge is classified as an independent planned project associated with DEF CON 34, not an official conference badge, registration benefit, access credential, organizer-endorsed product, or confirmed distribution.

Source note: CPEC repositories and DEF CON 34 registration source.

DEF CON 34 Shitty Add-On (narengogi) note

event association, distribution, and credential boundary · repository's DEF CON 34 description and official DEF CON event context · independent pre-event source project; authorization and handoff unrecovered

The repository description says SAO for defcon 34 and the source board includes DC 34 text, while DEF CON's registration page provides event context. No reviewed DEF CON, BadgeLife, village, marketplace, maker announcement, or distribution source identifies an authorized relationship, price, stock, fabrication, sale, giveaway, pickup, shipping, recipient, attendee handoff, official role, or admission function.

The catalogue preserves the exact public event label without presenting this small source project as an official DEF CON item, a confirmed BadgeLife artifact, a completed delivery, or an access credential.

Source note: narengogi repository/source snapshot and DEF CON 34 official registration page.

OWASP SAO (DEF CON 34) note

event association, distribution, and credential boundary · repository's exact DEF CON label and official DEF CON event context · independent pre-event source project; official relationship and handoff unrecovered

The project README calls its sketch firmware for the OWASP DefCon 34 SAO, while DEF CON's official registration page establishes the event setting. No reviewed OWASP, DEF CON, BadgeLife, village, marketplace, maker announcement, manufacturing, sales, or delivery source confirms authorization, production, price, stock, recipient eligibility, pickup, shipping, attendee handoff, organizer role, Human-badge status, or admission function.

The exact public event label remains discoverable without turning it into evidence of OWASP or DEF CON endorsement, a physical run, availability, a completed delivery, or a credential.

Source note: DC34-OWASP-SAO repository and commit-pinned README; DEF CON 34 official registration page.

Agency SAO Badge V2 (DEF CON 34) note

event association, distribution, credential, and Agency-lineage boundary · repository's exact DEF CON 34 label and official DEF CON event context · independent pre-event source project; authorization, distribution, and shared lineage unrecovered

The repository description and source header explicitly use DEF CON 34 / Agency wording, while DEF CON's registration page provides calendar and venue context. No reviewed event, village, vendor, maker, or distribution source says this project is authorized, sold, given away, fabricated, handed to attendees, part of registration, or an admission credential. No reviewed source connects it to the separately documented ATtiny1616 Agency Wand (DEF CON 34) maker line, so the records remain distinct.

The catalogue preserves an exact event label without inventing official status, availability, ownership, attendee access, or a relationship to another Agency-themed record.

Source note: MadmanTimmy3241 repository and source snapshot; DEF CON 34 official registration page; separate Agency Wand source trail reviewed without a shared-project reference.

Carolina Code Conference 2026 Circuit Board Badge note

event completion and distribution boundary · official dated event-week logistics and elapsed event dates · event complete; per-recipient handoff unverified

The organizer's August 10 guide describes planned check-in badge handoff for attendees and later/single-day arrivals, and the conference dates have passed. Reviewed sources do not provide completed-pickup counts, an individual receipt log, ticket-to-badge mapping, stock, failed delivery, replacement terms, or a recipient ledger.

The catalogue treats the dated conference as completed and its badge platform as source-backed without representing the logistics plan as proof that a particular person received a particular unit.

Source note: Carolina Code Conference 2026 Week guide, event details, registration listing, and current event date.

BSides Cheltenham 2024 UFO Badge note

event edition, date, organizer, allocation, and handoff boundary · explicit 2024 maker repository and internally inconsistent maker timeline · 2024 artifact documented; exact event date, organizer confirmation, and recipient scope unrecovered

The public repository explicitly calls this the UFO badge for BSides Cheltenham 2024 and says a companion flyer was given out on the day. Punk Security's historical timeline separately identifies it as badge sponsor with UFO badges, but its rendered timestamp is early 2023 and conflicts with the repository's 2024 identity. No organizer-side 2024 recap, exact date, venue confirmation, production count, ticket-tier eligibility, role allocation, recipient list, pickup/handoff record, replacement policy, or proof that all attendees received the badge was recovered in this pass.

The catalogue records a source-backed 2024 event artifact while making the timestamp conflict and all unsupported organizer, allocation, and handoff claims explicit.

Source note: Punk Security historical event timeline and bsides-cheltenham-2024-badge repository.

GreyCTF Summit 2025 GreyBadge note

event scope caveat · official summit page plus badge repository · documented

The official page frames GreyCTF Summit 2025 as a cybersecurity summit with talks, workshops, booths, and GreyCTF context, while the repository frames the artifact as the GreyCTF 2025 badge. This record treats it as a source-backed Singapore hacker-culture/security badge without overclaiming universal public distribution.

The event and badge are included, but distribution and admission-credential claims remain conservative.

Source note: GreyCTF Summit 2025 page and NUSGreyhats/greybadge25 README/release trail.

CactusCon 2014 PCB Badge note

event-context caveat · corroborated public sources · documented

The badge writeup identifies CactusCon and the public slide trail anchors CactusCon activity on April 4, 2014, but this pass did not recover a complete official 2014 event page with full venue, ticketing, or schedule archive.

The event edition is named by year and kept source-scoped rather than assigning an unsupported CactusCon edition number.

Source note: Robot Ambassador writeup and Malware Analysis and Forensics CactusCon April 4 2014 slide page.

BugCON 2022 Badge note

event-context depth caveat · repository metadata and README · needs archive/event-page recovery

The repository metadata and README prove a BugCON 2022 CDMX electronic badge, but this pass did not recover a stable official BugCON 2022 event page, ticket page, schedule page, distribution count, or venue source.

Event claims stay bounded to BugCON 2022 CDMX and the public badge repository instead of inventing dates, venue, ticket tier, or distribution scope.

Source note: ElectronicCats/Badge-BugCON-2022 repository metadata, README, and current BugCON site recheck.

Ekoparty 2021 Badge Artwork Set note

event-context gap · source-backed but incomplete · needs archive recovery

The current live site exposes the 2021 badge artwork attachments, but this pass did not recover a complete official 2021 event page tying venue, modality, schedule, and distribution mechanics to the badge set.

The record remains useful as a badge-art lineage entry while leaving event logistics and artifact distribution open for archive recovery.

Source note: Current Ekoparty site check and official media attachment pages.