Tron node
A Tron node for USDT payments. A private HTTP API, upgrades handled.
A Tron node is a java-tron full node that verifies every block and talks to nobody but you. Yours lives on a server sized for Tron, whose official minimum is a 3 TB SSD. No shared limits on your deposit checks.
- Full
- $139/mo
- Ready
- 24 h
02Node type
What a Tron full node keeps and serves.
One node type, the full java-tron node. The useful question is which API your code speaks.
Full node
$139/mo
- Keeps
- The Tron chain and its current state, as a java-tron FullNode
- Answers
- The Tron HTTP API: balances, blocks, receipts, contract calls and broadcasting transactions
- Reads
- TRC-20 transfers, including USDT, through contract calls and events
- Disk
- The official minimum is a 3 TB SSD, and 3.5 TB or more is recommended
Which API will you call?
Most Tron apps use the HTTP API. JSON-RPC exists, but it is off by default and speaks hex addresses only.
Sources: java-tron docs, installing java-tron, checked October 2026; java-tron docs, HTTP API, checked October 2026
03How it works
How a Tron node works: one program, three ways in.
java-tron checks the chain and offers several interfaces. Your endpoint uses the HTTP one.
java-tron
The reference Tron node. It checks blocks and keeps state.
HTTP API
Calls such as /wallet/getnowblock. This is what your endpoint speaks.
gRPC, port 50051
A second interface that is not exposed by default.
JSON-RPC, optional
Ethereum-shaped calls on port 8545. Off unless switched on.
Tron has three interfaces on one program. They do not behave alike, and they do not share defaults.
Your endpoint uses the HTTP API, which is what TronWeb and most payment code expect.
Peers connect to the node on their own. You never open a port to them yourself.
04Know the field
A Tron node is big, and it has to stay current.
java-tron is the reference client. The real gaps are disk and upgrades, not software choice.
The snapshot figure is for a full snapshot. A lite node keeps state only, so it cannot serve history.
FullNode
- Full
- A 3 TB SSD minimum, 3.5 TB or more recommended, and 100 Mbps. Linux and macOS only.
- Source
- java-tron install docs
Lite FullNode
- Full
- Since GreatVoyage-v4.1.0. A smaller database with state data only, so historical queries come back as plain text.
- Source
- java-tron HTTP API docs
Snapshot, LevelDB or RocksDB
- Full
- Network snapshot data exceeds 2 TB. The two database engines are not interchangeable, though a conversion tool exists.
- Source
- java-tron backup docs
GreatVoyage-v4.8.2.3
- Full
- Released 30 September and flagged as a mandatory upgrade, covering smart contract storage access and BN128 pairing speed.
- Source
- GitHub releases
Chainstack (third party) puts the steady state near 3 TB and advises 4 to 5 TB. The official minimum is the safer anchor for planning.
Sources: java-tron docs, installing java-tron, checked October 2026; java-tron docs, backup and restore, checked October 2026; java-tron releases (GreatVoyage-v4.8.2.3 released 30 September), checked October 2026; GetBlock, how to run a Tron node (third party), checked October 2026; Chainstack, running your own TRON node (third party), checked October 2026
05Tron, specifically
Six Tron facts that decide how your code behaves.
Anyone who has used Ethereum tools on Tron has met at least one of these.
Upgrades are mandatory
GreatVoyage-v4.8.2.3 is flagged mandatory. Chainstack says the network upgrades several times a year, and a node that misses one drifts off the chain.
JSON-RPC starts switched off
The setting node.jsonrpc.httpFullNodeEnable is off by default. When on, it listens on 8545, or 8555 for the solidity node.
Addresses are hex
JSON-RPC rejects addresses that start with T. The HTTP API takes hex addresses unless you pass visible=true.
Logs have a 5000-block window
getLogs covers at most 5000 blocks and 1000 addresses. Batches stop at 100 calls and replies at 25 MiB.
Errors arrive as success
Most HTTP API errors return status 200 with the error in the body, so check the body, not the status.
Sync stalls have names
The official troubleshooting page covers slow or stopped sync and the different resultCode stop. It suggests raising vm.maxTimeRatio from 20 to 50 on slow hardware.
Sources: java-tron releases (GreatVoyage-v4.8.2.3 released 30 September), checked October 2026; Chainstack, running your own TRON node (third party), checked October 2026; java-tron docs, JSON-RPC API, checked October 2026; java-tron docs, HTTP API, checked October 2026; Tron developers, node operations issues, checked October 2026
06Who rents one
Who rents a Tron node.
Tron carries a large share of stablecoin payments, and these teams live there.
USDT deposit detection
Exchanges and payment gateways match incoming TRC-20 transfers to orders and sweep them on.
Wallet backends
Broadcast transactions and read receipts quickly, from an endpoint that is not shared.
Indexers and trackers
Read TRC-20 transfers and contract events for dashboards and alerts.
Teams hitting public limits
When a public API starts throttling a busy app, a node of your own removes the cap.
07Price check
Allnodes charges more than twice as much for Tron.
Allnodes lists a dedicated Tron full node, so the bar chart compares one plan with one plan.
Full node
Allnodes: the cheapest dedicated plan on its Tron pricing page.
Source: Allnodes Tron pricing, checked October 2026
Chainstack
$199 plan, plus compute
TRON is on its dedicated list, behind a Pro plan or higher, with compute and storage billed on top.
Chainstack protocols and networks, checked October 2026
NOWNodes
From €1,000 a month
A blog price shared by Ethereum, BNB and Tron. Its dedicated page itself shows no number.
NOWNodes blog on dedicated nodes, checked October 2026
You save each month
$181 full
against the Allnodes list price above
08What you get
Choose your Tron node term.
Pick the node type and how long to prepay. The price updates as you choose.
Your Tron node
Term
- A dedicated server sized for Tron
- java-tron, with one private HTTP API endpoint
- A backup node, included
- A private endpoint on nodes.herorpc.com
- Your server logins
- No setup fee, ready within 24 hours
$139
a month, full node
Billed monthly
Pay in BTC, ETH, USDT, USDC, BNB, SOL, TRX, LTC, DOGE or XMR.
10Questions
Tron node questions
Real questions from node operators, answered plainly.
What are the Tron node requirements?
The official install docs list a 3 TB SSD as the minimum and 3.5 TB or more as recommended, with a 100 Mbps connection, on Linux or macOS.
Why does my Tron node sync slowly or stop?
The official troubleshooting page covers slow or stopped sync and the `different resultCode` error that halts it mid-block. For slow hardware it suggests raising `vm.maxTimeRatio` from 20 to 50.
Is JSON-RPC on by default on a Tron node?
No. In java-tron it is off unless you switch it on. Your endpoint speaks the Tron HTTP API.
Which Tron API should I use?
The HTTP API for most apps. JSON-RPC needs hex addresses and does not broadcast transactions. gRPC is a third option that is not exposed by default.
Why does my Tron call return 200 with an error?
Most HTTP API errors come back with status 200 and the error in the response body. Read the body.
What is a lite Tron node?
A lite FullNode keeps state only and has a much smaller database. Historical queries return plain text, so it cannot serve history.
Can I check USDT payments with it?
Yes. Your node serves the same chain data as any Tron node, so you can read TRC-20 USDT transfers and confirm transactions through the HTTP API.
Will TronWeb work with it?
Libraries that let you set a custom full node URL, such as TronWeb, can point to your endpoint.
How do I send calls to my Tron node?
Your dashboard shows the endpoint. Add the HTTP API path after the key in the URL, for example /wallet/getnowblock.
How much is a Tron node each month?
$139 a month for the node and its backup, without a setup fee.
When can I start using my Tron node?
Within 24 hours of payment. The first sync of a Tron node is slow, and it is finished before you get your endpoint.
A Tron node that keeps up with every upgrade.
$139 a month covers the node, its backup and every mandatory upgrade. Live within 24 hours.