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
2209 matching issue record(s)
BSides Canberra 2021 SAMD/ESP32 E-paper Badge note

source-depth caveat · source-backed but incomplete · needs source license and complete production archive

The recovered source trail documents the official badge page, schematic, frame STEP file, components, firmware-restoration flow, and production context, but this pass did not recover a complete BOM, board-file archive, readable firmware source release, image license, or explicit project license.

The catalogue records the verified SAMD21/ESP32/e-paper architecture while avoiding unsupported claims about full source release, exact add-on availability, final component values, or image reuse.

Source note: BSides Canberra 2021 badge page, BSidesCbr/2021Badge repository, Mos & Boo overview and reflashing guides, and attendee writeup.

LCA2019 Donkey Car note

source-depth caveat · source-backed but incomplete · needs public repository or hardware archive

The public trail documents the Donkey Car kit, Raspberry Pi camera control, TensorFlow training-data workflow, participant assembly, and self-driving attempts, but this pass did not recover a stable schematic, BOM, model archive, firmware repository, kit quantity, or explicit project license.

The record keeps hardware and software claims to official event context and first-hand evidence until deeper project archives are recovered.

Source note: LCA2019 programme/miniconf pages and Marc Merlin 2019 Donkey Car writeup.

LCA2020 DingoCar note

source-depth caveat · source-backed but incomplete · needs public repository or hardware archive

The public trail documents DingoCar sessions, Raspberry Pi control, TensorFlow-style training, and self-driving behavior, but this pass did not recover a stable schematic, BOM, model archive, firmware repository, kit quantity, or explicit project license.

The record keeps hardware and software claims to schedule-backed and first-hand evidence until deeper project archives are recovered.

Source note: LCA2020 schedule, Marc Merlin 2020 DingoCar writeup, and prior Open Hardware self-driving car lineage writeup.

AfricaHackOn 2018 Electronic Badge note

source-depth caveat · single official agenda source · needs badge-team archive

The public source trail proves an AfricaHackOn 2018 electronic conference badge and making-of session, but does not expose the badge's component list, firmware, repository, schematics, board files, distribution model, or challenge behavior.

The record is intentionally narrow and should be expanded only if a badge-team writeup, slide deck, code release, or surviving-board documentation is recovered.

Source note: OPCDE Kenya agenda.

FloridaMan 2026 Badge note

source-labelled generated product-media boundary · official storefront media filenames · not publishable under catalogue image policy

The current official storefront and product listing expose product-media filenames beginning Gemini_Generated_Image. Even if the files are visible on an official commerce page, their source labels make them generated imagery rather than cleared documentary photos or accepted upstream official raster artwork for this catalogue.

The catalogue preserves the product evidence and explains the image gap without treating generated marketing art as a picture of the actual badge or as an allowed public image asset.

Source note: FloridaMan 2026 storefront and FloridaMan 2026 Badge listing media URLs.

Overglade 2026 Zero-Power NFC E-Ink Badge note

source-license and media-provenance boundary · repository-root and image-policy review · public source archive; explicit licence and reusable media basis unrecovered

The reviewed public repository root did not expose an explicit licence file, and official/event/repository media did not pair a selected factual badge image with an image-specific reusable licence or explicit permission basis, attribution, source URL, and processing provenance. A public source archive is not treated as a blanket licence for code, design, branding, or imagery.

The record cites public design material as evidence but remains image-free and does not republish event photos, repository previews, screenshots, artwork, or approximate/generated imagery.

Source note: KaiPereira/Overglade-Badges repository root, official Hack Club pages, and badge.gallery image policy.

Greycademy 2026 Hackbadge note

source-license and media-provenance boundary · source and image-policy review · no public source-release or reusable media basis recovered

The organizer and maker pages document the event and artifact but do not provide a public source-code/hardware licence or a selected factual badge image with reusable licence or explicit permission basis, attribution, source URL, and processing provenance. LinkedIn, Telegram, and project-page media remain evidence only.

The entry is source-backed and image-free rather than copying social-media images, maker-project visuals, event media, screenshots, placeholders, or generated approximations.

Source note: NUS Greyhats official Telegram/LinkedIn sources, Hackin7 pages, maker record, and badge.gallery image policy.

Hackaday Supercon 2016 LED Matrix Badge note

