Skip to main content
This release adds Blast and Mantle as deployment targets, each covering Mainnet and Sepolia. Both are OP-Stack rollups, so every deployment pairs an execution node with a rollup node that derives the chain from Ethereum.

Blast support

Blast Mainnet and Blast Sepolia are now available as deployment targets, pairing a blast-geth execution node with a blast-node rollup node.
  • Blast Mainnet — chain ID 81457, explorer at blastscan.io
  • Blast Sepolia — chain ID 168587773, explorer at testnet.blastscan.io
  • Architecture — blast-geth serves the EVM JSON-RPC and WebSocket APIs, while blast-node derives the rollup from Ethereum and drives the execution node over the engine API
  • Storage — blast-geth uses the Pebble backend with path-based state and full sync
  • Sync — Mainnet bootstraps from a pre-built chain snapshot, and Sepolia syncs from genesis

Mantle support

Mantle Mainnet and Mantle Sepolia are now available as deployment targets, pairing a mantle-geth execution node with a mantle-node rollup node.
  • Mantle Mainnet — chain ID 5000, explorer at mantlescan.xyz
  • Mantle Sepolia — chain ID 5003, explorer at sepolia.mantlescan.xyz
  • Architecture — mantle-geth serves the EVM JSON-RPC and WebSocket APIs, while mantle-node derives the rollup from Ethereum and drives the execution node over the engine API
  • Peering — Mantle publishes no execution-layer bootnodes, so payloads reach mantle-geth over the engine API and mantle-node connects to the network’s static peers
  • Sync — both networks bootstrap from a pre-built chain snapshot
See System requirements for the full specification and Supported clients and protocols for the deployment catalog.

Component versions

Last modified on August 13, 2026