Hardy Index Quantum readiness, rated and tracked

Chain profile

Bittensor

TAO Debating

A Substrate chain signing with sr25519 whose own repository now carries a disabled ML-DSA-65 wallet implementation, a candidate with no activation date, no agreed scheme and no route for existing holders.

Is Bittensor quantum-safe?

No. Bittensor runs on Substrate, and its coldkeys and hotkeys are sr25519 key pairs, a Schnorr signature over the Ristretto group on Curve25519. Shor's algorithm breaks it in the same way it breaks the ECDSA and Ed25519 used elsewhere, so every TAO balance and every validator and miner registration on the network is protected by cryptography with no defence against a sufficiently large quantum computer. Post-quantum work has started: in October 2026 an ML-DSA-65 wallet implementation was merged into an integration branch of the official subtensor repository. Its own description calls it a disabled protocol candidate, not production activation, and says reference measurements and independent cryptographic review are required before it can be switched on. It is not on the main branch, it protects no funds, and no activation date or plan for existing accounts has been published. Because the chain is Substrate-based, switching a signature scheme on is a runtime upgrade rather than a multi-year fork negotiation, which is a materially easier position than Bitcoin's. Capacity to act is not action, and the readiness spine measures what has been done.

Where we are making a judgement call The post-quantum code this rating rests on is a disabled candidate on an integration branch, written and merged by the same maintainer, with automated reviews only. Its own description is partly out of date: an automated review on the pull request notes that the implementation uses one shared hashed-accounts switch and finite reference weights rather than the two switches and blocking weights the description lists. Either way it is off by default and protects no funds. Tier 4 records that the work is documented by people with authority over the chain, and nothing more; it is not a judgement on Bittensor's engineering or on the subnet economy it runs.

At a glance

On mainnet today

sr25519 (Schnorr over Curve25519) for coldkeys and hotkeys, the Substrate default

Post-quantum scheme

None deployed. ML-DSA-65 exists as a disabled candidate on an integration branch of the subtensor repository.

NIST standard

None adopted. The candidate, ML-DSA-65, is a parameter set of FIPS 204.

Readiness tier

Tier 4: Debating. Post-quantum work on the chain’s own signatures is documented by people with authority over it, in a formal improvement proposal or a public research programme, but no scheme is agreed and no timeline is published.

Cryptography in use

A role not listed is not evidenced either way. Every scheme, and which other chains share it, is in the cryptography registry.

Score breakdown

Each dimension scored 0 to 10. The weight beside it is its share of the total score.
Show the weighted arithmetic and the sourced note for each dimension
Bittensor Hardy Score by dimension, with weights and weighted contributions
No. Dimension Score Weight Contribution
1 Signature scheme 0 30% 0.0
2 Deployment stage 2 25% 5.0
3 NIST alignment 5 15% 7.5
4 Migration path 2 15% 3.0
5 Exposure 2 10% 2.0
6 Verification 3 5% 1.5
Hardy Score 19.0

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.

The deployment dimension is not a separate judgement. It is Tier 4 expressed as a number. See the tier mapping.

How it compares

