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
| 1 | Deploy a local layer 1 Ethereum chain |[ethereum.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/ethereum.star)| True |
56
49
| 2 | Deploy the CDK smart contracts on the L1 |[deploy_zkevm_contracts.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/deploy_zkevm_contracts.star)| True |
57
-
| 3 | Deploy the central environment, prover, and CDK erigon or zkEVM node databases |[databases.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/databases.star)| True |
58
-
| 4 | Deploy the CDK central environment |[cdk_central_environment.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_central_environment.star)| True |
59
-
| 5 | Deploy the CDK erigon package |[cdk_erigon.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_erigon.star) - included in step 4 deployment | True |
60
-
| 6 | Deploy the bridge infrastructure |[cdk_bridge_infrastructure.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_bridge_infra.star)| True |
61
-
| 7 | Deploy the AggLayer |[agglayer.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/agglayer.star)| True |
50
+
| 3 | Deploy the central environment, prover, and CDK erigon or zkEVM node databases | [databases.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/databases.star)
51
+
| 4 | Get the genesis file | n/a | False |
52
+
| 5 | Deploy the CDK central environment |[cdk_central_environment.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_central_environment.star)| True |
53
+
| 6 | Deploy the CDK erigon package |[cdk_erigon.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_erigon.star) - included in step 4 deployment | True |
54
+
| 7 | Deploy the bridge infrastructure |[cdk_bridge_infrastructure.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_bridge_infra.star)| True |
55
+
| 8 | Deploy the AggLayer |[agglayer.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/agglayer.star)| True |
| - | Input parser tool to help deployment stages |[input_parser.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/input_parser.star) - deployed immediately | n/a |
63
58
| - | zkEVM pool manager tool |[zkevm_pool_manager.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/zkevm_pool_manager.star) - deployed with CDK erigon node | n/a |
64
59
@@ -79,31 +74,22 @@ You can modify each of these parameters to customize the chain to your specific
79
74
80
75
## Run the chain locally
81
76
82
-
1.Run the [kurtosis clean](https://docs.kurtosis.com/clean)to remove any existing Kurtosis environments:
77
+
1.In the `kurtosis-cdk` directory, use the [kurtosis run](https://docs.kurtosis.com/run) command to deploy the chain on your local machine by executing the `main.star` script provided with the `params.yml` configuration file:
83
78
84
79
```bash
85
-
kurtosis clean --all
80
+
kurtosis run --enclave cdk github.com/0xPolygon/kurtosis-cdk
86
81
```
87
82
88
-
2. In the `kurtosis-cdk` directory, use the [kurtosis run](https://docs.kurtosis.com/run) command to deploy the chain on your local machine by executing the `main.star` script provided with the `params.yml` configuration file:
89
-
90
-
```bash
91
-
kurtosis run --enclave cdk-v1 --args-file params.yml --image-download always .
92
-
```
93
-
94
-
- `enclave cdk-v1` specifies the name of the enclave, or isolated environment, to use for the deployment process.
95
-
- `args-file params.yml` specifies the configuration file to use for the deployment process.
96
-
- `image-download` specifies to always download the latest Docker images for the deployment process.
97
-
98
-
3. This command typically takes a while to complete and outputs the logs of each step in the deployment process for you to monitor the progress of the chain setup. Once the command is complete, you should see the following output:
83
+
2. This command typically takes a while to complete and outputs the logs of each step in the deployment process for you to monitor the progress of the chain setup. Once the command is complete, you should see the following output:
99
84
100
85
```bash
101
86
Starlark code successfully run. No output was returned.
@@ -116,13 +102,29 @@ You can modify each of these parameters to customize the chain to your specific
116
102
117
103
```
118
104
119
-
3. Inspect the chain
105
+
The default deployment includes `cdk-erigon` as the sequencer, and `cdk-node` functioning as the sequence sender and aggregator.
120
106
121
-
Run the following command to see the status of the enclave and the services running within it at any time.
107
+
You can verify the default versions of these components and the default fork ID by reviewing `input_parser.star`. You can check the default versions of the deployed components and the default fork ID by looking at `input_parser.star`.
122
108
123
-
```sh
124
-
kurtosis enclave inspect cdk-v1
125
-
```
109
+
3. Customize the chain
110
+
111
+
To make customizations to the CDK environment, clone this repo, make any desired configuration changes, and then run:
112
+
113
+
```sh
114
+
# Delete all stop and clean all currently running enclaves
115
+
kurtosis clean --all
116
+
117
+
# Run this command from the root of the repository to start the network
118
+
kurtosis run --enclave cdk .
119
+
```
120
+
121
+
4. Inspect the chain
122
+
123
+
Get a feel for the entire network layout by running the following command:
124
+
125
+
```sh
126
+
kurtosis enclave inspect cdk
127
+
```
126
128
127
129
## Interacting with the chain
128
130
@@ -134,40 +136,57 @@ Below are a few examples of how you can interact with the chain.
134
136
135
137
Let's do some read and write operations and test transactions on the L2 with Foundry.
136
138
137
-
1. Use `cast` to view information about the chain, such as the latest block number:
139
+
1. To facilitate the operations, export the RPC URL of your L2 to an environment variable called `ETH_RPC_URL` with the following command:
140
+
141
+
```bash
142
+
export ETH_RPC_URL="$(kurtosis port print cdk cdk-erigon-node-001 rpc)"
143
+
```
144
+
145
+
2. Use `cast` to view information about the chain, such as the latest block number:
138
146
139
147
```bash
140
148
cast block-number
141
149
```
142
150
143
-
2. View the balance of an address, such as the pre-funded admin account:
151
+
3. View the balance of an address, such as the pre-funded admin account:
The `0xE34...9970` and `0x12d...c625` public-private key pair used in the above commands is the default admin account configured in `params.yml`.
157
-
158
164
### Load testing the chain
159
165
160
-
1. Export the RPC URL of your L2 to an environment variable called `ETH_RPC_URL` with the following command:
166
+
1. Use the [`polycli loadtest`](https://github.com/maticnetwork/polygon-cli/blob/main/doc/polycli_loadtest.md) command to send multiple transactions at once to the chain to test its performance:
161
167
162
168
```bash
163
-
export ETH_RPC_URL="$(kurtosis port print cdk-v1 cdk-erigon-node-001 http-rpc)"
2. Use the [`polycli loadtest`](https://github.com/maticnetwork/polygon-cli/blob/main/doc/polycli_loadtest.md) command to send multiple transactions at once to the chain to test its performance:
0 commit comments