source-license caveat · repository audit · documented for source only

The GitHub hacking template is MIT licensed, but that source license does not by itself clear article, manual, README, or project-page badge images for local publication.

Source-code claims can cite the repository, while the badge image remains empty until a separately cleared original photo or official render is selected.

Source note: GitHub license.txt and badge.gallery image policy.

MNSEC 2025 Electronic Badge Collection note

source-license, media-rights, and branding scope boundary · repository license and public-site review · BSD source/binary license recorded; selected-image rights unresolved

The repository root publishes a BSD 2-Clause license credited to DavgaBeelog, while Beelog's current public site reserves its own rights. The reviewed archive and event pages do not pair a selected factual physical badge photo or upstream render with a complete source URL, image-specific reuse basis, attribution, and processing provenance. The BSD source/binary statement is not assumed to licence all photographs, renders, artwork, brands, or physical artifacts.

The catalogue links the source archive and license but publishes no local badge image until an image-specific rights-cleared source is available.

Source note: MNSEC2025BADGE LICENSE, repository media tree, Beelog site, and badge.gallery image policy.

Open Sauce 2026 Badge note

source-license, visual-asset, and branding scope boundary · repository root-license review · MIT software/documentation license recorded; separate scopes unresolved

The root repository contains an MIT license naming Caleb Marting for software and associated documentation, but reviewed sources do not separately allocate copyright or image attribution for every assembly photo, board graphic, logo/art layer, physical board, Open Sauce name/mark, or third-party component/library asset. The attendee replacement repository separately says it has no license.

The entry may link the respective source archives and license statements while keeping physical-artifact, media, branding, downstream reuse, and local-image rights scoped rather than inferred.

Source note: calebmarting/os2026-badge LICENSE and asset tree; putnam/opensauce2026-badge README; badge.gallery image policy.

BSides Vancouver 2025 Electronic Badge note

source-license, visual-asset, and event-mark scope boundary · MIT license review · software/documentation license recorded; separate rights unresolved

The public archive's MIT license covers software and associated documentation under BSides Vancouver Society copyright, but reviewed sources do not separately allocate reusable rights for all badge photographs, physical-board art, logos, event names/marks, embedded media, third-party components, or individual source contributions.

The record may link the software and documentation license while keeping visual, branding, physical-artifact, and local-image reuse claims deliberately scoped.

Source note: BSides Vancouver public-source LICENSE and badge.gallery image policy.

BSides Cheltenham 2023 Delorean 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 archive does not 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.

Source note: GitHub repository metadata and file tree; Punk Security public event page; badge.gallery image policy.

BSides Cheltenham 2024 UFO 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 archive includes vector artwork and design assets but does not 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, case asset, or brand asset is copied or treated as licensed for reuse.

Source note: GitHub repository metadata and file tree; Punk Security public event page; badge.gallery image policy.

BSides Newcastle 2024 Plant 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 and schematic images, but neither it nor the maker event page pairs 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.

Source note: GitHub repository metadata and file tree; Punk Security public event page; badge.gallery image policy.

BSides Newcastle 2025 Space 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, manual assets, and signs, but neither it nor the 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.

Source note: GitHub repository metadata and file tree; BSides Newcastle and Punk Security public pages; badge.gallery image policy.

CyberNorth CyberFest 2025 Compass 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 and artwork, but neither it nor CyberNorth's 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.

Source note: GitHub repository metadata and file tree; CyberNorth and Punk Security public pages; badge.gallery image policy.

CSIDES 2025 Crab 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 and artwork, but neither it nor CSIDES/Punk Security 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.

Source note: GitHub repository metadata and file tree; CSIDES and Punk Security public pages; badge.gallery image policy.

BSides Bournemouth 2025 Skull 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, vector, and printed artwork, 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.

Source note: GitHub repository metadata and file tree; BSides Bournemouth and Punk Security public pages; badge.gallery image policy.

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.

Source note: GitHub repository metadata and file tree; BSides Exeter and Punk Security public pages; badge.gallery image policy.

AND!XOR DC26 Badge note

source-release caveat · primary logs and public-source recheck · needs archive recovery

The retrospective says source code would be posted, but this pass did not recover a stable public repository, firmware archive, schematic, BOM, or Gerber set for the DC26 badge.

