Issue dossier
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.
A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.
Back to issues index
firmware and challenge-safety boundary · commit-pinned README and firmware source · firmware variants documented; production mapping and safe challenge instructions withheld
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.
- Badge
- Div0 Tingkat eBadge (DEF CON Singapore 2026)
- Category
- firmware and challenge-safety boundary
- Severity
- note
- 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.
commit-pinned board-support notes
The pinned helper notes are explicitly RP2040-focused and show an rp2040:rp2040:rpipico FQBN example. They support a Pico-class firmware target, not a guarantee of the exact physical board, host compatibility, safe flashing, power design, or firmware used by every artifact.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
immutable firmware source
The pinned source imports Raspberry Pi Pico SDK headers and exposes serial-menu, LED, OLED, and challenge modules. Its menu banner says SINCON 2026 BADGE, producing a material identity conflict with the DEF CON Singapore repository title. The source file is not treated as a final-unit firmware map or an instruction set for readers.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
immutable maker documentation
The pinned README calls the artifact Div0 Tingkak eBadge and says the repository contains source code and relevant files used in the badge. It documents old/new firmware wording, a USB/serial challenge context, artwork, source, SAO, and UF2 directories; it does not name the organizer, a distribution channel, final hardware, a completed handoff, or a license grant.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
official community post
Division Zero's own post confirms its SG Community hands-on Kampungs and volunteers at completed DEF CON Singapore 2026. It provides community context only: it does not mention RestiaAshdoll8, Tingkat/Tingkak, the repository, a badge design, issuance, distribution, or image rights.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
official event page
DEF CON's official page supplies the April 28-30, 2026 Marina Bay Sands event context. It does not name this maker archive, certify its event identity, authorize a badge, identify a producer, establish ticket eligibility, or grant image reuse permission.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
public maker source repository
RestiaAshdoll8's public repository title names DEFCON-SG-2026-Div0-Tingkat-eBadge, while the root exposes artwork, code, SAO files, and a UF2. GitHub reports no detected repository license. The archive establishes a maker-published artifact trail, not DEF CON issuance, Division Zero authorization, recipient allocation, production, delivery, or image-reuse permission.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
DEF CON · retrieved 2026-05-15
Official event-context source for the April 28-30, 2026 Singapore conference at Marina Bay Sands. It does not identify this source-conflicted maker archive as an official badge, attendee benefit, village deliverable, or credential.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
Division Zero (Div0) · retrieved 2026-05-15
First-party Division Zero post-event recap confirming its community activity at DEF CON Singapore 2026. It does not name the maker archive, badge, firmware, manufacturer, event authorization, distribution, or image reuse rights.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
RestiaAshdoll8 / GitHub · retrieved 2026-05-15
Commit-pinned primary documentation saying the repository contains source code and relevant files used in the badge. It supports the maker's physical-artifact, firmware-variant, serial-challenge, art, SAO, and UF2 claims, but not a final unit configuration, license, organizer approval, distribution, or handoff claim.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
RestiaAshdoll8 / GitHub · retrieved 2026-05-15
Commit-pinned board-support notes describing an RP2040-focused workflow and an rp2040:rp2040:rpipico example. This is configuration evidence for the public source surface, not a claim that each physical artifact used a Raspberry Pi Pico board or one specific final firmware.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
RestiaAshdoll8 / GitHub · retrieved 2026-05-15
Commit-pinned firmware source for the Raspberry Pi Pico SDK surface, serial menu, LED/OLED modules, pin-map includes, and the SINCON 2026 BADGE menu banner. It creates a direct event-identity conflict with the repository title rather than resolving the badge as a SINCON or DEF CON Singapore official artifact.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)
RestiaAshdoll8 / GitHub · retrieved 2026-05-15
Primary maker-published repository whose title makes the DEF CON Singapore and Div0/Tingkat association. The root tree exposes art, code, SAO files, and a UF2, but GitHub reports no detected repository license and the source does not independently establish a final physical unit, official event role, organizer authorization, production, allocation, delivery, or media-reuse right.
Badge: Div0 Tingkat eBadge (DEF CON Singapore 2026)