Run a bridge operator

Overview

This guide demonstrates how to run a bridge operator node on the mainnet using Docker.

Before you start

Docker

Ethereum endpoint

You need an Ethereum RPC endpoint to listen for events from Ethereum chain and send events to Ethereum. This can be an Alchemy, Infura or any other Ethereum RPC endpoint.

Private keys

Generate two private keys as described in Generate keys:

One key for the bridge voter (if you're a governor)
One key for the bridge operator

System requirements

Recommended system requirements for running a bridge operator on the mainnet:

4-core CPU
8 GB RAM
100 GB high-speed SSD
x86-64 architecture

These requirements are rough guidelines, and each node operator should monitor their node to ensure good performance for the intended task. The size of your Ronin node will also grow over time.

Run the node

Set up directories:

Create a bridge directory:

mkdir ~/ronin-bridge

Go to the newly created directory:

cd ~/ronin-bridge

Create a directory for bridge data:

mkdir -p data

Create a file called docker-compose.yml:

vim docker-compose.yml

Paste the following into docker-compose.yml:

version: "3"
services:
  db:
    image: postgres:14.3
    restart: always
    command: postgres -c 'max_connections=1000'
    hostname: db
    container_name: db
    ports:
      - 127.0.0.1:5432:5432
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    volumes:
      - ~/ronin-bridge/data:/var/lib/postgresql/data
  bridge:
    image: ${BRIDGE_IMAGE}
    restart: always
    container_name: bridge
    environment:
      - RONIN_RPC=${RPC_ENDPOINT}
      - RONIN_BRIDGE_VOTER_KEY=${BRIDGE_VOTER_PRIVATE_KEY}
      - RONIN_BRIDGE_OPERATOR_KEY=${BRIDGE_OPERATOR_PRIVATE_KEY}
      - ETHEREUM_RPC=${ETHEREUM_ENDPOINT}
      - DB_HOST=db
      - DB_NAME=${DB_NAME}
      - DB_PORT=5432
      - DB_USERNAME=${DB_USERNAME}
      - DB_PASSWORD=${DB_PASSWORD}
      - VERBOSITY=${VERBOSITY}
      - CONFIG_PATH=${CONFIG_PATH}
      - RONIN_TASK_INTERVAL=${RONIN_TASK_INTERVAL}
      - RONIN_TRANSACTION_CHECK_PERIOD=${RONIN_TRANSACTION_CHECK_PERIOD}
      - RONIN_MAX_PROCESSING_TASKS=${RONIN_MAX_PROCESSING_TASKS}
      - ETHEREUM_GET_LOGS_BATCH_SIZE=${ETHEREUM_GET_LOGS_BATCH_SIZE}
      - BRIDGE_STATS_URL=${BRIDGE_STATS_URL}
      - BRIDGE_STATS_NODE_NAME=${BRIDGE_STATS_NODE_NAME}
      - BRIDGE_STATS_SECRET=${BRIDGE_STATS_SECRET}
    depends_on:
      - db

This compose file defines three services:

bridge, which pulls a bridge image.
db, which builds a Postgres database for the bridge.

Create an .env file to store configuration parameters for the services:

vim .env

Paste the following into .env and replace placeholder values (like BRIDGE_STATS_NODE_NAME) with your bridge's information:

# Your Ethereum RPC endpoint
ETHEREUM_ENDPOINT=ETHEREUM_ENDPOINT

# The latest version of the bridge's image as listed in https://docs.roninchain.com/bridge-operators/setup/upgrade-bridge-operator
BRIDGE_IMAGE=BRIDGE_IMAGE

# Your bridge operator private key without the 0x prefix
BRIDGE_OPERATOR_PRIVATE_KEY=BRIDGE_OPERATOR_PRIVATE_KEY

# If you're a governor, uncomment this line and replace with your bridge voter key, without the 0x prefix
# BRIDGE_VOTER_PRIVATE_KEY=BRIDGE_VOTER_PRIVATE_KEY

DB_NAME=bridge
DB_USERNAME=postgres

# The Postgres database password
DB_PASSWORD=DB_PASSWORD

CONFIG_PATH=config.mainnet.json
VERBOSITY=3

RPC_ENDPOINT=<replace_your_rpc_endpoint>

RONIN_TASK_INTERVAL=3
RONIN_TRANSACTION_CHECK_PERIOD=50
RONIN_MAX_PROCESSING_TASKS=200
ETHEREUM_GET_LOGS_BATCH_SIZE=100


BRIDGE_STATS_NODE_NAME=<your_node_name>
BRIDGE_STATS_URL=wss://ronin-stats-ws.roninchain.com/bridge
BRIDGE_STATS_SECRET=WSyDMrhRBe111

Start the bridge operator

cd ~/ronin-bridge && docker-compose up -d

This command pulls a Ronin node image, a bridge image, a Postgres database, and starts the services you defined.

After a few minutes, check the status of your node on the Ronin Network Status page. If it's green, the node is connected and up to date with the network.
Review the log for the bridge.

docker logs node -f --tail 100
docker logs bridge -f --tail 100

Verify the bridge is working

Whenever you wish to verify that your node is working, run the following command:

docker-compose logs bridge | head -n 20

Verify that the operator account address in the response matches your registered bridge operator address. If you're a Governing Validator, also check that the voter account address matches the registered bridge voter address.

bridge     | INFO [03-22|07:59:10.368] [RoninListener] Operator account         address=0x2e82D2b56f858f79DeeF11B160bFC4631873da2B
bridge     | INFO [03-22|07:59:10.368] [RoninListener] Voter account            address=0x2295EdAA6BD5c07fB3227628c62Af12248106667

Overview​

Before you start​

Docker​

Ethereum endpoint​

Private keys​

System requirements​

Run the node​

Verify the bridge is working​