Skip to content

What Are Post-Quantum Wallets on Bittensor? ML-DSA, Falcon and Activation Status

Runtime 488 added ML-DSA and Falcon wallet signatures on Bittensor, while existing wallets stay valid and live use depends on activation plus compatible wallet support.

Table of Contents

Post-quantum wallets on Bittensor are native accounts that can sign transactions with ML-DSA-65, Falcon-512, or Falcon-1024 instead of the network's older Sr25519 and Ed25519 schemes. Runtime 488 brought that support to mainnet, along with hashed accounts that rotate signing keys after transactions are included.

The change does not force existing TAO holders to move funds. Standard Sr25519 and Ed25519 wallets keep their addresses and remain valid, and Bittensor's wallet crypto documentation says those wallets require no migration. The main operational question is activation: the runtime includes the new account types, but root controls registration and signing through AdminUtils.HashedAccountsEnabled.

That status has changed since the first Runtime 488 news cycle. Taostats' protocol-change note, last reviewed Nov. 17, 2026, now says the feature is live on mainnet, switched on by root, and able to register and sign transactions. Users should still confirm current wallet-client support before sending funds or relying on a post-quantum account operationally, because the signing scheme, account mode, and client tooling all have to line up.

This guide explains what changed in Runtime 488, how ML-DSA and Falcon differ, why hashed accounts are a separate feature from post-quantum signatures, what the activation switch controls, and what TAO holders should do before treating these wallets as ordinary production accounts.

Post-Quantum Wallets In One Paragraph

Post-quantum wallets on Bittensor are native wallet accounts that use ML-DSA-65, Falcon-512, or Falcon-1024 signatures for transactions. Those schemes are designed around post-quantum cryptography, unlike the classical Sr25519 and Ed25519 schemes used by existing wallets. Bittensor also supports hashed accounts, which keep a permanent account identity while rotating signing keys over time. These are independent choices: ML-DSA and Falcon determine whether the signature scheme is post-quantum, while hashed mode determines whether the signing key rotates. Existing standard Sr25519 and Ed25519 wallets remain supported and do not need to migrate.

What Changed In Runtime 487 And Runtime 488

The post-quantum wallet work entered Bittensor's release path through Runtime 487 and shipped to Finney through Runtime 488. The Runtime 488 release notes, published Nov. 5, 2026, include "Release 487 - Quantum Resistant Wallets" and "Release 487 — Gamma + Quantum-Resistant Wallets" among the changes.

TAO Media's initial report on Bittensor's Runtime 488 post-quantum wallet support explained the distinction at launch: the code had reached mainnet, but post-quantum signing and hashed-account registration still depended on a root-controlled enable flag. That early reporting explains why readers may have seen conflicting language around whether the feature was "deployed," "enabled," or "live."

A runtime upgrade and an activation switch are different layers of the same rollout. Runtime 488 added the account profiles and transaction support. HashedAccountsEnabled controls whether the affected accounts can register and sign. A later runtime version does not automatically prove the switch is on or off; the live flag and client support are what matter for actual use.

Why Bittensor Added Post-Quantum Wallet Support

Bittensor wallets traditionally use elliptic-curve signature schemes. Sr25519 is the default native Bittensor scheme, and Ed25519 is also supported. These schemes are widely used in blockchain systems today, but a sufficiently powerful future quantum computer could threaten elliptic-curve signatures by deriving private keys from exposed public keys.

Post-quantum wallet support gives Bittensor a native path toward account signatures that do not rely on elliptic curves. That does not mean ordinary TAO wallets are already unsafe, and it does not mean Bittensor has become "quantum-proof" as a whole. It means the chain now has account types intended to reduce a specific long-term cryptographic risk.

Wallets sit at the base of Bittensor's operating model. Coldkeys, hotkeys, validators, miners, subnet owners, staking operations, and transfers all depend on accounts being able to authorize actions reliably. As Bittensor's tokenized AI network grows, wallet cryptography becomes part of the infrastructure supporting subnet participation and TAO custody. For broader network context, see TAO Media's guide to what Bittensor is.

The Five Signing Schemes Bittensor Supports

Bittensor now supports five wallet signing schemes: Sr25519, Ed25519, ML-DSA-65, Falcon-512, and Falcon-1024. Sr25519 and Ed25519 are classical schemes. ML-DSA-65, Falcon-512, and Falcon-1024 are the post-quantum options.

SchemePost-Quantum?Public KeySignatureMain Use In Bittensor
Sr25519No32 B64 BExisting default native wallet scheme
Ed25519No32 B64 BExisting classical wallet scheme
ML-DSA-65Yes1,952 B3,309 BNIST level 3 post-quantum option
Falcon-512Yes897 B666 B, paddedSmaller post-quantum key-and-signature footprint
Falcon-1024Yes1,793 B1,280 B, paddedHigher-security Falcon option

