Tron Blockchain v6.1.4

Release Date: August 27, 2026 Tags: RPC, FAILOVER, RELIABILITY, DEPOSITS, CONFIGURATION, TRON, TRX, TRC20, ECOSYSTEM

Overview

The Tron addon gives your Ecosystem installation TRX and TRC20 custody — deposit addresses, withdrawals and balance tracking on the Tron chain.

This is an environment-variable release. Tron can now be given more than one RPC endpoint and moves its reads to the next one when an endpoint is rate-limited or unreachable. It is opt-in, and it is configured entirely in your environment file: an install that changes nothing keeps its single endpoint and behaves exactly as before, down to the same error messages.

The keys this uses are ones the sample env file has long advertised for every chain, and until now Tron read one url out of them and ignored the rest. If you have already set them, what they hold starts being read the moment you update — and one way of writing them stops the Tron service starting at all. Read Upgrade Notes before you update.

Requires the Ecosystem addon and Core v6.7.3.

Update Instructions

# 1. Update the addon in Admin → System → Extensions
# 2. Restart the backend
pnpm updator

No schema change. No new tables and no seeders. A second endpoint is optional and is configured in your environment file, not in Admin.

Upgrade Notes

Check your Tron endpoint keys before you update

This applies only if you have set TRON_MAINNET_RPC, its Shasta or Nile equivalent, or TRON_MAINNET_RPC_FALLBACK. The sample env file tells operators that every chain accepts more than one endpoint. For Tron that has never been true — the addon took a single url and ignored anything else you put there — so anything beyond the first url has never been exercised. This release starts reading it.

• A list in TRON_MAINNET_RPC written the way the sample env file writes it for the EVM chains — comma, then a space — stops the Tron service starting once you update. It fails with "Invalid TRON RPC URL format", which takes Tron deposit scanning and withdrawals offline. Rewrite it with no space after the comma, or move the extra endpoints into TRON_MAINNET_RPC_FALLBACK, which accepts either form. Do this before you update, not after.
• Anything already sitting in TRON_MAINNET_RPC_FALLBACK was ignored by this addon until today and now carries live Tron reads.
• A value in either key that is not an http(s) url — a websocket url, say — is now discarded in favour of the public TronGrid endpoint, where before it was handed to the Tron client as written. Put an http(s) url there if you want your own node used.
• Once a key holds more than one endpoint, the Blockchain Requirements screen in Admin previews it as blank. The key is still read correctly; the screen only ever shows a single url.

Added

Failover across several Tron endpoints

Give Tron more than one endpoint and a read that is refused, rate-limited or left unanswered is retried on the next one. Endpoints come from TRON_MAINNET_RPC and TRON_MAINNET_RPC_FALLBACK — or the TRON_SHASTA_RPC and TRON_NILE_RPC pairs on those networks — and either key takes several. On a single endpoint there is still exactly one attempt and the same error as before, which is what makes a second endpoint worth adding: a TRC20 transfer whose confirmation read fails is skipped for thirty minutes before the monitor looks at that address again.

• Added endpoint failover across fifteen Tron read paths — TRX and TRC20 deposit scanning, the transaction lookups that turn an observed transfer into a credited balance, TRX and token balance reads, address activation, bandwidth, chain parameters, account resources and energy estimation.
• Added a rest period for a failing endpoint: three failures in a row take it out of rotation for fifteen seconds, doubling on repeat to at most five minutes, after which it returns on its own without a restart.
• Signing and broadcasting a withdrawal are never retried on a second endpoint, and the balance poll that waits for a fee top-up stays on the endpoint the top-up was sent to. A node that rejects a broadcast may still have put it on the network, and re-sending it is how one withdrawal becomes two. Both use whichever endpoint a read last proved healthy.

Changed

An endpoint that is not an http address

A websocket url, or anything else that is not an http or https address, used to be handed to the Tron client exactly as it was written in the environment file, with nothing checking it first.

• Changed entries in the Tron endpoint keys that are not http(s) urls are now discarded, and the addon uses the public TronGrid endpoint rather than an address it cannot dial.