Miden before partner mainnet: proofs on your device, rules inside the asset

ZEC is a $20.2B asset rn. Canton, the privacy network built for institutions, is $4.0B.

The open networks building programmable privacy (Midnight, ZAMA, Aleo, Aztec, Arcium) are worth $940M combined. Under 5% of ZEC.

The market pays for private money, and for privacy institutions can sign off on. It hasn't priced private apps on open chains yet.

Miden's pitch sits right in that gap: an open chain, private by default, with compliance built into the assets.

Tomorrow it goes live on (partner) mainnet.

7 years of R&D, first at Meta and then at Polygon. Spun out of Polygon in April 2025 with $25M from a16z, 1kx and Hack VC. Still no token.

Definitely one of the bigger privacy launches this year.

Why?

Because it changes where your transaction runs.

On every chain you use today, you send a transaction and every node re-executes it to check it. That's why everything onchain is public. Nodes can't verify what they can't see.

Miden flips the order.

Your device executes the transaction and generates a STARK proof of it. The network only verifies the proof and stores a commitment.

Execution and state move to the user. The team calls it an "edge blockchain", and three key things come with that approach:

What actually runs on your phone?

The Miden VM. A Turing-complete virtual machine built for proving: devs write contracts in Rust, they compile down to Miden Assembly, and every run comes out with a STARK proof attached.

Proving instead of re-executing changes the economics too:

How does a transfer work?

Every account owns its code, storage and assets, and only it can change its own state.

Accounts talk through notes. A note is assets plus a small script that says who can claim it and when.

Alice pays Bob 100 USDCx: she creates a note in her own transaction, Bob claims it later in his. Two separate proofs. Bob doesn't need to be online, and the public chain only sees hashes.

And sure, DeFi needs shared state. An AMM can't live on your phone.

For that Miden has network accounts: public accounts the operator executes, which consume the notes users send them. That's how @port0_sh runs its permissionless AMM, while @luminaengine is building a dark pool orderbook.

So far that's payments and DeFi.

The harder question: how does an issuer enforce rules on balances it can't see?

Miden's answer is what puts it in that gap: the issuer's rules travel with the asset.

Every transfer runs them inside your proof, on your device. The code is public, the execution stays private, and the issuer doesn't even need to be online.

@schmiddominik1 from Miden tested it on mainnet on Thursday with USDCx and @0xPredicate: a transfer from a blocklisted account couldn't even finish its proof.

That's how institutions get private stablecoins that still enforce a blocklist.

Okay cool.

But what actually goes live tmrw?

The chain is already producing blocks: 290k+ at ~3s, with all 3/3 validators healthy.

What's not there yet?

At launch you're private from other users, not from the operators.

Validators decrypt and re-execute every transaction as a safety net while the proof system matures. Guardian sees your account state, but can't move your funds.

There's also only one block producer on day one, run by Miden. Decentralization comes in phases.

Fair enough for a gated partner mainnet.

And the token?

There is none. Miden told the SEC's Crypto Task Force in June it chose not to launch one "at the current stage of network development".

The only hint on record is Polygon's line from April 2025: ~10% of native tokens to POL stakers. No ticker, supply or date since.

But if @sandeepnailwal's line holds up ("If ZEC is the private bitcoin, then Miden is the private Ethereum"), this could be pretty big.

Watching closely.

NFA ofc. DYOR.