TRON
KLEAR3 ResearchPublished 2026-08-25Updated
TronTRXTron is eighth by capitalisation, and the most useful thing to know about it is not its own token. It is one of the main rails for the largest dollar token, and its own supply is unusual for this list: 94,919,423,762 circulate out of 94,919,560,251 issued, a gap of barely a hundred thousand.
What does Tron actually do?
Tron runs programs and moves tokens cheaply, and in practice most of that traffic is one thing: dollars. It hosts a contract for the largest dollar token, which makes the chain infrastructure for an asset it did not issue and does not control.
That is the fact worth carrying away. The dollar token in question lives on many chains, and this is one of the two that carry most of it. A chain can matter for what it hosts rather than for what it issues, and Tron is the clearest case of that on this list.
The practical consequence is a trap we describe on several pages here. The same ticker on this chain and on another is not the same contract, and an address from one is useless on the other. The name gives no warning at all.
Source CoinGecko https://api.coingecko.com/api/v3/coins/tether, read 2026-08-25
Is the code actually open?
Yes, under LGPL-3.0, with 85 releases and a repository open since December 2017. The published address is correct, which on this list of ten is worth stating: four other entries carry a repository link that is stale, moved, archived or simply wrong.
The licence is the same one used by the chain one place above it, and both derive from the same lineage of client software. Sharing a licence is not sharing a design, and we did not measure how much code the two actually have in common.
Source GitHub https://api.github.com/repos/tronprotocol/java-tron, read 2026-08-25
No audit report is published in the repository, and none is listed. For a chain that carries this much of someone else’s dollar token, that absence is worth naming plainly, and it stays an absence of reports rather than a verdict.
Source 20 index publics de cabinets https://api.github.com/repos/{20 dépôts}/git/trees/HEAD?recursive=1, read 2026-08-26
Is anyone still working on it?
Yes, at a steady pace. The client took 52 commits from 13 distinct Git identities in the 90 days to 25 August 2026, the last on 6 August. That is far below Solana and Bitcoin, and far above a repository that has stopped.
The comparison worth making is with the busiest client on this list, which counted more than twenty times as many commits over the same window. Neither number is a verdict on quality; they describe two different stages of a project’s life, one still being built and one mostly being maintained.
The count is exact rather than capped: 52 objects sits below the hundred-per-page ceiling, so no pagination was needed to read it correctly.
Source GitHub https://api.github.com/repos/tronprotocol/java-tron/commits?since=2026-05-27T00:00:00Z&per_page=100, read 2026-08-25
- The token is issued
- The chain client goes public
Where does it actually run?
On its own chain, which we checked responds: a public node returned block 85 671 562 on 25 August 2026. Blocks are agreed by delegated proof of stake, meaning holders elect a limited set of producers rather than everyone taking part directly.
Delegation is the design decision here, and it is the same family of trade made by several fast chains: fewer producers, faster agreement, and a smaller number of parties who must be honest. How that election plays out in practice is the question, and it is one we did not examine.
Against the chain that hosts the other large share of the same dollar token, the contrast is instructive: two very different designs carrying the same asset, with the choice between them mostly made on fees.
Source api.trongrid.io https://api.trongrid.io/wallet/getnowblock, read 2026-08-25
TronNetwork verified by reading its current block height on a public node.
What the token actually does
TRX pays for transactions and network resources, and is used to vote for block producers. There is no cap, but almost the entire issued supply is already circulating, which sets it apart from most entries on this list and from what a price chart assumes.
The gap between issued and circulating is roughly one hundred thousand tokens out of ninety-five billion. Practically, everything that exists is in someone’s hands, so there is no schedule of future releases hanging over the price.
Compare that with an entry where a third of the supply sits outside circulation and the difference in what you are buying is real. Neither is better; they simply put different amounts of future supply in play.
- What the token is forDirectly verified
- How many existThird-party supported
- How new ones appearNot verified
- Who can change the rulesThird-party supported
KLEAR3 rating
- Open code5
public repository · LGPL-3.0 licence · 85 published releases · 52 commits in 90 days
- Audits0
absence searched for: 20 firm indexes swept, 3,573 reports, none commissioned by the project
What holds it back no report in our registry · no report opened: we do not know what they found
- Business model5
business model published by the protocol · paid by celui qui envoie la transaction · collected by le réseau, en ressources gelées · un virement simple ne coûte aucun TRX : il consomme de la bande passante
- Governance5
decided by tip-process, with no vote · 153 improvement proposals published · process open for 8 years
- Token alignment1
supply measured, with no cap: nothing bounds issuance · circulating share known
What holds it back emission schedule unknown
- Maturity4
8 years of public code · 1 network verified by us
We rate the protocol: how it is built, how much of it can be checked, how its token lines up. Never an investment. A high score is not advice to buy, and a low one is not advice to sell.
What we could not establish
Audits, how block producers are elected in practice, and how concentrated that election is. We read the repository and the chain, not the arrangements around them, and we do not describe what we have not opened. The election question weighs more here than the code.
The election question carries more weight here than the code does. A chain whose blocks come from a limited elected set depends on who wins those elections and on how often that changes, and measuring it properly needs a different campaign than this one.
Frequently asked questions
Why is so much of the largest dollar token on Tron?
We report that it is, not why. What the measurement shows is a contract for that token on this chain, and cheap transfers. The usual explanation offered is cost, and we did not examine it, so this page does not assert it as a cause.
What matters more for a reader is the consequence. Holding a dollar token here means depending on this chain as well as on its issuer, which is two risks stacked rather than one.
It also means the chain is load-bearing for something it did not create. If this ledger stopped, the token would not disappear, but a large share of its transfers would have to move somewhere else, and the cost of that move would fall on holders rather than on either issuer. That is one reason this chain appears in the ranking at all.
What does delegated proof of stake actually change?
It replaces open participation with an election. Instead of every holder taking part in producing blocks, holders vote for a limited set of producers who do it on their behalf, which makes agreement faster and concentrates it among fewer parties.
The honest framing is that this is a trade rather than a flaw. Speed comes from having fewer parties to convince, and every fast chain on this list pays that same bill in one currency or another.
What would settle the debate is data we did not gather: how many distinct entities actually hold producer slots over time, and how often the set turns over. Without that, any claim about how decentralised the result is remains a claim, however confidently it is made. We did not gather it, so we do not repeat it.
Is Tron a copy of Ethereum?
It runs programs in a similar style and its client shares a software lineage with other chains of that generation, but we did not measure how much code is actually common. Calling it a copy without that measurement would be an assertion, not a finding.
The comparison that does hold is functional: both run programs, both host tokens issued by others, and both are chosen partly on fees. Their differences show up in who produces blocks, not in what the chains are for.
For a reader, the useful test is not lineage but consequence. Where does the asset you hold actually live, who has to behave honestly for it to keep working, and what would it cost you to move it elsewhere. Lineage answers none of those three. Only the chain you are actually on answers them, and it answers them differently.
Next: our Figure HELOC profile shows an entry whose chain we could not reach at all, and our Hyperliquid profile one whose protocol code is not published.
Ask an assistant to summarise it and check what it claims.