@@ -64,71 +64,83 @@ optimism_package:
64
64
network_params :
65
65
name : rollup-1 # can be anything as long as it is unique
66
66
network_id : 12345 # can be anything as long as it is unique
67
+ ethereum_package :
68
+ - participants :
69
+ - el_type : geth
70
+ cl_type : teku
67
71
` ` `
68
72
69
- Save the above configuration to a file. For the rest of this tutorial, we'll assume you've saved it to ` network-config.yaml`.
70
-
71
73
## Start your network
72
74
73
75
Now that you've configured your network, you can start it up using the Kurtosis CLI. Run the command below:
74
76
75
77
` ` ` bash
76
- kurtosis run github.com/ethpandaops/optimism-package --args-file ./network-config .yaml
78
+ kurtosis run github.com/ethpandaops/optimism-package --args-file https://raw.githubusercontent.com/ethpandaops/optimism-package/main/network_params .yaml
77
79
```
78
80
79
- This command will start up your network and deploy the OP Stack based on the configuration you created . The command will
81
+ This command will start up your network and deploy the OP Stack based on the ethpandaops configuration . The command will
80
82
produce a lot of output and will take about five minutes to complete. Once it's done, you'll see a message that looks like
81
83
the one below:
82
84
83
85
```
84
- INFO[2024-09-23T00:31:29-06:00] ===================================================
85
- INFO[2024-09-23T00:31:29-06:00 ] || Created enclave: blue-marsh ||
86
- INFO[2024-09-23T00:31:29-06:00] ===================================================
87
- Name: blue-marsh
88
- UUID: 91af529557cb
86
+ INFO[2025-02-25T02:10:37Z] == ===================================================
87
+ INFO[2025-02-25T02:10:37Z ] || Created enclave: proud-crater ||
88
+ INFO[2025-02-25T02:10:37Z] == ===================================================
89
+ Name: proud-crater
90
+ UUID: eb959a72177b
89
91
Status: RUNNING
90
- Creation Time: Mon, 23 Sep 2024 00:29:58 MDT
92
+ Creation Time: Tue, 25 Feb 2025 02:07:56 UTC
91
93
Flags:
92
94
93
95
========================================= Files Artifacts =========================================
94
96
UUID Name
95
- a5824b041b28 1-lighthouse-geth-0-63-0
96
- f7c0e13e9871 el_cl_genesis_data
97
- bfa022049aea final-genesis-timestamp
98
- 0b5c53e3940f genesis-el-cl-env-file
99
- 46a78cc34966 genesis_validators_root
100
- 038ad1a753ed jwt_file
101
- 4fbc4bde03c2 keymanager_file
102
- c36887606978 op-deployer-configs
103
- d638c3222e56 op-deployer-fund-script
104
- b02f20c287ac op_jwt_filerollup-1
105
- 655d57862785 prysm-password
106
- 28203054f5ec validator-ranges
97
+ 14b79c110784 1-teku-geth-0-63
98
+ 80829197fe1c dashboards-0
99
+ 80e45cc0080f divine-butterfly
100
+ ddae8880a93f el_cl_genesis_data
101
+ 271d9f5d46ec final-genesis-timestamp
102
+ df11dac8789a genesis-el-cl-env-file
103
+ ca839becbe40 genesis_validators_root
104
+ 40da51373335 grafana-config
105
+ cb782c178dfd jwt_file
106
+ 0fcd752154b6 keymanager_file
107
+ e724c1671e85 op-deployer-configs
108
+ e880f062cd24 op-deployer-fund-script
109
+ bb31dbb7e788 op_jwt_file
110
+ d8d4758b14c8 prometheus-config
111
+ 3eafd3a35757 prysm-password
112
+ 0fb6d6f67d26 validator-ranges
107
113
108
114
========================================== User Services ==========================================
109
115
UUID Name Ports Status
110
- 29643e475cb7 cl-1-lighthouse-geth http: 4000/tcp -> http://127.0.0.1:33639 RUNNING
111
- metrics: 5054/tcp -> http://127.0.0.1:33640
112
- tcp-discovery: 9000/tcp -> 127.0.0.1:33641
113
- udp-discovery: 9000/udp -> 127.0.0.1:32920
114
- e7dfdc2588ae el-1-geth-lighthouse engine-rpc: 8551/tcp -> 127.0.0.1:33636 RUNNING
115
- metrics: 9001/tcp -> http://127.0.0.1:33637
116
- rpc: 8545/tcp -> 127.0.0.1:33634
117
- tcp-discovery: 30303/tcp -> 127.0.0.1:33638
118
- udp-discovery: 30303/udp -> 127.0.0.1:32919
119
- ws: 8546/tcp -> 127.0.0.1:33635
120
- 5ff43094ccc3 op-batcher-rollup-1 http: 8548/tcp -> http://127.0.0.1:33650 RUNNING
121
- aa30d376acc9 op-cl-1-op-node-op-geth-rollup-1 http: 8547/tcp -> http://127.0.0.1:33648 RUNNING
122
- tcp-discovery: 9003/tcp -> 127.0.0.1:33649
123
- udp-discovery: 9003/udp -> 127.0.0.1:32922
124
- af4abdbbe939 op-el-1-op-geth-op-node-rollup-1 engine-rpc: 8551/tcp -> 127.0.0.1:33645 RUNNING
125
- metrics: 9001/tcp -> 127.0.0.1:33646
126
- rpc: 8545/tcp -> http://127.0.0.1:33643
127
- tcp-discovery: 30303/tcp -> 127.0.0.1:33647
128
- udp-discovery: 30303/udp -> 127.0.0.1:32921
129
- ws: 8546/tcp -> 127.0.0.1:33644
130
- 578ee2b5bfe7 validator-key-generation-cl-validator-keystore <none> RUNNING
131
- aa69f73e96c1 vc-1-geth-lighthouse metrics: 8080/tcp -> http://127.0.0.1:33642 RUNNING
116
+ 976820378d51 cl-1-teku-geth http: 4000/tcp -> http://127.0.0.1:32802 RUNNING
117
+ metrics: 8008/tcp -> http://127.0.0.1:32803
118
+ tcp-discovery: 9000/tcp -> 127.0.0.1:32804
119
+ udp-discovery: 9000/udp -> 127.0.0.1:32775
120
+ 12ee5b7e5a18 el-1-geth-teku engine-rpc: 8551/tcp -> 127.0.0.1:32799 RUNNING
121
+ metrics: 9001/tcp -> http://127.0.0.1:32800
122
+ rpc: 8545/tcp -> 127.0.0.1:32797
123
+ tcp-discovery: 30303/tcp -> 127.0.0.1:32801
124
+ udp-discovery: 30303/udp -> 127.0.0.1:32774
125
+ ws: 8546/tcp -> 127.0.0.1:32798
126
+ e3e534981b75 grafana http: 3000/tcp -> http://127.0.0.1:32821 RUNNING
127
+ aa9a19bf1413 op-batcher-rollup-1 http: 8548/tcp -> http://127.0.0.1:32815 RUNNING
128
+ metrics: 9001/tcp -> 127.0.0.1:32816
129
+ d63d3aeaa06b op-challenger-rollup-1 metrics: 9001/tcp -> 127.0.0.1:32819 RUNNING
130
+ 632c061ac1b7 op-cl-1-op-node-op-geth-rollup-1 http: 8547/tcp -> http://127.0.0.1:32812 RUNNING
131
+ metrics: 9001/tcp -> 127.0.0.1:32813
132
+ tcp-discovery: 9003/tcp -> 127.0.0.1:32814
133
+ udp-discovery: 9003/udp -> 127.0.0.1:32777
134
+ 0e0d1e6c2269 op-el-1-op-geth-op-node-rollup-1 engine-rpc: 8551/tcp RUNNING
135
+ metrics: 9001/tcp
136
+ rpc: 8545/tcp
137
+ tcp-discovery: 30303/tcp
138
+ udp-discovery: 30303/udp
139
+ ws: 8546/tcp
140
+ 544b3f952009 op-proposer-rollup-1 http: 8560/tcp -> http://127.0.0.1:32817 RUNNING
141
+ metrics: 9001/tcp -> 127.0.0.1:32818
142
+ 5b8cc317a573 prometheus http: 9090/tcp -> http://127.0.0.1:32820 RUNNING
143
+ 61ba4bff3ab8 validator-key-generation-cl-validator-keystore <none> RUNNING
132
144
```
133
145
134
146
Also take note of the last log line above this message, which contains the address of the standard bridge. You'll
@@ -162,13 +174,13 @@ To move ETH onto your L2, run the following command. Make sure to replace the va
162
174
163
175
``` bash
164
176
cast send --mnemonic ' test test test test test test test test test test test junk' --mnemonic-path " m/44'/60'/0'/0/0" \
165
- --to "<standard bridge address>" --amount "<amount in ETH>eth" --rpc-url "http://127.0.0.1:<rpc port of el-1-geth-lighthouse service>"
177
+ --to " <standard bridge address>" --amount " <amount in ETH>eth" --rpc-url " http://127.0.0.1:<rpc port of el-1-geth-teku service>"
166
178
```
167
179
168
180
Wait \~ 30 seconds, then check your balance on L2 by running the following command:
169
181
170
182
``` bash
171
- export ETH_RPC_URL="http://127.0.0.1:<rpc port of el-1-geth-lighthouse service>"
183
+ export ETH_RPC_URL=" http://127.0.0.1:<rpc port of el-1-geth-teku service>"
172
184
export ADDRESS=" 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266"
173
185
cast balance " $ADDRESS "
174
186
```
0 commit comments