A Note on Node Synchronization

During installation, Veriscope needs to download & install historical data. There are two elements to this:

  • Relay Node synchronization with the Shyft Network

  • "Event" synchronization with transactions on the Shyft Network and their corresponding emitted events.

These processes are sequential and the Relay (Nethermind) Node must be synchronized before the event data is downloaded and synced. The event data comes from the Node itself.

The expected duration for both processes to complete is between 4-6 hours (assuming 2 CPU cores, 16 GB RAM)

Relay Node (Nethermind) synchronization

Nodes in green are fully synchronized.

If you can't see your Node at either of the domains above and you haven't hidden it (i.e. set `ethstats` to false in your Nethermind config file), SSH into your machine and restart all services. Run the `setup-vasp.sh` script and select `w` to restart services.

Additionally, you can run the following command to check your Node is online and is syncing:


systemctl status nethermind

== "Event" synchronization

Events in this context are:

* Verified Trust Anchors,
* Discovery Layer Key Value Pairs, and
* Attestations

Downloaded events can be seen in your Veriscope application in the Backoffice section.


If you suspect some events are missing, SSH into your machine and restart all services. Run the setup-vasp.sh script and select w to restart services. This will initiate a re-sync.

Additionally, you can run the following commands to check the event sync (aka eth-sync) and are running as expected

systemctl status ta-node-1
journalctl -f -u ta-node-1