ML-DSA-65 is specified in FIPS 204, while Falcon-512 and Falcon-1024 use Falcon parameter sets. In Bittensor's comparison, ML-DSA-65 has the fastest signing time, Falcon-512 has the smallest key-and-signature footprint, and Falcon-1024 targets the highest security level of the three post-quantum options.

Those figures describe wallet-cryptography characteristics, not a fee model. Post-quantum signatures are larger than classical signatures, and transaction size can matter, but runtime weights, call data, and the specific operation also affect fees and execution behavior. Bittensor also uses the original Falcon padded signature format and does not claim compatibility with final FN-DSA encodings.

Standard Vs Hashed Accounts

The new wallet system involves two separate decisions: the signing scheme and the account mode.

The signing scheme is the cryptographic choice among Sr25519, Ed25519, ML-DSA-65, Falcon-512, and Falcon-1024. The account mode is the operational choice between a fixed signing key and one that rotates while preserving the same account identity.

Scheme And Mode Are Independent Choices

A standard account uses one fixed signing key. A hashed account keeps a permanent account identity but rotates signing keys after transactions are included. Bittensor supports both modes across the available schemes.

This distinction prevents two common misunderstandings. A standard ML-DSA or Falcon account is still post-quantum even though its signing key is fixed. A hashed Sr25519 or Ed25519 account still uses classical cryptography even though its signing key rotates. The post-quantum property comes from ML-DSA or Falcon, not from key rotation alone.

Rotation Does Not Make Sr25519 Or Ed25519 Quantum-Resistant

Key rotation can reduce how long a particular public key remains active, but it does not change the mathematical assumptions behind Sr25519 or Ed25519. A rotating Sr25519 wallet is still an Sr25519 wallet, and a rotating Ed25519 wallet is still an Ed25519 wallet.

This affects validators, miners, and users who manage hotkeys. Hashed mode changes account behavior, but it does not turn a classical signature scheme into a post-quantum one.

Standard ML-DSA And Falcon Accounts

Standard ML-DSA and Falcon accounts use ordinary SS58 addresses, require no registration deposit, and do not need account registration before first use. They use fixed signing keys and normal native nonces.

A standard post-quantum wallet is a new account identity, not an upgrade applied to an existing Sr25519 or Ed25519 address. Restoring or creating a wallet with the same mnemonic but a different scheme or mode produces a different account, so users need to record the scheme and account mode alongside the recovery phrase.

Hashed Or Rotating Accounts

Hashed accounts require registration before use and rely on a tao_ receiving address that carries information compatible wallets need to check or arrange registration. The receiving address remains stable as signing keys rotate.

The default registration deposit is 0.2 TAO. That amount is a permanently reserved deposit for registration, not a general transfer fee, and root can change the amount for future registrations through the relevant admin call. Standard ML-DSA and Falcon wallets do not use this hashed-account registration deposit.

Activation Status: The Feature Is Deployed, And The Switch Controls Use

Root controls registration and signing for all hashed accounts and all ML-DSA/Falcon accounts through AdminUtils.sudo_set_hashed_accounts_enabled(enabled). The current value is stored in AdminUtils.HashedAccountsEnabled.

At launch, public reporting described Runtime 488 as deployed but activation-pending. Taostats now says the feature is live on mainnet and switched on by root, with post-quantum and hashed accounts able to register and sign transactions. Editors and operators should still check the current chain state and wallet-client behavior close to use, because the flag can be changed and because signing support also depends on compatible software.

What The Switch Covers

The enable switch covers hashed Sr25519 and Ed25519 accounts, standard ML-DSA-65 accounts, rotating ML-DSA-65 accounts, standard Falcon-512 and Falcon-1024 accounts, and rotating Falcon-512 and Falcon-1024 accounts.

Ordinary fixed Sr25519 and Ed25519 wallets are unaffected by the switch. They continue to work as normal whether the post-quantum and hashed-account feature set is enabled or paused.

Root Governance Controls Activation

Activation sits with root governance authority rather than individual wallet users. For readers who want background on Bittensor protocol control, TAO Media's explainer on who controls Bittensor provides context for root, Senate, and governance powers.

That governance context should not be confused with personal wallet guidance. The practical user question is whether the relevant scheme and account mode are enabled on chain and supported by the wallet software being used.

What TAO Holders Should And Should Not Do

Existing TAO holders do not have to migrate because of Runtime 488. Standard Sr25519 and Ed25519 wallets keep their addresses, remain valid, and continue to operate under the existing account model.

