1 Signature scheme 6/10, weighted 30%
Band 4 to 6: A post-quantum signature is available on mainnet only as an opt-in, application-level or experimental primitive.
SPHINCS+ is available on mainnet as an audited, production-ready lock script supporting twelve parameter sets, and a desktop wallet ships with it. It is opt-in rather than the default, and normal CKB addresses remain secp256k1.
source
Placement in the band The top of the band rather than a 4 or a 5: the lock script is audited, production-ready and shipped in a desktop wallet, which is well past experimental. It cannot reach 7 because it is opt-in at the application layer and normal CKB addresses remain secp256k1.
2 Deployment stage 8/10, weighted 25%
Band 8: Tier 2: Shipping.
Tier 2: Shipping. A post-quantum signature scheme protects real funds on CKB mainnet today and users can migrate to it now, which is the defining test for this tier.
source
3 NIST alignment 10/10, weighted 15%
Band 9 to 10: The scheme in use is covered by a final NIST standard (FIPS 204, FIPS 205, or SP 800-208).
SPHINCS+ was standardised by NIST as SLH-DSA in FIPS 205 in August 2024. CKB is using a finalised standard rather than a candidate, which of the chains in this index only NEAR also does for a scheme live on mainnet.
source
Placement in the band A 10 rather than a 9: SLH-DSA is final in FIPS 205 and the scheme is live on mainnet, so this is a finalised standard actually in use rather than one named for future adoption.
4 Migration path 9/10, weighted 15%
Band 9 to 10: Holders can migrate today, or the published plan is dated, specific, and executable under the chain’s existing governance.
CKB's migration is among the cleanest in the index. A user creates an address referencing the new lock script's code hash and transfers assets to it. No hard fork is required, the network does not need to coordinate, old addresses keep working, and the upgrade can proceed gradually and permissionlessly.
source
Placement in the band Not a 10: holders can migrate today with no fork and no coordination, which is what puts this at the top of the band, but migration is manual and per-holder rather than something the protocol performs, and most supply has not moved.
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.
CKB uses a cell model in which addresses commit to a lock script hash, so a public key is not revealed until an output is spent. That limits exposure compared with account-model chains where the address is the public key, but the majority of supply still sits under secp256k1 locks and every spent cell has revealed its key.
source
Placement in the band The top of the band rather than a 3 or a 4: the cell model reveals a key only when an output is spent, so never-spent holdings stay unharvestable. It cannot reach 6 because most supply still sits under secp256k1 locks and every spent cell has published its key.
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.
The quantum-resistant lock script is open source and completed a security audit by ScaleBit. The claim is checkable on-chain and in the public repository rather than resting on marketing.
source
Placement in the band The top of the band: the lock script completed a named third-party audit by ScaleBit, which is what the upper half of this band asks for. It stops short of 9 because the audit covers an opt-in script rather than a protocol-wide deployment.