Ztarknet: a Starknet L2 for Zcash
A proposal that verifies an L2's state-transition proofs on L1 with a built-in STARK verifier (TZE), keeping privacy on Zcash and moving scalability to the L2.
Ztarknet is a proposal to bring a Starknet-style L2 to Zcash. Following on from the earlier discussion of "STARK verification as a TZE", it adds one narrow extension point to Zcash L1, a built-in STARK proof verifier that uses the TZE mechanism envisioned by ZIP-222. This verifier does just one thing: it takes proof bytes and public inputs and returns true or false inside consensus.
The L2 handles most transactions and app logic and posts the previous state root, the new state root and a proof to Zcash. Full nodes verify the proof with the TZE, and if it is valid, L1 accepts the update. There are no shielded pool changes, no new L1 scripting language and no L1 programmability, and the ZEC value-conservation rules remain the same. The proposed verifier (provisionally STARK_VERIFY_V1) has a fixed algorithm and parameters, a cap on proof size, and no path to issue ZEC.
The L2 executes Cairo programs and produces Circle STARK proofs with the Stwo/Cairo prover. An L2 block proceeds in the order of sequencer execution, proof generation, posting a Zcash L1 transaction, and full-node verification. For deposits, ZEC is locked in a bridge UTXO on L1, and for withdrawals, an L2 exit operation is proven and the same TZE authorizes the release of an L1 output. Fees are paid in ZEC by the settlement transaction, and there is also a policy option to denominate L2 gas in ZEC.
In the risk assessment, the proposal admits that the consensus change is not zero risk, and stresses that it limits the new surface to a single verifier. It says there is no trusted setup, it relies on hash security, and L1 funds are safe even if the L2 halts or is upgraded. On development status, there is a ztarknet.cash PoC site and an L1 testnet explorer, and it can be tried through a local devnet setup, a Zebra fork (verification) and a Madara fork (Cairo execution).
This summary is based on the original; check the original for exact details.