Country dossier
Worldwide badge coverage for Singapore, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.
Seeded artifacts
Singapore ESP8266 CTF badge
NUS Greyhats' X-CTF 2016 finals used a custom ESP8266 electronic badge documented by the official event page, the badge designer's hardware and firmware writeups, and public hardware and firmware repositories.
Singapore building-shaped serial CTF badge
SINCON 2023's first badge was a Khong Guan Building-inspired interactive CTF badge with a custom single-sided PCB, ABOV A96S174 MCU, CH340G USB-serial bridge, micro-USB, CR2032 holder, 12 MHz crystal, SMD passives, and 1206 LEDs.
Singapore dual-screen Octopus badge
Off-By-One Conference 2024 used an Octopus-themed hardware badge with ESP32-S3 and ATmega328P controllers, dual 128x128 GC9A01 round LCDs, IR, WS2812 LEDs, buttons, a user-flashable MicroPython challenge surface, and six published challenge flags.
Singapore RP2350 and ECP5 FPGA challenge badge
NUS Greyhats' public GreyBadge archive identifies the 2025 GreyCTF badge as GreyMecha/Army, with RP2350-side CircuitPython firmware, KiCad hardware files, an ECP5U_25 FPGA schematic, GC9A01 SPI display, Li-ion power-path circuitry, summit UF2/filesystem releases, and named challenge apps.
ESP32-C6 attendee badge with Laser* Tag and hardware-hacking workflow
The inaugural DEF CON Singapore attendee badge, DC-SG-1, is an official electronic badge issued to ticket holders. Public event workshop and game documentation identifies an ESP32-C6 platform with eight megabytes of flash, an interactive hardware-hacking workflow, USB-C access, and a conference-wide infrared Laser* Tag game.
Unofficial CH32V305 SDR badge preorder
A community HFSDR badge preorder for DEF CON Singapore 2026, documented through Hackin7's r/Defcon preorder post and the linked public rhgndf/hfsdr hardware, firmware, host-software, and WebUSB archive.
HTX village badge with illuminated public-safety icons
HTX's official DEF CON Singapore coverage documents Public Safety Village badges, including a badge image described as featuring illuminated icons of emergency vehicles, alongside the first DEF CON Public Safety Village.
CSIT C517 finalist BLE mesh challenge hardware
A source-backed TISC@DEF CON SG finals challenge artifact: CSIT's official C517 page documents the on-site TISC finals, and a finalist writeup says each of the top-50 finalists received an ESP32 hardware trinket running a customized BLE mesh chat protocol to reverse engineer.
Maker-documented RP2040 community eBadge with firmware, art, and SAO sources
RestiaAshdoll8's public DEFCON-SG-2026-Div0-Tingkat-eBadge repository says it contains source code and relevant files used in a physical Div0 Tingkak eBadge. It preserves a UF2, RP2040/Pico-focused source, artwork, and SAO project files. Its sources conflict on event identity: the repository title names DEF CON Singapore while its firmware menu banner says SINCON 2026 BADGE. This record keeps the DEF CON Singapore association maker-declared rather than resolving that conflict into official event status.
Source-backed CH32V003 student-bootcamp electronic badge
Hackin7's public project page identifies a deployed electronic PCB Hackbadge created for Greycademy 2026. NUS Greyhats' official announcement says program participants could take home electronic badges, while the primary maker record identifies a CH32V003 coin-cell design and reports an event-day power-reliability repair across more than 200 programmed units. The public trail does not define every recipient, final firmware image, or all-unit configuration.
Singapore custom PCB hackathon badge
NUS Hackers' Hack&Roll 2026 introduced the event's first custom PCB badge, documented by the organizer recap, a Friday Hacks making-of talk, and a public MIT-licensed ESP-IDF firmware and component archive.
Maker-documented RP2040 e-ink/NFC game-jam badge
Kai Pereira's public archive identifies these as Overglade hackathon badges designed for the completed Singapore game jam. The device has an RP2040, passive NFC, an onboard e-ink driver, and an exposed ticket-shaped PCB with public KiCad and MicroPython source trees. Official Hack Club pages establish the event, but not a badge entitlement or all-recipient allocation.
Events
The June 18, 2016 NUS Greyhats student cybersecurity finals in Singapore whose participants received a custom ESP8266 electronic badge with LCD, buttons, LiPo power, and public challenge firmware.
The Singapore SINCON Reloaded 2023 edition held 5-6 January 2023 at Voco Orchard Singapore, where the first SINCON badge became a Khong Guan Building-shaped interactive CTF badge.
The June 26-27, 2024 first Off-By-One Singapore offensive-security conference whose source-backed Octopus hardware badge carried dual screens, ESP32-S3 and ATmega328P controllers, MicroPython challenge apps, and a six-flag badge challenge.
The July 5, 2025 NUS Greyhats cybersecurity summit in Singapore whose public GreyBadge archive documents the GreyMecha/Army badge, setup workflow, KiCad hardware, CircuitPython filesystem, FPGA files, and summit firmware releases.
The April 28-30, 2026 official DEF CON Singapore conference at Marina Bay Sands, represented here by the official DC-SG-1 attendee badge, a source-backed unofficial/community HFSDR badge, HTX Public Safety Village badge artifact, CSIT TISC finalist ESP32 challenge trinket, and a maker-labelled Div0 Tingkat eBadge whose firmware and repository event labels conflict; no non-DC-SG-1 record is treated as a universal admission badge.
The completed January-February 2026 A.YCEP × Greycademy cybersecurity bootcamp and CTF program in Singapore, run by NUS Greyhats in collaboration with the Cyber Security Agency of Singapore's Advanced Youth Cyber Exploration Programme. Official announcements give the January 24-25 workshops, January 26-30 practice, and January 31 / February 7 qualifier-and-final schedule and say participants could take home electronic badges; the organizer's post confirms the program was held. A primary maker page documents a deployed Hackbadge created for Greycademy, while recipient allocation, final unit configuration, official hardware ownership, source release, and media rights remain bounded.
The January 17-18, 2026 NUS Hackers student hackathon in Singapore whose organizers introduced their first custom PCB badge, later documented through a public ESP-IDF firmware and I/O component archive.
The completed January 29-February 2, 2026 Hack Club game jam in Singapore. The retained official Overglade page describes its physical game-jam framing, and a current Hack Club page identifies a January 2026 Singapore Overglade that took place. Kai Pereira's public project archive explicitly calls its RP2040, e-ink, and NFC devices Overglade hackathon badges, while organizer allocation, final production variation, software deployment, licensing, and image rights remain bounded.
Lifecycle
The hardware tree includes an ECP5U_25 CABGA256 schematic and the firmware tree includes ECP5 projects, tests, and a UART coprocessor example with open FPGA tooling notes.
The repository setup flow flashes a CircuitPython UF2, then copies the RP2350 filesystem to CIRCUITPYTHON for the badge runtime.
The documented hardware includes IR transmitter/receiver and an SAO connector alongside the main badge controls and lights.
The Espressif component package exposes badge-specific control of Hack&Roll 2026 LEDs and buttons through the built-in GPIO expander.
The badge CTF uses serial interaction, OSINT, crypto, and stegano story challenges, six floor unlocks, elevator navigation, remembered flags, and a final trophy/leaderboard prompt.
The writeup documents USB file access, Python files, and six challenge flags across web, BLE, roulette, file, and inter-controller puzzle surfaces.
The firmware repository preserves applet, challenge, Wi-Fi scanner, LCD, and game source modules for the event badge firmware.
The filesystem README names the Grey finals challenges as Hornet Revenge, Leaky Pin, Bricked Up, Shooting Flags, Secure Memory, and CatCore.
The public README identifies an onboard e-ink driver and describes the badge as visually displaying a configured name. It does not establish the exact final panel, update behavior, display contents, power state, accessibility behavior, or participant configuration used at the event.
The design journal describes a passive NFC tag and antenna receiving harvested energy, alongside I2C/control wiring intended for possible active-NFC customization. This preserves the layered NFC design concept without asserting a final attendee-unit NFC IC, protocol, provisioned data, reader behavior, access-control role, enabled active mode, deployment, safety certification, or privacy practice.
The badge carried two 128x128 GC9A01 circular LCDs, buttons, WS2812 LEDs, USB-C, and a visible Octopus board shape.
The finalist writeup says each TISC@DEF CON SG finals participant was handed an ESP32 hardware trinket for one of the on-site challenges.
Hackin7's preorder post offered the HFSDR badge for collection at DEFCON SG, with battery and no-battery kit pricing and possible later handoff at Hackaday Europe or DEFCON US.
The public DC-SG-1 badge talk describes the electronic hacker badge as given to ticket holders for entry to DEF CON Singapore.
The badge used multiple buttons for menu and challenge interaction, with GPIO support preserved in the public firmware.
The Cryptocurrency Village workbook lists feature, simulator, and development workshops for the badge, including an ESP-IDF toolchain workflow and USB Type-C cable requirement.
The main schematic includes a GC9A01 IPS SPI display, while the firmware README describes user-customizable 240x240 JPG/GIF badge images.
The firmware and hardware trail document a Nokia 5110-style PCD8544 LCD as the badge display surface.
CSIT documents TISC@DEF CON SG as an online qualifier followed by on-site finals, while the finalist writeup says the top 50 finalists qualified and had six hours for five challenges.
Badges retained hit records locally and periodically synchronized results through internet-connected exhibit-hall base stations using ESP-NOW with periodic channel and data-rate hopping.
Friday Hacks #287 framed the badge as an electronic-badge production story for over 1,000 units, spanning artwork, electronics/code, assembly, and programming.
The firmware README and main C source document a simple dice-lighting program driven by badge buttons and LEDs.
The badge is played by turning off battery power, connecting micro-USB, opening a terminal or Arduino IDE serial monitor at 9600 baud with Both NL & CR, and sending three stars to enter CTF mode.
The GitHub release trail now includes v1.0 during DEF CON Singapore and v1.1 afterward, with v1.1 documenting new graphics and a USB streaming reliability fix.
The preorder kit included solderable LEDs/resistors and SMA connector work, plus badge PCB, antenna, encoder, and screen.
The attendee writeup identifies an ESP32-S3 running Arduino and an ATmega328P running MicroPython, with the two controllers talking over I2C.
The host guide documents a Python probe and GNU Radio examples for streaming samples from the HFSDR USB device.
Every powered-on official badge played an infrared Laser* Tag game with five color teams, valid-hit cooldowns, and individual contributions to aggregate team scores.
The programme invited attendees to explore the Infocomm Z-Machine simulator with I/O on the USB CDC console and optionally program the badge.
The releases page preserves Prototype 3 BOM/CPL/Gerber/schematic assets plus summit_v1 and summit_v2 firmware and filesystem release files.
The hardware writeup and repository document the badge around an ESP8266 module with USB serial programming and Wi-Fi features.
The primary maker account identifies a CH32V003 controller and coin-cell power for the Greycademy Hackbadge. It does not identify the exact cell type, power circuit, components, display, input/output surface, connector, pinout, safety validation, or final-unit configuration.
The public repository acknowledgements say Espressif Systems sponsored ESP32-C3-WROOM-02-N4 modules for the Hack&Roll 2026 hardware badge.
The official badge supported the public OpenLASIR infrared protocol, allowing compatible third-party devices to join the game while tracking official and third-party interactions separately.
The hardware trail documents lithium-polymer battery power and MCP73831-based charging for portable badge use.
The maker reports an early coin-cell brownout issue and says more than 200 already programmed badges were reprogrammed before distribution to improve battery life. This records a bounded field-repair history, not a released firmware, recipe, full validation result, or proof of universal final-unit parity.
The public repository includes native KiCad schematic, PCB, project, and production-data files plus MicroPython-oriented configuration, main application, e-ink driver, and bitmap assets. The archive does not expose an explicit root repository licence, release, or proof that it matches every produced or participant-configured unit.
The repository README documents rotary-encoder controls for FM audio output and cycling LED modes when the device is used without a PC.
The HTX Public Safety Village page ties the village to AI and IoT public-safety challenges and says top HTX CTF finalists unlocked limited-edition DEF CON Singapore Public Safety Village swag.
HTX's launch report image metadata identifies a Public Safety Village badge featuring illuminated icons of emergency vehicles; no component or firmware details are public.
The repository describes pairing through the WebUSB UI, setting frequency and gain, pairing again, and then observing the waterfall.
The trinket ran a customized mesh chat protocol over BLE, with the challenge requiring reverse engineering to gain access to an administrative system broadcasting over the protocol.
The SINCON hardware village used the badge for a soldering activity with tiny SMD LEDs mounted upside down, pairing hardware work with the software CTF.
Operational history
The catalogue includes it as a source-backed C517 Village challenge artifact while avoiding an official admission-badge claim.
The catalogue uses the writeup to prove challenge behavior while avoiding full challenge-solution reproduction in the badge summary.
The record keeps an attributable production/reliability history visible without offering repair instructions, declaring the hardware safe, or generalizing a maker observation into a verified universal outcome.
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.
The event and badge are included, but distribution and admission-credential claims remain conservative.
The record treats the score and synchronization system as documented event-time behavior, not a permanently available badge service.
The entry retains a useful public firmware trail without turning it into operating instructions, a security challenge walkthrough, a guarantee of USB behavior, or proof of a final event configuration.
The software section describes the recovered badge firmware without overclaiming complete event infrastructure publication.
The record is included as a hackable hacker-culture event artifact while keeping the event type explicit.
The dossier describes only the substantiated hardware and software surface instead of inferring a complete board design or claiming that the separate OpenLASIR repository is DCSG1 firmware.
Hardware and software claims stay limited to the finalist writeup's challenge description.
Hardware claims stay limited to the organizer posts, repository README, code, component registry, and acknowledgements.
Hardware and software fields stay limited to the attendee writeup, licensed photos, and public event context.
Hardware claims are limited to preorder text, repository structure, README behavior, and host-guide protocol documentation.
Readers can inspect the source-backed electronic surface without treating it as an electrical guarantee, a safe host/SAO compatibility statement, a full open-hardware release, or proof of how many real badges were made or received.
The record documents the verified village badge artifact without inventing electronics, firmware, production, or distribution details.
Hardware files are cited as evidence, but repository images are not copied locally and reuse claims stay limited.
The badge record remains limited to the organizer wording and maker's high-level factual account rather than inventing technical details or treating a repaired field unit as a fully published hardware release.
The Singapore record can show a real badge photo with source URL, license, attribution, preserved local source original, and optimized WebP delivery rather than generated or unclear imagery.
No repository art, PNG, screenshot, source graphic, social image, or generated approximation is copied into the public image directories; the record remains source-linked and image-free pending complete reusable-image provenance.
The record preserves the maker-declared DEF CON Singapore association while explicitly avoiding a claim of DEF CON or SINCON official issuance, attendee-wide allocation, organizer authorization, sponsor status, credential function, or an event-specific final handoff.
The Singapore record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The official Singapore attendee-badge record remains image-free rather than copying a guide illustration, social post, documentation screenshot, or generated approximation.
The record remains image-free rather than copying the HTX article photo, using a documentation screenshot, or substituting generated badge art.
The Singapore record remains source-backed and image-free rather than copying repository photos, sponsor artwork, or blog images without complete image rights.
The Singapore record remains source-backed and image-free rather than copying event photos or documentation screenshots without a complete image provenance record.
The Singapore entry remains source-backed and image-free rather than copying project photos without a complete image provenance record.
The Singapore record remains source-backed and image-free rather than copying repository artwork, social media, slides, screenshots, or generated badge art.
The Singapore record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The Singapore C517 record remains source-backed and image-free rather than copying an article photo, screenshot, or generated substitute.
The Singapore record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The Singapore record remains source-backed and image-free rather than copying social-media previews, repository screenshots, repository artwork, or generated imagery.
The catalogue documents a real event-specific electronic artifact without presenting it as a universal attendee entitlement, admission credential, official hardware release, or completed allocation account.
The record is stronger for firmware artifacts but remains classified as community/unofficial unless an official DEF CON source identifies it as the official conference badge.
Repository files are cited as public evidence, but local reuse is limited: no repository images, artwork, hardware files, firmware, or slides are copied into the catalogue as licensed assets.
The catalogue cites repository facts as public evidence but does not reuse repository images, hardware files, or code assets as licensed local content.
The dossier records the observable hardware and serial CTF flow while avoiding unsupported repository or source-code claims.
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.
The entry is source-backed and image-free rather than copying social-media images, maker-project visuals, event media, screenshots, placeholders, or generated approximations.
The record is included as a Singapore hacker-culture competition badge while keeping the event type explicit.
Software claims stay limited to the recovered repository, filesystem README, and release assets.
The record is included as a source-backed community badgelife artifact connected to DEF CON Singapore, not as an official DEF CON badge claim.
The software section separates the recoverable ESP-IDF workshop code from any unrecovered event firmware or private production tooling.
Hardware and software descriptions remain tied to the public design archive rather than promoted to a fully known, uniform, deployed event build.
