<aside> 💡

IMPORTANT (as of Jan 30, 2025): All node operators are strongly encouraged to upgrade to the v1.101411.6 release of op-geth as soon as possible. This update includes a critical security fix. For more details, please refer to the op-geth release notes here.

Please make sure you are running the following releases with your node setup:

This guide provides instructions on setting up a Minato node using Docker, Docker Compose, and binary installation.

Minato Node Configuration Files

The following files are needed for the configuration of the Soneium Minato node.

sample.env

minato-rollup.json

minato-genesis.json

docker-compose.yml

Hardware requirement

We recommend using the i3.2xlarge AWS instance type or equivalent hardware. If you want to set it up as a public RPC, you will need to adjust node resources based on your traffic.


Docker installation

Prerequisites

Make sure you have the latest versions of Docker and Docker Compose installed.

Setup Instructions

  1. Generate JWT Secret

    Generate a JWT secret by running the following command:

    openssl rand -hex 32 > jwt.txt
    
  2. Rename Environment File

    Rename sample.env to .env:

    mv sample.env .env
    
  3. Update Environment Variables

    Open the .env file in a text editor and update the following variables:

    L1_URL=https://sepolia-l1.url
    L1_BEACON=https://sepolia-beacon-l1.url
    P2P_ADVERTISE_IP=<Node Public IP>
    

    In some node providers, you need to specify your node's public IP for op-geth. To do this, replace <your_node_public_ip> with your actual public IP in the --nat=extip:<your_node_public_ip> parameter within the docker-compose.yml file, specifically under the op-geth-minato service settings.

    Recommendation: For faster synchronization, it's recommended to have the L1 node geographically close to the Minato node.