Running an ApeChain Replica Node (Nitro v3.9.9)

Overview

v3.9.9 brings the fork (almost) up to date with upstream Nitro and includes the Arbitrum security fixes shipped in that release, so upgrade promptly.

Running a Replica

Prerequisites

• Docker (and Docker Compose).
• An Arbitrum One RPC endpoint (the parent chain). Use a private endpoint because public RPCs get rate-limited during sync.
• Network reachability to ApeChain's DAS REST aggregator and feed (no credentials needed).

Procedure

1. Get the config bundle then unzip it:

   nitro-replica-apechain.zip

2. Read the README.md, but briefly: in docker-compose.yml, switch the Arbitrum RPC endpoint from public to your private or you'll be rate-limited.

3. If you already have a replica then:

   1. Stop your node
   2. If you have a data directory in your replica's folder:
      1. Run mv docker-compose.novol.yml docker-compose.yml
      2. Copy data to the bundle's folder.
   3. If you instead have a snapshot:
      1. Run mv docker-compose.novol.yml docker-compose.yml
      2. Run mkdir -p data/apechain
      3. Then copy your snapshot into data/apechain/nitro
   4. If you have neither then you are using a docker volume. You don't need to do anything more.

4. Start the node (docker-compose up -d)

Verify

1. Check docker-compose logs -f. You should see created block
2. Check that your block number rises: cast block-number && sleep 15 && cast block-number
   1. NOTE: If you already had a replica then the block number should be near to the tip, which is over 40 million blocks.