Skip to content

Commit 01216fe

Browse files
authored
Merge pull request 0xPolygon#206 from 0xPolygon/EmpieichO-patch-1
Update production-node.md
2 parents 9a64240 + 01c0938 commit 01216fe

File tree

1 file changed

+17
-7
lines changed

1 file changed

+17
-7
lines changed

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

Lines changed: 17 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -73,24 +73,34 @@ Let's start setting up our zkNode:
7373
ZKEVM_CONFIG_DIR=./path_to_config
7474
```
7575

76-
1. Download and extract the artifacts. Note that you may need to [install unzip](https://formulae.brew.sh/formula/unzip) before running this command.
76+
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-
```bash
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+
80+
```bash
81+
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
82+
```
83+
84+
And use this second command for either mainnet or testnet (Goerli):
85+
86+
```bash
7987
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
8088
```
8189

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

8492
```sh
8593
cp $ZKEVM_DIR/$ZKEVM_NET/example.env $ZKEVM_CONFIG_DIR/.env
8694
8795
```
8896

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

9199
Edit the .env file with your favourite editor (we'll use nano in this guide): ```nano $ZKEVM_CONFIG_DIR/.env```
92100
93101
```bash
102+
# ZKEVM_NETWORK = "mainnet" or ZKEVM_NETWORK = "cardona" or ZKEVM_NETWORK = "testnet"
103+
94104
# URL of a JSON RPC for Goerli
95105
ZKEVM_NODE_ETHERMAN_URL = "http://your.L1node.url"
96106
@@ -101,13 +111,13 @@ Let's start setting up our zkNode:
101111
ZKEVM_NODE_POOLDB_DATA_DIR = "/path/to/persistent/data/pooldb"
102112
```
103113
104-
5. To run the zkNode instance, run the following command:
114+
6. To run the zkNode instance, run the following command:
105115
106116
```bash
107117
sudo docker compose --env-file $ZKEVM_CONFIG_DIR/.env -f $ZKEVM_DIR/$ZKEVM_NET/docker-compose.yml up -d
108118
```
109119
110-
6. Run this command to check if everything went well and all the components are running properly:
120+
7. Run this command to check if everything went well and all the components are running properly:
111121
112122
```bash
113123
docker compose --env-file $ZKEVM_CONFIG_DIR/.env -f $ZKEVM_DIR/$ZKEVM_NET/docker-compose.yml ps
@@ -120,7 +130,7 @@ Let's start setting up our zkNode:
120130
- **zkevm-pool-db**
121131
- **zkevm-prover**
122132
123-
7. You should now be able to run queries to the JSON-RPC endpoint at `http://localhost:8545`.
133+
8. You should now be able to run queries to the JSON-RPC endpoint at `http://localhost:8545`.
124134
125135
## Testing
126136

0 commit comments

Comments
 (0)