Veriscope Implementation Checklists for VASPs

Install Veriscope (Phase 0)

Start by installing Veriscope. If you have a machine provisioned, this should take no-longer than ~30-60 minutes.

  • Provision a machine that is reachable over the internet on ports 80 and 443 and has a DNS name that points to it

  • Follow the installation guide and install Veriscope via the set-up script

  • Check that your node is synchronized with the Shyft Network

  • Sign and return the Shyft Mutual Non-Disclosure Agreement

  • Sign and return the Veriscope Trust Anchor Agreement. Available on request.

  • Request your trust anchor account to be verified on testnet / mainnet

Phase 1 - POST

  • Log-in to the Veriscope web-application and post your VASP Discovery Layer data on-chain

  • Explore and test the Veriscope APIs Postman Collection

  • Discuss your implementation plan/approach with the Veriscope team

  • Complete phase 1 and start posting attestations!

Phase 2 - LISTEN

  • Start listenting to attestations on addresses that you own

  • Engage with your peers and discuss how to share IVMS data

  • Decide if you are going to require VASPs to respond to your attestations with address proofs

  • Decide if you are going to respond to attestations with address proofs; if yes, generate & cache proofs

Phase 3 - RESPOND

  • Log-in to the Veriscope web-application and complete your VASP IVMS Profile

  • Test the end-to-end flow (including peer-to-peer data transfer, address proofs, accept/reject messages) using the Veriscope (Postman Collection)

  • Understand the Veriscope state machines and webhook events/statuses

  • Finalize your backend/server-side architecture and optionally discuss with the Veriscope team (Recommended before your start the implementation!)

  • Implement logic to respond to attestations, encrypt/decrypt user data, and post kyc-templates

  • Conduct an end-to-end test with the Veriscope team and at least one other VASP

  • Sign and return the Veriscope Information Form (VIF). Available on request.

  • Acquire native mainnet SHFT tokens (to enable you to post data on-chain)

  • Ensure your production/mainnet infrastructure is secure and update environment variables

  • Request to be onboarded & verified on mainnet

  • (Optional) Request verification and attestation on-chain via a third party

Address Proofs

  • Sign the Veriscope Trust Anchor agreement or an addendum to your existing agreement

  • Request access to the ShyftNetwork/addressproofs repo. The GitHub username that you provide will be added to the repo as a collaborator.

  • Generate a GitHub classic personal access token with scopes equal to repo (full access).

  • Install Veriscope

  • Once the installation is complete run step 16 in the set-up script. You will be prompted to enter the GitHub token created above. Enter and hit return. This downloads the proofs onto your node.

  • Verify that the addressproofs folder exists at /opt/veriscope/veriscope_addressproofs

  • Next, install the proofs by running the following commands:

pip3 install -r requirements.txt

Also install protobuf compiler from your system’s package manager:

sudo apt-get install protobuf-compiler

For some proof types, NodeJS is required. The Python library will call out to Javascript to run these verifications. Install NodeJS and then run:

npm install
Moving to Shyft Mainnet

Once you have successfully tested the end-to-end flow with both Veriscope and at least one other VASP, you can request to be onboarded to mainnet. Please reach-out to your Veriscope contact or email [email protected].

Each VASP must sign & return a Veriscope Information Form (VIF) before being onboarded to mainnet. This is available on request.