Configuring the tool

Configuration for the Züs network by default is stored in network/config.yaml file of the zwallet github repo which we will copy to a new config.yaml file in our local system .

Configuration File

  1. Make a new .zcn folder in the home directory of your system

mkdir $HOME/.zcn

Note: For windows create a folder named .zcn at `C:\Users\<windows_username>`path. 2. Copy config.yaml from zwalletcli repo to .zcn directory

cp network/config.yaml $HOME/.zcn/config.yaml
  1. Open the config.yaml file located at $HOME/.zcn path of your system.The contents should be similar to the file below.

---
block_worker: https://demo.zus.network/dns
signature_scheme: bls0chain
min_submit: 50
min_confirmation: 50
confirmation_chain_length: 3
max_txn_query: 5
query_sleep_time: 5
# # OPTIONAL - Uncomment to use/ Add more if you want
# preferred_blobbers:
#   - http://one.devnet-0chain.net:31051
#   - http://one.devnet-0chain.net:31052
#   - http://one.devnet-0chain.net:31053

Zwallet connects to the Züs network using the block_worker field. These network details are automatically fetched from the blockWorker's network API. Preferred Blobbers are also present which you can uncomment for using specified storage providers for handling your files.

Overriding the Network

Network nodes are automatically discovered using the block_worker provided on config file.

To override/limit the nodes used on zwallet, create ~/.zcn/network.yaml as shown below.

cat > ~/.zcn/network.yaml << EOF
miners:
  - http://demo1.zus.network:31201
  - http://demo1.zus.network:31202
  - http://demo1.zus.network:31203
sharders:
  - http://demo1.zus.network:31101
EOF

Overriding the nodes can be useful in local chain setup. In some cases, the block worker might return URLs with IP/alias only accessible within the docker network.

Last updated