The DEF CON Badge Is a Trojan Horse for Open Silicon

DEF CON badges have a familiar life cycle: four days of blinking LEDs, a puzzle, maybe a soldering session, then a drawer. The badge for DEF CON 34 (August 6–9 in Las Vegas) breaks that pattern in a way that matters well beyond the con. Per Wired's reporting, this year's electronic badge is built by Andrew "bunnie" Huang around his Baochip-1x — a custom RISC-V system-on-chip with mostly open RTL — and it doubles as a working security key you're meant to keep using after the lights come down. DEF CON's own teaser calls it a "first-of-its-kind inspectable platform" for regaining "agency and security," which is organizer-speak for the same thing.

Strip away the badge theatrics and the real story is economic: open-source secure silicon just got about 40x cheaper, and DEF CON is the distribution mechanism.

The chip nobody was supposed to afford

Custom silicon on a modern node is normally a seven-figure entry fee, which is why "open-source secure element" has mostly meant FPGAs. Huang's own Precursor proved the model — an inspectable, pocketable security device running the open betrusted-soc design — but it cost $450+ because emulating a CPU on an FPGA is expensive per unit. That price ceiling kept open secure hardware a niche for the seriously paranoid.

Baochip-1x gets to real silicon through a genuinely clever piggyback, detailed on Huang's blog. Crossbar, an RRAM memory company, was taping out a 22nm chip at TSMC and wanted an open-source security enclave; Huang dropped a VexRiscv core into unused floorplan space. The same die serves Crossbar's ARM Cortex-M7 customers and Huang's RISC-V users, so the mask costs — the killer expense — are shared. The result: a production-qualified 22nm SoC whose evaluation board, the Dabao, sells for $9.50 on Crowd Supply, with bare chips headed to mainstream distributors late this year.

The spec sheet reads like a legitimate secure microcontroller, not a badge toy: a 350 MHz VexRiscv core with an MMU, four 700 MHz PicoRV32 I/O coprocessors, 4 MB of on-chip RRAM, 2 MB of SRAM, a ring-oscillator TRNG, accelerators for RSA, ECDSA, X25519, and SHA/Blake, plus secure mesh, glitch sensors, ECC-protected RAM, hardware key slots, and one-way counters. The MMU is the sleeper feature — neither the RP2350 nor NXP's i.MX RT class parts have one — because it lets the OS put each app in its own virtual address space. That's what makes "loadable third-party apps on a security token" a sane sentence.

"Mostly open" is doing honest work

Precision matters here, because "open-source chip" headlines tend to overclaim. The compute logic — CPUs, crypto blocks — is published RTL on GitHub. The AXI bus fabric, USB PHY, and analog blocks (PLL, regulators, I/O pads) remain closed, standard foundry-ecosystem IP that Huang characterizes as "effectively wires": data in matches data out. You should read that as a design argument, not a proof.

The more interesting trust claim isn't the license — it's inspectability. The chip is designed for IRIS, Huang's technique for non-destructively imaging silicon through the package with infrared light, so you can check that the die in your device matches the published design. That's a different answer to the supply-chain question than anyone else gives. Google's OpenTitan is open silicon root-of-trust, but it's aimed at hyperscalers and ships soldered to someone else's board on their terms. Tropic Square's TROPIC01 opens the design for audit but you still trust the fab. Traditional secure elements from NXP or Infineon are NDA'd black boxes with a CC certificate stapled on. Baochip's bet is that verify-what-you-hold beats trust-the-paperwork — a very DEF CON thesis, and one that's now cheap enough to test at scale.

Scale is what the badge provides. DEF CON draws tens of thousands of attendees; handing each a Baochip device plausibly makes this the widest deployment of user-inspectable secure silicon anywhere. It also means thousands of the most adversarial hardware people on Earth will spend a weekend attacking it. That's either the best security validation money can't buy, or an August full of glitching write-ups. Both outcomes are useful.

What you'd actually do with it

If you want the hardware without a Vegas trip, the path is the $9.50 Dabao board (USB-C, 41×21 mm, headers exposing SPI/I2C/UART/PWM). The software stack is Xous, Huang's pure-Rust microkernel, which already runs the Vault app from Precursor — plaintext password management, TOTP, and FIDO2 credentials in one framework. That's the substance behind "doubles as a security key": the badge inherits a working authenticator stack, not a demo.

The trade-offs are real. Xous is not Zephyr, let alone Linux — the ecosystem is small, the toolchain is Rust-first, and you're on an OS with a contributor count you can memorize. Don't expect FIDO Alliance certification, which means enterprise policies that whitelist certified authenticators won't accept it; this is not a YubiKey replacement for your compliance team. It's a single-source part from a single fab, and broad distributor availability is still a "late 2026" promise. And 22nm with RRAM is a fine security node but nobody's building application processors here — this is an MCU-class root of trust, full stop.

Who should care anyway: anyone building devices that currently embed an NDA'd secure element and would rather ship something auditable — hardware wallets, HSM-ish side projects, IoT fleets where you'd like provisioning you control end to end. The Betrusted stack's "self-sealing" model, where no third party provisions your keys, is precisely the property most commercial secure elements refuse to give you.

The verdict

This is the rare badge story that isn't hype. Not because a conference badge does FIDO2 — a Pico can fake that — but because the economics underneath it changed. The piggyback-on-a-commercial-tapeout model took open secure silicon from $450 FPGA boards to a $10 real chip without a foundation-scale budget, and that template is reusable by others. The honest caveats — closed analog blocks, embryonic ecosystem, no certifications — put it years from displacing incumbent secure elements in commercial products. But as the cheapest hardware root of trust you can actually read the source for, it has no competition at all. Order the dev board before the con talks land; after tens of thousands of hackers spend a weekend with one on a lanyard, the interesting bugs — and the interesting projects — will come fast.