All 80 rated chains on the 0 to 100 scale. Bittensor is marked. Select any point to open that profile.
Hyperliquid, Hardy Score 5.5 Cronos, Hardy Score 7.0 MemeCore, Hardy Score 7.0 Beldex, Hardy Score 7.5 Ozone Chain, Hardy Score 7.5 0G, Hardy Score 8.5 AIOZ Network, Hardy Score 8.5 Akash Network, Hardy Score 8.5 Arweave, Hardy Score 8.5 Avalanche, Hardy Score 8.5 Bitcoin SV, Hardy Score 8.5 Celestia, Hardy Score 8.5 Chiliz Chain, Hardy Score 8.5 Conflux, Hardy Score 8.5 dYdX Chain, Hardy Score 8.5 eCash, Hardy Score 8.5 Filecoin, Hardy Score 8.5 GateChain, Hardy Score 8.5 Gnosis Chain, Hardy Score 8.5 Injective, Hardy Score 8.5 KCC (KuCoin Community Chain), Hardy Score 8.5 Kite, Hardy Score 8.5 Mina Protocol, Hardy Score 8.5 MultiversX, Hardy Score 8.5 Polygon PoS, Hardy Score 8.5 Provenance Blockchain, Hardy Score 8.5 Theta Network, Hardy Score 8.5 THORChain, Hardy Score 8.5 VeChain, Hardy Score 8.5 WEMIX, Hardy Score 8.5 Whitechain, Hardy Score 8.5 Dogecoin, Hardy Score 9.0 Kaia, Hardy Score 10.0 Vaulta, Hardy Score 10.0 Decred, Hardy Score 10.5 IOTA, Hardy Score 10.5 Litecoin, Hardy Score 10.5 Midnight, Hardy Score 10.5 Qtum, Hardy Score 10.5 TON, Hardy Score 11.0 Ethereum Classic, Hardy Score 13.0 Flare, Hardy Score 13.0 Internet Computer, Hardy Score 13.0 Bitcoin, Hardy Score 14.5 Sonic, Hardy Score 14.5 Terra Classic, Hardy Score 14.5 Dash, Hardy Score 16.5 Neo, Hardy Score 17.0 Monero, Hardy Score 17.5 Bittensor, Hardy Score 19.0 BNB Chain, Hardy Score 20.0 Monad, Hardy Score 20.0 XDC Network, Hardy Score 20.0 Kaspa, Hardy Score 20.5 Cosmos Hub, Hardy Score 23.5 Sei, Hardy Score 24.5 Cardano, Hardy Score 34.0 Tron, Hardy Score 34.5 Polkadot, Hardy Score 36.5 Tezos, Hardy Score 37.5 Zcash, Hardy Score 38.0 Ethereum, Hardy Score 38.5 Aptos, Hardy Score 39.0 Stellar, Hardy Score 39.0 Hedera, Hardy Score 39.5 Sui, Hardy Score 42.0 XRP Ledger, Hardy Score 43.0 Solana, Hardy Score 53.0 Bitcoin Cash, Hardy Score 62.0 Nexus, Hardy Score 73.0 Nervos CKB, Hardy Score 76.0 Algorand, Hardy Score 77.0 NEAR Protocol, Hardy Score 80.0 Abelian, Hardy Score 84.0 QoreChain, Hardy Score 84.5 Mochimo, Hardy Score 89.0 Tidecoin, Hardy Score 89.0 Quantum Resistant Ledger, Hardy Score 92.5 Dilithion, Hardy Score 93.5 Quantus Network, Hardy Score 94.0 Bittensor 19.0

Nearest chains in the ranking

The 9 chains Bittensor sits among, out of 80 rated. The last column is the gap in Hardy points from Bittensor.

Chains ranked immediately around Bittensor, with tier, Hardy Score and the gap to Bittensor
Rank Chain Tier Hardy vs TAO
27 Kaspa 4: Debating 20.5 +1.5
28 BNB Chain 4: Debating 20.0 +1.0
29 Monad 4: Debating 20.0 +1.0
30 XDC Network 4: Debating 20.0 +1.0
31 Bittensor this chain 4: Debating 19.0
32 Monero 4: Debating 17.5 -1.5
33 Neo 4: Debating 17.0 -2.0
34 Dash 5: Exposed 16.5 -2.5
35 Bitcoin 4: Debating 14.5 -4.5

Roadmap

  1. 18 October 2026 proposed

    ML-DSA-65 wallet support merged into the codex/hashed-accounts integration branch of subtensor as a disabled protocol candidate, with independent cryptographic review required before activation. source

  2. No published date proposed

    Activation on mainnet and a route for existing sr25519 accounts. Neither has been scheduled. source

If holders never migrate

No stated policy

No post-quantum migration plan or policy on unmigrated coldkeys has been published. The ML-DSA-65 candidate adds new account records and does not say how existing accounts would move.

As of 4 November 2026. Published beside the score, not in it. Every chain's stance is compared on the commitments page.

Exposure

Exposure measures how much of the chain's value already sits behind a public key that an attacker can record today and break later. This is the part of the threat that a future upgrade cannot undo.

