Initia Optimistic Rollup Bots.

• Batch Submitter: Submit batch to L1 node
• Output Submitter: Submit output to L1 node
• Challenger: Challenge invalid output
• Bridge Executor: Execute bridge transaction

• Postgres 14+
• Node.js 16+
• Node LCD/RPC (L1 and L2)

To run OPinit bots, you should check the following version. This is needed to ensure that the bots are compatible with the node version.

Before running rollup bots, you should create bridge between L1 and L2. If you use initia.js, you can create bridge using MsgCreateBridge message as follows.

import { MsgCreateBridge, BridgeConfig, Duration } from '@initia/initia.js';

const bridgeConfig = new BridgeConfig(
  challenger.key.accAddress,
  outputSubmitter.key.accAddress,
  new BatchInfo(batchSubmitter.accAddress, config.PUBLISH_BATCH_TARGET),
  Duration.fromString(submissionInterval.toString()),
  Duration.fromString(finalizedTime.toString()),
  new Date(),
  this.metadata
);
const msg = new MsgCreateBridge(executor.key.accAddress, bridgeConfig);

You should set .env file for each bot in bots/worker. To transfer assets between L1 and L2, you should run executor and output submitter at least.

In OPinit bots, we use .dotenv for managing environment variable for development. If you want to set .env by worker, you should name it as .env.{WORKER_NAME} and set WORKER_NAME in [executor, output, batch, challenger]. For example, if you want to set .env for executor, you should name it as .env.executor and set WORKER_NAME=executor in local environment. .env files should be located in OPinit/bots directory.

• typeorm setting

❗ You should set common settings for typeorm in .env.xxx file ❗

TYPEORM_CONNECTION=postgres               # database connection (currently only support `postgres`)
TYPEORM_HOST=localhost                    # database host
TYPEORM_USERNAME=username                 # database username
TYPEORM_PASSWORD=password                 # database password
TYPEORM_DATABASE=rollup                   # database name
TYPEORM_PORT=5432                         # database port
TYPEORM_SYNCHRONIZE=true                  # synchronize database schema
TYPEORM_LOGGING=false                     # enable logging
TYPEORM_ENTITIES=dist/orm/*Entity.js      # entity path

• .env.executor

Note that if EXECUTOR_L1_MONITOR_HEIGHT and EXECUTOR_L2_MONITOR_HEIGHT are not set, executor will start monitoring from height stored on state table. If you want to start monitoring from specific height, you should set them in .env.executor file.

• .env.output

• .env.batch

• .env.challenger

• Install dependencies

  npm install

• Bridge Executor

Bridge executor is a bot that monitor L1, L2 node and execute bridge transaction. It will execute following steps.

1. Configure .env.executor file

2. Run executor bot

   npm run executor

• Output Submitter

Output submitter is the component to store the L2 output root for block finalization. Output submitter will get the L2 output results from executor and submit it to L1.

Before running output submitter, you should set executor first. It will get the L2 output results from executor and submit it to L1.

1. Configure .env.output file

2. Run output submitter bot

   npm run output

• Batch Submitter

Batch submitter is a background process that submits transaction batches to the BatchInbox module of L1 or Celestia.

NOTE To run celestia batch submitter, you have to set celestia light node

1. Configure .env.batch file

2. Run batch submitter bot

   npm run batch

• Challenger

Challenger is an entity capable of deleting invalid output proposals from the output oracle.

NOTE > challenger should be independent from executor and output submitter. It will monitor the output oracle and delete invalid output proposals.

1. Configure .env.challenger file

2. Run challenger bot

   npm run challenger