Tron founder Justin Sun wrote on X on Saturday that Tron’s post-quantum cryptography “is now live on testnet” and that the network is “ready to bring quantum resistance to mainnet at any time”. He added that Tron is “set to be one of the few major blockchains that is quantum-resistant before Q-Day”, the point at which a quantum computer could break today’s signatures. The testnet part is not new: the code has been public since late June.
What is on the testnet
A digital signature proves that the owner of a coin approved a payment. Tron, like bitcoin and Ethereum, uses ECDSA, a signature scheme based on elliptic curves, which a large enough quantum computer could in theory break. Post-quantum signatures use different mathematics, which no known quantum algorithm solves efficiently.
Tron’s testnet, called Nile, has had a release that adds two such schemes since 30 Jun: Falcon-512, which the proposal labels FN-DSA-512, and Dilithium-2, labelled ML-DSA-44. The design is set out in TIP-899, a Tron improvement proposal opened on 1 Jul and still marked “Draft”. It says each scheme is switched on by its own on-chain governance proposal and is off by default, and that addresses keep their current format. The cost is size. An ECDSA public key is 33 bytes and a signature 65; the proposal lists 896 bytes and up to 667 bytes for Falcon-512, and 1,312 and 2,420 for ML-DSA-44.
TRON’s core developers invited users to try it on the testnet on 2 Jul. Their post says a post-quantum transaction is accepted only once the matching proposal has been voted in by Tron’s Super Representatives, the elected block producers.
What our check found
We read the public parameter lists of both networks at about 13:45 UTC on Saturday. On Nile, the Falcon-512 switch, getAllowFnDsa512, reads 1, which the proposal’s author has said in a comment means activated. The ML-DSA-44 switch, getAllowMlDsa44, is listed with no value, which the core developers’ guide treats as not yet activated. Mainnet’s list has 80 entries to Nile’s 82, and neither post-quantum switch is among them. The six most recent mainnet node releases, the latest dated 30 Sep, do not mention post-quantum signatures in their release notes.
That fits Sun’s wording, but it does not settle what “at any time” means. Mainnet would need a node release that includes the code, and then its own governance votes. We found no sign of either step. Crypto Briefing, which we have not been able to match to a Tron source, reports that the original plan was testnet in the second quarter and mainnet readiness in the third, and that the mainnet target has moved to the end of the year.
Where the claim holds, and where it is open
The steelman is fair. Tron has done the slow part in public: working code, a written specification, a testnet where one of two schemes already runs, and a design that leaves old addresses alone. Making the schemes opt-in also means a mainnet launch would not force anyone to move at once.
The test is the part a founder’s post cannot show. The specification is still a draft, and the developers’ own comments in August were settling how public keys would be stored. Larger signatures mean more bandwidth and storage per transaction, and wallets, exchanges and smart contracts would all have to support the new keys. Quantum resistance on a chain is only as useful as the share of coins that moves to protected keys, which is the argument I made in my 7 Oct note on the Europol quantum report; the basics are in what a quantum attack on bitcoin means.
My base case I will call the staged switch: more likely than not, Tron turns on one scheme on mainnet first, probably Falcon-512 since that is the one already live on Nile, and the practical protection arrives only as wallets and exchanges adopt it. Other teams are on similar paths, from Zcash’s plan for January to Starknet’s layer-1 idea.
What would change my mind. A mainnet node release carrying the code, or a Super Representative proposal naming an activation date, would make “at any time” concrete. A stall in the TIP, or a testnet problem that keeps ML-DSA-44 switched off, would point the other way.
The bottom line
Tron’s testnet work is real and public, and mainnet is where the exposure sits. Until a mainnet release and vote exist, “ready” describes the code on the testnet rather than the coins on the chain.
The bottom line: a post-quantum scheme running on a testnet is a good start, and it protects no mainnet account until it is voted in and people use it.
— Alasdair
This article is for information only and is not investment advice.