Skip to main content
Using a snapshot significantly reduces the initial time required to sync a Base node. Snapshots are updated regularly. If you’re a prospective or current Base node operator, you can restore from a snapshot to speed up your initial sync. Follow the steps below carefully.

Restoring from Snapshot

These steps assume you are in the cloned node directory (the one containing docker-compose.yml).
  1. Prepare Data Directory:
    • Before running Docker for the first time, create the data directory on your host machine that will be mapped into the Docker container. This directory must match the volumes mapping in the docker-compose.yml file.
      mkdir ./reth-data
      
    • If you have previously run the node and have an existing data directory, stop the node (docker compose down), remove the contents of the existing directory (e.g. rm -rf ./reth-data/*), and proceed.
  2. Download Snapshot: Choose the appropriate snapshot for your network and client from the table below. Use wget (or similar) to download it into the node directory.
    NetworkSnapshot TypeDownload Command (wget …)
    TestnetArchive (recommended)wget -c https://sepolia-reth-archive-snapshots.base.org/$(curl https://sepolia-reth-archive-snapshots.base.org/latest)
    TestnetPrunedwget -c https://sepolia-reth-pruned-snapshots.base.org/$(curl https://sepolia-reth-pruned-snapshots.base.org/latest)
    MainnetArchive (recommended)wget -c https://mainnet-reth-archive-snapshots.base.org/$(curl https://mainnet-reth-archive-snapshots.base.org/latest)
    MainnetPrunedwget -c https://mainnet-reth-pruned-snapshots.base.org/$(curl https://mainnet-reth-pruned-snapshots.base.org/latest)
    Ensure you have enough free disk space to download the snapshot archive (.tar.gz / .tar.zst file) and extract its contents. The extracted data will be significantly larger than the archive.
  3. Extract Snapshot: Untar the downloaded snapshot archive. Replace snapshot-filename with the actual downloaded filename:
    tar -xzvf <snapshot-filename.tar.gz>
    
    # For .tar.zst 
    tar -I zstd -xvf <snapshot-filename.tar.zst>
    
  4. Move Data: The extraction process will likely create a reth directory.
    • Move the contents of that directory into the data directory you created in Step 1:
      mv ./reth/* ./reth-data/
      rm -rf ./reth    # Clean up empty extracted folder
      
    • The goal is to have the chain data directories (e.g., chaindata, nodes, segments, etc.) directly inside ./reth-data, not in a nested subfolder.
  5. Start the Node: Now that the snapshot data is in place, return the root of your Base node folder and start the node:
    cd ..
    docker compose up --build
    
Your node should begin syncing from the last block in the snapshot.
  1. Verify and Clean Up: Monitor the node logs (docker compose logs -f <service_name>) or use the sync monitoring command to ensure the node starts syncing from the snapshot’s block height. Once confirmed, you can safely delete the downloaded snapshot archive (.tar.gz file) to free up disk space.

Proofs Snapshots

If you are running the historical proofs ExEx, snapshots of the proofs database are available to skip the 24-48 hour backfill.
NetworkDownload Command (wget …)
Testnetwget -c https://sepolia-reth-proofs-snapshots.base.org/$(curl https://sepolia-reth-proofs-snapshots.base.org/latest)
Mainnetwget -c https://mainnet-reth-proofs-snapshots.base.org/$(curl https://mainnet-reth-proofs-snapshots.base.org/latest)
The restore process is the same as above — follow the Restoring from Snapshot steps using this archive instead.