One release, no new protocols, and a lot of upgrade work underneath — September was a hardening month for Chainstack Self-Hosted. The headline release landed on September 22: v2.64.0 moved Avalanche, World Chain, Mantle, and Plasma deployments onto the client versions their mandatory mainnet upgrades require, fixed a deposit-transaction security issue on OP Stack reth clients, and refreshed client images across the catalog. Elsewhere in the month, is*hosting joined the infrastructure partners where Self-Hosted can be pre-installed straight from server setup.
Upgrade readiness: Avalanche, World Chain, Mantle, and Plasma
A missed mandatory upgrade is the fastest way to take a self-hosted node off the network, so v2.64.0 moved the affected deployments to the client versions they need. Avalanche, World Chain, and Mantle deployments now run the versions required for the Helicon, Karst, and Elysium hardforks. Karst activated on World Chain mainnet on September 21 at 12:00 UTC and Helicon on Avalanche mainnet on September 22 at 15:00 UTC; nodes on older client versions diverge from the network once an upgrade activates. Plasma deployments now configure the Aquila protocol upgrade automatically; Aquila was already live on Plasma testnet and was scheduled to activate on mainnet at block 33,300,000.
| Protocol | Upgrade | Client in the catalog |
|---|---|---|
| Avalanche | Helicon — mainnet activation on September 22, 15:00 UTC | AvalancheGo v1.15.0 (Mainnet and Fuji) |
| World Chain | Karst — mainnet activation on September 21, 12:00 UTC | World-Chain v2.4.3 + OP-Node v1.19.7 |
| Mantle | Elysium | Mantle-Geth v1.6.3 + Mantle-Node v1.6.3 |
| Plasma | Aquila — mainnet at block 33,300,000 | Reth v1.11.3 + PlasmaBFT v1.1.0 |
Breaking RPC changes to check before you upgrade
Three of the updated clients change RPC behavior, so check your integrations before you upgrade existing nodes:
- Avalanche — Helicon removes the
admin,warp, andpersonalJSON-RPC namespaces and several debug methods from the C-Chain API, and changes what thelatestandsafeblock tags resolve to. The full list of removed methods and the new tag behavior are in the Avalanche Helicon network upgrade guide. - OP Stack — the
optimism_syncStatusresponse no longer includescross_unsafe_l2. If a dashboard or health check reads that field, update it. - Starknet — Pathfinder now disconnects WebSocket clients that stop answering keepalive pings, so make sure your client responds to them.
Security fix and client updates
The same release fixes a deposit-transaction security issue on OP Stack reth clients — if you run OP Stack deployments on reth, this is the upgrade to take. It also updates client images across the catalog for compatibility and reliability, including Sui, Arbitrum, Starknet, TRON, Sonic, Tempo, and Solana. Here is where those clients stand in the supported deployments catalog:
| Protocol | Client in the catalog |
|---|---|
| Sui | Sui-Node v1.79.1 (Mainnet), v1.80.0 (Testnet) |
| Arbitrum | Nitro v3.11.4 |
| Starknet | Pathfinder v0.24.0 |
| TRON | Java-Tron GreatVoyage-v4.8.2.2 (Mainnet) |
| Sonic | sonicd v2.2.2 |
| Tempo | Tempo v1.14.0 |
| Solana | Agave v4.2.2 |
is*hosting joins as an infrastructure partner
Chainstack Self-Hosted is now available on is*hosting, a bare-metal provider with dedicated servers in five locations (plus VPS and storage across 40+). Pick your hardware, choose Ubuntu 24.04 + Chainstack as the OS, and Chainstack’s tooling is preinstalled from first boot. Code CHAINSTACK20 takes 20% off your first dedicated server purchase on is*hosting. is*hosting joins Vultr, Hostkey, Velia, Serverside, and BreezeHost on the trusted infrastructure partners list — see the partnership announcement for the details.
Solana is the workload where hardware choice matters most, and is*hosting’s Solana-tagged bare-metal configurations are built for it. Our step-by-step guide, How to run a self-hosted Solana node on is*hosting, walks through picking the right server, installing Self-Hosted, and deploying an Agave node from the Control Panel.
Two new reads from September:
- How to run a self-hosted Solana node on is*hosting — a step-by-step guide to deploying a self-hosted Solana RPC node on is*hosting bare metal: real Agave hardware sizing, Control Panel setup, and the partner discount code.
- How much does it cost to self-host a blockchain node in 2026 — Bitcoin, Robinhood Chain, and Solana compared: hardware, bandwidth, and hosting costs, plus the engineering time that actually decides the bill.
Try Chainstack Self-Hosted
That’s it for September. Want the same node operations layer on infrastructure you control, on hardware from the partner of your choice? Get started with Chainstack Self-Hosted and deploy your first node with monitoring, updates, and self-healing.
Read more
Full September changelog:
From the blog:
- Introducing Chainstack’s partnership with is*hosting
- What we shipped to Chainstack Self-Hosted in August
Docs: