# TronLink Developer Documentation

> TronLink is a decentralized wallet for the TRON ecosystem, available as a browser extension and a mobile app. This documentation covers integrating DApps with TronLink across the browser extension, the mobile app (via DeepLink), and AI/agent tooling (MCP servers, CLI, signer SDK).

> Updated: 2026-05-21T14:08:15Z · Commit: e724781c635f

How integration works: TronLink injects a `window.tron` provider into every page, exposing a `tronWeb` instance, a `request` method, and `on` / `removeListener` for events. A DApp detects the wallet via TIP-6963, requests authorization via `eth_requestAccounts` (TIP-1102), then builds, signs, and broadcasts transactions through `tronWeb`. Account/network changes arrive as passive `accountsChanged` / `chainChanged` events.

Networks: Mainnet `chainId` `0x2b6653dc` (EVM `728126428`), Shasta testnet `0x94a9059e`, Nile testnet `0xcd8690dc`. `chainId` values are case-sensitive.

## Getting Started

- [Introduction](introduction/): Overview of TronLink and the TRON ecosystem
- [HD Wallets](hd-wallets/): BIP-32 / BIP-44 hierarchical deterministic wallets and TRON address derivation
- [Start Developing](dapp/getting-started/): End-to-end DApp flow — detect (TIP-6963), authorize (`eth_requestAccounts`), get `tronWeb`, sign and broadcast a TRX transfer

## TronLink Wallet Extension

- [Proactively Request TronLink Plugin Features](plugin-wallet/active-requests/): Connect website (TIP-1102 / EIP-1102), provider discovery (TIP-6963), normal/multi-sig transfer, message signing, `wallet_watchAsset`, switch network (TIP-3326), and legacy `window.tronLink` methods
- [Receive Messages from TronLink](plugin-wallet/passive-messages/): `accountsChanged`, `chainChanged`, `connect`, `disconnect` (TIP-1193) events and legacy 3.x messages
- [Ledger v-field Compatibility](plugin-wallet/ledger-signing-update/): Normalization of the signature `v` byte (`01`→`1c`, `00`→`1b`) for transaction, message, and EIP-712 signing

## DApp Integration

- [General Transfer](dapp/transfer/): Build, sign, and broadcast a TRX transfer
- [Multi-Signature Transfer](dapp/multi-sign-transfer/): `multiSign` with an active permission id
- [Message Signature](dapp/message-signing/): `signMessageV2` for hex-message login verification
- [Stake 2.0](dapp/stake2/): `__options` / `__resource` fields for delegate/undelegate resource transactions

## TronLink App (Mobile)

- [Asset Management](mobile/asset-management/): Adding custom TRC-20 / TRC-721 tokens
- [DeepLink](mobile/deeplink/): `tronlinkoutside://` scheme for open wallet, open DApp, login, transfer, sign transaction, sign message, plus result codes
- [DApp Support](mobile/dapp-support/): In-app DApp Explorer injection (`tronWeb`, `tronLink`, `iTron`)

## AI Support

- [AI Support Overview](ai-support/ai-llms/): Entry point to TronLink's AI/agent tooling and machine-readable resources
- [MCP Server TronLink](ai-support/mcp-server-tronlink/): MCP server exposing on-chain, multi-sig, and GasFree tools
- [TronLink MCP Core](ai-support/tronlink-mcp-core/): Framework library — session manager, capability interfaces, tool definitions, flow recipes
- [TronLink Skills](ai-support/tronlink-skills/): Agent skill set for wallet, token, market, swap, resource, and staking commands
- [MCP TronLink Signer](ai-support/mcp-tronlink-signer/): MCP server wrapping the signer SDK
- [TronLink Signer](ai-support/tronlink-signer/): Standalone signer SDK — connect, sendTrx, sendTrc20, signMessage, signTypedData
- [TronLink CLI](ai-support/tronlink-cli/): Command-line tool for queries, transfers, staking, delegation, and voting

## Reference

- [Networks & Addresses](reference/networks/): chainIds (mainnet/Shasta/Nile), RPC endpoints, explorers, faucets, address formats, units, and common token contracts
- [Glossary](reference/glossary/): Definitions of TRX/SUN, TRC standards, Energy/Bandwidth, TIP/EIP standards, ABI, chainId, and wallet objects
- [Error Code Map](reference/error-code-map/): Horizontal join of DApp provider (EIP-1474), DeepLink (5-digit), MCP (`TL_*`), and CLI exit codes keyed by business meaning, with retryable flags
- [FAQ](reference/faq/): Common integration questions — wallet detection, connection rejection, tronWeb readiness, network switching, resources

## Localized

The site is bilingual. Chinese pages live at the same slugs under `zh/` (served by the mkdocs-material i18n plugin); for single-fetch ingestion, use the Chinese full-text bundle below.

- [llms-full.txt](llms-full.txt) — every English page, single-fetch (built from `docs/llms-full.en.txt`; the `.en` suffix is stripped at deploy)
- [zh/llms-full.txt](zh/llms-full.txt) — every Chinese page, single-fetch (built from `docs/llms-full.zh.txt`; lives under the Chinese locale root)
- [zh/llms.txt](zh/llms.txt) — curated Chinese index (built from `docs/llms.zh.txt`)

Each bundle's first lines record the generating commit SHA, UTC timestamp, page count, and a coarse token estimate. The same page in EN and ZH is a translation pair (same slug minus the language suffix); pages are emitted in the navigation order declared in `mkdocs.yml`.

## Optional

- [TronWeb Documentation](https://tronweb.network/docu/docs/intro): Full `tronWeb` API reference
- [TRON Developer Center](https://developers.tron.network/): TRON network developer documentation
- [TRON Official Site](https://tron.network/)