Users considering post-quantum accounts should focus on three practical checks. First, confirm the current activation state rather than relying on old deployment headlines. Second, use wallet software that explicitly supports the selected scheme and account mode. Third, record the scheme and mode with the recovery phrase, because account recovery depends on all three pieces of information.

For ML-DSA and Falcon, Bittensor uses 24-word mnemonics. Recovering the same mnemonic under a different scheme or account mode derives a different account. That makes documentation and custody procedures more important than they are for users who only manage a single default Sr25519 wallet.

This article is not a migration guide and does not recommend moving funds into a new address simply because a new wallet type exists. TAO holders should treat post-quantum wallets as a new account option that requires current client support, careful recovery records, and ordinary operational caution.

Limits And Compatibility Considerations

Post-quantum wallet support expands Bittensor's account system, but it does not automatically upgrade every tool or adjacent account type.

Browser extensions, Ledger apps, Polkadot Vault, custodians, and other signing tools need explicit support for the chosen scheme before they can sign transactions. A wallet type existing in the runtime does not mean every client interface can create, recover, display, or use it safely.

ML-DSA and Falcon hotkeys also do not support arbitrary message signing or HTTP authentication. That matters for workflows that use hotkeys outside normal transaction signing, including services that rely on signed messages for authentication.

EVM wallets remain separate. Bittensor's native post-quantum accounts do not make Ethereum-style ECDSA wallets post-quantum, and associating an EVM address with a native identity does not merge the accounts or let the ECDSA key sign for the native post-quantum address.

Multisig and proxy safety depends on how authority is constructed. New safe composite modes are designed to avoid certain classical-key bypass issues, but a multisig is only as post-quantum-resistant as the quorum and delegates actually chosen. A quorum controlled by classical keys should not be treated as post-quantum simply because another participant uses ML-DSA or Falcon.

FAQs

What Are Post-Quantum Wallets On Bittensor?

Post-quantum wallets on Bittensor are native wallet accounts that use ML-DSA-65, Falcon-512, or Falcon-1024 signatures instead of classical Sr25519 or Ed25519 signatures. They give Bittensor account holders a path toward signatures that do not rely on elliptic-curve cryptography.

Is The Feature Live, And Can I Spend From A Post-Quantum Wallet Today?

Taostats now says post-quantum and hashed accounts are live on mainnet, switched on by root, and able to register and sign transactions. Users should still verify current chain status and wallet-client support before moving funds or relying on one of these accounts operationally.

Do I Have To Migrate My Existing Bittensor Wallet?

No. Existing standard Sr25519 and Ed25519 wallets keep their addresses and require no migration. Post-quantum wallets are new account options, not an automatic conversion of current wallets.

What Is The Difference Between ML-DSA-65, Falcon-512 And Falcon-1024?

ML-DSA-65, Falcon-512, and Falcon-1024 are the three post-quantum signature schemes supported by Bittensor's wallet documentation. ML-DSA-65 is listed at NIST security level 3, Falcon-512 at level 1, and Falcon-1024 at level 5. Falcon-512 has the smaller key-and-signature footprint, while Falcon-1024 targets a higher security level.

Does Key Rotation Make My Wallet Quantum-Resistant?

No. Key rotation changes how signing keys are used over time, but it does not make Sr25519 or Ed25519 post-quantum. Quantum resistance depends on the signing scheme, and ML-DSA and Falcon are the post-quantum schemes in Bittensor's wallet system.

What Is HashedAccountsEnabled?

HashedAccountsEnabled is the on-chain value controlled through AdminUtils.sudo_set_hashed_accounts_enabled. It gates registration and signing for hashed accounts and for ML-DSA/Falcon accounts. Ordinary fixed Sr25519 and Ed25519 wallets are unaffected.

What Happens If I Send TAO To A Post-Quantum Address Before Activation?

When the feature is switched off, funds can be sent to a post-quantum address but cannot be spent from it until activation and client support are available. Because Taostats now reports the switch as on, the more relevant current check is whether the specific wallet software supports the scheme and mode being used.

How Do I Recover A Post-Quantum Wallet?

Recovery requires the original mnemonic plus the same signing scheme and account mode. ML-DSA and Falcon wallets use 24-word mnemonics, and restoring the same phrase with a different scheme or mode produces a different account.

Bottom Line

Bittensor's post-quantum wallet support adds ML-DSA-65, Falcon-512, and Falcon-1024 as native account options while preserving existing Sr25519 and Ed25519 wallets. Runtime 488 delivered the underlying support, and the relevant activation flag controls whether the new post-quantum and hashed-account types can register and sign.

For TAO holders, the takeaway is measured. Existing wallets do not need to migrate. Post-quantum accounts are available as new wallet types, but users should verify the current activation state, client compatibility, recovery procedure, and account mode before moving funds or assigning operational roles.

Comments

Latest