Maintaining & updating your Node

Releases of Veriscope occur often. Before deploying a new release, ensure you have backed-up your trust anchor account (TRUST_ANCHOR_ACCOUNT) and trust anchor private key (TRUST_ANCHOR_PK).

In the event you wish to do a clean deploy, after you complete the installation, replace the newly created trust anchor account with your backup.

cd /opt/veriscope/veriscope_ta_node/.env

#From v3.6.0, Multiple Trust Anchors can be added as illustrated
#DO NOT INCLUDE "0x" prefix in TRUST_ANCHOR_PK
TRUST_ANCHOR_PREFNAME="Singapore VASP", "ta1", "ta2"
TRUST_ANCHOR_ACCOUNT=0x...15, 0x...25, 0x...35
TRUST_ANCHOR_PK=aa...10, ab...20, ac...30
WEBHOOK_CLIENT_SECRET=abcdefg*

HTTP="http://localhost:8545"
WS="ws://localhost:8545"
WEBHOOK="http://localhost:8000/webhook"
HTTP_API_PORT=8080
TEMPLATE_HELPER_PORT=8090

CONTRACTS=/opt/veriscope/veriscope_ta_node/artifacts/

#Veriscope Smart Contracts
TRUST_ANCHOR_MANAGER_CONTRACT_ADDRESS="0x........06"
TRUST_ANCHOR_STORAGE_CONTRACT_ADDRESS="0x........66"
TRUST_ANCHOR_EXTRA_DATA_GENERIC_CONTRACT_ADDRESS="0x.......4c"
TRUST_ANCHOR_EXTRA_DATA_UNIQUE_CONTRACT_ADDRESS="0x........a8"

#redis
REDIS_URI=redis://127.0.0.1:6379
LOG_LEVEL=info

SIGN_MESSAGE="VERISCOPE"

As mentioned in the example, do not include "0x" prefix in TRUST_ANCHOR_PK value(s)!

Then restart ta-node-1 and ta-node-2 as as follows:

sudo systemctl stop nethermind
sudo systemctl restart ta-node-1
sudo systemctl restart ta-node-2