The record cites project-owner logs and hands-on technical coverage while avoiding stronger open-source hardware/software claims until a repository or archive mirror is recovered.

Source note: AND!XOR DC26 retrospective, LULZCODE log, ARG log, and current public-source check.

LayerOne 2016 Conference Badge note

source-release gap · project logs but incomplete source recovery · needs artifact-level archive

The all-at-once log says Eagle files and software would be uploaded to GitHub, but this pass did not recover a complete public final repository, release package, board-production archive, or challenge/software bundle for the 2016 badge.

Hardware and software claims remain tied to the public HHV page and Hackaday.io logs instead of treating planned source publication as recovered source.

Source note: LayerOne 2016 All at once log and current source search.

Hacker Pager (DEF CON 34 Revision) note

source-to-2026-revision, production, and image-provenance boundary · maker announcement, project site, and repository release context · new-revision claim published; exact physical revision and cleared media unrecovered

The maker calls the DEF CON 34 device a new revision, while the reviewed electronics and case repositories show their own public source/release histories. No source maps those design files, a particular firmware label, part substitutions, colour/edition, case configuration, or manufacturing batch to each planned 2026 unit. Product, project, and repository images are not reused because no selected factual image is paired with complete source URL, reusable license or explicit permission basis, attribution, and processing notes.

The record remains image-free and source-conservative rather than treating open design files or promotional media as proof of exact 2026 unit parity or reusable catalogue artwork.

Source note: Exploitee.rs Hacker Pager announcement/project site and public electronics/case repositories.

Retia DEF CON 32 Badge note

source-year, event-edition, and provenance boundary · immutable Retia source release and official DEF CON archive · 2024 source label retained; exact DC32 naming and contemporaneous publication unrecovered

Retia's public repository name says DefconBadge2026, while its current description, immutable first commit, README, and hardware filenames label the project 2024. DEF CON's official archive makes 2024 DEF CON 32, so the catalogue attaches the artifact to that edition as an explicit calendar mapping. No reviewed Retia or DEF CON page calls this artifact by the exact DC32 name or provides a contemporaneous 2024 publication date.

The record preserves the source's 2024 identity and its catalogue placement without silently converting a later repository name into a 2026 badge, an official DEF CON classification, or a verified contemporaneous event artifact announcement.

Source note: RetiaLLC/DefconBadge2026 repository metadata, immutable July 8 2026 source-release commit/README/tree, and DEF CON 32 event archive.

Camp++ 2026 Identity Artifacts note

sparse ticket-page caveat · official page recheck · current source boundary

The current 2026 ticket page only exposes a tickets heading and navigation, so older random-ID, privacy/deletion, checksum-verification, and completion claims are not retained for this edition.

The 2026 dossier is limited to the current home, how-to, ticket-page, and CfP facts instead of assuming the detailed ticketing model or successful outcome from earlier Camp++ editions.

Source note: Camp++ 2026 ticket and how-to pages rechecked 2026-08-25.

DC503 Wagon Party Badge note

sprite-artwork license boundary · public repository archive · documented

The repository includes generated sprite/image assets and source comments naming image2cpp and ezgif, but this does not establish a reusable badge-photo license, upstream render permission, or attribution record for catalogue publication.

Sprites remain source evidence for firmware behavior only and are not promoted into `Public/images/`.

Source note: sprites.h, images directory, and badge.gallery image policy.

Ouroboros Badge (DEF CON 34) note

stock, replenishment, pickup, and fulfillment boundary · first-party storefront and maker announcement · sold out; future order and DEF CON pickup are stated as tentative

The current Tindie page is out of stock and says a new order is coming, with a hope of bringing units to DEF CON. The maker's Reddit comment/post describes possible buyer-arranged pickup and a shipping refund. The sources do not establish actual stock, production completion, unit count, order status, event arrival, handoff, shipping, refund, replacement, support, or completed distribution.

The catalogue preserves dated seller and maker intent without representing the item as available, delivered, or confirmed for DEF CON.

Source note: Ouroboros Badge #BadgeLife product page and first-person r/Defcon announcement.

CarolinaCon Online 2 Conference PCB Badge note

store-link boundary · official archived page · documented

