Deploy a rollup node

Learn how to run a node for the B2.

System Requirements

hardware requirements

  • CPUs: 16 vCPUs

  • RAM: 32 GB

  • Storage: 1 TB NVMe Storage

  • 100MBps bidirectional internet connection

You can run B2 on lower-spec hardware, but you may find that it is not highly performant or prone to crashing.

software requirements

OS:As long as Docker Engine can be installed, the operating system will suffice.

Pre-install

Install Docker

Please refer to the Install Docker Engine

Install Docker-compose

Please refer to the Install Docker Compose

Download Snapshot Data

The snapshot file will be updated every Friday. The download will be temporarily unavailable. Please wait a while and try again.

Setup B2 Node

Generate jwt secret:

Create a docker-compose.yaml file and mount the data directory and json files which downloaded above.

Changelog for the docker-compose.yaml:

Users who have already been set up can also upgrade,The upgrade will improve block synchronization.

  • L2 image change to us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101315.2

  • OP image change to us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.7

  • OP_NODE_P2P_STATIC: "/dns/b2-mainnet-bootnodes.altlayer.network/tcp/32046/p2p/16Uiu2HAm1hkacTvu8HzwPs2Mv8cHo6RfMX9vbEi4T8FuXFRK7VEM,/dns/b2-mainnet-bootnodes.altlayer.network/tcp/32048/p2p/16Uiu2HAm1oTTtY6QkUdVUY8qn86Aa6MPR8FxMR4VQzXKT6tCPEun,/dns/b2-mainnet-bootnodes.altlayer.network/tcp/32050/p2p/16Uiu2HAmJhSCro27M9ZQ4yPkEQjYcRx1QJ9BmzfunNPPHbJsXnGV,/dns/b2-mainnet-bootnode1.bsquared.network/tcp/9222/p2p/16Uiu2HAkwyquyg55Jnmo97czvXfB6Evove1C4jUdMoFRQEQkgbnn,/dns/b2-mainnet-bootnode2.bsquared.network/tcp/9222/p2p/16Uiu2HAmSP44jYc7aJVXJhKVoYUFqkotwpEU1zqxYCksvUWwcyFT"

  • GETH_BOOTNODES: "enode://55b79017f15cad10bb8ad433fb991e6a0d0ca5ccef3f9123618869ee405d61b564a44dee1b87c47e62dba51e63a9172e356714a7ecdf20594d041ddf9013136c@b2-mainnet-bootnodes.altlayer.network:32045,enode://ad371eb83f665586985f4482adc8bb7fff793370843d73124e8b23c7aa69f01b6db93e5782ccbf7524d04aa5345e6bd1feeca4ec7bb1a515c3af67484604a5a8@b2-mainnet-bootnodes.altlayer.network:32047,enode://274310e51ffbc42167dbf1adbcf0ef43f50db9f8f0c84d9f25ac6cf1659ca57b09c9398fbc881485865170c8090250b8b803cb2f1be11aa65b488b3c8337be2d@b2-mainnet-bootnodes.altlayer.network:32049,enode://7ddd900597dde5cca6508cf33264dd528b945563d3d6ff5d0d2b16ecf8e14ca92ebf44fdabe9ecef44532aa0caeb54945c7d40af9d5a08e4b81853308a91ed27@b2-mainnet-bootnode1.bsquared.network:30303,enode://01c15b6db86024b708a3f3e2cdea2769264bc81dc8997752b44b904daff98f2ca15ca1e3096ed601debe7ad0f057c12d30bf93aeaeb227a59443059402c57dec@b2-mainnet-bootnode2.bsquared.network:30303"

Now, All preparations are complete, and the data directory structure is as follow:

The next step is to start the service.

Start The Node

Verify Result

Watch the L2 container logs

Block synchronization takes some time, please wait patiently. After some while,can check the syncing process by below command:

The block will catch up to the latest block once the request returns false.

Last updated