Skill Issue Dev | Dax the Dev

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The whole F_RP framework, as written today, is completely broken by Shor's algorithm.

1.

Two of the big three quietly raised egress this quarter while announcing "AI-friendly" pricing on inbound.

1.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; MEV is the second-order tax on public DeFi.

1.

Threw a live-crowd HUD on the pike_pupday site.

Added CompressedTokenHelper.compress(...) and .decompress(...) to the z_trade SDK.

A user reported they couldn't sell tokens that had graduated from the launchpad to the open AMM.

Shipped the macOS sidecar bundling pass for vanta-desktop.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; I've now spelled out the full F_RP framework.

Spent yesterday writing the price-discovery design for vanta-swap.

Shipped the btc-tunnel.sh family for vanta-desktop.

The explorer used to render ZK transfers as "unknown opcode" because the parser was Bitcoin-Core-flavoured and didn't speak our witness-v2.

The explorer was running as two separate Fly machines: one Node API at :3000, one nginx-served SPA at :80.

For users on phones or low-end laptops, generating a Groth16 proof in 1.5s is still 1.5s of dead UI.

Bitcoin uses COINBASE_MATURITY=100 (you can't spend a coinbase output until 100 blocks deep).

import { Aside } from "@/components/mdx"; The x402 spec carries the payment amount as a JSON string, not a number.

Stood up the SDK devnet docs + quickstart guide.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The previous six posts derived F_RP at the level of relations and theorems.

Found a fun chain-init bug.

Subtle wallet UX win: when a user has both a 5 BTC note and three 1.66 BTC notes, the wallet would pick whichever combo summed closest to the target output.

Vite 5 with "type": "module" rejects require("crypto").

Two features in one commit: Auto-shield mining rewards — when a Vanta block matures (30 confirmations), the wallet automatically converts the coinbase into a shielded note.

ZL1 seed-node deploy lands.

Hit 144 tests across the zera-sdk monorepo today.

Wallet v3 has the Groth16 proving core wired in, plus a real data layer (no more localStorage mocks).

import { Aside } from "@/components/mdx"; The single most exciting thing about x402 is the AI-agent UX.

Data dominates.

Pushed the SOLMAL writeup with confirmed proofs-of-concept against the x402 (HTTP 402 micropayment) protocol.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; SPST gave us self-paying private value transfer.

cruiser Phase 30 lands: a master gossip topic that all nodes join on first boot, plus a small set of seed nodes pinned in the binary.

Spent an hour fighting Xcode Cloud CI for the Cruiser+ iOS build.

Three commits in 5 minutes: 4e67803 rename bundle ID to com.cruiserplus.app 1cc74bd rename bundle ID to com.cruisergay.app, fix RGBA icons 2eed5f8 fix Cruiser+ name in Xcode project Lesson: Apple's review process treats cruiserplus and cruisergay very dif…

Cruiser+ is now a real iOS app.

Wrote up the SECURITY.md plus a "current status" analysis.

Shipped @zera-sdk/mcp — a Model Context Protocol server that exposes the SDK's note/commitment/nullifier API as a JSON-RPC tool surface.

The bottom-up SDK API was great for crypto folks but hostile to first-time users.

The wallet needs the Merkle root to generate proofs, and ideally the full tree to scan for owned notes.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; Ring signatures and TAB hide the submitter on-chain.

The cross-platform location story before this was: macOS used CoreLocation, Windows used IP geolocation, Linux used "open a dialog and let the user type their lat/long".

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; SPST hides what value moved.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The first time I sat down to deploy a Groth16 circuit in anger, I spent more time on the ceremony — the multi-party computation that produces the per-circuit proving and verification…

Simon's been hammering on this framing for two years and it's finally landed: any agent that has private data + untrusted input + ability to exfiltrate is, by construction, a prompt-injection victim waiting to happen.

Cloudflare Pages build kept failing with Type 'HospitalResult' is not exported.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; The most-asked engineering question on every ZK SDK call I take is some shape of: "Why are you using snarkjs in the browser when you have a Rust core?"

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote } from "@/components/mdx"; For a decade the dominant question in proof-system engineering was which curve.

import { Mermaid, Sandbox, TradeoffTable, Aside, Quote, RustPlayground } from "@/components/mdx"; A recursive SNARK is a proof that proves another proof was checked correctly.

import { Mermaid, TradeoffTable, Aside, Quote } from "@/components/mdx"; SPST gave us private value transfer with self-paying fees on a smart-contract chain.

import { Mermaid, RustPlayground, TradeoffTable, Aside, Quote } from "@/components/mdx"; When Zcash open-sourced Halo2 in 2020, it was a research artefact attached to a single deployment target — Zcash's Orchard pool — and a single arithmetisation choice —