Summary: Miden is a zk rollup that pushes execution and proving to the client side instead of asking the network to re-run everything. The note matters because the account-plus-note model is a real design branch, and because the project is legible as more than a zkVM memo: there is a node stack, client tooling, and some concrete product surfaces, even if the network is still early and operator-shaped.
What it does:
Lets users and applications execute transactions locally and submit zero-knowledge proofs plus resulting state commitments to the network
Models all entities as accounts with reusable components, storage, vaults, and nonces, making wallets and apps first-class programmable contracts
Uses notes as programmable UTXO-like objects for asset transfer, conditional claims, and multi-step transaction flows
Ships a real operational stack around the protocol, including a node, RPC/gRPC interfaces, Rust and web clients, hosted testnet services, and browser-focused SDKs
Extends the privacy-first execution model into higher-level products such as Guardian-backed private multisig with offline fallback and threshold signing workflows
Key claims:
The official site says Miden combines programmable privacy, quantum resistance, and scalability, with local and private transaction execution as the defining architectural choice
Miden docs say transactions execute on the client and only a cryptographic proof is submitted to the network, giving privacy by default, parallel execution, and lower-fee verification
Protocol docs describe each transaction as a state transition of a single account plus zero or more notes, which removes the need for a global state lock and is central to Miden’s parallel-execution model
Node-operator docs show a concrete network architecture with store, block-producer, network transaction builder, and RPC components, which makes Miden more legible as real rollup infrastructure than as a pure zkVM library
Current GitHub readmes explicitly describe both the client and node as still alpha-stage and note that public-network operation is currently centralized rather than fully decentralized or consensus-driven
Whitepaper: No classic standalone whitepaper or litepaper was found in the official materials reviewed during this pass. The most informative primary sources were the official site, current docs, node and client repositories, and solution docs like private multisig; see ../whitepapers/miden-primary-sources-2026-04-27.md.