21 Travel Rule: Version 3.1 Released

What is new in Version 3.1:

● Unified API for easier integration with your current workflows

● Various Travel Rule details are now linkified (transaction ID, address, asset name, physical address, etc.) for further inspection

● Overhauled settings screen for easier navigation

● PostgreSQL as the new default database

● Native login & signup screen

● Increasing security by replacing OpenSSL with Rustls [1][2]

● Other various improvements

Today we release version 3.1 of our core product, 21 Travel Rule. In this release, we made some major changes in the architecture of our software, which provides virtual asset service providers (VASPs) with more flexibility, stability and security when complying with the Financial Action Task Force (FATF) Travel Rule.

Leveraging PostgreSQL, 21 Travel Rule provides battle-tested access management and data security functionality, following the BitMEX Travel Rule Data Storage Principles published by 100x Chief Compliance Officer Malcolm Wright.

Our new software architecture simplifies the integration of our solution with VASPs current workflows, using our new unified API. At the same time, it also makes it more robust and encapsulates different services (such as OpenVASP, TRP and AOPP) even more. This enables you to transact crypto assets and Travel Rule data in the most secure, reliable and stable way. 

Most visible to the end-user are our various UI improvements. By linking to several external sources, compliance officers can now easily collect and review more information about a specific transaction, address, and customer-specific data.

If you would like to learn more about our Travel Rule solution and the technology behind it, reach out to us!

[1] https://security.googleblog.com/2021/02/mitigating-memory-safety-issues-in-open.html

[2] https://daniel.haxx.se/blog/2021/02/09/curl-supports-rustls/