Ethereum beacon chain RPC providers

Following Ethereum's Dencun upgrade in March 2024, child chains like Arbitrum will be able to rollup and post batches of transaction data on Ethereum in the form of a new transaction format called a Blob. This Blob data will be part of the beacon chain and is fully downloadable by all consensus nodes. This means that data stored in blobs are inaccessible by the EVM, unlike calldata.

What does this mean for node operators?

To run a node for an Arbitrum child chain (i.e., Arbitrum One, Arbitrum Nova, and L3 Arbitrum chains), your node will need access to blob data to sync up to the latest state of your Arbitrum child chain. Blob data on Ethereum is stored on the beacon chain and is inaccessible to the EVM, hence why dedicated RPC endpoints for the beacon chain will be required after the Dencun upgrade. You can find more details on node requirements in the Run a full node guide.

Furthermore, new node operators joining a network or node operators who come online following an extended period of offline time will require access to historical blob data to sync up to the latest state of their Arbitrum chain. If you run your own beacon node, see Beacon nodes: historical blobs for the client flags needed to retain and serve historical blob data through the Fusaka upgrade.

List of Ethereum beacon chain RPC providers

The list curated here is not comprehensive and in no way does Offchain Labs endorse or benefit from your use of any of these providers.

Please reach out to these teams individually if you need assistance with setting up your validator with any of the above providers.