Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
The official app page says visitors can print a Networking Badge with their digital badge to facilitate connections with fellow attendees.
SourceThe official comms log says the top 50 solvers of the A-Maze-ing Phase 2 puzzle receive the Jupigotchi MiniBadge alongside a conference ticket.
SourceThe organizer's October 3 programme schedules badge pickup during the registration-and-breakfast period. The short schedule entry does not identify badge form, ticket eligibility, pickup mechanics, collection status, or delivery outcome.
SourceThe public agenda says attendees arrive and check in to get their badge, bag, and available gadgets. That is a future registration workflow statement, not proof that an artifact has been produced, collected, or delivered.
SourceThe official update describes an operating layer capable of supporting multiple Cart applications on the planned V2 badge.
SourceGrrCON's terms say that if selected to volunteer, a person will be given a GrrCON staff badge. The same terms say dismissal results in revocation of that badge. The wording does not identify a specific unit, physical form, ticket relationship, access mechanism, pickup procedure, or completed handoff.
SourceThe maker says hardware documentation and a stub firmware will be provided after the conference. That is a public future-release statement, not a currently available repository, license, binary, final firmware, completed design release, or guarantee of timing/scope.
SourceThe 2026 sponsor prospectus distinguishes sponsor-ticket rows marked Electronic Badge from rows marked Non-Electronic.
SourceThe official ticket page lists an Exclusive donator badge with the 1 zł Donation pass. It does not state whether the named form differs physically or technically from the general Exclusive badge or establish production, allocation, or completed handoff.
SourceThe official ticket page lists an Exclusive badge with the free General Admission and AGH Student passes. It does not identify the artifact's material, physical form, technology, quantity, maker, production status, recipient ledger, or completed handoff.
SourceBlack Hat's pass-comparison page states that Student Pass badge pickup is Thursday, December 10 only. The date does not prove physical production, collection by a particular student, or completed delivery.
SourceThe public Badge.Team firmware repository gives the badge a recoverable software trail instead of leaving the dossier at a hardware-only record.
SourcePID.codes names Troopers 2022 badges in the Badge.Team platform identifier record, tying the badge to the wider Badge.Team ecosystem even though hardware and firmware details remain unrecovered.
SourceThe March 2025 update tracks firmware, app, documentation, module redesign, and production work, showing the platform evolving like a badge ecosystem rather than a static product page.
SourceThe brochure promoted a HIDIOT Hackster project-submission path with a prize for the best attendee project.
SourceSprite_tm documented adapting a Gameboy emulator to the SHA2017 badge's e-paper display, preserving a concrete example of post-camp app hacking under unusual display constraints.
SourceAfter camp, the badge could function as a small Arduino-like development board, keeping the badge useful for learning and experiments beyond the event.
SourceThe 28C3 update promised an improved mesh network, l0dables for interactive installations, and support for the next flame generation.
SourceThe post-event Arduino-style source contains Wi-Fi, local web-server, SPI, preferences, and ILI9341 display code. The catalogue records this high-level source context without publishing connection details, credentials, URLs, endpoints, challenge answers, access steps, or a claim that the visible code was deployed at the event.
SourceThe 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.
SourceAfter AC9, the official badge page published four booth/village unlock codes for people who missed them during the event.
SourceThe public repository calls the devices owl badges of the SecretCon 26 convention, and its commit-pinned README says it exists for SecretCon 26 attendees. This is a narrow community post-event signal, not an organizer-defined artifact name, a ticket-tier map, a delivery count, a hardware or firmware specification, a use recommendation, or evidence of completed handoff for any individual.
SourceThe organizer's public feed re-shares an attendee thanking BSides Nashville and SkillBit for coins after the event. This corroborates attendee-side coin receipt but does not establish all-recipient delivery, a coin count, maker role, material, or variant inventory.
SourceA March 24 post-event update by Dr Paul Black says the conference badge had 20 puzzles to solve and that full source code was released. The post directs readers through a short link whose final archive target was not independently recovered in this pass.
SourceHardwear.io documents leaving the badge's presentation mode around the 6:30 mark and uploading pictures afterward, turning the attendee object into a reusable e-paper display target.
SourceBadge.Team published a post-event guide for completing the mixed-reality challenge without the original hotel props, magnetic maze, and badge-to-badge team formation.
SourceMarc Merlin's writeup and repository document Arduino-environment support for many IoTuz peripherals, demo code, calibration work, and board bring-up fixes.
SourceBSides Porto's official organizer feed says the 2026 second edition wrapped and links a photo archive. It verifies completion of the conference but does not establish an electronic badge's final hardware, distribution, or image-reuse status.
SourceThe report places PWNEDCR 0x08 at Auditorio Nacional in the Centro Costarricense de Ciencia y Cultura in San José, Costa Rica on October 18-19, 2025, with three simultaneous tracks and more than 650 attendees. That event context does not identify badge quantity, eligibility, registration tier, price, pickup, delivery, admission role, or universal attendee distribution.
Sourcekrim404's public GPL-3.0 CDC Badge OS describes an ESP-IDF/PlatformIO application stack with hardware-key, identity, plugin, and BLE capabilities, but labels itself pre-1.0 beta and warns of data loss on flashing. It is not a verified 39C3 deployment image.
SourceThe Europe CFP says attendees could reflash the badge after Hackaday Europe and use it as a Meshtastic device.
SourceThe official page links a post-event experiment for controlling extra addressable LEDs from the badge through WLED-style firmware work.
SourceCyber Saiyan reused the RHC22 badge as a MOCA 2024 workshop and contest target, publishing a dedicated firmware branch and inviting owners to bring the badge, a PC, and USB cable.
SourceElectrolama describes flashing Tasmota by default so the badge could continue as a room sensor after camp when paired with an external sensor.
SourceRepository sketches include production-test, serial-sensor, and MQTT sensor firmware; Marc Merlin's writeup adds a participant LED-strip blinky reuse trail.
SourceA public attendee activity message says the attendee made a Wi-Fi analyzer at BSidesGVL, corroborating that the advertised conversion occurred for at least one reported participant.
SourceMarx314's post-event attendee account identifies an observed NorthSec 2026 badge with ESP32-S3-WROOM-1, 16 MB flash, ST25R3916 NFC, a six-button D-pad, an 18-pixel NeoPixel ring, and an e-ink display path. NorthSec's later official map corroborates the common controller/peripheral shape but not the reported module capacity or every production variant.
SourceThe wrap-up describes the badge as capable of doubling as a breadboard after the event.
SourceThe bsidesbrisbane/badge-2026 repository documents the badge as a manually controllable 555/74LS clock module and publishes Gerbers, BOM/CPL data, a case STL, and an actual board photo after the event.
SourceAt 37C3, Hardware Hacking Area mentors provided HiP badges to teams for embedded-programming practice and allowed the devices to be taken home after the showcase.
SourceThe official organizer feed reposted a report of smooth badge handout and badge engagement, while Jeff Shouse publicly reported helping make the badge with an active badge team.
SourceNorthSec publicly released the separate nsec/badge-2026 source tree after the event, including hardware, firmware, animations, CTF content, dock material, and source artwork. Its historical commit timestamps are retained project chronology, not proof of public availability before the event.
SourceThe manual provides a post-conference conversion path for turning the badge into a RetroPie device after the event.
SourceThe post-event WiFi guide documents how owners can attach the badge to a home or workshop network after the camp infrastructure is gone.
SourceThe public timeline mirror preserves CypherCon's repost of a message saying CypherCon badges were programmed, tested, and packaged before the event, and records opening and wrap messages for CypherCon 9. The repost does not identify a device, badge tier, firmware, test criteria, quantity, production entity, or successful attendee handoff.
SourceThe archive's history places the initial public refactored v2.4.0 source and workshop docs on May 29, 2026, with related v2.4.1 and deck updates through June 1. It increases transparency around the 2025 board but does not establish a 2026 badge reissue or production-firmware parity.
SourceThe 2021 evolution talk documents continuing firmware, Hatchery, BLE, companion-app, sensor, and reuse work after Camp 2019.
SourceRahul Thareja's public, commit-pinned project calls the design the Seasides 2026 Roulette Badge, says more than 300 people assembled it live, and provides a C firmware, schematic, and Gerber trail. That is strong maker documentation of a real physical artifact, but the official event sources do not independently name the design or confirm the claimed count and unit parity.
Source