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.
Bittensor wallets are built from sr25519 key pairs, the Substrate default, used for both the coldkey that holds TAO and the hotkey that mines and validates. sr25519 is a Schnorr signature over Curve25519 and is broken by Shor's algorithm. Nothing post-quantum protects funds or registrations on the network.
source
2 Deployment stage 2/10, weighted 25%
Band 2: Tier 4: Debating.
Tier 4: Debating. Post-quantum work on Bittensor's own account signatures is documented in the chain's own repository. Pull request 3259, merged on 18 October 2026 into the codex/hashed-accounts integration branch of RaoFoundation/subtensor, adds fixed-key and rotating ML-DSA-65 wallets alongside the existing sr25519 accounts. Its description calls it a disabled protocol candidate, not production activation, with the switches defaulting to off, and says reference measurements and independent cryptographic review are required before activation. It is not on the main branch, and no activation date, agreed mainnet scheme or migration plan for existing holders has been published, so it goes no further than Tier 4.
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.
The one post-quantum scheme on the table for Bittensor's signatures is ML-DSA-65, a parameter set of the final FIPS 204 standard, implemented in the chain's own repository as a disabled candidate on an integration branch.
source
Placement in the band The top of the band rather than a 3 or a 4: the candidate is a single, specific parameter set of a final standard, already written for this chain's accounts. It cannot reach 6 because the code calls itself a candidate rather than a selection, and nothing has been proposed for activation on mainnet.
4 Migration path 2/10, weighted 15%
Band 0 to 2: No agreed migration path, or the proposals on the table would strand or freeze holder funds.
No migration plan for existing holders has been published. The ML-DSA-65 candidate creates new account records in separate storage rather than migrating existing ones, and does not describe how an sr25519 account would move to it. The one genuine mitigating fact is architectural: a Substrate runtime upgrade can change a signature scheme without a contentious hard fork, so the governance obstacle that dominates Bitcoin's migration problem is largely absent here.
source
Placement in the band A 2 rather than a 0, because the upgrade path a Substrate runtime provides is a real and unusual advantage that a chain with no such mechanism does not have. It goes no higher because the only post-quantum code is a disabled candidate that offers new accounts, not a route for the funds already on the chain.
5 Exposure 2/10, weighted 10%
Band 0 to 2: Public keys are exposed for effectively all accounts, or a large, measured share of total supply sits in exposed addresses.
A Substrate account address is an SS58 encoding of the public key itself rather than a hash of it, so the key protecting a Bittensor account is readable by anyone who knows the address, before that account has ever signed. Validator and miner hotkeys are registered on-chain by construction and are therefore public for the entire active set.
source
Placement in the band At the top of the band rather than lower: the address format publishes the key, so every account of any kind is exposed from creation, which meets the band on its structural limb, but no measured share of at-risk supply has been published for this chain to place it nearer the floor.
6 Verification 3/10, weighted 5%
Band 3 to 5: A post-quantum component exists, on mainnet, on a persistent testnet or as a merged implementation, but is unreviewed.
A post-quantum component exists as merged, open source code: the ML-DSA-65 wallet implementation merged into an integration branch of the official subtensor repository on 18 October 2026. Its only reviews are automated ones; a requested human review was still pending at merge, and the description itself says independent cryptographic review is still required. It protects no funds.
source
Placement in the band The floor of the band rather than a 4: the code is merged, but on an integration branch rather than the main line, and nobody outside the authoring team has reviewed it. It is not a 2 because a real, open source implementation of the chain's replacement signatures exists.