Chain profile
Blockchain-native
TRON.
Abstract. TRON Foundation (Singapore-registered non-profit per public disclosure) · Justin Sun as founder + operationally-involved across HTX, Just Network, BitTorrent — see discipline header for honesty markers
Facts
Chain identity at a glance.
- Type
L1
- Native settlement
- TRX · USDT · USDC · USDD
- Account model
- TVM (Tron Virtual Machine — largely EVM-compatible at bytecode level; Bandwidth + Energy resource model rather than per-transaction gas pricing — non-standard vs. EVM gas semantics) · secp256k1-derived account addresses with Base58Check encoding
Vendor stack · L5 → L1
The 5-layer Stable Stack.
Each row is one named vendor slot from the chain's vendorStack. Solid markers are code-enforced
(the chain blocks or signs); dashed markers are
policy-enforced (the chain flags, humans or systems act on
the signal).
L5 → L1 — application down to network
L5 · Application
wallet
TronLink (canonical Tron wallet) · Trust Wallet (Tron support) · Ledger Live (Tron support) · Binance Web3 Wallet (Tron support)
C1 ◇ policy-enforced
stablecoin-issuer
Tether Limited (USDT issuer with TRC-20-level freeze authority — single most operationally-active compliance surface on the chain; ~$60B+ Tron USDT outstanding) · Circle (USDC on Tron — substantially smaller than Ethereum / Base / Solana USDC) · Just Network JustStables (USDD over-collateralized stablecoin)
C13C14 ◆ code-enforced
defi-suite
Just Network (JustLend lending · JustStables USDD · JustSwap DEX · JST governance token — Sun-aligned DeFi suite)
C13 ◇ policy-enforced
L4 · Account
account
Tron Account (TRX account · secp256k1-derived addresses with Base58Check encoding · Bandwidth + Energy resource model rather than per-transaction gas pricing)
C1 ◆ code-enforced
custody
Binance custody (largest CEX-held Tron position; Binance has historically held the majority of CEX-custodied USDT-on-Tron) · OKX · Huobi/HTX · Bybit · institutional custodians with Tron support (Fireblocks · BitGo)
C1 ◇ policy-enforced
L3 · Execution
swap
SunSwap (Sun-aligned canonical Tron DEX · Uniswap-v2-style AMM) · JustSwap (Just Network DEX)
C13 ◆ code-enforced
off-chain-sanctions
TRM Labs Tron coverage · Chainalysis Tron coverage · Elliptic Tron coverage (off-chain KYT / sanctions screening; no chain-level OFAC Oracle deployment with the prominence of the Ethereum equivalent)
C2 ◇ policy-enforced
issuer-freeze
Tether USDT TRC-20 issuer freeze authority (code-enforced at the contract layer; operationally exercised at the issuer level in coordination with OFAC / DOJ / law enforcement; T3 Financial Crime Unit reports $450M+ cumulative illicit-USDT freezes across 23+ jurisdictions by mid-2026)
C2C3 ◆ code-enforced
bridge
JustLink (Sun-aligned Chainlink-equivalent oracle layer) · Multichain (defunct after 2023; Tron previously load-bearing on Multichain) · LayerZero (Tron support) · cross-CEX off-ramp / on-ramp as de facto bridge between Tron USDT and Ethereum / Solana USDT
C7 ◇ policy-enforced
L2 · Consensus
consensus
Tron DPoS (27 Super Representatives elected by TRX token-holder vote — much smaller validator set than Ethereum or Solana · effective governance even narrower due to TRX-weighted SR election and Sun-aligned vote-share concentration)
C10 ◆ code-enforced
L1 · Network
network
Tron P2P network · Bandwidth + Energy resource accounting (TRX-stakable resource units rather than per-transaction gas pricing — non-standard vs. EVM gas semantics)
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- LayerZero (VERIFY current Tron support)
- Cross-CEX off-ramp/on-ramp as de facto USDT bridge
- Historical: Multichain (defunct 2023) · JustLink-adjacent bridges (VERIFY current operational status)
Related paths
Paths that route through TRON.
Compliance paths whose settlementChains
include tron or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/tron.ts —
full discipline header, sources, and per-field VERIFY
inventory live in the chain-profile source file. See the path resolver to see
this chain in a resolved compliance journey.
Explore the architecture
Pick a thread.