From a4ff8f3dcb8ff2b45fc89b9d99d8f354bb14b545 Mon Sep 17 00:00:00 2001 From: Zach Date: Wed, 26 Apr 2023 14:43:32 -0400 Subject: [PATCH 1/3] optimism: on error, wait, then re-run 'deploy up' --- app/data/stacks/fixturenet-optimism/README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/app/data/stacks/fixturenet-optimism/README.md b/app/data/stacks/fixturenet-optimism/README.md index 7664a7c3..02e06a44 100644 --- a/app/data/stacks/fixturenet-optimism/README.md +++ b/app/data/stacks/fixturenet-optimism/README.md @@ -2,7 +2,7 @@ Instructions to setup and deploy an end-to-end L1+L2 stack with [fixturenet-eth](../fixturenet-eth/) (L1) and [Optimism](https://stack.optimism.io) (L2) -We support running just the L2 part of stack, given an external L1 endpoint. Follow [l2-only](./l2-only.md) for the same. +We support running just the L2 part of stack, given an external L1 endpoint. Follow the [L2 only doc](./l2-only.md) for the same. ## Setup @@ -28,6 +28,8 @@ Build the container images: laconic-so --stack fixturenet-optimism build-containers ``` +Note: this will take >10 mins depending on the specs of your machine, and **requires** 16GB of memory or greater. + This should create the required docker images in the local image registry: * `cerc/go-ethereum` * `cerc/lighthouse` @@ -48,12 +50,14 @@ Deploy the stack: laconic-so --stack fixturenet-optimism deploy up ``` -The `fixturenet-optimism-contracts` service may take a while (`~15 mins`) to complete running as it: +If you get the error `service "fixturenet-optimism-contracts" didn't complete successfully: exit 1` with ~25 lines of Traceback, wait 15-20 mins then re-run the command. + +The `fixturenet-optimism-contracts` service takes a while 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: +To list and monitor the running containers: ```bash laconic-so --stack fixturenet-optimism deploy ps -- 2.45.2 From 73419c341a427133161264e9bee5e6082bc918ce Mon Sep 17 00:00:00 2001 From: David Boreham Date: Thu, 27 Apr 2023 10:22:21 -0600 Subject: [PATCH 2/3] Remove > --- app/data/stacks/fixturenet-eth-tx/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/data/stacks/fixturenet-eth-tx/README.md b/app/data/stacks/fixturenet-eth-tx/README.md index 9af9ee3d..f6ae483a 100644 --- a/app/data/stacks/fixturenet-eth-tx/README.md +++ b/app/data/stacks/fixturenet-eth-tx/README.md @@ -26,7 +26,7 @@ It is easy to export data from the fixturenet for offline processing of the raw For example: ``` -❯ app/data/container-build/cerc-fixturenet-eth-lighthouse/scripts/export-ethdb.sh 500 +$ app/data/container-build/cerc-fixturenet-eth-lighthouse/scripts/export-ethdb.sh 500 Waiting for geth to generate DAG.... done Waiting for beacon phase0.... done Waiting for beacon altair.... done -- 2.45.2 From aa74438b7e67721f35af77c3a38006b93c7ca4cc Mon Sep 17 00:00:00 2001 From: David Boreham Date: Thu, 27 Apr 2023 10:52:06 -0600 Subject: [PATCH 3/3] Add foundry to the fixturenet-eth-tx stack --- app/data/stacks/fixturenet-eth-tx/stack.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/app/data/stacks/fixturenet-eth-tx/stack.yml b/app/data/stacks/fixturenet-eth-tx/stack.yml index 0c3b45a3..0a0a6bd6 100644 --- a/app/data/stacks/fixturenet-eth-tx/stack.yml +++ b/app/data/stacks/fixturenet-eth-tx/stack.yml @@ -1,15 +1,18 @@ -version: "1.1" +version: "1.2" name: fixturenet-eth-tx decription: "Ethereum Fixturenet w/ tx-spammer" repos: - cerc-io/go-ethereum - cerc-io/tx-spammer + - dboreham/foundry containers: - cerc/go-ethereum - cerc/lighthouse - cerc/fixturenet-eth-geth - cerc/fixturenet-eth-lighthouse - cerc/tx-spammer + - cerc/foundry pods: - fixturenet-eth + - foundry - tx-spammer -- 2.45.2