BNB Smart Chain support
BNB Smart Chain (BSC) Mainnet and Testnet are now available as deployment targets, running a single reth-bsc node.- BNB Smart Chain Mainnet — chain ID 56, explorer at bscscan.com
- BNB Smart Chain Testnet — chain ID 97, explorer at testnet.bscscan.com
- Architecture — a single reth-bsc node serves the EVM JSON-RPC and WebSocket APIs, exposing the eth, net, web3, txpool, and debug namespaces
- Storage — the node runs in pruned mode, keeping recent state rather than the full history
- Sync — both networks bootstrap from a pre-built chain snapshot
Kaia support
Kaia Mainnet and the Kairos testnet are now available as deployment targets, running a single kend node.- Kaia Mainnet — chain ID 8217, explorer at kaiascan.io
- Kaia Kairos — chain ID 1001, explorer at kairos.kaiascan.io
- Architecture — a single kend node serves both JSON-RPC and WebSocket, exposing Kaia’s native klay namespace alongside the standard eth, net, web3, and debug namespaces
- Storage — the node runs full sync with full garbage collection, so it retains the state needed to serve current-block queries
- Sync — both networks sync from genesis
Ronin Saigon support
The Ronin Saigon testnet is now available as a deployment target, and is the first deployment to run an OP-Stack rollup on an alternative data-availability layer.- Ronin Saigon — chain ID 202601, explorer at saigon-explorer.roninchain.com
- Architecture — a conduit-reth execution node serves the EVM JSON-RPC and WebSocket APIs, an op-node rollup node derives the chain from Ethereum and drives the execution node over the engine API, and an EigenDA proxy retrieves the rollup’s batch data
- Data availability — Ronin Saigon posts batches to EigenDA instead of Ethereum calldata, so the rollup node reads generic commitments and resolves the underlying blobs through the proxy
- Sync — the execution node bootstraps from a published state export, reaching the chain head without replaying history
Hyperliquid Testnet support
The Hyperliquid testnet is now available as a deployment target, running a single node.- Hyperliquid Testnet — chain ID 998, explorer at app.hyperliquid-testnet.xyz/explorer
- Architecture — a single node serves the EVM JSON-RPC API
- Storage — the node prunes its logs on a rolling 48-hour window, keeping disk use flat over long runs
Monitoring dashboards 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. Installations that skip monitoring are unaffected — the proxy route only renders when Grafana is deployed.
See System requirements for the full specification and Supported clients and protocols for the deployment catalog.