16GB+ RAM
8C+ CPU
1000GB+ disk (HDD works for now, SSD is better)
10mb/s+ download
git clone https://github.com/mantlenetworkio/networks.git
generate the ‘jwt_secret_txt’ file and the ‘p2p_node_key_txt’
cd networks/
mkdir sepolia/secret
node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" > sepolia/secret/jwt_secret_txt
cast w n |grep -i "Private Key" |awk -F ": " '{print $2}' |sed 's/0x//' > sepolia/secret/p2p_node_key_txt
We recommend that you start the node with latest shapshot, so that you don’t need to wait a long time to sync data.
First, create a path for ledger:
mkdir -p ./data/sepolia-geth
Second, download the latest official snapshot:
# Download tarball
SEPOLIA_CURRENT_TARBALL_DATE=`curl https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/current.info`
wget -c https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst
# Then you can verify your download
SEPOLIA_CURRENT_TARBALL_CHECKSUM=`curl https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst.sha256sum | awk '{print $1}'`
echo "${SEPOLIA_CURRENT_TARBALL_CHECKSUM} *${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst" | shasum -a 256 --check
# You should get the following output:
# ${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst: OK
Third, unzip snapshot to the ledger path
tar --use-compress-program=unzstd -xvf ${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst -C ./data/sepolia-geth
Check the data was unarchived successfully:
$ ls ./data/sepolia-geth
chaindata
use mantle da-indexer to pull the data for rollup node, and you need to set up L1_RPC_SEPOLIA
export L1_RPC_SEPOLIA='https://rpc.ankr.com/eth_sepolia' #please replace
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml up -d
Will start the node in a detached shell (-d), meaning the node will continue to run in the background. You will need to run this again if you ever turn your machine off.
Congratulations, the node has been deployed!
use L1 beacon chain to pull the data for rollup node, you need set up L1_BEACON_SEPOLIA and L1_RPC_SEPOLIA
L1_BEACON_SEPOLIA is for querying data from eth blob
export L1_RPC_SEPOLIA='https://rpc.ankr.com/eth_sepolia' #please replace
export L1_BEACON_SEPOLIA='https://eth-beacon-chain-sepolia.drpc.org/rest/' #please replace
docker-compose -f docker-compose-sepolia-upgrade-beacon.yml up -d
If you’d rather run reth instead of op-geth as the execution client, use docker-compose-sepolia-reth.yml. It uses the L1 beacon chain to pull data for the rollup node (same as 4.2), so you need L1_RPC_SEPOLIA and L1_BEACON_SEPOLIA set the same way.
reth only starts from a snapshot — there’s no genesis-sync path, so restore one into ./data/sepolia-reth before the first up -d:
mkdir -p ./data/sepolia-reth
# Download the latest official snapshot
SEPOLIA_RETH_TARBALL_DATE=`curl https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/current-reth.info`
wget -c https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/${SEPOLIA_RETH_TARBALL_DATE}-sepolia-reth.tar.zst
# Then you can verify your download
SEPOLIA_RETH_TARBALL_CHECKSUM=`curl https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/${SEPOLIA_RETH_TARBALL_DATE}-sepolia-reth.tar.zst.sha256sum | awk '{print $1}'`
echo "${SEPOLIA_RETH_TARBALL_CHECKSUM} *${SEPOLIA_RETH_TARBALL_DATE}-sepolia-reth.tar.zst" | shasum -a 256 --check
# Unzip snapshot to the ledger path
tar --use-compress-program=unzstd -xvf ${SEPOLIA_RETH_TARBALL_DATE}-sepolia-reth.tar.zst -C ./data/sepolia-reth
Then bring the stack up:
export L1_RPC_SEPOLIA='https://rpc.ankr.com/eth_sepolia' #please replace
export L1_BEACON_SEPOLIA='https://eth-beacon-chain-sepolia.drpc.org/rest/' #please replace
docker-compose -f docker-compose-sepolia-reth.yml up -d
Query through the proxyd service, not op-reth directly (${PROXYD_HTTP_PORT:-1545} / ${PROXYD_WS_PORT:-1546} on the host, default http://localhost:1545). reth only has chain data from a fixed height onward (see the init-state/import-op step in docker-compose-sepolia-reth.yml), and a few methods (eth_getProof, debug_trace*) are unreliable on reth regardless of height. proxyd forwards both cases to the public RPC (rpc.sepolia.mantle.xyz) instead of failing locally — see sepolia/proxyd.toml for the exact routing rules. Querying op-reth’s own port directly (${VERIFIER_HTTP_PORT:-8545}) skips this fallback and will error on pre-cutoff blocks or those methods.
Follow these steps to check if the installation is successful
If the service status is ‘up,’ it means that the service has started without any issues.
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml ps
Use the command ‘cast bn’ to execute multiple times and check if the height increases.
example:
# query local op-geth latest block height
cast bn
# query latest block height from mantle rpc
cast bn --rpc-url https://rpc.sepolia.mantle.xyz
Use the command ‘cast rpc optimism_syncStatus’ to execute multiple times and check if the safe_l2 and inalized_l2 increases. It may need to be increased after thirty minutes
example:
cast rpc optimism_syncStatus --rpc-url localhost:9545 |jq .finalized_l2.number
cast rpc optimism_syncStatus --rpc-url localhost:9545 |jq .safe_l2.number
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml down
Will shut down the node without wiping any volumes. You can safely run this command and then restart the node again.
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml down -v
Will completely wipe the node by removing the volumes that were created for each container. Note that this is a destructive action, be very careful!
docker-compose logs <service name>
Will display the logs for a given service. You can also follow along with the logs for a service in real time by adding the flag -f.
The available services are:
Note: When upgrading, please follow the correct update order: update mantle-op-geth first, then update mantle-op-node. Reversing this order may cause unexpected issues.
⚠️ Important for v1.5.3 Upgrade: When updating to v1.5.3 version, you must ensure that mantle-op-geth starts before mantle-op-node. Failure to follow this order may cause chain fork. If a fork occurs, please rebuild the RPC node by following the full setup instructions in this document.
⚠️ Important for v1.6.3 Upgrade:
L1_RPC_SEPOLIA(andL1_BEACON_SEPOLIAif you use the beacon variant) must beexport-ed in the same shell session, right before thedocker-compose ... up -dcommand below. If youdownandup -din a new shell without re-exporting them, docker-compose does not error — it silently substitutes an empty string,OP_NODE_L1_ETH_RPCends up blank, and op-node fails to sync from L1 with no obvious error pointing at the cause. Always re-export in the same session you runup -din, even if you exported them before during a previous run.
docker-compose -f docker-compose-sepolia.yml down
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml down
docker-compose -f docker-compose-sepolia-upgrade-beacon.yml down
# If your local code have changes, please use 'git stash' to cache first
git pull
If you start the node using your own way, please refer to the three files from this upgrade. Otherwise, it may cause irreversible damage to the node.
export L1_RPC_SEPOLIA='https://rpc.ankr.com/eth_sepolia' #please replace
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml up -d
use L1 beacon chain to pull the data for rollup node
you need to edit L1_BEACON_SEPOLIA and L1_RPC_SEPOLIA
L1_BEACON_SEPOLIA is for querying data from eth blob
then start with
export L1_RPC_SEPOLIA='https://rpc.ankr.com/eth_sepolia' #please replace
export L1_BEACON_SEPOLIA='https://eth-beacon-chain-sepolia.drpc.org/rest/' #please replace
docker-compose -f docker-compose-sepolia-upgrade-beacon.yml up -d
docker-compose ... up -d recreates the containers even if the image tag is unchanged in your shell’s image cache, so confirm the new version is actually running rather than assuming the command succeeded:
docker exec <op-geth container name> geth version
docker exec <op-node container name> op-node --version
Expect v1.6.3 in both outputs. If you still see v1.5.3, the pull_policy: always on op-geth/op-node should have forced a fresh pull — re-run docker-compose -f <your compose file> up -d and check again before assuming something else is wrong.
Use the command ‘cast bn’ to execute multiple times and check if the height increases.
example:
# query local op-geth latest block height
cast bn
# query latest block height from mantle rpc
cast bn --rpc-url https://rpc.sepolia.mantle.xyz
Use the command ‘cast rpc optimism_syncStatus’ to execute multiple times and check if the safe_l2 and inalized_l2 increases. It may need to be increased after thirty minutes
example:
cast rpc optimism_syncStatus --rpc-url localhost:9545 |jq .finalized_l2.number
cast rpc optimism_syncStatus --rpc-url localhost:9545 |jq .safe_l2.number
If your node’s data is corrupted due to abnormal operations, please refer to the following steps for recovery
rm -fr ./data/sepolia-geth
mkdir -p ./data/sepolia-geth
# download the latest official snapshot
SEPOLIA_CURRENT_TARBALL_DATE=`curl https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/current.info`
wget -c https://s3.ap-southeast-1.amazonaws.com/snapshot.sepolia.mantle.xyz/${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst
# unzip snapshot to the ledger path
tar --use-compress-program=unzstd -xvf ${SEPOLIA_CURRENT_TARBALL_DATE}-sepolia-chaindata.tar.zst -C ./data/sepolia-geth
If you use da-indexer
docker-compose -f docker-compose-sepolia-upgrade-da-indexer.yml up -d
Otherwise
docker-compose -f docker-compose-sepolia-upgrade-beacon.yml up -d