Bittensor's exposure is total and structural, and it is worse than the Ethereum-style chains with hashed addresses. A Substrate address is an SS58 encoding of the public key, not a hash of it, so knowing an address means knowing the key. There is no equivalent of the never-spent Bitcoin address whose key stays hidden until first use: on this chain every account publishes its key at creation, and an adversary harvesting keys today needs only the address book. The active set is more exposed still, because validator and miner hotkeys must be registered on-chain to participate at all. Nobody has published a measurement of at-risk supply for Bittensor, and given the address format the honest answer is that the share is effectively all of it.

What this rating means for you

If you hold Bittensor

Bittensor has acknowledged the threat without agreeing a plan, so nothing is going to change for holders in the near term. That makes address hygiene the part worth attending to.

Editorial guidance from the Hardy Index.

From the newsroom

What we have published about this chain

Embed this rating

Paste this anywhere to show Bittensor's current rating. It renders live from the index, so it updates when the rating does, and the review date is written into the image. There is nothing to sign up for and nothing to pay.

<a href="https://hardyindex.com/chains/bittensor"><img src="https://hardyindex.com/badge/bittensor.svg" width="260" height="76" alt="Quantum readiness rated by the Hardy Index"></a>

The image is /badge/bittensor.svg. It is a plain SVG with no script and no tracking, it sets no cookie, and it records nothing about whoever loads it.

Questions

Is Bittensor quantum-safe?

No. Bittensor coldkeys and hotkeys are sr25519 key pairs, a Schnorr signature over Curve25519, which Shor's algorithm breaks. An ML-DSA-65 wallet implementation was merged into an integration branch of the subtensor repository in October 2026, but it is a disabled candidate with no activation date, and it protects no funds.

Does Polkadot's post-quantum work cover Bittensor?

Not automatically. Bittensor is built on Substrate, the same framework Polkadot uses, and Polkadot has an active RFC discussing post-quantum primitives and a migration mechanism. That is Polkadot's document, governing Polkadot. Bittensor has started its own work separately, with an ML-DSA-65 candidate in its own repository. This index scores each chain on what it has done, not on what its technology stack makes possible.

Why is Bittensor's exposure worse than Ethereum's?

Because of the address format. An Ethereum address is a hash of the public key, so a funded address that has never signed keeps its key private. A Substrate address is an SS58 encoding of the public key itself, so the key is readable from the address alone, whether or not the account has ever transacted. On Bittensor there is no such thing as an unexposed funded account.

Could Bittensor migrate quickly if it wanted to?

More easily than most, yes. Changing a signature scheme on a Substrate chain is a runtime upgrade rather than a contentious hard fork, so the governance obstacle that dominates Bitcoin's migration problem is largely absent. That is why the migration dimension scores above zero here. It does not score higher because capacity to act is not the same as a plan: the candidate code offers new ML-DSA-65 accounts, and no route for existing accounts has been published.

Sources

  1. Bittensor documentation Bittensor · primary · checked 17 August 2026
  2. RaoFoundation/subtensor, the Bittensor blockchain node Opentensor · primary · checked 17 August 2026
  3. FIPS 204: Module-Lattice-Based Digital Signature Standard NIST · primary · checked 17 August 2026
  4. Add compatible ML-DSA wallet support (subtensor pull request 3259) Opentensor · primary · checked 4 November 2026
Cite this rating

A rating is only true as of the day an editor last reviewed it, so both forms below carry that date and the methodology version, with the date its cited sources were last checked. If you are quoting the score, quote those too.

Plain text

The Hardy Index (2026). Bittensor: quantum readiness assessment. Hardy Score 19.0 of 100, Tier 4: Debating. Methodology v1.8. Last reviewed 4 November 2026; sources checked 17 November 2026. https://hardyindex.com/chains/bittensor

BibTeX
@misc{hardyindex_bittensor_2026,
  author       = {{The Hardy Index}},
  title        = {Bittensor: quantum readiness assessment},
  year         = {2026},
  howpublished = {\url{https://hardyindex.com/chains/bittensor}},
  note         = {Hardy Score 19.0 of 100, Tier 4: Debating. Methodology v1.8},
  urldate      = {2026-11-17}
}

The whole dataset is reusable under the terms on the about page. A machine-readable version of this page is at /chains/bittensor.md.

This is a security-readiness assessment, not investment advice.