Tron chain ID, RPC URL and network config

Last updated: September 23, 2026

Tron network identifiers

The chain ID is signed into every transaction (EIP-155); the network ID is what net_version reports. They are separate values that happen to match on most chains — see chain ID vs network ID and the chain ID glossary entry.

Tron RPC URLs

Public-endpoint limits are as each operator publishes them, checked 23 September 2026.

Plans and per-category rate limits: pricing. Network overview: Tron RPC; method reference: Tron documentation.

Tron config for viem, ethers, Hardhat and Foundry

import { createPublicClient, defineChain, http } from "viem";

export const tron = defineChain({
  id: 728126428,
  name: "Tron",
  nativeCurrency: { name: "TRX", symbol: "TRX", decimals: 18 },
  rpcUrls: { default: { http: ["https://triport.io/r/<API_KEY>/tron"] } },
});

export const client = createPublicClient({ chain: tron, transport: http() });

import { JsonRpcProvider, Network } from "ethers";

const network = Network.from({ name: "tron", chainId: 728126428 });
export const provider = new JsonRpcProvider("https://triport.io/r/<API_KEY>/tron", network, { staticNetwork: network });

// hardhat.config.ts
export default {
  networks: {
    tron: { url: "https://triport.io/r/<API_KEY>/tron", chainId: 728126428 },
  },
};

# foundry.toml
[rpc_endpoints]
tron = "https://triport.io/r/<API_KEY>/tron"

curl https://triport.io/rpc/tron \
  -H "x-token: <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Keys in URLs vs headers

A keyed URL is the same credential as a header, in a less private place: it lands in shell history, CI logs and screenshots. Use it only where a header is impossible (wallets, hardhat.config, foundry.toml), send x-token from server code, and rotate a key that leaked.

Verify you are on Tron mainnet

Call eth_chainId first. It must return 0x2b6653dc — a client whose configured chain ID disagrees with the reply refuses to connect, which explains most failures when adding a network by hand.

curl https://triport.io/rpc/tron \
  -H "x-token: <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Sources: the chain's own documentation and the CAIP-2 namespace specs cited in the tables above; EVM chain IDs come from Triport's chain registry and match them.