What it is. Tron is the network that carries most of the world's stablecoin dollar transfers, and in April 2026 its founder publicly said it would be the first big network to go quantum-safe.
What we found. That promise was words only: no code was written, no test version exists, no date was set with anything to hold the team to it, and a rival network had already done the real work months earlier.
Why it matters. Roughly eighty-seven billion dollars in stablecoins still sit on the older protection a future quantum computer could break, and nobody has said what happens to your balance if it is not moved across in time.
Justin Sun's April 14, 2026 X post + 15+ press articles claim Tron will be the 'first major mainstream public chain to deploy NIST-standardized post-quantum signatures on mainnet', but no TIP, no java-tron PR, no testnet, no chosen primitive, no dated milestone. Announcements/shipped ratio is effectively infinite (>5.0): narrative-only. The 'first major' claim is contestable on facts (a different chain's Falcon shipment in Nov 2025 has tx-level verification).
Summary
Tron QRI 16 ± 8 (Band 2 Acknowledged), Migration Stage 0 (announcement without primitive selection). Justin Sun's April 14, 2026 X post and 15+ press articles in 7 days promise NIST-standardized PQ signatures, but the technical roadmap is undelivered: no TIP filed, no java-tron PR, no chosen primitive, no testnet, no dated milestone with enforcement mechanism. The announcement-to-shipped delta classifies as narrative-only (>5.0), fires a QRI cap 65 that is non-binding because raw QRI sits at 16. DPoS with 27 Super Representatives gives the chain structurally low Nakamoto coefficient (~14 of 27 → BFT fault). Per v3.1 rule, 4f is N/A (DPoS uses ECDSA secp256k1 block signing, no BLS aggregation). The systemic risk concentration is $86.7B USDT TRC-20 (Mar-Apr 2026) sitting on classical ECDSA secp256k1 with no migration path declared. 4 of 4 vendor tiles lack PQC roadmap (TronLink, Trust Wallet, Ledger; TronGrid, Wormhole; Binance, OKX, Bybit, Tether). Mainnet-Traffic + Architecture-Execution Gap (42pt) + Milestone-Discipline + Supply-Chain caps all fire. Both Gates 1a-Sig and 1a-KEM FAIL.
What the gates say
- Gate 1a, Hybrid signature: FAIL , no documented hybrid signature composition; Sun's April 14, 2026 announcement promises NIST-standardized PQ signatures but does not specify whether deployment will be parallel, AND-composed, or OR-composed; no spec exists
- Gate 1a, Hybrid KEM: FAIL , no hybrid KEM composition for transport-layer encryption; validator gossip, RPC TLS use classical X25519/RSA/ECDH only
- Gate 1b, Commit-to-hash: COND , no OR-composition declared
- Gate 2, Evidence reconstruction: PASS , every sub-score reconstructible from cited URLs within 48 hours
- Gate 3, Primitive naming: PASS , every sub-score names specific primitives, ECDSA secp256k1, SHA-256, Keccak-256; Sun's announcement itself does not name primitives, but our scoring of the chain's actual stack does
Burn-vs-rescue policy on file
Declared option f, Undeclared. Tron Foundation has not published a policy on what happens to unmigrated balances post-quantum-mainnet-cutover. Sun's April 14, 2026 statement promises 'no TRON user ever loses their assets to quantum threats' but provides no enforcement mechanism. The most consequential question, what happens to USDT TRC-20 balances frozen in unmigrated multisig vaults, exchange hot wallets, or smart-contract escrows, is unanswered.
Seven dimensions
Each dimension scores 0–100 internally; the weighted roll-up produces the QRI.
1 Cryptographic Exposure weight 15% 26 / 100
Tron does not publish a single canonical primitive-inventory document; primitives are reconstructable from java-tron source and TIPs.
ECDSA over secp256k1 (account model and transaction signing per TRC120 spec) · SHA-256 (block hashing) · Keccak-256 (TVM/EVM-compatible state and event hashing) · ECDSA over secp256k1 (Witness/Super Representative block signing) Every signing primitive is Shor-vulnerable; no PQ-safe primitive is in active mainnet use.
ECDSA secp256k1→ Shor-break-via-DL-without-pairingsSHA-256→ Grover-weaken (256→128bit)Keccak-256→ Grover-weaken (256→128bit)
0 PQ families deployed (lattice 0, hash-based 0, code 0, isogeny 0). Classical-only stack. Diversity Cap (lattice-monoculture) does not yet apply because no PQ family is deployed at all; the cap will become relevant once a chosen scheme is named.
ECDSA secp256k1: 128-bit classical, no NIST PQC category; SHA-256: pre-PQC NIST hash; Keccak-256: pre-PQC NIST hash. No primitive in active mainnet use carries a NIST PQC category-1-through-5 label.
formal_verif: none documented for java-tron crypto layer; constant_time depends on underlying ECDSA library (BouncyCastle in java-tron), no dudect validation public; library_provenance: java-tron and tronj client libraries (Apache-licensed Tron Foundation repos), no published cryptographic audit by an independent firm. statefulness: stateless. cryptanalytic_tier: tier 1 (classical ECDSA + SHA-2/3).
2 Quantum Recovery Exposure weight 10% 14 / 100
Tron's account model exposes the secp256k1 public key on first outbound transaction (consistent with EVM-compatible chains). USDT TRC-20 ($86.7B circulating on Tron as of Mar-Apr 2026) is the dominant on-chain asset; multisig vaults, exchange hot wallets, and active retail addresses all reveal pubkeys with each transaction.
Mainnet launched 2018; ~7 years of accumulated dormant balances. Exchange-held TRX (Binance, OKX, Bybit) is the larger fraction of circulating supply, not classic dormant cold storage in the Bitcoin sense. Genesis-era Tron Foundation reserve addresses are publicly identified; exposure is concentrated rather than long-tail.
Every historical TRX transaction is ECDSA-signed; signatures permanently embedded in the chain become forgeable post-Shor for any unsealed account where the public key is or becomes known. No protocol-level signature-rotation primitive.
Validator gossip, RPC endpoints (TronGrid, public nodes), and inter-node TLS use classical X25519/ECDHE/RSA for transport encryption. No protocol-level payload encryption (Tron is a transparent ledger). HNDL exposure exists at the transport layer for any captured RPC traffic, but content payloads on-chain are public.
3 Metadata, Anonymity & Confidentiality weight 13% 14 / 100
Pseudonymous transparent ledger. USDT TRC-20 transactions are fully observable on Tronscan. Industry analytics consistently identify Tron as the leading rail for stablecoin-denominated illicit flows, which generates external de-anonymization pressure (sanctions enforcement, OFAC freezes).
TronGrid (Tron Foundation infrastructure) is the dominant public RPC; secondary providers (Ankr, GetBlock, NowNodes) are smaller. The 27-Super-Representative consensus set is small and Tron Foundation-aligned, concentrating mempool observability. No publicly declared validator-metadata retention policy.
JustLink, SunSwap-bridged assets, and Tether's own cross-chain swap mechanism (USDT moving between Ethereum and Tron via Tether redemption) all create source-to-destination correlation surface. April 2026 USDT freeze ($344M frozen by Tether at U.S. request on Tron) demonstrates operator-level traceability.
Shor on secp256k1 retroactively exposes any pseudonymous Tron address whose public key has been revealed (i.e., almost every active address). No on-chain privacy layer to protect historical content; full ledger transparency means de-anonymization risk is largely about external linkage (KYC at on-ramps, exchange compliance), not on-chain cryptographic privacy.
No native or widely-used on-chain mixer or shuffle protocol.
4 Migration Architecture weight 10% 44 / 100
TVM is EVM-compatible. Tron has no documented protocol-level algorithm-switch primitive (analog of EIP-7702) live in production. Hard-fork-by-Foundation is the upgrade path; Sun's April 14, 2026 X post promises a roadmap but no spec is published as of evidence cutoff.
No native account abstraction. Tron supports multi-signature accounts at the protocol level (permission-based account model with custom permissions for owner/active/witness keys), which provides limited key-rotation flexibility. No ERC-4337-equivalent or EIP-7702-equivalent. No client-layer PQC path declared.
Tron Foundation coordinates upgrades through java-tron releases; track record of completed upgrades over the past 3 years (Plonk, GreatVoyage, Tron 4.x series) is consistent under centralized coordination. No contested forks. The cost is governance-centralization, not coordination failure.
No published hybrid-signature spec (no AND-composition, no OR-composition with commit-to-hash). Sun's April 14, 2026 X post stated a 'technical roadmap is coming soon' but, as confirmed in Unchained's April 16, 2026 reporting, no formal governance proposal or technical documentation had been released by Tron DAO as of April 15, 2026. Hybrid is architecturally feasible but not announced or specified.
Default for stateless schemes, Tron does not use stateful hash schemes (XMSS, LMS, leanXMSS) in any deployed or announced form.
Tron's DPoS uses 27 Super Representatives with ECDSA secp256k1 block signing; no BLS aggregation in consensus. Per v3.1 rule, 4f is N/A for chains using non-aggregating signatures at consensus. Renormalized to /80 → 35/80 → 44/100 on rubric scale.
5 Deployment Execution weight 22% 2 / 100
0% PQC mainnet signing traffic. No PQ primitive deployed.
No PQC code merged in java-tron or any official Tron Foundation client repo as of evidence cutoff.
Zero Super Representatives have PQC signing keys in active use; consensus is ECDSA-only.
Sun's April 14, 2026 X post named 'testnet Q2 2026, mainnet Q3 2026' timing in subsequent press; the X post itself promised a 'technical roadmap coming soon' but did not publish enforcement-mechanism-backed milestones (no TIP number, no java-tron PR, no governance vote). v3.1 rule: 5d voided to 0 when 5a = 0 (Milestone-Discipline). Independently, even without that void, the milestones lack enforcement mechanism.
Announced PQC: Sun's April 14, 2026 X post + 15+ unique press articles in 7 days. Shipped PQC: 0 mainnet bytes signed under any named PQ primitive. Ratio: 15+ announcements / 0 shipped = effectively infinite (denominator zero). Tweet text not directly verified at evidence cutoff (WebFetch returned 402 X paywall). Tag: narrative-only (>5.0). Apply 10pt deduction at sub-score level + QRI-cap-65 review at chain level.
Undisclosed. No public selection of an algorithm; no published bytes-per-block or vbyte multiplier estimate from Tron Foundation. Press cites '10 to 121× larger' as a generic NIST-PQC range, not a Tron-specific figure.
6 Supply Chain Vendor Readiness weight 22% 8 / 100
Top-3 Tron wallets: TronLink (Tron Foundation-aligned, Chrome extension + mobile), Trust Wallet (Binance), Ledger (hardware). None publish a PQC roadmap that names PQ primitives or migration timeline. Trust Wallet and Ledger have generic security-update policies but no Tron-specific PQ commitment.
Top bridges by Tron-flow volume: Tether's native cross-chain swap (Ethereum↔Tron USDT issuance/redemption), JustLink, SunSwap-bridged assets. Wormhole supports Tron but Wormhole has no published PQC roadmap. None of the active bridges to Tron have published PQC commitments.
Top custodial holders of TRX and TRC-20 USDT: Binance, OKX, Bybit (exchange custody); Tether reserve infrastructure for USDT issuance. Binance has cited general PQ readiness intent but no published roadmap. Tether has not published PQC migration plans for its multi-chain stablecoin issuance infrastructure.
TronGrid (Tron Foundation), Ankr, GetBlock, NowNodes. None publish PQC roadmaps. Tron Foundation infrastructure dominates RPC traffic; no HSM or TEE attestation chain disclosure.
7 Governance & Coordination weight 8% 31 / 100
27 Super Representatives elected every 6 hours by TRX-frozen voting. Nakamoto coefficient is structurally low (~14 of 27 SRs collude → BFT fault). Tron Foundation and founder-aligned entities historically over-represented in the SR set.
Foundation-coordinated hard forks ship reliably (java-tron release cadence is steady). Centralized coordination is a strength for execution velocity and a weakness for resilience under adversarial pressure on the foundation itself.
Named: Justin Sun (founder, public face); Tron DAO; Tron Foundation. Sun himself is the de-facto coordination lead. No published mandate document for a quantum-migration WG; no separate 'PQ Tron WG' comparable to Ethereum's PQ research team.
Tron has executed coordinated upgrades under regulatory pressure (SEC March 2023 lawsuit settled June 2025; sanctions enforcement events including the April 2026 $344M USDT freeze) but these are operator-level/legal-coordination precedents, not cryptographic-coordination-under-active-attacker. No precedent of Tron coordinating a crypto-primitive change while an attacker was active.
None. No community honeypot, no rate-limited spending rule, no cryptographic tripwire embedded in consensus.
X + Y vs Z, when does the math turn against you?
v3.1 demotes the X+Y vs Z timing test to a secondary signal, the headline output is Migration Stage. The timing test still answers the question: can this chain finish migrating before the threat lands?
Verdict
X+Y reaches 2031–2041, Crisis Zone (vs Z10 2030); Outside risk window for upper end (vs Z25 2035)
Z-compliance
Outside compliance window for upper-end X+Y vs NIST 2035, Tron's largest user base sits in jurisdictions (EU, US, UK, ASEAN) where NIST 2030 deprecation / 2035 disallowance, BSI Migrationsplan, and EU NIS2 PQ guidance increasingly bite
Source-disagreement disclosure
v3.1 requires every chain card to publish material divergences among authoritative sources, plus the delta-QRI under alternative weighting.
Primary divergence is between Sun's 'first mainstream public chain to deploy NIST-standardized PQ signatures on mainnet' framing and the deployment reality (no spec, no testnet, 0 PQ code in java-tron). Independent press (Unchained April 16, 2026; Crypto Times April 15, 2026) flagged the absence of a technical roadmap explicitly. A different chain shipped Falcon (FN-DSA / FIPS 206) on mainnet in November 2025; tx-level verification exists. Tron's claim depends on what counts as 'deploy' (consensus-level mandatory vs. opt-in opcode).
Under a deployment-heavy weighting (Dim 5 weight 30%, Dim 4 weight 7%), Tron's QRI drops to ~13. Under an architecture-heavy weighting (Dim 4 weight 20%, Dim 5 weight 12%), Tron's QRI rises to ~18. In neither case does Tron leave Band 2 (Acknowledged); the cap structure binds independent of weighting profile.
Delta-QRI under alternative weighting
Under alternative weighting profiles, QRI shifts -3 to +2; band unchanged (still Band 2).
Announcement-to-shipped ratio
Announced: 15. Shipped: 0. Ratio: 999.
Tag: narrative-only (>5.0), 15+ named-press articles in 14 days following April 14, 2026; 1 founder X post with ~3.9M-follower reach; 0 prior PQ statements from Tron Foundation in 2025; 0 shipped. Tweet text not directly verified (WebFetch returned 402 X paywall); independent press attributes ML-DSA / FN-DSA / SLH-DSA to Sun's announcement.
Peers in the L1 profile
9 chains closest to Tron by Stage then QRI.