Country dossier

Spain

Worldwide badge coverage for Spain, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.

6 badge(s) · 5 event(s) · 5 series · 2017-2026

Back to countries

Seeded artifacts

Badges

2017

r2con 2017 Friends Badge

Limited electronic badge for r2con speakers and friends

A limited electronic badge made for r2con 2017 speakers and friends in Barcelona, documented by the official badge-manufacturing talk and first-hand reporting that says it showed project-status information such as build state, last commit, and GitHub stars.

2026

Barcelona Cybersecurity Congress 2026 Digital Access Badge

Planned app-issued venue-access identity artifact

Barcelona Cybersecurity Congress 2026's official app page tells visitors to download the official app and secure a digital badge, calling it the essential key for venue access. The same page says the app will be available in September 2026, before the November 3-5 Barcelona event. This record models a planned app-issued access identity artifact only; it does not infer a physical badge, a PCB, a ticket entitlement, an account or credential format, or a final access workflow.

2026

Barcelona Cybersecurity Congress 2026 Networking Badge

Planned printable networking identity artifact

Barcelona Cybersecurity Congress 2026's official app page says that, with the event digital badge, visitors can print a Networking Badge to facilitate connections with fellow attendees. It names the registration desk and the Hall 2.1 info point as print locations. This record captures that planned printable networking artifact without assuming its physical medium, design, personal-data fields, access rights, or relationship to the separate digital venue-access badge.

2026

C1B3RTR4CKS 2026 CH32V003 Badge

Source-backed RGB LED-matrix event badge

SEIF-UAM's public C1B3RTR4CKS 2026 badge repository documents an event badge with a CH32V003 RISC-V microcontroller, 8×16 RGB LED matrix, five-button control surface, public C firmware, games, and a personal-name marquee. The official event site and a contemporaneous attendee report place the physical artifact at the completed May 29 Madrid event; final allocation and production details are not public.

2026

h-c0n 2026 CTF BADge

Madrid Hackplayers electronic development-board CTF badge

A source-backed Spanish hacker-conference electronic badge record: the official h-c0n post says Hackplayers finally produced an electronic badge for the sixth 2026 edition, describes it as a fully functional development board, and ties pickup to the February 6 conference registration and CTF start; the public `therealdreg/hcon2026hwctf` repository and Hackplayers post-event write-up document RP2350/RISC-V firmware, tooling, named co-creators, and winner write-ups.

2026

RootedCON 2026 Pacman Badge

Spanish ESP32 PACMAN CTF badge with project-builder and community-reversal evidence

RootedCON 2026's PACMAN-themed attendee CTF badge is documented by both community reversals and a first-hand TechFrontiers project-builder write-up. David Melendez Cano reports original colored Ghost boards that attendees could choose, an ESP32-WROOM-32 platform, ESP-NOW game-server interaction, per-badge NVS identity/key material, and digitally signed questions and answers. Community reversals independently identify an ESP32-D0WD-V3, 1.77-inch ST7735 128x160 display, directional controls, and native quiz-server CTF protocol for the March 5-7 sixteenth edition at Kinepolis Madrid.

Events

Camp and Event Editions

r2con 2017

r2con · Barcelona · 2017 · 1 badge(s)

The September 6-9, 2017 radare2 reverse-engineering congress in Barcelona, whose official schedule included NighterMan's r2con badge manufacturing talk and whose attendee reporting documents a limited speaker/friends electronic badge.

Barcelona Cybersecurity Congress 2026

Barcelona Cybersecurity Congress · Barcelona - Gran Via Venue, Hall 2 · 2026 · 2 badge(s)

The planned November 3-5, 2026 Barcelona Cybersecurity Congress edition. Its official app page says visitors secure a digital badge in the app as the key for venue access and can print a Networking Badge at registration or the Hall 2.1 info point. Current official material does not describe the credentials' implementation, final printed form, hardware, or reusable image rights.

C1B3RTR4CKS 2026

C1B3RTR4CKS · Escuela Politécnica Superior, Universidad Autónoma de Madrid, Cantoblanco, Madrid, Spain · 2026 · 1 badge(s)

The completed May 29, 2026 fifth C1B3RTR4CKS cybersecurity and cyberintelligence event at Universidad Autónoma de Madrid. The organizer-linked SEIF-UAM repository identifies the C1B3RTR4CKS 2026 badge and public event firmware, while a contemporaneous attendee report describes the physical LED-matrix badge credential. Public sources do not establish a recipient ledger, final board revision, production archive, or reusable image rights.

h-c0n 2026

h-c0n · Centro Cultural Sanchinarro, Madrid · 2026 · 1 badge(s)

