DEF CON Singapore 2026 · Singapore · 2026

Div0 Tingkat eBadge (DEF CON Singapore 2026)

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.

EventDEF CON Singapore 2026
SeriesDEF CON Singapore
LocationMarina Bay Sands, Singapore
CountrySingapore

People

Authors & Credits

DEF CON Singapore community-context publisher

Division Zero (Div0)

Division Zero's own recap confirms its hands-on SG Community presence at DEF CON Singapore 2026. It does not name the archive or establish badge authorship, issuance, production, distribution, official approval, or image-reuse authority.

Source

source archive publisher

RestiaAshdoll8

The public GitHub account publishes the commit-pinned archive and README. This handle-level credit records source publication only; it is not expanded into a verified real-world identity, sole design/firmware/artwork role, manufacture, event authorization, distribution, or image-reuse credit.

Source

Why It Mattered

It records a distinct, source-published Singapore electronic-artifact trail without merging it into the official DC-SG-1, the HFSDR, the Public Safety Village badge, or the TISC finalist trinket. Keeping the repository and firmware labels side by side makes the uncertainty visible instead of silently assigning a maker archive to either DEF CON Singapore or SINCON.

Hardware

The public code imports Raspberry Pi Pico SDK headers, and its accompanying board-support notes are explicitly RP2040-focused with an rp2040:rp2040:rpipico FQBN example. Its pin map declares UART, two buttons, a WS2812 data line, I2C OLED pins, and analog/digital challenge GPIO. The root tree includes a UF2 and separate SAO EDA/coin-cell-adapter files, but no disclosed main-badge schematic, PCB layout, BOM, exact controller package, board revision, power source, unit count, or physical build photo tied to this archive.

Software & Apps

The archive publishes Arduino/Pico-style source and a UF2 with a serial menu plus LED, OLED, and challenge modules. Its README describes older and newer firmware presentations and a battery-oriented firmware tradeoff affecting ordinary USB challenge access. No tagged production release, source-to-unit map, final build configuration, complete challenge deployment, or evidence that every physical badge used the same firmware is public; the catalogue does not reproduce flashing, serial, or challenge-solving procedures.

Lore

The repository separates art and SAO directories, with Singapore food-themed filenames including chilli crab, kaya, and kueh alongside the SAO EDA files. It does not say which artwork or SAO variation shipped, whether any complete unit was distributed, or why the README spells the artifact Tingkak while the repository title uses Tingkat. Division Zero's post-event community recap confirms its hands-on presence at DEF CON Singapore but does not name this exact archive.

Source-backed hardware metadata

Technical Profile

Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.

Artifact type

  • Electronic badge documented

    The commit-pinned maker README says the archive contains source code and relevant files used in a Div0 Tingkak eBadge, including firmware, art, and SAO files. Its DEF CON Singapore repository title and SINCON 2026 firmware banner conflict, so event association, official status, configuration, and distribution remain separately bounded.

    Signal source

Lifecycle

Add-ons & Upgrades

Operational history

Issues & Camp Impact

firmware and challenge-safety boundary note

The README distinguishes older and newer firmware behavior, while the source includes serial-menu, LED/OLED, and challenge modules. The public archive does not supply a tagged production release, signed binary provenance, source-to-unit mapping, complete intended challenge deployment, support policy, or confirmation that each physical artifact used the same firmware. The catalogue deliberately does not republish flashing, serial-access, flag, or challenge-solving procedures from the archive.

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.

Confidence
commit-pinned README and firmware source
Status
firmware variants documented; production mapping and safe challenge instructions withheld
Timeframe
2026 archive pass
Source note
Div0 Tingkak eBadge commit-pinned README and firmware source.
hardware configuration, power, and distribution scope gap note

The source publishes Pico SDK code, an RP2040-focused support helper, pin declarations, a UF2, and SAO EDA files. It does not publish a main-badge schematic, PCB layout, BOM, exact controller/package, display part, LED population, battery or power path, charging/protection design, pinout/SAO compatibility, assembly/testing evidence, production count, serial/revision inventory, recipient list, price, pickup, mailing terms, or completed delivery. The EDA material is under SAO/adapter paths and is not promoted into an undocumented main-badge hardware release.

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.

Confidence
commit-pinned firmware, support notes, and repository tree
Status
Pico-class source surface published; physical-unit configuration unrecovered
Timeframe
2026 archive pass
Source note
Commit-pinned firmware source, RP2040 support notes, and repository tree.
license, artwork, and image-provenance boundary note

GitHub reports no detected repository license, and the reviewed root contains no visible license file. The archive includes artwork and image assets, but none is paired in the reviewed source trail with a badge-specific reusable license or explicit permission basis, attribution, processing notes, and a source-to-physical-artifact mapping. The spelling/artwork differences and event-label conflict make selecting a factual representative image even less defensible.

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.

Confidence
repository metadata, root tree, and commit-pinned README review
Status
source tree public; reuse license and rights-cleared badge image unrecovered
Timeframe
2026 archive pass
Source note
RestiaAshdoll8 repository metadata, root tree, and commit-pinned README; badge.gallery image policy.
maker-to-event and event-identity conflict note

The public repository is titled DEFCON-SG-2026-Div0-Tingkat-eBadge and its README calls the artifact Div0 Tingkak eBadge, but the pinned firmware's menu banner says SINCON 2026 BADGE. DEF CON's event page and Division Zero's recap establish the conference and Div0 community context without naming this archive. No reviewed primary source reconciles the conflicting labels, names the maker as a DEF CON Singapore badge contributor, or ties the source to a specific SINCON edition.

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.

Confidence
commit-pinned maker archive plus independent official/community event sources
Status
repository labels DEF CON Singapore; firmware banner labels SINCON 2026
Timeframe
2026 post-event archive pass
Source note
RestiaAshdoll8 commit-pinned README and firmware source; Division Zero post-event recap; DEF CON Singapore official event page.
missing rights-cleared image note

No Div0 Tingkat eBadge (DEF CON Singapore 2026) 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 Singapore record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

Confidence
local project policy
Status
needs licensed original replacement
Timeframe
current catalogue build
Source note
badge.gallery image policy and RestiaAshdoll8's commit-pinned Div0 Tingkat archive and firmware sources, Division Zero post-event community recap, and DEF CON Singapore official event context.

Resources

Sources