Integration

How to integrate with the TRON network — for DApp developers, wallet developers, exchanges, infrastructure providers, and hardware-wallet integrators. This chapter is a role-based map to the right starting point.

"Integrating with the TRON network" means different things to different people. A DApp developer wires up wallet connection in the browser. A wallet developer derives keys and signs transactions on a user's device. An exchange operator monitors deposits and broadcasts withdrawals at scale. An infrastructure team runs nodes or selects a hosted RPC provider. A hardware-wallet integrator delegates signing to a Ledger device.

This chapter is a role-based map. Identify your role below, then jump to the matching sub-section.

📘

Prerequisites


Who this chapter is for

Your roleWhat you'll integrateStart here
DApp developerBrowser-based wallet connection, signing, asset display, event listeningDApp integration
Wallet developerAddress derivation, signing, broadcasting, resource accountingWallet developer guide
Exchange or custodial wallet operatorDeposits, withdrawals, balance queries, optional stakingExchange and custodial wallet integration
Infrastructure or RPC providerNode operation, indexer choices, hosted RPCRPC and indexer providers

DApp integration

Building a DApp means connecting end-user wallets, asking them to sign transactions, listening for state changes (account switch, network switch), and presenting assets in their wallet's UI. On TRON, the primary path is through TronLink (the dominant browser extension wallet); the multi-wallet path uses TronWallet Adapter.

Go to DApp integration


Wallet developer integration

You're building a wallet that supports TRON — either a new wallet or an existing multi-chain wallet adding TRON. The work breaks down into key derivation (BIP-44 path, address encoding), transaction construction, offline signing, broadcasting, balance and history queries, and resource accounting. Optionally: staking flows, multi-sig, and hardware-wallet signing.

Go to wallet developer guide


Exchange and custodial wallet integration

You're operating a centralized service that holds TRX or TRC tokens for users — an exchange, a custodial wallet, a payment platform. The core operations are deposit monitoring (detect inbound transfers within minutes), withdrawal construction (build, sign, broadcast), balance and history queries, and optional staking services. Two implementation paths exist: use the hosted TronGrid service, or run your own full node.

Go to exchange and custodial wallet integration


Infrastructure: RPC and indexer providers

Your application needs to send RPC calls somewhere. The options are: TronGrid (the most widely used hosted service for TRON), third-party RPC providers, or your own full node. Each has trade-offs in cost, latency, rate limits, and the indexer features they expose on top of raw chain data.

Go to RPC and indexer providers


Cross-chain and Layer 2

For cross-chain workflows and Layer 2, see:

  • BTTC — TRON's Layer 2 — bridging TRON ↔ Ethereum ↔ BSC through BitTorrent Chain
  • Ecosystem — third-party bridges, oracles, DeFi protocols

This Integration chapter does not duplicate that material.


Common building blocks

Every role here depends on a small set of TRON-specific concepts. If you haven't read these yet, do that first:


Related resources

  • Tracks by role — eight role-based reading tracks (exchange, wallet, DApp, smart-contract, SR, RPC, hardware wallet) plus one-liners for cross-chain, AI, DeFi, token, NFT, and scripting roles
  • Tools and SDKs — TronWeb, Trident, GoTron SDK, TronBox, and the SDK decision matrix
  • Node operations — running your own full node
  • Ecosystem — DeFi, BTTC, oracles, community projects