cerc-io/stack-orchestrator
17
1
Fork 1
Code Issues 111 Pull Requests 13 Actions Packages Projects Releases 473 Wiki Activity
53516f3109
stack-orchestrator/app/data/stacks/fixturenet-optimism/l2-only.md
Nabarun Gogoi 63fbaa7ae3 Add ability to run mobymask-v2 stack with external optimism endpoint (#279) 
* Set optimism geth endpoint from env file

* Set L1 account private keys from env

* Only deploy contract and generate invite in mobymask container

* Add readme for running mobymask v2 stack independently

* Modify mobymask container to stop running server and update readmes

* Check deployer account balance before deploying contract

* Fix for checking account balance before deploying

* Update readme description

* Update MobyMask repo tag in readme

Former-commit-id: 94e38ceaba
2023-04-05 17:26:38 +05:30

2.4 KiB
Raw Blame History

fixturenet-optimism

Instructions to setup and deploy L2 fixturenet using Optimism

Setup

Prerequisite: An L1 Ethereum RPC endpoint

Clone required repositories:

laconic-so --stack fixturenet-optimism setup-repositories --exclude cerc-io/go-ethereum

Checkout to the required versions and branches in repos:

# Optimism
cd ~/cerc/optimism
git checkout @eth-optimism/sdk@0.0.0-20230329025055

Build the container images:

laconic-so --stack fixturenet-optimism build-containers --include cerc/foundry,cerc/optimism-contracts,cerc/optimism-op-node,cerc/optimism-l2geth,cerc/optimism-op-batcher

This should create the required docker images in the local image registry:

  • cerc/foundry
  • cerc/optimism-contracts
  • cerc/optimism-l2geth
  • cerc/optimism-op-batcher
  • cerc/optimism-op-node

Deploy

Update the l1-params.env file with L1 endpoint (L1_RPC, L1_HOST and L1_PORT) and other params

  • NOTE:
    • Stack Orchestrator needs to be run in dev mode to be able to edit the env file
    • If L1 is running on the host machine, use host.docker.internal as the hostname to access the host port

Deploy the stack:

laconic-so --stack fixturenet-optimism deploy up --include fixturenet-optimism

The fixturenet-optimism-contracts service may take a while (~15 mins) to complete running as it:

  1. waits for the 'Merge' to happen on L1
  2. waits for a finalized block to exist on L1 (so that it can be taken as a starting block for roll ups)
  3. deploys the L1 contracts

To list down and monitor the running containers:

laconic-so --stack fixturenet-optimism deploy --include fixturenet-optimism ps

# With status
docker ps

# Check logs for a container
docker logs -f <CONTAINER_ID>

Clean up

Stop all services running in the background:

laconic-so --stack fixturenet-optimism deploy down --include fixturenet-optimism

Clear volumes created by this stack:

# List all relevant volumes
docker volume ls -q --filter "name=.*fixturenet_geth_accounts|.*l1_deployment|.*l2_accounts|.*l2_config|.*l2_geth_data"

# Remove all the listed volumes
docker volume rm $(docker volume ls -q --filter "name=.*fixturenet_geth_accounts|.*l1_deployment|.*l2_accounts|.*l2_config|.*l2_geth_data")

Troubleshooting

See Troubleshooting