Skip to content

Commit efe2c81

Browse files
authored
Update production-node.md
Adding Cardona v0.5.6 link
1 parent df02b34 commit efe2c81

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/zkEVM/get-started/setup-nodes/production-node.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -75,26 +75,26 @@ Let's start setting up our zkNode:
7575

7676
2. Download and extract the artifacts. Note that you may need to [install unzip](https://formulae.brew.sh/formula/unzip) before running this command. Also, unlike the mainnet and the Goerli testnet that use the latest version, Cardona testnet uses a specific version.
7777

78-
So use the next `curl` command specifically for Cardona, which uses version 0.5.5 (Note that the latest version, Cardona v0.5.6, is available and can equally be used.):
79-
78+
So use the next `curl` command specifically for Cardona, which uses version 0.5.5 (Note that the latest version, [Cardona v0.5.6](https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.5.6), is available and can equally be used.):
79+
8080
```bash
8181
curl -L https://github.com/0xPolygonHermez/zkevm-node/releases/download/v0.5.5/$ZKEVM_NET.zip > $ZKEVM_NET.zip && unzip -o $ZKEVM_NET.zip -d $ZKEVM_DIR && rm $ZKEVM_NET.zip
8282
```
8383

8484
And use this second command for either mainnet or testnet (Goerli):
85-
85+
8686
```bash
8787
curl -L https://github.com/0xPolygonHermez/zkevm-node/releases/latest/download/$ZKEVM_NET.zip > $ZKEVM_NET.zip && unzip -o $ZKEVM_NET.zip -d $ZKEVM_DIR && rm $ZKEVM_NET.zip
88-
```
88+
```
8989

90-
4. Copy the `example.env` file with the environment parameters:
90+
3. Copy the `example.env` file with the environment parameters:
9191

9292
```sh
9393
cp $ZKEVM_DIR/$ZKEVM_NET/example.env $ZKEVM_CONFIG_DIR/.env
9494
9595
```
9696

97-
5. The `example.env` file must be modified according to your configurations.
97+
4. The `example.env` file must be modified according to your configurations.
9898

9999
Edit the .env file with your favourite editor (we'll use nano in this guide): ```nano $ZKEVM_CONFIG_DIR/.env```
100100
@@ -111,13 +111,13 @@ Let's start setting up our zkNode:
111111
ZKEVM_NODE_POOLDB_DATA_DIR = "/path/to/persistent/data/pooldb"
112112
```
113113
114-
6. To run the zkNode instance, run the following command:
114+
5. To run the zkNode instance, run the following command:
115115
116116
```bash
117117
sudo docker compose --env-file $ZKEVM_CONFIG_DIR/.env -f $ZKEVM_DIR/$ZKEVM_NET/docker-compose.yml up -d
118118
```
119119
120-
7. Run this command to check if everything went well and all the components are running properly:
120+
6. Run this command to check if everything went well and all the components are running properly:
121121
122122
```bash
123123
docker compose --env-file $ZKEVM_CONFIG_DIR/.env -f $ZKEVM_DIR/$ZKEVM_NET/docker-compose.yml ps
@@ -130,7 +130,7 @@ Let's start setting up our zkNode:
130130
- **zkevm-pool-db**
131131
- **zkevm-prover**
132132
133-
8. You should now be able to run queries to the JSON-RPC endpoint at `http://localhost:8545`.
133+
7. You should now be able to run queries to the JSON-RPC endpoint at `http://localhost:8545`.
134134
135135
## Testing
136136

0 commit comments

Comments
 (0)