TON Blockchain v6.0.9

Release Date: August 27, 2026 Tags: ENDPOINTS, CONFIGURATION, RELIABILITY

Overview

An endpoint-configuration release. TON can now be pointed at several RPC endpoints and move reads to the next one when an endpoint fails, and the name of the endpoint setting it reads is now worked out from the TON_NETWORK value itself.

That second change is the one to look at before you upgrade. A TON_NETWORK value that is not spelled exactly used to fall through harmlessly to the mainnet endpoint; it now sends TON looking for a setting nobody has set. Check the value in your .env first — see Upgrade Notes.

Nothing has been renamed and no new setting is required. An install whose TON_NETWORK is exactly mainnet or exactly testnet, or which has never set it, carries on unchanged with one endpoint. Requires Core v6.7.3.

Update Instructions

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

There is no database change. If TON_NETWORK is set in your .env, read the Upgrade Notes before you restart.

Upgrade Notes

Check how TON_NETWORK is spelled, before upgrading

TON works out the name of its endpoint setting from the TON_NETWORK value, so that value now has to be spelled exactly. Until now anything that was not literally testnet fell through to the mainnet pair, so a misspelling such as "mainet" or "prod" was harmless. It no longer is: an unrecognised value makes the platform look for a setting that does not exist, find nothing, and dial the free public toncenter.com endpoint instead of the TON node you configured. A capitalised "Testnet" or "TESTNET" is sharper still — it now selects your TON_TESTNET_RPC endpoint where it previously used TON_MAINNET_RPC, moving deposit polling and balance reads onto a different network, while the API key is still taken from TON_MAINNET_RPC_API_KEY.

• Changed the endpoint lookup, which now builds the setting name from the TON_NETWORK value rather than treating everything that is not testnet as mainnet.
• Before upgrading, open your .env and confirm TON_NETWORK reads exactly mainnet or exactly testnet in lower case, or leave it unset. Correct anything else.
• MAINNET and Mainnet are still fine and still resolve to TON_MAINNET_RPC — only the lower-case spelling of testnet matters.
• TON_MAINNET_RPC, TON_TESTNET_RPC and both API-key settings behave exactly as they always have.

Added

Several TON endpoints, and failover between them

• Added support for more than one RPC endpoint, with reads moving to the next one when an endpoint fails or rate-limits. Put several URLs, comma separated, in the key you already use — TON_MAINNET_RPC or TON_TESTNET_RPC, whichever TON_NETWORK selects — or list them in the new TON_MAINNET_RPC_FALLBACK / TON_TESTNET_RPC_FALLBACK.
• What fails over is reads: deposit scanning, transaction history and balance lookups. Withdrawals deliberately do not — the funding check, the broadcast and the confirmation polling all stay on the single endpoint that last answered a read, because re-sending an ambiguous broadcast to a second node is how one withdrawal becomes two.
• Worth knowing before you add a second endpoint: the toncenter credential in TON_MAINNET_RPC_API_KEY is sent to every endpoint in the list, and a fallback cannot yet be given a key of its own.
• One URL still means one attempt and the same error you got before, and an install that has set nothing still dials the same toncenter endpoint it always did.