Roadmap

The layers ship in order and the order is fixed. Proving is clean and moving value is shaped like a mixer.

Bundled from the start, the risky one drags the clean one down, and the option to be a pure attestation business disappears if regulation tightens.

Phases

One phase is marked current. The others are ordered rather than scheduled, and the order is the argument.

1. Close the loop

   Now

   The narrowest path that produces a real on-chain attestation from a real Ironwood note. Anything not on that path stays dark and honestly labelled.

   • An attester that signs a proof, so something on Solana can read oneno code
   • Design the attester quorum: size, membership, slashing, and who pays the gasundecided
   • Seed a witness run for a restored phrase, which walks from Ironwood's activation because it carries no birthday to start belowknown cost
   • An attestation account program that checks quorum signaturesno code
   • Run the whole chain end to end with money somebody ownsuntried
   • Wire VERIFY, which reads an attestation nothing has written yetsurface only
   • Wire SEND, which needs spend proving rather than the shielding path, and a directory to address a Zolar user byno code
   • Wire RECEIVE, which needs a program that converts what lands at a Solana account and forwards it shieldedno code

2. Layer 1, PROVE, complete

   Next

   A Solana account that can prove it holds shielded ZEC, with the ZEC never having moved. Open source, explicit about its trust assumptions, and readable in three minutes.

   • Attestation expiry and revocation semantics
   • Anchor status, the TOOLS entry that says what the attester set last posted and how old it is
   • The reader's side: verifying an attestation without connecting a wallet
   • A quorum larger than one, with the slashing that makes signing a lie expensive
   • An external audit of the circuit, funded rather than deferred

3. Layer 2, DISCLOSE

   After Layer 1

   A viewing-key hierarchy and non-interactive payment disclosure. This is the layer that makes the third one shippable at all, because it puts compliance inside the protocol instead of bolting it on afterwards.

   • Scoped viewing key: incoming only, inside a date range, per counterparty
   • Payment disclosure without handing over a viewing key
   • Memo decoder, which reads the encrypted note that rode along with a payment
   • The institutional case: shielded ZEC that survives an audit

4. Layer 3, MOVE

   Gated on an audit and legal advice

   Where value finally moves. Deposits arrive through existing rails, non-custodially: you sign, a solver executes, and ZEC lands directly at your own Zcash address. There is no moment at an address Zolar controls, and holding it briefly would still be custody.

   • Rail integration for deposits: routing, never wrapping
   • Shielded ZEC as collateral, settled back into the pool
   • Not touched before Layer 2 works