Issue dossier
A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.
The entry stays image-free rather than publishing lanyard art, social-media photos, generated art, placeholders, or unlicensed images.
Evidence
Official homepage documenting September 23-25, 2026 dates and Royce Hotel & Casino in Clark for ROOTCON 20; the September 26 through 30, 2026 rechecks after the elapsed dates still show the pre-event banner, while the post-event material appeared on the media server instead.
General ROOTCON badge taxonomy source for electronic, non-electronic, black, and electi badge definitions applied to the RC20 record.
Official RC20 guide documenting September 23-25, 2026 dates, Royce Hotel & Casino in Clark, first-come electronic badge distribution, and Type-B non-electronic fallback; unchanged in the September 30, 2026 media-server recheck.
1,595,248-byte ESP32-S3 application image (SHA-256 3def651c51f2131cd4399c17375772f16a4edf415874d8794039a199c0559a5a) uploaded September 28, 2026. Its app descriptor names project rc20, build 5b987d4-dirty, ESP-IDF 5.5.5, and a September 6, 2026 build date; its strings identify the ROOTCON 20 Badge, a Meshtastic stack, SX1262 LoRa, SSD1315 128x64 display, four WS2812B LEDs, a PH_433 region lock, and Tetris and Breakout. No source, licence, or flashing notes are published.
Official twentieth-edition magazine PDF in the September 28 media drop. Its badges section traces ROOTCON badges from passes to hackable hardware, credits Electronic Cats and AND!XOR for earlier badge work, and names Mr. Blinky Bling as the hands behind the ROOTCON 20 badge under a Before the Reveal heading; it does not describe the final hardware.
Official ROOTCON media-server directory for the edition. The September 30, 2026 recheck found Artwork, Badge, Speakers, and Talks folders added on September 28, 2026, three days after the event, next to the September 16 pre-event Downloads folder.
Official TRACK01 and TRACK02 tar archives of ROOTCON 20 presentation decks uploaded September 28, 2026, used as post-event evidence that the scheduled conference tracks took place; they contain no badge talk.
Official ROOTCON Black Badge policy source for contest/community-award context and free-pass perk framing.
Source trail
Primary pre-event source for September 23-25, 2026 dates, Royce Hotel & Casino in Clark, first-come electronic badge distribution, and Type-B non-electronic fallback. The September 30 media-server recheck found the September 16 guide unchanged alongside the sponsors primer.
Official event source for September 23-25, 2026 dates and Royce Hotel & Casino in Clark venue. September 26 through 30 rechecks after the elapsed dates still found the banner announcing the dates and no homepage wrap-up or archive entry for ROOTCON 20; post-event evidence comes from the official media server instead.
Official policy source for ROOTCON Black Badge contest and community-award context.
Primary badge-taxonomy source for electronic, non-electronic, black, and electi badge definitions used to frame the RC20 record.
Primary official post-event source: Artwork, Badge, Speakers, and Talks folders dated September 28, 2026, including track slide archives and speaker bios, establish that the September 23-25 edition was held. The drop does not state electronic-badge counts, Type-B allocation, or who received which badge.
Official commemorative magazine whose ROOTCON 20 Badge / Before the Reveal page credits Mr. Blinky Bling with the twentieth-anniversary badge. The PDF was produced on August 15, 2026, before the event, so it is a credit source rather than a distribution record.
Primary technical source, inspected locally from the official binary: ESP32-S3 image header, rc20 app descriptor built September 6, 2026 with ESP-IDF 5.5.5 from PlatformIO environment rc20-human-fw, ROOTCON 20 Badge banner strings, Meshtastic mesh modules, SX1262 radio driver, SSD1315 128x64 display, 4x WS2812B GPIO37, ROOTCON 20 region lock forcing PH_433, NimBLE, libpax counting, and Tetris and Breakout high-score files. String evidence describes the compiled build only; it does not prove every feature was enabled on shipped boards.