Networks

Mainnet, Shasta, and Nile testnet connection details, and how to choose the right one for your work.

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


Choosing a network

Use caseNetworkTRX cost
ProductionMainnetReal TRX
First-time learning, tutorials, and final pre-production testingShasta TestnetFree (faucet)
Trying upcoming features, parameter changes, and governance proposalsNile TestnetFree (faucet)
Local development or CIPrivate chainNone (own genesis)

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.

ServiceEndpoint
Block explorerTronScan
HTTP API (TronGrid)https://api.trongrid.io
JSON-RPChttps://api.trongrid.io/jsonrpc
gRPC (Fullnode)grpc.trongrid.io:50051
gRPC (Solidity)grpc.trongrid.io:50052
Database snapshotsMainnet snapshots

Public seed and Fullnode peers

These 19 public Mainnet nodes serve a dual role: they are seed nodes for peer discovery when running your own Fullnode, and they expose Fullnode endpoints (port 18888) so you can also reach them directly for occasional queries or emergency fallback.

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

  • Primary use: Configure these as seed nodes in your own Fullnode's config.conf for peer discovery.
  • Acceptable secondary use: Occasional verification queries, ad-hoc debugging, or emergency fallback when your primary infrastructure is down.
  • Do NOT build production applications, indexers, or high-traffic services on top of these endpoints. They have limited throughput and are shared by the entire community — sustained or frequent traffic from a single source degrades the network for everyone.
  • For production workloads, run your own Fullnode (recommended) or use a dedicated RPC provider (see the third-party providers table below).

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.

ProviderCoverageNotes
AnkrMainnetMulti-chain RPC and indexer; free tier with paid upgrades
GetBlockMainnetMulti-chain; shared and dedicated nodes; API key required
QuickNodeMainnetMulti-chain RPC; free tier with usage caps
NOWNodesMainnetMulti-chain; API key required
ChainstackMainnet, Nile testnetMulti-chain managed RPC; the only listed provider currently serving a TRON testnet
TatumMainnetMulti-chain RPC + SDK
TronQLMainnetTRON-native provider
AlchemyMainnetMulti-chain RPC and indexer

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.

ServiceEndpoint
Websitehttps://www.trongrid.io/shasta
Block explorerhttps://shasta.tronscan.org
FaucetGet Shasta TRX
HTTP APIhttps://api.shasta.trongrid.io
JSON-RPChttps://api.shasta.trongrid.io/jsonrpc
gRPC (Fullnode)grpc.shasta.trongrid.io:50051
gRPC (Solidity)grpc.shasta.trongrid.io:50052
📘

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.

ServiceEndpoint
Websitehttp://nileex.io
Block explorerhttps://nile.tronscan.org
FaucetGet Nile TRX
HTTP APIhttps://api.nileex.io
HTTP API (TronGrid)https://nile.trongrid.io
JSON-RPChttps://api.nileex.io/jsonrpc
gRPC (Fullnode)grpc.nile.trongrid.io:50051
gRPC (Solidity)grpc.nile.trongrid.io:50061
Network statushttp://nileex.io/status/getStatusPage
Database snapshotsNile snapshots

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