Built at NEAR HACKATHON 2026 · read-only · live from NEAR mainnet
Adding a post-quantum key doesn't retire the old one.
NEAR accounts can now hold ML-DSA-65 keys (NEP-645). An existing account adds one by signing with its classical key, and that classical key keeps full control until the owner deletes it. Residual reads accounts at one pinned block and shows whether classical full-access authority is still live.
A single scan checks which access keys exist now. Historical key retirement requires a previous key inventory and a later pinned observation. See the post-submission retirement-evidence extension (trusted-RPC evidence; not a cryptographic state proof).
Classical full-access key, no post-quantum key.
Post-quantum and classical full access together. The classical key is still a way in.
Post-quantum full access, no classical full access left.
Post-quantum keys limited to contract calls, no full access.
Couldn't classify, always with a reason. Kept in the totals.
Check an account
Reads the account's access keys at the latest finalized block, straight from a public NEAR RPC endpoint in your browser.
Try:
Live sample
Pins the latest finalized block, walks back through recent blocks, collects every account that signed a transaction, and draws a sample seeded by the block hash, so anyone can rebuild the same draw. Accounts that added an ML-DSA-65 key in that window are read as a separate group.
Recorded evidence
A dated mainnet observation with the block hash, sample denominator and source data. This recorded report is not a live ecosystem-wide adoption measure.
Loading the latest snapshot…
How it works
- Pin one block. Every read uses the hash of one finalized block, so the whole result describes one moment of the chain.
- Read the access keys.
view_access_key_listfor each account. Each key's prefix and decoded length are checked:ed2551932 bytes,secp256k164,ml-dsa-65-hash32. - Classify, and keep the unknowns. Failed reads, missing accounts and unrecognized keys stay in the denominator with a reason code.
Who it's for
- Account holders checking whether their own migration is finished.
- Wallets and custodians who need to know which accounts still depend on a classical key.
- Foundations and researchers tracking post-quantum migration with a number anyone can rerun.
What it does not claim
- "PQ full access only" describes access keys at one block. It is not a certificate of quantum safety.
- Answers come from the RPC endpoint and are not verified with light-client proofs.
- The live sample covers recently active signers, not all NEAR accounts.
- Before deleting any key, confirm your wallet can sign with the key you keep. Deleting your only working key locks you out.