Skill Issue Dev | Dax the Dev

This blog has accumulated, at this point, several long-form posts covering individual chapters of how I got from a Navy reactor compartment to running Zera Labs.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; In the previous post I argued that on account-model chains the fee paradox is what forces relayer dependence.

Today I learned Postgres ships with a first-class BIT(n) and BIT VARYING(n) type — not a bytea, not an int you bit-twiddle yourself.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote } from "@/components/mdx"; There are two ways to write a zero-knowledge circuit.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote } from "@/components/mdx"; The first time I watched a Groth16 proof finish inside a Chrome tab — Poseidon-128, two-input Merkle membership, a couple of range checks — the spinner ran for 11.4 seconds.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote, RustPlayground } from "@/components/mdx"; The cheapest piece of state in a privacy pool — and the most contested one — is the commitment tree.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The first time I read the Tornado Cash whitepaper I missed the fee paragraph.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; I've been writing a paper.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote, RustPlayground } from "@/components/mdx"; A SHA-256 of "abc" inside a SNARK takes about 24,000 R1CS constraints.

The worst kind of bug in DeFi is the one where users can deposit but can't withdraw.

The advice founders get most often, once you cross the line from "engineer with a side project" to "engineer with a company," is: stop coding.

The 2026-04-17 commit message — wallet-ui: merge privacy view into unified dashboard + rescan endpoint — is one of the smallest functional commits in the Vanta repo and one of the most consequential UX decisions.

You can read this post as the technical version of Why I started Zera Labs.

The 2026-04-17 commit message — planning: price-discovery design for private atomic swaps — is one of the more interesting things in the Vanta repo, because it isn't code.

This is a follow-up to Vanta: a Bitcoin fork with ZK at consensus and a sibling to Nullifiers without the witchcraft.

In the original Vanta L1 post I wrote: The ZK layer is in the vanta/ subtree, written in Rust against RISC Zero's zkVM, running entirely outside the C++ core.

The atomic-swap CLI I wrote about needs two RPC endpoints: one for the VANTA chain (easy — there's a vantad running on the desktop dev box) and one for the BTC chain (less easy — I'm not running a full Bitcoin Core node on every laptop I develop on).

There is a very specific feeling you only get when a small piece of hardware sitting on your desk solves a block on a chain you wrote.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote, RustPlayground } from "@/components/mdx"; Every production ZK system you can name in 2026 — Zcash Sapling, Aleo, Mina, Filecoin's PoRep, Solana's alt_bn128_* syscalls, the Ethereum precompile at 0x06…

There is a phrase we keep using internally at Zera Labs: privacy's broadband moment.

A privacy chain in 2026 cannot ship as a one-page marketing site with a PDF link.

import { Mermaid, RustPlayground, TradeoffTable, Aside } from "@/components/mdx"; The companion to Private atomic swaps and the price-discovery problem is a piece of code, not a planning document.

The Vanta Desktop walkthrough is the architectural story: a Tauri 2.x wallet that ships its own full node, supervises three sidecar binaries, and exposes everything through #[tauri::command] IPC.

The user-facing pitch for Vanta is short: open the wallet, click send, watch a private transaction settle on a chain you can verify yourself.

The 2026-04-13 commit d3d532cc deploy: vanta v1 LIVE on Latitude is the moment Vanta moved from "regtest on a Mac mini under my desk" to "mainnet on a real-world internet host."

The first wallet I shipped for Vanta wasn't a desktop app.

The 2026-04-13 commit eff33f7a chain+build: mined genesis nonce + libconsensus links FFI and the 2026-04-23 commit 0edddc82 build: darwin frameworks, wallet-ui node types, v2 test renames are the bookends of the macOS build story.

A 1-minute-block Bitcoin Core fork with ZK proofs at consensus has a problem the README doesn't volunteer: you need the validator to check the proofs, but you don't want to write the proof system in C++.

import { Mermaid, Sandbox, TradeoffTable, Quote, Aside } from "@/components/mdx"; The L2 sidecar I wrote about previously has four jobs: watch L1, serve a REST API, snapshot state, and gossip with peers.

There is a class of bug in a Bitcoin-style chain that you only ever see when the mempool is non-trivially full.

I wrote about mining VANTA with a Bitaxe BM1368 — the hardware, the watts, the difficulty math, why solo mining a privacy fork actually pays off where solo mining Bitcoin in 2026 doesn't.

When you're forking Bitcoin Core, you can't get away with not having a block explorer.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote, RustPlayground } from "@/components/mdx"; A confidential transaction has to prove one annoying little thing: that the hidden amount is non-negative and bounded.

When we scaffolded the SDK monorepo in early March, the first non-obvious decision was including an MCP server in the box.

The zeralabs.org front page lists three "Cryptographic Innovations": Pedersen Commitments, Zero-Knowledge Proofs, Nullifier Generation.

The ZERA Labs site lists three "Cryptographic Innovations" on the front page: Pedersen Commitments, Zero-Knowledge Proofs, Nullifier Generation.

"add comprehensive test suite for sdk (144 tests)" That's 80927, 2026-03-31.

Most wallet posts start with the cryptography.

The Zera SDK is the engine.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The x402 protocol has a fee model where the facilitator pays gas.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The trust split in x402 is unusual.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The cleanest vulnerability in the x402 protocol — also the one that's easiest to fix and the one most likely to bite production deployments.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; Coinbase shipped x402 — a micropayment protocol that piggybacks on HTTP 402 (Payment Required) — in late 2025.

"init monorepo structure" That commit message — af8cc28, 2026-03-05T21:54:29Z — is when the Zera SDK began.

The dating app market in 2026 is two things: dystopian centralized platforms (Match Group's stable: Tinder, Hinge, OkCupid, etc.) and crypto-bro-coded alternatives that promise decentralization but ship a Mongo cluster behind the API.

This is the post I keep wanting to skip.

A week after the AMM shipped I had two open feature requests from people who were actually using it: "I want to bet on whether $TOKEN graduates by Friday."

The OG image is the thing that decides whether your link gets clicked on Twitter, Discord, or Telegram.

The unspoken rule of demo apps is that they're built for laptops.

The whole zera_med_demo repo exists because someone asked me, "if your privacy chain is real, prove it works for something other than crypto bros."