The archived page links to a shop product for the swag bag, but the stable evidence retained in this pass is the archived CarolinaCon page text rather than a current mutable storefront listing.

The catalogue can cite the official archived event page for bundle contents without depending on a live store page that may change or disappear.

Source note: CarolinaCon Online 2 official home page.

2026 eChallengeCoin (DEF CON 34) note

story, organization, authorship, and endorsement boundary · maker story and manufacturing wording only · creative and contributor context recorded; relationships unsubstantiated

AoSC's story references the British Museum and its own Sara Cladlow/T.E.C. characters, while its manufacturing section says Bradán Lane STUDIO engraved brass faces and unnamed local high-school students made brass blanks. No reviewed source establishes permission, affiliation, sponsorship, endorsement, authorship allocation, artwork rights, relationship with the British Museum, relationship with a charity/school/DEF CON/CircuitPython, or media-reuse authority.

The dossier preserves source-named narrative and manufacturing context without assigning ownership, cultural/institutional relationship, approval, sponsorship, final manufacturing responsibility, or image rights beyond the published statements.

Source note: AoSC 2026 eChallengeCoin page and CircuitPython Coin M0 profile.

RISC-V Summit Europe 2026 FPGA Badge note

summit prototype and post-event source-revision boundary · primary team statement and dated repository history · physical initiative established; exact current-source-to-unit mapping unrecovered

The public event-associated material establishes physical boards/prototypes, while a later August Version 1.6 commit fixes design issues and changes silkscreen after the June summit. The reviewed sources do not map the current repository files, gallery render, or all listed fixes to a particular physical summit board.

Current open design sources are linked for research but are not represented as the definitive exact event-unit design, final production revision, or a factual image of every distributed unit.

Source note: SemiTO-V Developer Zone and prototype updates; riscv-fpga-badge-2026 Version 1.6 commit.

GreyCTF Summit 2025 GreyBadge note

summit/finals firmware boundary · public release trail and filesystem README · documented

The public repository has both finals and summit firmware assets. The badge record describes the shared GreyMecha/Army badge archive and challenge surfaces without claiming every final attendee image, provisioning step, or private competition backend was public.

Software claims stay limited to the recovered repository, filesystem README, and release assets.

Source note: greybadge25 README, RP2350 filesystem README, and GitHub releases page.

NilbinSec DC34 Main Badge Fuzzer SAO note

target revision, interface, compatibility, and authorization boundary · maker purpose statement and pre-event timing · built against initial public information; final compatibility unknown

The README says the SAO was designed from initial public information about the DEF CON 34 main badge and may be reflashed as challenge information develops. It does not establish that a final badge uses the same port wiring, pull states, wake signal, I²C behavior, firmware, protections, or challenge interface, or that an owner has permission to test it.

Readers should not treat the public source as a compatibility guarantee, a target-specific exploit claim, an endorsement to connect the SAO, or authorization to interact with another attendee's hardware.

Source note: NilbinSec DC34 Main Badge Fuzzer SAO README and firmware source.

BSides Chennai 2026 Event Badge note

technical and CTF-linkage gap · official event, schedule, ticket, and CTF-page review · separate CTF documented; badge technology unreported

The official site separately documents the concluded 2026 CTF and a ticket-included Event Badge, but no reviewed source connects them technically or publishes badge hardware, firmware, app, repository, protocol, challenge behavior, source release, maker credit, support path, or safety/privacy characteristics.

No electronic, software, CTF, radio, power, data-use, or operational claim is inferred from the shared conference context.

Source note: BSides Chennai 2026 official event, ticket, schedule, and CTF pages.

BSides Mumbai 2026 Badge Pickup note

technical and CTF-linkage gap · official event and ticket-page review · CTF and pickup separately announced; badge technology unreported

The organizer announces a two-phase CTF and separately schedules badge pickup, but no reviewed source technically connects them or publishes badge firmware, application, repository, protocol, hardware, challenge behavior, source release, maker credit, support path, safety information, or privacy characteristics.

No electronic, software, CTF, radio, power, data-use, or operational claim is inferred from common event context.

Source note: BSides Mumbai 2026 official event and ticket page.

Red Team Summit 2025 Electronic Badge note

technical and distribution archive gap · official historical source · documented source limitation

