TRISA

• Name: TRISA
• URL: https://travelrule.io/
• Category: Travel Rule transport protocol / VASP identity-and-directory infrastructure / secure inter-VASP messaging rail
• Summary: TRISA is the transport-and-directory baseline for Travel Rule messaging. The useful parts are plain: PKI-backed VASP identity, directory lookup, and peer-to-peer encrypted exchange. It is not the workflow stack, not the sanctions brain, and not a chain feature.
• What it does:
  • Defines an out-of-band protocol for VASPs to exchange required originator and beneficiary information without changing blockchain transaction mechanics
  • Uses a certificate-authority and PKI model so counterparties can authenticate one another before exchanging Travel Rule data
  • Maintains a global VASP directory and related directory-service software for participant discovery and identity lookup
  • Specifies the message layer as a gRPC API with protocol buffers and publishes an open-source Go reference implementation
  • Ships Envoy as an open-source node package so operators can run TRISA and TRP connectivity without building the transport stack from scratch
  • Treats translation and interoperability as first-class concerns because Travel Rule messaging is fragmented across regions 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 is meant to satisfy FATF and FinCEN-style Travel Rule requirements without modifying blockchain protocols, increasing transaction costs, or altering peer-to-peer value transfer itself
  • The homepage and whitepaper both make the trust model plain: certificate-authority issuance, PKI-authenticated counterparties, and a global VASP directory are core infrastructure, not side details
  • 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 stack is broader than one spec file: core protocol, Envoy node, global directory service, certificate tooling, testnet, and supporting libraries all sit in the same operator path
  • TRISA materials repeatedly foreground interoperability and translation, which is the clearest sign that this is a transport-and-identity rail for a fragmented compliance market rather than a single vendor workflow product
• Whitepaper: An official TRISA whitepaper exists as a web document. The strongest current source surface is the whitepaper plus the homepage, developer docs, and public GitHub repositories; see ../../whitepapers/trisa-primary-sources-2026-04-27.md.
• Sources:
  • https://travelrule.io/
  • https://travelrule.io/trisa-whitepaper/
  • https://trisa.dev/
  • https://github.com/trisacrypto
  • https://github.com/trisacrypto/trisa

Internal linkages

• API-first routing and beneficiary-discovery cousin: travel-rule-protocol.
• For the workflow-control layer above transport, keep one operator anchor in view: notabene.

Control surface

• TRISA matters because it decides who counts as a recognized counterparty, how identity is vouched for, how peers discover one another, and how Travel Rule payloads move between institutions.

• The practical leverage sits in certificate issuance, directory policy, transport implementation, and interoperability gateways.

• Treat it as the transport-and-directory rail beneath Travel Rule workflow vendors, not as the workflow vendor itself.

• Last reviewed: 2026-06-13 UTC