VerifyVASP is a recently created Singapore-based decentralized Travel Rule messaging protocol created by South Korean cryptocurrency exchange Upbit. This article covers factors to consider when choosing VerifyVASP as a Travel Rule messaging protocol.
VerifyVASPs’ architecture is based upon a decentralized protocol that facilitates information sharing between VASPs, immediately and securely, via API communication while utilizing a robust encryption algorithm to secure data in transmission. The protocol mitigates risk associated with the sharing and transmitting of personal data while supporting the transfer of various types of digital assets on its decentralized architecture.
VerifyVASP is a closed network Travel Rule messaging protocol.
VerifyVASP is a decentralized protocol for secure and immediate data sharing amongst VASPs. Companies will still need to partner with a fully integrated Travel Rule solution provider or build additional components to integrate VerifyVASP.
With a simple API integration, VerifyVASP has a low and manageable integration effort.
VerifyVASP adopts the InterVASP Messaging Standard (IVMS101) data format, which helps pave the way for future interoperability with other solution providers.
VerifyVASP’s governance model is centralized, comprising only Upbit.
VerifyVASP is live.
VerifyVASP does not support transactions between non-custodial wallets.
VerifyVASP is a new protocol in its early days, yet there seems to be interest from Korean VASPs to support it.
Companies may become alliance members at no cost.
Notabene is looking to add support for VerifyVASP in Q4 2021.
For many companies, it is not enough to just integrate VerifyVASP, as they will likely have counterparties outside of the group of VerifyVASP supporters.
There has not been a testnet using VerifyVASP. However, VerifyVASP does have a sandbox for VASPs to test the protocol.
Notabene will be able to assist VASPs with each implementation step.
VerifyVASP Alliance Members are invited to connect to the Value Transfer Protocol Solution via API connectivity. Each Alliance Member is required to integrate with VerifyVASP’s servers by downloading a Docker image and using it to host their enclave server in their own environment.
The API key allows interaction between the enclave server hosted by the individual Alliance Member and VerifyVASP’s Central API Server. Each Alliance Member must implement the User Validation API to access VerifyVASP’s enclave server hosted in their environment.