Multiple Trust Anchors

Veriscope now supports multiple trust anchors (MTAs) thus enabling VASPs and Service Providers to deploy a single Veriscope instance and run multiple trust anchor accounts.

This is particularly useful for VASPs that operate multiple entities (e.g. Binance Australia, Bahrain, Cyprus etc.) and Service Providers who service 100s of individual VASP entities (e.g. Sygna).

Support for MTAs was introduced in Veriscope v3.6.0 and is backwards compatible. To upgrade an earlier version of Veriscope, please follow the instructions in our Veriscope Change Log.

How MTAs are handled

MTAs are handled in the Veriscope Node .env file:

cd ~/veriscope/veriscope_ta_node/.env

  1. which includes three variables for trust anchor(s):

    • TRUST_ANCHOR_PREFNAME

    • TRUST_ANCHOR_ACCOUNT

    • TRUST_ANCHOR_PK

Multiple trust anchors can be added via a comma separated list, e.g.:

* `TRUST_ANCHOR_PREFNAME`="ta1", "ta2", "ta3", "ta4", "ta5"
* `TRUST_ANCHOR_ACCOUNT`=0x...15, 0x...25, 0x...35, etc.
* `TRUST_ANCHOR_PK`=aa...10, ab...20, ac...30, etc.

There is no upper limit to how many trust anchors can be added.

Sample Node .env file 
#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)!

Veriscope UI

The Veriscope UI now supports multiple trust anchors. In particular, the VASP Profile (prev. Manage Your Organization) page where trust anchor data is viewed, IVMS data is added, and key-value pairs are set have all been updated. To view the latest UI, see the Get comfortable with the Veriscope Web Application page.

Veriscope API

The Veriscope API nows support multiple trust anchors. Trust anchor account address has been added as a variable to each of the following endpoints:

Endpoints Added

  • …​/api/v1/server/get_verified_trust_anchors

  • …​/api/v1/server/set_ta_key_value_pair

  • …​/api/v1/server/get_ta_key_value_pairs/[INSERT_TA_ACCOUNT]

Endpoints Removed

  • …​/api/v1/server/get_verified_trust_anchor

Endpoints Updated

  • …​/api/v1/server/create_kyc_template: ta_account added as an input key

  • …​/api/v1/server/retry_kyc_template?attestation_hash=&ta_account=: ta_account added as a query param

For more information on each of these endpoints, check-out the Veriscope API docs and supporting examples.

Postman Collection

The Veriscope Postman Collection has been updated to support multiple trust anchors. Please make sure you download the latest collection.