You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+42-23Lines changed: 42 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,5 @@
1
-
## Welcome to Optimism Package
1
+
# Welcome to Optimism Package
2
+
2
3
The default package for Optimism. The kurtosis package uses [op-deployer](https://github.com/ethereum-optimism/optimism/tree/develop/op-deployer) to manage
3
4
the L2 chains and all associated artifacts such as contract deployments.
4
5
@@ -33,7 +34,8 @@ Please note, by default your network will be running a `minimal` preset Ethereum
33
34
You can also completely remove `ethereum_package` from your configuration in which case it will default to a `minimal` preset Ethereum network.
34
35
35
36
## Quickstart
36
-
#### Run with your own configuration
37
+
38
+
### Run with your own configuration
37
39
38
40
Kurtosis packages are parameterizable, meaning you can customize your network and its behavior to suit your needs by storing parameters in a file that you can pass in at runtime like so:
39
41
@@ -51,7 +53,7 @@ kurtosis clean -a
51
53
52
54
This will stop and remove all running enclaves and **delete all data**.
53
55
54
-
####Run with changes to the optimism package
56
+
### Run with changes to the optimism package
55
57
56
58
If you are attempting to test any changes to the package code, you can point to the directory as the `run` argument
57
59
@@ -60,11 +62,11 @@ cd ~/go/src/github.com/ethpandaops/optimism-package
60
62
kurtosis run . --args-file ./network_params.yaml
61
63
```
62
64
63
-
# L2 Contract deployer
64
-
The enclave will automatically deploy an optimism L2 contract on the L1 network. The contract address will be printed in the logs. You can use this contract address to interact with the L2 network.
65
+
## L2 Contract deployer
65
66
66
-
Please refer to this Dockerfile if you want to see how the contract deployer image is built: [Dockerfile](https://github.com/ethpandaops/eth-client-docker-image-builder/blob/master/op-contract-deployer/Dockerfile)
67
+
The enclave will automatically deploy an optimism L2 contract on the L1 network. The contract address will be printed in the logs. You can use this contract address to interact with the L2 network.
67
68
69
+
Please refer to this Dockerfile if you want to see how the contract deployer image is built: [Dockerfile](https://github.com/ethereum-optimism/optimism/blob/develop/op-deployer/Dockerfile.default)
68
70
69
71
## Configuration
70
72
@@ -73,6 +75,20 @@ The full YAML schema that can be passed in is as follows with the defaults provi
73
75
74
76
```yaml
75
77
optimism_package:
78
+
# Interop configuration
79
+
interop:
80
+
# Whether or not to enable interop mode
81
+
enabled: false
82
+
# Default supervisor configuration
83
+
supervisor_params:
84
+
# The Docker image that should be used for the supervisor; leave blank to use the default op-supervisor image
85
+
image: ""
86
+
87
+
# A JSON string containing chain dependencies
88
+
dependency_set: ""
89
+
90
+
# A list of optional extra params that will be passed to the supervisor container for modifying its behaviour
91
+
extra_params: []
76
92
# An array of L2 networks to run
77
93
chains:
78
94
# Specification of the optimism-participants in the network
@@ -403,7 +419,7 @@ ethereum_package:
403
419
404
420
#### L1 customization
405
421
406
-
It is required you to launch an L1 Ethereum node to interact with the L2 network. You can use the `ethereum_package` to launch an Ethereum node. The `ethereum_package` configuration is as follows:
422
+
It is required for you to launch an L1 Ethereum node to interact with the L2 network. You can use the `ethereum_package` to launch an Ethereum node. The `ethereum_package` configuration is as follows:
407
423
408
424
```yaml
409
425
optimism_package:
@@ -501,6 +517,7 @@ ethereum_package:
501
517
- dora
502
518
- blockscout
503
519
```
520
+
504
521
Note: if configuring multiple L2s, make sure that the `network_id` and `name` are set to differentiate networks.
505
522
506
523
#### Rollup Boost for External Block Building
@@ -525,49 +542,51 @@ optimism_package:
525
542
526
543
#### Run tx-fuzz to send l2 transactions
527
544
528
-
Compile https://github.com/MariusVanDerWijden/tx-fuzz locally per instructions in the repo. Run tx-fuzz against the l2 EL client's RPC URL and using the pre-funded wallet
545
+
Compile [tx-fuzz](https://github.com/MariusVanDerWijden/tx-fuzz) locally per instructions in the repo. Run tx-fuzz against the l2 EL client's RPC URL and using the pre-funded wallet:
0 commit comments