Skip to content

ConstellationCrypto/replica-guide-rivalz-mainnet

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 

Repository files navigation

Rivalz Replica Guide

Architecture Overview

  • l2: this service is the nitro node
  • celestia-light-node: this service is the celestia light node that is used to fetch rollup data from the celestia network
  • celestia-das-server: this service is the DAS server the nitro node uses to interact with the celestia light node

Requirements

  • 4 core CPU
  • 16GB of RAM
  • 256GB SSD (the celestia light node needs at least 100GB, nitro node storage requirements scale with the # of txns on the rollup)

Setup

  1. Set the all env var in .env for docker-compose.
CELESTIA_LIGHT_NODE_AUTH_TOKEN=
CELESTIA_LIGHT_NODE=
API_KEY_ALCHEMY=
  1. Run docker-compose up -d
  2. Wait for the celestia light node to sync to tip, note that this may take up to 6 hours. During this time, you will see these errors in the logs of the l2 (nitro node) service
ERROR[03-01|13:24:44.862] Failed to resolve blob pointer from celestia err="request timed out"
WARN [03-01|13:24:44.862] error reading inbox                      err="request timed out"
  1. Once the celestia light node completes syncing, you will begin seeing the nitro node building blocks:
INFO [03-01|13:26:01.178] created block                            l2Block=1 l2BlockHash=a3a1db..3c1a2d

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published