TRON links USDT liquidity to LI.FI for multichain access

TRON DAO announced on April 21, 2026 from Geneva that LI.FI has integrated the TRON blockchain. The integration connects TRON’s stablecoin-focused settlement layer to LI.FI’s universal liquidity layer, allowing developers and applications using LI.FI to route TRON USDT liquidity for cross-chain bridging and swaps between TRON and major EVM and non-EVM networks.

LI.FI’s tooling will route swaps and cross-chain transfers into and out of TRON so developers using the protocol do not need to build or maintain separate bridge integrations for TRON liquidity. TRON’s blockchain is characterized by low transaction fees and high throughput, factors both organizations noted in relation to stablecoin payments, remittances and on-chain settlement use cases.

TRON provided network metrics with the announcement. As of April 2026 the blockchain hosts more than $85 billion in circulating USDT and reportedly handles roughly $21 billion in daily transfer volume. TRON also reported over 376 million user accounts, more than 13 billion total transactions and about $27 billion in total value locked.

LI.FI describes itself as a non-custodial, open-source protocol that aggregates access to third-party bridges and decentralized exchanges into a single API. Founded in Germany in 2021, LI.FI says it works with more than 800 partners and provides developer tools to simplify multi-chain flows.

The integration enables developers to route stablecoin flows through TRON’s liquidity pools and settlement rails using LI.FI’s orchestration. End users of LI.FI-enabled applications will be able to bridge and swap stablecoins into and out of TRON directly within those apps.

Sam Elfarra, Community Spokesperson for TRON DAO, said, “Connecting to LI.FI’s orchestration layer further strengthens access to TRON’s infrastructure across the entire blockchain ecosystem.” Philipp Zentner, LI.FI’s CEO and co-founder, added that the arrangement lets developers tap TRON’s stablecoin liquidity through LI.FI’s API without managing multiple integrations.

Both organizations provided media contacts with the announcement. They did not publish independent third-party verification of the performance figures cited in their statements.