1 Signature scheme 0/10, weighted 30%
Band 0: Classical signatures only on mainnet, with nothing post-quantum protecting live funds. Short-lived devnets and one-off benchmarks sit here: they demonstrate research rather than something a user can hold keys on.
Zcash spend authorisation uses RedDSA and RedPallas, both elliptic-curve signature schemes, and the Halo 2 proving system rests on the same curve mathematics. Nothing post-quantum authorises spends on mainnet today.
source
2 Deployment stage 5/10, weighted 25%
Band 5: Tier 3: Committed.
Tier 3: Committed. ZIP 2005 is live on mainnet rather than pending: it activated with the NU6.3 network upgrade at block 3,428,143, creating the Ironwood pool whose notes are built to stay recoverable through a later post-quantum transition. That is a recovery path and not a migration, and no post-quantum signature authorises spends on mainnet.
source
3 NIST alignment 5/10, weighted 15%
Band 3 to 5: NIST schemes are referenced as candidates without a committed selection, or the work is bespoke research.
Zcash has committed to a direction and to a recovery mechanism, but we could not confirm a specific NIST-standardised signature scheme selected for the full transition. The recoverability work in ZIP 2005 is a bespoke construction rather than an adoption of FIPS 204 or FIPS 205.
source
Placement in the band The top of the band rather than a 3 or a 4: Zcash has committed to a direction and to a specific recovery mechanism, which is more than referencing candidates. It cannot reach 6 because ZIP 2005 is a bespoke construction and no NIST-standardised signature scheme has been confirmed for the full transition.
4 Migration path 8/10, weighted 15%
Band 6 to 8: A credible published plan exists with a mechanism identified, but key parts are unbuilt or undated.
The strongest sequencing logic in the committed group. Rather than waiting for a full migration, Zcash shipped a recovery path first, so that funds held in the Ironwood pool remain recoverable into a future post-quantum protocol even if the shielded protocols had to be disabled in an emergency. Solving the rescue case before the upgrade case is the right order. The limit is that it covers only what is moved: ZIP 2005 states that funds still in the Sprout, Sapling or Orchard pools would be inaccessible once those protocols were disabled.
source
Placement in the band The top of the band: shipping a recovery path before the migration itself solves the rescue case first, which is the right order. It is not a 9 because moving into Ironwood buys recoverability rather than post-quantum spend authorisation, which no holder can obtain today, and the full transition remains undesigned.
5 Exposure 5/10, weighted 10%
Band 3 to 5: Most active accounts have revealed a public key, or the chain has no live supply to assess.
Shielded Zcash is a genuine exception in this index. Funds held in shielded pools do not publish a spending public key on-chain in the way a transparent account does, which materially limits what an attacker can harvest today. Transparent addresses behave like Bitcoin's and are exposed on spend.
source
Placement in the band The top of the band rather than a 3 or a 4: shielded funds genuinely do not publish a spending key on-chain, which no other chain in this index can say. It cannot reach 6 because transparent addresses behave like Bitcoin's and are exposed on spend.
6 Verification 8/10, weighted 5%
Band 6 to 8: Open source with public review or a named third-party audit of the relevant component.
Zcash's protocol is specified in a public document, changes go through numbered public ZIPs, the cryptography is peer-reviewed and the implementation is open source. The quantum recoverability work is identified by a specific ZIP number rather than described in a blog post.
source
Placement in the band The top of the band: a public specification, numbered ZIPs, peer-reviewed cryptography and open source, with the quantum work identified by ZIP number rather than described in a blog post. It stops short of 9 because the recoverability construction, now activated at NU6.3, carries no published independent audit.