Twelve releases, seventeen new protocols, and forty-one new deployment targets — August was Self-Hosted’s biggest month yet for network coverage. Of those forty-one, thirty-two came from the seventeen brand-new protocols; the other nine were testnets added for protocols Self-Hosted already supported. The headline release landed on August 24: Solana joined the deployment catalog on Mainnet and Devnet.
Solana: Mainnet and Devnet on Self-Hosted
Solana joined Ethereum, Arbitrum, Base, Robinhood Chain, TRON, Bitcoin, and Hyperliquid on Chainstack Self-Hosted’s protocol list on August 24 — non-voting RPC nodes on the Agave client, deployable the same way as every other protocol on the platform: pick Solana in the deployment wizard, pick Mainnet or Devnet, deploy. The addition brought Self-Hosted to 30 protocols across 60 network deployments. Validator support is on the roadmap, following the same pattern as other protocols on the platform.
| Network | Client | vCPU | RAM | Storage |
|---|---|---|---|---|
| Mainnet | Agave v4.2.0 | 16 | 256 GiB | ~3.5 TB |
| Devnet | Agave v4.2.0 | 8 | 64 GiB | ~2.2 TB |
Both networks bootstrap from a pre-built snapshot rather than syncing from genesis — plan for roughly 2× the storage figure above during deploy, since the compressed archive and the extracted state briefly coexist. Solana is also less forgiving of undersized infrastructure than most chains on the platform: Agave’s own hardware guidance calls for high clock-speed CPUs, up to 512 GB of RAM once account indexing is enabled, and accounts and ledger split across separate NVMe drives. Self-Hosted ships pre-installed on several trusted infrastructure partners if you’d rather not source that hardware cold — see the announcement post for the current list.
📖 For a deeper walkthrough — MEV and trading workloads, the account-indexing tradeoffs, where to source snapshots — see Running your own Solana node.
Sixteen more protocols on the deploy menu
Solana wasn’t alone. August also added sixteen other protocols to the deploy menu — the widest single-month protocol expansion since Self-Hosted launched.
| Protocol | Highlights | Sizing |
|---|---|---|
| Avalanche | Single AvalancheGo node serving the whole Primary Network (C/X/P-Chain), Mainnet + Fuji | 4 vCPU, 16 GiB, 300–400 GB |
| Arc | Paired execution + consensus, non-validator, Testnet (Circle’s USDC-native L1) | 8 vCPU, 32 GiB, ~315 GB |
| World Chain | Joins the OP Stack family, Mainnet + Sepolia | 6–12 vCPU, 24–48 GiB, 100 GB – 1.3 TB |
| XRP Ledger | Single xrpld node, non-validator full mode, HTTP + WebSocket, Mainnet + Testnet | 4–8 vCPU, 16–32 GiB, 50 GB |
| Sonic | Single sonicd node, Mainnet + Testnet | 4–8 vCPU, 32–64 GiB, 800 GB – 2.5 TB |
| Stable | CometBFT consensus + embedded EVM in one stabled process, Mainnet + Testnet | 4 vCPU, 16 GiB, 50–200 GB |
| opBNB | OP Stack settling to BNB Smart Chain rather than Ethereum, Mainnet + Testnet | 6–12 vCPU, 24–48 GiB, 500 GB – 2 TB |
| Berachain | Bera-Reth execution + Beacond consensus over CometBFT, Mainnet + Bepolia | 6–8 vCPU, 24–36 GiB, ~165–250 GB |
| Cronos | Cosmos SDK chain with an embedded EVM in one cronosd process, Mainnet + Testnet | 4–8 vCPU, 16–32 GiB, 50–100 GB |
| Blast | OP Stack on the Pebble storage backend, Mainnet + Sepolia | 6 vCPU, 24 GiB, 200–500 GB |
| Mantle | OP Stack, connects over the network’s static peers, Mainnet + Sepolia | 6 vCPU, 24 GiB, 300–600 GB |
| BNB Smart Chain | Single reth-bsc node, pruned mode, Mainnet + Testnet | 4 vCPU, 16 GiB, 900 GB – 5.5 TB |
| Kaia | Single kend node, native klay namespace, Mainnet + Kairos | 4–8 vCPU, 16–32 GiB, ~1.2–2.75 TB |
| Ronin | First OP Stack rollup on Self-Hosted reading batch data from EigenDA instead of Ethereum calldata, Saigon testnet | 7 vCPU, 28 GiB, 220 GB |
| Hyperliquid | Single node, rolling 48-hour log pruning, Testnet + Mainnet | 4–8 vCPU, 16–32 GiB, 250–300 GB |
| Stellar | Paired stellar-core + stellar-rpc, Mainnet + Testnet | 4 vCPU, 16 GiB, 64–400 GB |
Every new deployment ships with the same Chainstack-managed control plane every other Self-Hosted protocol gets: self-healing, in-console monitoring, tracked configuration revisions, and one-click deploy. Full per-chain sizing and endpoint configuration in the supported deployments catalog.
Nine more deployment targets on protocols you already run
Not every August addition was a new protocol. One release — v2.53.0, August 20 — rounded out testnet coverage for protocols Self-Hosted has supported on mainnet since June, plus completed the Hyperliquid Mainnet/Testnet pair covered above:
- Base Sepolia, Optimism Sepolia, Zora Sepolia, Unichain Sepolia — the OP-Stack family’s mainnets have been on the deploy menu since June; their Sepolia testnets landed in August
- Polygon Amoy — Polygon PoS Mainnet has been available since June
- Starknet Sepolia — alongside the Starknet Mainnet added in June
- TRON Nile — alongside TRON Mainnet, also from June
- Bitcoin Signet and Bitcoin Testnet4 — alongside Bitcoin Mainnet, from June
The same release also let snapshot-based bootstrapping accept an already-unpacked archive as a data source, so a node with unpacked snapshot data on hand can skip the extract step.
Operator quality-of-life and reliability work
- Grafana in the Control Panel — when you install the monitoring stack, the Control Panel now proxies Grafana at
/monitoring/, so node dashboards open in the same interface as the deployments they describe. The bundled Kubernetes node and pod dashboards also got a rendering fix earlier in the month, after panels were coming up empty. - Graceful node shutdown — node workloads now shut down with a client-appropriate grace period instead of a fixed timeout, reducing the chance of a corrupted database after a restart, a rescale, or an upgrade.
- OP-Stack and Ronin Saigon reliability — OP-Stack execution clients no longer need the sequencer HTTP endpoint to be reachable for transaction pool admission, and Ronin Saigon’s execution client now gets a trusted peer, removing a source of sync stalls.
- Client image updates ahead of Arc’s hardfork — Sui, Arc, Polygon, and Tempo node images were updated for protocol compatibility and reliability, and the Stellar RPC image was updated on both networks. The Arc update specifically gets ahead of the Zero8 hardfork scheduled for September 3, 2026.
Two new reads from August:
- Running your own Solana node: infrastructure for MEV and trading — who actually self-hosts Solana and why, what it really costs against managed RPC, and when running Agave yourself is worth it versus when it isn’t.
- Running your own Polygon node: infrastructure for prediction markets — the real cost of running the paired Bor + Heimdall setup yourself, why prediction markets like Polymarket push Polygon infrastructure at scale, and when self-hosting pays off.
Try Chainstack Self-Hosted
That’s it for August. Want the same node operations layer on infrastructure you control, across a lineup that just grew by seventeen protocols? Get started with Chainstack Self-Hosted and deploy your first node with monitoring, updates, and self-healing.
Read more
Full August changelog:
From the blog:
Docs: