The goal of the Travel Rule Information Sharing Architecture (TRISA) is to enable compliance with the FATF and FinCEN Travel Rules for cryptocurrency transaction identity information without modifying core blockchain protocols, and without incurring increased transaction costs or modifying virtual currency peer-to-peer transaction flows. The TRISA protocol and specification is defined by the TRISA Working Group; to learn more about the specification, please read the current version of the TRISA whitepaper.
This site contains the developer documentation for the TRISA protocol and reference implementation which can be found at github.com/trisacrypto/trisa. The TRISA protocol is defined as a gRPC API to facilitate language-agnostic, high-performance, peer-to-peer services between Virtual Asset Service Providers (VASPs) that must implement Travel Rule compliance solutions. Both the API and message interchange format are defined via protocol buffers, which can be found in the
protos directory of the repository. In addition, a reference implementation in the Go programming language has been made available in the
pkg directory of the repository. In the future, other implementations will be made available as library code for specific languages, found in the
lib directory of the repository.
Please visit the API Documentation for more information about the TRISA package.
Note: Translations of this documentation are done periodically by human translators, and may become out-of-sync with the English text or reflect errors. If you notice an error, please open a bug report to notify us.