Summary: TRISA (Travel Rule Information Sharing Architecture) is an open, peer-to-peer compliance protocol for virtual asset service providers that need to exchange originator and beneficiary information under FATF-, FinCEN-, and similar Travel Rule regimes without modifying core blockchain protocols. Its primary materials jointly expose a PKI-based trust model, certificate-authority and global-directory components, a gRPC/protobuf protocol, a translation layer for interoperability, and an open-source Envoy node for real deployments. It is best cataloged as compliance messaging and identity infrastructure for crypto institutions rather than as a consulting alliance or policy-only working group.
What it does:
Defines an out-of-band protocol for VASPs to exchange required transaction identity data while leaving blockchain transaction flows unchanged
Uses a certificate-authority and public-key-infrastructure model to verify VASP identities and establish secure peer-to-peer communication channels
Maintains a global VASP directory and related directory-service implementation so counterparties can discover and authenticate one another
Specifies the protocol as a gRPC API with protocol buffers and publishes an open-source reference implementation in Go
Ships Envoy as an open-source self-hosted node to accelerate adoption of the TRISA and TRP protocols
Frames translation/interoperability as a first-class feature because multiple Travel Rule messaging approaches coexist across jurisdictions and vendors
Key claims:
The TRISA homepage positions the project as decentralized cryptocurrency Travel Rule compliance and describes it as open, peer-to-peer, secure, privacy-preserving, and available now
The official whitepaper says TRISA’s goal is to enable compliance with FATF and FinCEN Travel Rules without modifying core blockchain protocols, increasing transaction costs, or changing peer-to-peer transaction flows
The whitepaper and homepage both emphasize a certificate-authority model, global VASP directory, and PKI-based authentication as core trust infrastructure
The developer docs define TRISA as a gRPC API using protocol buffers, with the reference implementation and message definitions published in the public GitHub repo
The public GitHub organization shows the project spans more than a single specification, including repositories for the core protocol, Envoy node, global directory service, testnet, certificate delivery tooling, and related libraries
TRISA’s materials explicitly foreground interoperability and translation because global Travel Rule compliance requires message exchange across heterogeneous regulatory and vendor environments
Whitepaper: An official TRISA whitepaper exists as a web document, and the clearest current source surface is the combination of that whitepaper, the TRISA homepage, developer docs, and public GitHub repositories; see ../whitepapers/trisa-primary-sources-2026-04-27.md.
Keep this note on the strongest adjacent reads: travel-rule-protocol for the API-first routing cousin, notabene for the commercial operator stack above the transport problem, and sumsub for the broader compliance-control-plane version.