Tron Blockchain v6.1.3

Release Date: August 11, 2026 Tags: WITHDRAWALS, LEDGER, ACCOUNTING, TRON, TRX, TRC20, BUG-FIXES, ECOSYSTEM

Overview

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

This release is a single correction, and it lands in the platform's record of its own money. When a customer's own Tron address cannot fund their withdrawal — normal when their balance arrived from P2P or another off-chain credit — the addon sends from one of your other custodial Tron addresses and records what that address lent. That record is what keeps the same address from being chosen and drained past what it holds. On an address the platform did not derive itself the record was rejected, and the failure was caught and written only to the log: the withdrawal completed, and nothing on the platform showed which address had paid for it.

Draws already taken are not reconstructed by updating, and your Tron custody figures may read high because of them. Read Upgrade Notes before you update.

Requires the Ecosystem addon and Core v6.6.3.

Update Instructions

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

No schema change. No new tables, no seeders, nothing to configure.

Upgrade Notes

An address that funded someone else's withdrawal still reads as fully funded

Updating stops new draws going unrecorded. It cannot reconstruct the ones already lost: the amount owed and the decrement of the lending address's tracked balance were written as one step, and that step was abandoned whole, so nothing survives to rebuild them from. Until you correct those addresses by hand, the platform goes on counting coins that have already left them.

• If your backend log carries Tron errors about failing to update the ledger for an alternative wallet, you were affected. Every such line is one withdrawal that drew on another address without recording it.
• Compare the on-chain balance of your Tron custodial addresses against the balances the platform records for them. An address that lent reads higher on the platform than it holds on-chain, by the amount it lent, and correcting its recorded balance is what takes it out of the running.
• Your Ecosystem custody figures in Admin subtract recorded draws to work out what the platform can still settle, so a draw that was never recorded makes TRX and TRC20 coverage read higher than it is. Treat those figures as optimistic until you have checked the addresses.
• An affected address stays eligible to fund the next withdrawal, and each one it funds draws it down further while the platform's figure for it stands still. Once its real on-chain balance runs out, the withdrawal that picks it fails at the point of sending — a customer's withdrawal, failing over a shortfall on an address that is not theirs.
• No customer balance was altered by any of this, and no withdrawal was short-paid. What went missing is the platform's own record of where its on-chain funds sit.

Fixed

A Tron withdrawal funded by another address left no record of the loan

When a customer's own Tron address cannot fund their withdrawal — it holds too little on-chain, or on a token withdrawal it has no usable key at all — the addon searches your custodial Tron addresses for one that can, and sends from that. It then records what the lending address paid out, and the search subtracts what an address is already owed before weighing it for the next withdrawal, so an address is not drawn on beyond what it really holds. That record is filed against the lending address under the derivation index the address was created with, which the record requires but the address itself does not have to carry, and which is empty on addresses the platform did not derive that way — the P2P-credited and legacy addresses this search deliberately allows through. Where it was empty the record was refused, and because the record and the decrement of that address's tracked balance were written as one step, the refusal discarded both. The error was caught and logged, the withdrawal reported success, and the coins left the lending address while it stayed exactly as eligible as before.

• Fixed both the TRX and the TRC20 withdrawal paths to file the draw under a derivation index of zero when the lending address has none — the same value the rest of the platform already writes where there is no derivation index. The search that picks a lending address does not match on that index, so it reads the record either way.