Fix readme (#18)

stakewise · Feb 17, 2022 · f195b64 · f195b64
1 parent fd1a8a3
commit f195b64
Showing 1 changed file with 9 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -28,10 +28,10 @@ In your post you must include the `Specification` section that was generated in
 
 ### Step 4. Deploy ETH2 infrastructure
 
-If the proposal from the previous step got approved by the DAO, follow the instructions [here](https://docs.stakewise.io/node-operator/infrastructure)
+If the proposal from the previous step got approved by the DAO, follow the instructions [here](https://docs.stakewise.io/node-operator/stakewise-infra-package)
 to deploy the ETH2 staking infrastructure.
 
-### Step 5. Sync keys to the Vault
+### Step 5. Sync keys to the Vault or locally
 
 You must **use the same mnemonic** as generated in step 1.
 **NB! Using the same mnemonic for multiple vaults will result into validators slashings**.
@@ -42,13 +42,19 @@ Run the following command to sync new validator keys to the vault:
 ./operator-cli sync-vault
 ```
 
+or to sync them locally
+
+```bash
+./operator-cli sync-local
+```
+
 After uploading the keys, make sure you have the right number of validators running and restart those that got new keys added.
 
 ### Step 6. Commit Operator
 
 Once you're 100% ready for Ether assignments, commit your operator:
 
-- Go to the Operators smart contract ([Goerli](https://goerli.etherscan.io/address/0x0d92156861a0BC7037cC21470327Bd3Bc750EB1D#writeProxyContract), Mainnet)
+- Go to the Operators smart contract ([Goerli](https://goerli.etherscan.io/address/0x0d92156861a0BC7037cC21470327Bd3Bc750EB1D#writeProxyContract), [Mainnet](https://etherscan.io/address/0x002932e11E95DC84C17ed5f94a0439645D8a97BC))
 - Click on `Connect to Web3` button and connect your wallet. The address must match the one used during proposal generation.
 - Call `commitOperator` function. If that's your onboarding, you must deposit 1 ETH (specified in Wei) collateral together with the call.
 
@@ -60,8 +66,6 @@ Your validators will get ether assigned, and you can claim your operator rewards
 
 | Variable                       | Description                                                                      | Required | Default                                                                 |
 |--------------------------------|----------------------------------------------------------------------------------|----------|-------------------------------------------------------------------------|
-| MAINNET_WITHDRAWAL_CREDENTIALS | The withdrawal credentials of the validators used in mainnet deposit data        | No       | 0x0100000000000000000000002296e122c1a20fca3cac3371357bdad3be0df079      |
-| PRATER_WITHDRAWAL_CREDENTIALS  | The withdrawal credentials of the validators used in prater testnet deposit data | No       | 0x010000000000000000000000040f15c6b5bfc5f324ecab5864c38d4e1eef4218      |
 | IPFS_PIN_ENDPOINTS             | The IPFS endpoint where the deposit data will be uploaded                        | No       | /dns/ipfs.infura.io/tcp/5001/https                                      |
 | IPFS_FETCH_ENDPOINTS           | The IPFS endpoints from where the deposit data will be fetched                   | No       | https://gateway.pinata.cloud,http://cloudflare-ipfs.com,https://ipfs.io |
 | IPFS_PINATA_API_KEY            | The Pinata API key for uploading deposit data for the redundancy                 | No       | -                                                                       |