Skip to content

Commit e911ab1

Browse files
update the quickstart to run services
1 parent a7d97fe commit e911ab1

File tree

2 files changed

+12
-17
lines changed

2 files changed

+12
-17
lines changed

docs/cdk/get-started/deploy-validium/node/configure-deployment.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ jq '.aggregatorClientHost = "127.0.0.1" | .databaseURL = "postgresql://cdk_user:
1919
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:
2020

2121
```bash
22-
$ source /tmp/cdk/.env
23-
$ ./dist/zkevm-node encryptKey --pk=$TEST_PRIVATE_KEY --pw="testonly" --output=/tmp/cdk/account.keystore
24-
$ find /tmp/cdk/account.keystore -type f -name 'UTC--*' | head -n 1 | xargs -I xxx mv xxx /tmp/cdk/account.key
22+
source /tmp/cdk/.env
23+
./dist/zkevm-node encryptKey --pk=$TEST_PRIVATE_KEY --pw="testonly" --output=/tmp/cdk/account.keystore
24+
find /tmp/cdk/account.keystore -type f -name 'UTC--*' | head -n 1 | xargs -I xxx mv xxx /tmp/cdk/account.key
2525
```
2626

2727
!!! important
@@ -31,8 +31,7 @@ jq '.aggregatorClientHost = "127.0.0.1" | .databaseURL = "postgresql://cdk_user:
3131

3232
3. Create a file `node-config.toml` inside `/tmp/cdk/` and paste in the following content.
3333

34-
??? "`node-config.toml`"
35-
```bash
34+
??? "`node-config.toml`"
3635
#/tmp/cdk/node-config.toml
3736
IsTrustedSequencer = true
3837

@@ -209,7 +208,6 @@ jq '.aggregatorClientHost = "127.0.0.1" | .databaseURL = "postgresql://cdk_user:
209208
Port = "5432"
210209
EnableLog = false
211210
MaxConns = 200
212-
```
213211

214212
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.
215213

@@ -337,17 +335,16 @@ Now let’s configure the Data Availability Committee.
337335

338336
## Configure bridge service
339337

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.
341339

342340
```bash
343-
cd ~/cdk-validium/cdk-bridge-service-0.3.1/
341+
cd ~/cdk-validium/zkevm-bridge-service-0.3.1/
344342
make build
345343
```
346344

347345
2. Create a starter bridge config `bridge-config.toml` inside `/tmp/cdk` using the following config file:
348346

349347
```bash
350-
nano /tmp/cdk/bridge-config.toml
351348
#/tmp/cdk/bridge-config.toml
352349
[Log]
353350
Level = "info"

docs/cdk/get-started/deploy-validium/node/run-node-services.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,12 @@
1-
## Running the components
1+
## Run the prover
22

3-
### Run the prover
4-
5-
Since the prover is large and rather compute expensive to build, we will use a docker container
3+
Since the prover is large and compute-expensive to build, we will use a docker container.
64

75
```bash
86
docker run -v "/tmp/cdk/test.prover.config.json:/usr/src/app/config.json" -p 50061:50061 -p 50071:50071 --network host hermeznetwork/zkevm-prover:v3.0.2 zkProver -c /usr/src/app/config.json
97
```
108

11-
### Run the node
9+
## Run the node
1210

1311
```bash
1412
~/cdk-validium/cdk-validium-node % ./dist/zkevm-node run --network custom --custom-network-file /tmp/cdk/genesis.json --cfg /tmp/cdk/node-config.toml \
@@ -21,7 +19,7 @@ docker run -v "/tmp/cdk/test.prover.config.json:/usr/src/app/config.json" -p 500
2119
--components l2gaspricer
2220
```
2321

24-
Run the additional approval scripts for node:
22+
### Run the additional approval scripts for the node
2523

2624
```bash
2725
~/cdk-validium/cdk-validium-node % ./dist/zkevm-node approve --network custom \
@@ -31,13 +29,13 @@ Run the additional approval scripts for node:
3129
--password "testonly" --yes --key-store-path /tmp/cdk/account.key
3230
```
3331

34-
### Run the DAC
32+
## Run the DAC
3533

3634
```bash
3735
~/cdk-validium/cdk-data-availability-0.0.3 % ./dist/cdk-data-availability run --cfg /tmp/cdk/dac-config.toml
3836
```
3937

40-
### Run the Bridge Service
38+
## Run the bridge service
4139

4240
```bash
4341
~/cdk-validium/cdk-bridge-service % ./dist/zkevm-bridge run --cfg /tmp/cdk/bridge-config.toml

0 commit comments

Comments
 (0)