DCZia MK9 Badge at DEF CON 34 · United States · 2026

DCZia MK9 Badge (DEF CON 34)

Maker-documented DEF CON 34 macropad badge with build guide and released UF2

DCZia's MK9 is a public-source 3×3 mechanical macropad intended as a neck-wearable DEF CON 34 BadgeLife project. Project documentation specifies nine MX switches, RGB per-key and edge lighting, an accelerometer, two 6-pin SAO connectors, USB-C or three-AAA power, CircuitPython firmware, and QMK-compatible hardware. During the August 6-9 conference the repository gained a purchaser-facing build guide saying the badge is pre-flashed with firmware, six build photos, and an August 4 UF2 commit describing the image as released on badges. This is a maker-documented independent badge release, not an official DEF CON admission credential.

EventDCZia MK9 Badge at DEF CON 34
SeriesDCZia
LocationLas Vegas Convention Center and DEF CON BadgeLife pickup context, Las Vegas, Nevada
CountryUnited States

People

Authors & Credits

badge project and public source-archive publisher

DCZia

The public repository is owned by the `dczia` GitHub account and identifies the MK9 as DCZia's 2026 DEF CON 34 badge; reviewed sources do not name individual designers or assign more specific roles.

Source

Why It Mattered

It adds a current independent DEF CON BadgeLife release with a notably complete public technical record: KiCad design material, BOM and fabrication outputs, CircuitPython source, hardware pinout, a documented user-flashing path, and during-event delivery-facing build documentation. The dossier preserves the distinction between publicly visible source files and an explicit reuse or source license, and between maker-documented release and a verified production count or attendee allocation.

Hardware

The MK9 documentation describes a 3×3 grid of nine standard-MX-footprint mechanical switches with translucent blue keycaps, nine WS2812B LEDs under the switches, six side-firing SK6812 LEDs, an RP2040, a 3-axis accelerometer, two standard 6-pin SAO connectors with I2C and two GPIOs each, USB-C for power/data, a three-AAA battery pack with power switch, and Reset and BOOTSEL buttons. The during-event build guide identifies the shipped switches as Gateron Blues and documents soldering the nine switches and the battery-pack wires, or powering over USB-C instead. The public hardware tree includes KiCad schematic/PCB/project files, a BOM spreadsheet, fabrication-output directory, drill material, and a STEP file. A public launch announcement additionally says a planned add-on board can expose three more keys or an I2C display. The reviewed sources do not establish final production quantity, final shipped battery-holder details, completed add-on distribution, enclosure/accessory scope, or radio capability.

Software & Apps

The badge ships with CircuitPython firmware according to the project documentation. Its public firmware README describes an RP2040 CircuitPython 8+ state machine, a 3×3 `keypad.KeyMatrix`, 15 NeoPixel LEDs on GP22, an MSA301-compatible accelerometer on I2C1, dual SAO I2C/GPIO pinout, a startup diagonal colour wipe, rainbow/breathing/sparkle patterns, accelerometer tilt and shake behavior, per-key ripples, and USB HID numpad output with N-key rollover. An August 4 commit added the UF2 image describing it as released on badges, and the during-event build guide says each badge is pre-flashed with firmware and should be good to go, with a manual BOOTSEL-to-`RPI-RP2` UF2 drag-and-drop reserved for updates or new code. The same week a commit relabelled the README software section as MicroPython while the firmware README itself continues to document CircuitPython, so the record keeps the CircuitPython detail and flags the relabel contradiction rather than resolving it. The project calls the hardware QMK-compatible but says QMK setup instructions will be posted separately, so no final QMK firmware or setup is claimed here.

Lore

The project page presents the MK9 as a badge that can be worn at DEF CON and then used as a desk macropad. A public August 2 announcement identifies it as the 2026 DCZia badge, links the public source tree, and says Friday and Saturday BadgeLife pickup is planned at 12:30. An August 7 build guide, committed during the conference, opens by thanking purchasers of the 2026 DCZia MK9 badge and walks through switch soldering, battery wiring, key functions, and optional re-flashing. At the September 25 recheck the repository still published no production count, recipient list, or distribution report, and DEF CON's official news confirms only that the host conference wrapped on August 10. The MK9 is an independent BadgeLife project, not the official DEF CON 34 Human badge.

Lifecycle

Add-ons & Upgrades

badge expansion publicly documented / announced add-on plan

SAO and planned add-on expansion

