Skip to main content
This release adds two protocols as deployment targets. Berachain covers Mainnet and the Bepolia testnet, each pairing a Bera-Reth execution node with a Beacond consensus node, and Cronos covers Testnet with a single cronosd node.

Berachain support

Berachain Mainnet and Berachain Bepolia are now available as deployment targets, each running a paired Bera-Reth execution node and Beacond consensus node.
  • Berachain Mainnet — chain ID 80094, explorer at berascan.com
  • Berachain Bepolia — chain ID 80069, explorer at testnet.berascan.com
  • Architecture — Bera-Reth is a Reth-based execution client that serves the EVM JSON-RPC and WebSocket APIs, while Beacond, Berachain’s BeaconKit consensus client, provides consensus over CometBFT
  • Mode — the node runs as a non-validator in full mode, with block building disabled on the consensus client
  • Sync — both networks bootstrap from a pre-built chain snapshot, then follow the network’s peers

Cronos support

Cronos Testnet is now available as a deployment target, running a single cronosd node.
  • Cronos Testnet — chain ID 338, explorer at explorer.cronos.org/testnet
  • Architecture — Cronos is a Cosmos SDK chain with an embedded EVM, so one cronosd node carries both CometBFT consensus and the EVM JSON-RPC and WebSocket APIs
  • Storage — the node uses the RocksDB backend with versioned state enabled and default pruning
  • Sync — the network bootstraps from a pre-built chain snapshot, then follows the network’s peers
See System requirements for the full specification and Supported clients and protocols for the deployment catalog.

Component versions

Last modified on August 12, 2026