Solana Blockchain v6.1.2

Release Date: August 27, 2026 Tags: SOLANA, RPC, CONFIGURATION, ENVIRONMENT, FAILOVER, DEPOSITS, WITHDRAWALS, WALLETS, ECOSYSTEM, NETWORK

Overview

An environment-variable release. The Solana wallet service now dials the endpoint named in SOL_<NETWORK>_RPC instead of Solana's free public cluster, so a node you pay for can finally carry your deposits and withdrawals — and several endpoints can be listed, with reads moving between them on their own.

There is one thing to do before you restart, and it applies whether or not you have ever touched a Solana setting: set SOL_NETWORK=mainnet. A new creditability rule in core reads that variable, and unset it means devnet on Solana alone — which withdraws SOL from your deposit screen until you correct it. If you have set SOL_<NETWORK>_RPC, most likely because you run the Swap add-on, that value also stops being decoration and starts carrying custodial traffic. Read Upgrade Notes before you upgrade.

Requires Core v6.7.3 and the Ecosystem extension.

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. The endpoint keys are read from your environment file, so a change there needs the restart above.

Upgrade Notes

Set SOL_NETWORK=mainnet before you upgrade, or SOL deposits stop being offered

Core 6.7.3 adds a rule that withholds a deposit address for any chain this deployment cannot actually credit, and for Solana that rule reads SOL_NETWORK. It compares the network recorded on your SOL token rows against the network the Solana service is really on.

Those two variables default in opposite directions. SOLANA_NETWORK, the name the wallet registry used until this release, defaults to mainnet. SOL_NETWORK, which the Solana service has always dialled and which the new rule now reads, defaults to devnet. Solana is the only one of the seventeen chains where an unset value does not mean mainnet.

So an install running Solana on mainnet that never set SOL_NETWORK — because nothing made it necessary — resolves to devnet after upgrading. Its SOL rows say mainnet, the rule sees devnet, they disagree, and SOL stops appearing as a deposit option for every customer. Balances and existing addresses are untouched; no money is lost. New deposits simply cannot be started until the variable agrees.

• Open your .env and set SOL_NETWORK=mainnet if you run Solana on mainnet. Do this before you restart.
• Only mainnet and testnet are recognised. mainnet-beta — the name Solana's own documentation uses — is not one of them, and selects devnet.
• If you deliberately run devnet or testnet, set the value to match your token rows rather than leaving it unset.
• SOLANA_NETWORK is now only a label stamped into wallet address records. It no longer decides anything, so setting it alone will not fix this.

An endpoint you already have set starts carrying deposits and withdrawals

Until this release the Solana wallet service ignored SOL_<NETWORK>_RPC completely. The key was listed on the admin blockchain-requirements screen and honoured by the Swap add-on, but the wallet itself always dialled the public cluster. From this release that key is what deposit scanning, balance reads, and the blockhash and fee reads before a withdrawal dial — so a value that was harmless while nothing read it is now live custodial traffic.

• Before upgrading, look at SOL_MAINNET_RPC — or SOL_TESTNET_RPC / SOL_DEVNET_RPC, whichever matches your SOL_NETWORK.
• If it holds a stale, expired or unreachable URL, point it at a working HTTPS Solana node or clear it. A dead value that cost you nothing while the key was ignored will break Solana deposits and withdrawals once it is read.
• If the key is unset, do nothing. Your install keeps the public cluster it has always used.
• Which key is read follows SOL_NETWORK, and that is unchanged: only mainnet and testnet are recognised. Every other value — unset, or the plausible-looking mainnet-beta — selects devnet, and with it SOL_DEVNET_RPC.
• Only http:// and https:// URLs are used. A websocket URL in the key is ignored, and if nothing in the key parses the public cluster is dialled instead.
• The Solana entry on the admin blockchain-requirements screen still describes this key as display-only. It is not; that screen has not caught up.

Added

Failover across several Solana endpoints

An operator who paid for a dedicated Solana node had no way to make the platform use it. The wallet service built one connection to the free public cluster, which rate-limits under real deposit load, and there was nothing to point anywhere else.

• Added support for several endpoints in SOL_<NETWORK>_RPC, separated by commas, with a further list accepted in SOL_<NETWORK>_RPC_FALLBACK. Reads settle on the fastest endpoint that is answering, move to the next one when it fails, and take an endpoint that has failed three times in a row out of rotation for fifteen seconds — doubling to at most five minutes — before trying it again, with no restart.
• Added a deliberate exception for broadcasting a signed transaction, which is never retried on a second endpoint. A send goes to whichever endpoint the reads before it proved alive, because re-sending a withdrawal that may already have reached the cluster is how one payout becomes two.

Changed

SOL_<NETWORK>_RPC now drives the Solana wallet connection

The key was already on the admin requirements screen and already honoured by the Swap add-on, but the wallet service never read it. It always talked to Solana's free public cluster and could not be pointed anywhere else, so it rate-limited under real deposit load.

• Changed the Solana wallet service to use the endpoint named in SOL_<NETWORK>_RPC — SOL_MAINNET_RPC when SOL_NETWORK is mainnet — for deposit scanning, balance reads, and the blockhash and fee reads that precede a withdrawal. An install that has never set the key keeps exactly the public-cluster behaviour it had before; an install that has set it hands that value its custodial traffic, which is what Upgrade Notes asks you to check.