The board documents two standard six-pin SAO connectors with I2C and GPIO access. A public launch announcement separately says a planned add-on board can expose three more keys or an I2C display; final add-on distribution remains unconfirmed.

Compatibility: DCZia MK9 Badge (DEF CON 34)

Source
delivery-facing maker documentation maker-documented during the event

Pre-flashed delivery firmware and build guide

The August 7, 2026 build guide, committed during DEF CON 34, addresses purchasers directly, states each badge is pre-flashed with firmware and should be good to go, identifies the shipped Gateron Blue switches, and documents assembly and key functions. It evidences maker-documented delivered units without a production count, recipient ledger, or sale-channel record.

Compatibility: DCZia MK9 Badge (DEF CON 34)

Source
firmware workflow publicly documented

CircuitPython flashing and customization

The project documents BOOTSEL entry, a CircuitPython UF2 copied to `RPI-RP2`, library and Python-file copy steps, and source-level paths for remapping keys, patterns, colours, and states. The August 4 UF2 commit describes its image as released on badges, and the during-event build guide says shipped badges are pre-flashed, making manual flashing an update path rather than a first-use requirement.

Compatibility: DCZia MK9 Badge (DEF CON 34)

Source
input and host interface publicly documented

Mechanical macropad and USB HID

The MK9 is a nine-switch 3×3 mechanical macropad with N-key-rollover USB HID output; the published badge mode maps it as a numpad when connected to a host.

Compatibility: DCZia MK9 Badge (DEF CON 34)

Source
interactive lighting publicly documented

RGB and accelerometer interaction

The public firmware documentation describes nine per-key WS2812B LEDs and six SK6812 edge LEDs, plus tilt-reactive colour changes, shake-to-cycle patterns, and per-key ripple effects using an MSA301-compatible accelerometer.

Compatibility: DCZia MK9 Badge (DEF CON 34)

Source

Operational history

Issues & Camp Impact

QMK and final configuration boundary note

The project says the hardware is QMK-compatible but says QMK setup instructions will be posted separately, and the September 25 recheck found none. The same week the README's software section was relabelled MicroPython while the firmware README continues to document CircuitPython, and the reviewed sources do not establish the exact recipient population or completed three-key/I2C add-on distribution.

The record distinguishes current CircuitPython documentation and documented hardware capability from an asserted shipping QMK configuration or final delivery configuration, and flags the firmware-label contradiction instead of resolving it.

Confidence
public project documentation
Status
partially documented
Timeframe
rechecked 2026-09-25
Source note
DCZia MK9 repository README, firmware README, August 7 relabel commit, and launch announcement.
missing rights-cleared image note

No DCZia MK9 image is published because the public repository, source documentation, and launch announcement do not pair a specific badge image with source URL, reusable license or explicit permission basis, attribution, and processing notes. The August 7 badge_build_photos set is maker-published documentary material under a repository with no detected license, so it stays unpublished.

The United States entry remains source-backed and image-free rather than copying repository files, Reddit media, store media, screenshots, placeholders, or generated approximations.

Confidence
local project policy
Status
needs licensed original replacement
Timeframe
current catalogue build
Source note
badge.gallery image policy and reviewed DCZia MK9 sources.
release and fulfillment boundary note

The August 7 build guide addresses purchasers and says badges ship pre-flashed, and the August 4 UF2 commit describes the image as released on badges, so the release is maker-documented. The reviewed sources still provide no production count, recipient list, sale-channel or giveaway record, or completed distribution report, and the planned add-on board's distribution remains unconfirmed.

The catalogue records a maker-documented independent badge release, not a verified run size, universal attendee issue, or official DEF CON distribution.

Confidence
public project source and during-event build guide
Status
maker-documented release; production count and recipient ledger absent
Timeframe
rechecked 2026-09-25
Source note
DCZia MK9 project repository, August 4 and 7, 2026 commits, and public August 2 announcement, rechecked 2026-09-25.
source license and reuse gap note

DCZia publicly describes the design files and firmware as available and the repository exposes KiCad, BOM, fabrication, CircuitPython, and UF2 material, but the reviewed repository root and the September 25 GitHub metadata recheck still expose no explicit software, hardware, or image-reuse license, release, or tag.

The record may describe the publicly visible technical material but does not treat availability as a license to redistribute source, hardware, firmware, or images.

Confidence
public repository inspection
Status
needs explicit license statement
Timeframe
rechecked 2026-09-25
Source note
dczia/mk9-badge repository root, public file tree, and GitHub metadata endpoint.

Resources

Sources