The February 5-7, 2026 Hackplayers h-c0n edition in Madrid, with workshops at Exe Madrid Norte and talks at Centro Cultural Sanchinarro, whose official post announced the CTF BADge electronic development-board challenge.

RootedCON 2026

RootedCON · Kinepolis, Madrid · 2026 · 1 badge(s)

The March 5-7, 2026 sixteenth RootedCON edition in Madrid whose direct TechFrontiers project-builder account and community reversing repositories document a PACMAN Ghost ESP32 attendee badge with display, directional controls, ESP-NOW CTF interaction, and a native quiz-server protocol.

Lifecycle

Add-ons & Upgrades

RootedCON 2026 Pacman Badge direct project-builder account

event CTF and badge networking

Ed25519-signed ESP-NOW CTF interaction

The builder describes ESP-NOW question distribution, Ed25519 verification before display, and individual badge-signed replies to the game server. This preserves the source-described event architecture without publishing packet construction, key-recovery steps, backend endpoints, final protocol source, cryptographic review, or a general security guarantee.

h-c0n 2026 CTF BADge source-backed

event challenge window

Registration pickup and timed CTF

The official post says participants could start the CTF when registration opened on February 6, 2026 at 16:45, with the competition ending on February 13 at 17:00 or when three participants solved every flag.

event firmware

Public game-console firmware

SEIF-UAM publishes C and PlatformIO source for the event badge's menu and compact game collection. The catalogue links the source but does not reproduce build, flashing, game-control, or hidden-feature instructions.

h-c0n 2026 CTF BADge repository-backed

firmware challenge

RP2350 RISC-V CTF firmware

The public hcon2026hwctf repository provides ctf.uf2 and describes RP2350/RISC-V Hazard3 exploitation challenges for the HC0N 2026 hardware CTF.

personalization software

Personal-name marquee

The event guide documents a personal-name editor and scrolling marquee as attendee-facing firmware features; it does not establish whether all handed-out badges shared the same final configuration.

h-c0n 2026 CTF BADge post-event documented

post-event CTF archive

Winner write-up archive

The Hackplayers recap links the first three winner write-ups and summarizes their approaches: firmware extraction, RISC-V reversing, logical-flaw exploitation, static and dynamic analysis, validation weaknesses, and state manipulation.

RootedCON 2026 Pacman Badge direct project-builder account

power and debug architecture

LiPo/UVLO, USB serial, and screen-power design surface

The builder describes LiPo 1S, integrated charging, under-voltage lockout, automatic USB-serial RESET/EN control, exposed UART0, and an extra screen-ground MOSFET on some boards. The account does not establish cell capacity, charge settings, board-revision coverage, electrical testing, safe modification, or a production-service procedure.

Operational history

Issues & Camp Impact

credential allocation and recipient boundary · contemporaneous attendee report plus official event and repository sources · partially documented

A contemporaneous report describes the physical badge as the event credential and says badges were limited, but recovered sources do not state a final quantity, ticket entitlement, recipient ledger, variant allocation, access-control technology, or completed handoff record.

The dossier documents a real badge at the event without turning an attendee observation into an unsupported universal issuance or credential-system claim.

firmware release and challenge boundary · public source-tree review · source available but release parity unknown

The organizer-linked repository exposes source and user documentation, but no tagged event release, signed image, installation ledger, or complete post-event challenge archive was recovered. The catalogue intentionally withholds operational use instructions and any claim about exact source-to-unit parity.

Public code remains an important preservation resource without being presented as a verified reproduction image or complete challenge solution set.

formal license and repository-media boundary · GitHub metadata and project image policy · needs explicit license or permission

Observed GitHub metadata reports no formal repository license, and the README's embedded badge media lacks the complete image-specific reuse license or permission basis, attribution, and processing provenance required by this catalogue.

The public source is linked for evidence, but no repository attachment, official-page image, or social-media image is copied into the catalogue and the badge remains image-free.

hardware and production archive gap · public guide and repository review · needs hardware archive

The public guide and firmware establish the controller, LED matrix, buttons, and software surface, but no recovered source provides schematic, PCB files, BOM, battery/power specification, final hardware revision, manufacturing record, test record, or firmware image/hash installed on event units.

The record stays precise about the documented interface while avoiding claims that the current source tree exactly describes each physical unit.

hardware, data, security, and privacy specification gap · official app page · digital badge named; implementation unreleased

The source names a digital badge and app but does not identify a QR code, barcode, NFC/RFID, Bluetooth, wallet pass, account model, device binding, encrypted credential, personal-data fields, consent/visibility controls, authentication, telemetry, offline behavior, data retention, third-party sharing, security review, source release, terms, or privacy policy specific to the badge.

The dossier does not convert the access statement into a claim about a particular technology, secure-design property, personal-data practice, mobile-platform compatibility, or physical/electronic badge hardware.

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

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

