Shyft Veriscope

Protocol details

Open Source




Data transport protocol


Installed on-premise


Blockchain based


VASP authentication method

Shyft Network Smart Contract


Together with the Shyft Network, Veriscope enables VASPs to discover which VASP owns a (hosted) wallet address and is the only solution that solves for address discovery at scale without impacting the end-user experience.

Veriscope enables VASPs to:

  • Post attestations (i.e. requests to withdraw/transfer funds to a wallet address)

  • Listen to attestations on wallet addresses

  • Respond to attestations via a secure peer-to-peer https channel and:

    • Include an address ownership proof

    • Share encrypted KYC/IVMS data

    • Accept/Reject transactions

Registration & set-up process

  1. Install Veriscope. This will create a VASP "trust anchor" account on the Shyft Network.

  2. Complete VASP profile and request it to be verified

  3. Start posting attestations and encourage counterparties to join the network

  4. Start listening attestations

  5. Start responding to attestations

For more information, see the Veriscope implementation guide.

Transfer workflow(s)

Veriscope supports advanced workflows including the exchange of encrypted IVMS data between VASPs and accept/reject. VASPs have the option to soft reject and request further information or else hard reject and decline to send or receive the transfer.

veriscope data share
Sequence diagram text file

To generate or update the diagram above, paste the following into

title Veriscope workflow

sender->oVASP:Submit withdrawal request
oVASP->oVASP:Post attestation
bVASP->oVASP:Respond to attestation with proof and signature data
oVASP->bVASP:Send signature data and encrypted IVMS
bVASP->oVASP:Send encrypted IVMS
oVASP->oVASP:Decrypt IVMS and risk check
oVASP->bVASP:Accept/Reject transfer
bVASP->bVASP:Decrypt IVMS and risk check
bVASP->oVASP:Accept/Reject transfer
oVASP->on-chain:Process the withdrawal
oVASP-->bVASP:Update transfer with on-chain transaction hash

For more information, see the Veriscope documentation on end-to-end flow.