Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(gwyneth): add reth-based private network , and L1 contract deployment #19

Merged
merged 9 commits into from
Jul 15, 2024
Merged

feat(gwyneth): add reth-based private network , and L1 contract deployment #19

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
227c9e6
Add deployment manual and script
Jul 8, 2024
67b2f4b
modify comment in MockSgxVerifier
Jul 8, 2024
dffc809
change anvil to reth-based private network
Jul 9, 2024
a090c06
Change config as Kurtosis PR
Jul 9, 2024
2fe94df
typo fix
Jul 10, 2024
5ac4a0b
update readme with local reth image deployment
Jul 10, 2024
c5e2838
Update everything (except core protocol) to lates, because of deps
Jul 11, 2024
19461a0
delete some unused contracts and bring over guardian prover
Jul 12, 2024
6f2b50e
Merge pull request #20 from taikoxyz/brought_over_latest_taiko_mono
adaki2004 Jul 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 11 additions & 21 deletions packages/protocol/deployments/local_deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,28 +11,18 @@ brew install kurtosis-tech/tap/kurtosis-cli

### 1. Define the network config parameters

Create a `network_param.json` file.
Create a `network_param.yaml` file.

```shell
{
"participants": [
{
"el_type": "reth",
"el_image": "ghcr.io/paradigmxyz/reth",# We can use custom image, like ethpandaops/reth:main-9c0bc84 with MacOs with M1 chip or taiko.xyz/taiko-reth for example
"cl_type": "lighthouse",
"cl_image": "sigp/lighthouse:latest",
"count": 1
},
{
"el_type": "reth",
"el_image": "ghcr.io/paradigmxyz/reth", # We can use custom image, like ethpandaops/reth:main-9c0bc84 with MacOs with M1 chip or taiko.xyz/taiko-reth for example
"cl_type": "teku",
"cl_image": "consensys/teku:latest",
"count": 1
}
],
"launch_additional_services": false
}
participants:
- el_type: reth
el_image: ghcr.io/paradigmxyz/reth # We can use custom image, like ethpandaops/reth:main-9c0bc84 with MacOs with M1 chip or taiko.xyz/taiko-reth for example
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you have to create one of these images to test stuff out? Can't just run from local build somehow to more quickly (?) test stuff out.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can reference local images of course!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the 'howto' into the markdown.

cl_type: lighthouse
cl_image: sigp/lighthouse:latest
- el_type: reth
el_image: ghcr.io/paradigmxyz/reth # We can use custom image, like ethpandaops/reth:main-9c0bc84 with MacOs with M1 chip or taiko.xyz/taiko-reth for example
cl_type: teku
cl_image: consensys/teku:latest
```

### 2. Spin up the network
Expand All @@ -41,7 +31,7 @@ Create a `network_param.json` file.
kurtosis run github.com/ethpandaops/ethereum-package --args-file YOUR_NETWORK_FILE/network_params.json
```

It will show you a lot of information in the terminal - along with the genesis info, network id, addresses with pre-funded ETH, etc.
It will show you a lot og information in the terminal - along with the genesis info, network id, addresses with pre-funded ETH, etc.
adaki2004 marked this conversation as resolved.
Show resolved Hide resolved

### 3. Set .env vars and run deployment script
Paste one PK and ADDR pair from anvil output to .env file and set the correct corresponding (PRIVATE_KEY and MAINNET_CONTRACT_OWNER) variables.
Expand Down
Loading