The Spain record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

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

No h-c0n 2026 CTF BADge image is published because the official blog media, Hackplayers recap media, and repository photos have not been paired with complete reusable image rights, attribution, source URL, and processing provenance for catalogue publication.

The Spanish h-c0n record remains source-backed and image-free rather than copying blog images, repository photos, prize photos, screenshots, logos, or generated badge art.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No Barcelona Cybersecurity Congress 2026 digital access-badge image is published because the official app, event, and Hacking Village pages do not pair a selected factual credential image with a reusable licence or explicit permission basis, attribution, source URL, and processing record.

The planned Spanish record remains source-backed and image-free rather than copying app-store art, event graphics, page images, screenshots, social-media media, placeholders, or generated approximations.

missing rights-cleared image · local project policy · needs selected, attributable, cleared original

No Barcelona Cybersecurity Congress 2026 Networking Badge image is published because the official app, event, and Hacking Village pages do not pair a selected factual printed artifact image with a reusable licence or explicit permission basis, attribution, source URL, and processing record.

The planned Spanish record remains source-backed and image-free rather than copying app-store art, event graphics, page images, screenshots, social-media media, placeholders, or generated approximations.

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

No RootedCON 2026 Pacman Badge image is published because neither the event, community repositories, nor the TechFrontiers builder post pairs a selected original badge photo or upstream raster with the complete reusable source URL, permission basis, attribution, and processing record.

The Spanish record remains source-backed and image-free rather than copying community repository diagrams, the LinkedIn post image, screenshots, social media, placeholders, or generated approximations.

post-event source gap · official and post-event source wording · documented; monitor deeper archive

The official post intentionally withheld rear-side component details before attendees received the badge, and the later public trail improves the creator, firmware, tooling, and winner-write-up record without exposing board files, schematics, BOM, production files, final quantity, or full component identity.

The catalogue records only the official development-board, Hackplayers recap, and repository-backed RP2350/RISC-V challenge claims while withholding exact board-design and manufacturing claims.

pre-event app, credential, and access workflow boundary · official app page · planned app and access function announced; page timing copy is internally ambiguous

The official page says the app will be available in September and calls the digital badge the essential key for access, but a lower section on the same page also says the new official BCC app is now available without a BCC26-specific release date or version. The congress has not yet occurred, and the reviewed sources do not resolve that timing wording or establish app publication, download availability, ticket qualification, enrollment, issuance, credential activation, access-control integration, venue acceptance, reliability, exception handling, support, revocation, or an attendee's completed entry.

The catalogue retains a precise planned access-artifact statement without presenting conflicting event-app copy as a delivered credential, universal entitlement, or verified access outcome.

pre-event printing and distribution boundary · official app page · print locations announced; app-timing copy is internally ambiguous and completed output unverified

The official page says visitors can print a Networking Badge at registration or the Hall 2.1 info point, and its BCC26 section says the app will be available in September; a lower section on the same page also says the new official BCC app is now available without a BCC26-specific release date or version. The event has not occurred, and the reviewed source does not resolve that timing wording or establish eligibility, print-hours, staff/equipment availability, paper or card stock, print quantity, naming or personalization policy, queueing, reprints, failed-print handling, recipient allocation, collection, or completed delivery.

The catalogue records a concrete proposed print path without presenting conflicting event-app copy as a universal attendee benefit, an issued physical artifact, or a verified onsite workflow.

print form, data, consent, and access-function gap · official app page · networking purpose named; artifact and data model unreleased

The source says the Networking Badge facilitates attendee connections and is printable with the digital badge, but does not identify medium, dimensions, design, personal-data fields, QR/barcode/RFID/NFC behavior, app-to-print data flow, consent/opt-in controls, visibility settings, contact sharing, retention, security, accessibility, credential authentication, venue-access role, challenge role, or privacy terms specific to the printable artifact.

The dossier does not turn a networking purpose into a claim about badge technology, identity verification, data handling, contact exchange, physical construction, or permission to access the venue.

project-builder confirmation and official-archive gap · direct project-builder post plus community sources · direct build/CTF confirmation; official archive unrecovered

The TechFrontiers write-up directly attributes the PACMAN Ghost badge build and CTF design to David Melendez Cano and Gabriela G., while community reversals independently document several component and firmware details. Neither source set supplies an official RootedCON design repository, complete schematic/PCB/BOM/Gerber archive, production ledger, final revision map, battery/charger documentation, backend/protocol source, release, or license.

The catalogue now records direct builder attribution and event architecture without portraying a personal project post or community reverse-engineering tree as an official RootedCON source release, complete production specification, firmware security audit, or reusable-image permission.

Resources

Sources