TRON is an open protocol, and multiple independent networks implement it. TRON has one Mainnet (production) and two testnets — Shasta and Nile — maintained by the TRON community. Anyone can also run a private network, typically for development or CI.

This page lists the connection endpoints for each network, helps you decide which to use, and shows how to reach the network through TronGrid, third-party RPC providers, or your own Fullnode.

📘

Prerequisites

• Accounts and keys

Choosing a network

If you are new to TRON, start with Shasta. Shasta is the default environment for most tutorials and examples, and it has a public TronGrid endpoint. Switch to Nile when you specifically need to test upcoming features, parameter changes, or governance proposals.

Mainnet

The production network where real TRX value is transacted, secured by the active 27 Super Representatives and the broader staker community.

Public seed nodes

These Mainnet addresses are public seed nodes for P2P peer discovery when running your own Fullnode. Port 18888 is the P2P listen port, not an HTTP or gRPC query endpoint.

3.225.171.164:18888
52.53.189.99:18888
18.196.99.16:18888
34.253.187.192:18888
18.133.82.227:18888
35.180.51.163:18888
54.252.224.209:18888
18.231.27.82:18888
52.15.93.92:18888
34.220.77.106:18888
13.127.47.211:18888
13.124.62.58:18888
13.229.128.108:18888
35.182.37.246:18888
34.218.41.201:18888
15.207.144.3:18888
13.124.142.115:18888
15.207.147.245:18888
13.231.82.66:18888

⚠️

Recommended usage

• Configure these addresses as seed nodes in your Fullnode's config.conf for peer discovery.
• To help keep the public seed nodes' P2P service stable, avoid using their HTTP or gRPC APIs as chain-data query endpoints; use your own Fullnode or a published API endpoint from an RPC provider instead.

These IPs are stable but not guaranteed permanent — for the authoritative current list, see the java-tron config repo.

For more on running your own node, see Deploying a node.

Third-party RPC providers

Beyond TronGrid, several third-party providers offer hosted RPC access to TRON Mainnet. Each has its own pricing, free-tier limits, and feature set — check the linked page for current details before depending on one in production.

Provider details change. The TRON developer documentation does not endorse a specific provider — pick based on your region, SLA, pricing, and the features you need (archive access, WebSocket subscriptions, dedicated nodes, etc.).

Shasta Testnet

Shasta closely mirrors the Mainnet's features and governance proposals. Its network parameters and software versions are kept in sync with the Mainnet, providing a highly realistic environment for final testing before deploying to production.

📘

Shasta does not currently accept new node operators.

Nile Testnet

Nile is a forward-looking testnet where new features and governance proposals are launched first for developers to experience. Consequently, its codebase is typically ahead of the Mainnet — use Nile to try upcoming features before they reach Mainnet.

Third-party RPC providers for Nile

Most third-party providers in the Mainnet table above serve only Mainnet. Chainstack is one exception — it provides managed RPC access to the Nile testnet alongside its Mainnet support. For other providers, plan on using TronGrid or running your own Nile node.

Private networks

For local development, integration testing, and CI workflows, you can run a fully self-contained TRON network with its own genesis block. A private network gives you complete control over chain parameters, fast resets, and no faucet dependency, at the cost of having no other peers.

For setup, see TRON private chain.

Related resources

• Getting testnet tokens — Get TRX on Shasta or Nile
• Deploying a node — Run your own Fullnode
• TRON private chain — Run a private network
• TronGrid — TronGrid hosted node service