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
2. Create a keystore for reference in the `config.toml` configuration file. Use the private key we generated previously and stored in the `/tmp/cdk/.env` file and encrypt it with a basic password. For example:
4. Modify the `URL` parameter in`[Etherman]` to the URL of the RPC Provider, along with the parameters `L2Coinbase` in `[SequenceSender]` and `SenderAddress` in `[Aggregator]` to the address we generated earlier by running the following script.
215
213
@@ -337,17 +335,16 @@ Now let’s configure the Data Availability Committee.
337
335
338
336
## Configure bridge service
339
337
340
-
1. Navigate into the `cdk-bridge-service-0.3.1` directory and build the files.
338
+
1. Navigate into the `zkevm-bridge-service-0.3.1` directory and build the files.
341
339
342
340
```bash
343
-
cd ~/cdk-validium/cdk-bridge-service-0.3.1/
341
+
cd ~/cdk-validium/zkevm-bridge-service-0.3.1/
344
342
make build
345
343
```
346
344
347
345
2. Create a starter bridge config `bridge-config.toml` inside `/tmp/cdk` using the following config file:
0 commit comments