The official history establishes that the Redmond 2025 summit had an electronic badge, but it does not publish the artifact's physical form, components, PCB, power system, firmware, app, challenge, creator, licence, production quantity, ticket or invitation eligibility, recipient allocation, collection, delivery, issue history, or final configuration.

The catalogue records the confirmed electronic-badge milestone without turning a one-sentence historical designation into an invented hardware, software, credential, distribution, or manufacturing dossier.

Source note: Red Team Summit official history.

BSides Knoxville 2025 Fox Pick ESP32-S3 Badge note

technical archive and source-release boundary · public maker talk and source recovery · maker states QR-linked source; direct archive unlocated

Morgan Rogers' talk says source code was made available through a QR-linked GitHub page, but this pass did not recover the destination URL. No source license, repository ownership record, source snapshot, release/tag, build instructions, final binary, schematic, Gerbers, BOM, or board files were recovered.

The catalogue can retain the maker's source-release statement while avoiding a fabricated repository link, open-source license claim, reproducible build claim, or unsupported source-code detail.

Source note: The 2025 BSides Knoxville Badge: Tips, Tricks, and Tribulations public AllBSides mirror/transcript.

HITBSecConf2024 Bangkok Badge Village Device note

technical archive gap · official source but incomplete · needs deeper archive recovery

The official page identifies the Raspberry Pi Pico core and fault-injection purpose, but this pass did not recover schematic, BOM, PCB files, firmware, exact circuit details, or production quantity.

The dossier records the verified training-device surface while avoiding unsupported implementation claims.

Source note: HITBSecConf2024 Bangkok Badge Village page.

LayerOne 2026 Three-Button Keyboard Badge note

technical source gap · official status page and post-event sources · awaiting public badge archive

Official sources prove the electronic keyboard badge, assembly model, blinkies, UV-resin art layer, and repair response, but do not identify its controller, LEDs, power, radio, display, connectors, PCB files, schematic, BOM, firmware, binary, build process, challenge, or software license. The official badge-status page still says the 2026 information is forthcoming.

The catalogue records the verified artifact and hands-on event context without upgrading a visual or assembly description into unsupported electrical or software claims.

Source note: LayerOne 2026 wrap-up, Hardware Hacking Village page, and official badge-status page checked 2026-08-03.

DC503 DEF CON 26 VIP Banglet note

technical-source caveat · public repository archive · needs deeper production archive

The repository exposes Eagle CAD, firmware sketches, and 3D-print files, but this pass did not recover a final BOM, ordered assembly record, firmware release tag, complete user manual, or post-event challenge writeup.

Hardware and software claims remain limited to the public repository files and official talk description.

Source note: pdxbadgers/2018-banglet repository tree, sketches README, firmware, and 3D-print README.

CarolinaCon Online 2 Conference PCB Badge note

technical-source caveat · official source but incomplete · needs artifact archive

The recovered official pages prove a Conference PCB Badge and electronic-badge merch bundle, but do not publish component, firmware, schematic, BOM, battery, image-rights, or challenge-source detail.

The record preserves the artifact while avoiding unsupported claims about hardware design or firmware behavior.

Source note: CarolinaCon Online 2 home, about, and schedule pages.

BSidesSF 2024 Hardware Challenge Village Badge note

technical-source caveat · official source plus attendee report but incomplete archive · needs badge-team archive

The official schedule proves a specially designed HCV badge and badge CTF contest, and a Veritas attendee report documents the screen, joystick, USB-C/battery power, and clue-exchange behavior, but no source recovered here publishes component identifiers, schematics, firmware, PCB files, production notes, or challenge source.

The catalogue can describe observed user-facing badge behavior while leaving schematic, firmware, and manufacturing details for a later badge-team archive.

Source note: BSidesSF 2024 Hardware Challenge Village schedule description and Veritas attendee report.

BSidesSF 2025 Hardware Challenge Village Badge note

technical-source caveat · official source but incomplete · needs badge-team archive

The official schedule proves a badge designed specifically for the Hardware Challenge Village CTF, but does not publish component identifiers, schematics, firmware, PCB files, production notes, challenge source, or scoreboard archive.

The catalogue records the verified village badge and leaves hardware/software archaeology for a later source recovery pass.

Source note: BSidesSF 2025 Hardware Challenge Village schedule description.