The short answer
Tron's score rose on 15 August because four dimensions had been scored on stale evidence. TIP-899 specifies Falcon-512 and ML-DSA-44, and Falcon-512 is activated on the public Nile testnet. Signature, NIST alignment, migration and verification all moved up. The tier does not move, because there's still no funded roadmap with public dates.
What moved and why
Tron's entry used to record an announced intention to adopt NIST post-quantum signatures, and deliberately gave it no credit. It said the score would move if Tron published a specification, a named parameter set, or a testnet implementation. All three already existed when that entry was written.
TIP-899, Post-Quantum Signature Support, was opened in Tron's own improvement-proposal repository. It specifies two signature schemes across transactions, block production, node relay handshakes and the TVM, down to canonical wire encodings and how addresses are derived. That's a specification, not a press release.
Falcon-512 was then activated on the public Nile testnet by governance proposal. You can check this yourself: the chain parameter getAllowFnDsa512 reads 1 on Nile, and the parameter is absent from mainnet entirely.
- Signature goes from 0 to 2: a post-quantum scheme is live on a persistent public test network. It's held at 2 rather than 3 because ML-DSA-44 is staged on Nile at 0 and has not been switched on.
- NIST alignment goes from 4 to 7: named standardised parameter sets, specified to the byte, are a committed selection rather than a candidate reference.
- Migration goes from 2 to 5: TIP-899's permission-weight coexistence is a genuine route off a vulnerable key. A mechanism is not a plan, and no sunset or date is proposed.
- Verification goes from 5 to 7: open specification, open source client, and a state you can query on chain.
What this does not mean
None of this is on Tron mainnet. If you hold TRX today, your keys are still secured by ECDSA on the secp256k1 curve, which is the signature scheme a large fault-tolerant quantum computer would break. Nothing about that changed this week.
TIP-899 also carries the status Draft. A draft proposal is not deployed code, and a testnet activation is not a mainnet default. Only one of the two specified schemes is actually running on Nile: ML-DSA-44 is written down and staged, but off.
And the tier holds. Our tier bands ask for a funded roadmap with published dates before a chain leaves the debating band, and TIP-899 offers no dates and no sunset for old key types. That's why the score can jump sharply while the tier sits still: they measure different things. A high score with no schedule means real engineering with no commitment attached.
On the correctionThis is the index working on one axis and failing on another. The evidence was public in Tron's own repository and readable from a public API. It should not have taken until now to notice.
The record
Public, checkable events behind the change.
- NIST publishes FIPS 204, the final standard for ML-DSA, one of the two schemes TIP-899 names. source
- TIP-899, Post-Quantum Signature Support, is opened in the Tron improvement-proposal repository with status Draft, specifying Falcon-512 and ML-DSA-44 across transactions, block production, relay handshakes and the TVM. source
- The Nile testnet chain parameters return getAllowFnDsa512 set to 1. The equivalent parameter is absent from mainnet. source
If you hold TRX
Practically, your position is unchanged today, and your outlook is better documented than it was. Tron has moved from talking about post-quantum signatures to specifying them at the byte level and running one of them on a public network. That's the hard part of the work, and it's the part most chains skip.
What to watch next, in order: ML-DSA-44 activated on Nile, then any mainnet parameter for either scheme, then a dated plan for moving existing accounts off secp256k1 keys. The third one is what would move the tier, not the score.
If you want the general framing for why testnet activations matter less than migration schedules, start with how to protect crypto from quantum computers, or compare across chains in most quantum resistant blockchain. The full entry and dimension breakdown lives on the Tron chain page, and this correction is logged in the changelog.
Where to go next
- Tron: the full rating Every dimension score, with the source behind each one, and what the rating means if you hold it.
- Is my crypto safe from quantum computers? If you have seen the scary headlines about quantum computers and crypto, here is the calm version. What is true, what it means for the coins you hold, and what is worth doing about it.
- Which is the most quantum-resistant blockchain? One question, one answer, with the working shown. This page is a summary of the Hardy Index, which is the live ranking behind it.
- Moving to a quantum-ready chain If you have decided you want assets on a chain built for the quantum era, this is how that works in practice, and the honest case for not doing it.
Sources
Every dated event above carries its own primary source. These are those sources, each checked on the date shown.
- TIP-899: Post-Quantum Signature Support tronprotocol/tips on GitHub · primary · checked 21 August 2026
- Nile testnet chain parameters (getAllowFnDsa512) Nile testnet API · primary · checked 21 August 2026
- FIPS 204, Module-Lattice-Based Digital Signature Standard NIST · primary · checked 21 August 2026
- java-tron client source tronprotocol on GitHub · secondary · checked 21 August 2026
This is a security-readiness assessment, not investment advice.