Global Travel Rule

• Name: Global Travel Rule
• URL: https://www.globaltravelrule.com/
• Category: Travel Rule workflow stack / self-hosted-wallet verification middleware / IVMS101 interoperability wrapper
• Summary: Global Travel Rule (GTR) is vendor-run Travel Rule workflow middleware. The GitHub repos are real, but the actual product is counterparty coordination, wallet verification, and IVMS101 handling around ordinary transfers. Useful operator plumbing, not a transport baseline.
• What it does:
  • Offers a single-integration Travel Rule platform for connected VASPs and supported counterparties
  • Provides QR-code-based self-hosted-wallet verification with expiration handling, callbacks, and optional screening signals
  • Exchanges IVMS101-style originator, beneficiary, and VASP data across counterparties
  • Maintains open-source protocol, schema, encryption, and integration repositories that help integrations around the hosted product
  • Positions the same stack as usable across multiple chains and jurisdictions rather than tied to one asset network
• Key claims:
  • The homepage says GTR is a one-stop global Travel Rule solution built around single integration and partner-network interoperability
  • The wallet-verification materials say users of self-hosted wallets can prove wallet ownership through privacy-preserving cryptographic signature flows
  • The docs describe pre-transaction and post-transaction verification flows, expiration semantics, callback delivery, and optional advisory address-screening results
  • The supported-networks page presents broad multi-chain wallet-verification coverage across Bitcoin, EVM, Solana, and additional networks
  • The public GitHub organization exposes protocol, schema, encryption, PII-matching, and tooling repos, which is real implementation surface even if the product remains vendor-operated
  • The IVMS101 protocol repo frames its schemas for VASPs, other obliged entities, and Travel Rule solution providers rather than for open retail use
• Whitepaper: No canonical standalone Global Travel Rule whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official homepage, wallet-verification docs, supported-networks page, GitHub org, and IVMS101 protocol repo; see ../whitepapers/global-travel-rule-primary-sources-2026-05-01.md.
• Sources:
  • https://www.globaltravelrule.com/
  • https://www.globaltravelrule.com/documentation/gtr-solutions/wallet-verification
  • https://www.globaltravelrule.com/documentation/wallet-verify/overview-wallet-verify
  • https://www.globaltravelrule.com/documentation/gtr-wallet-verification-supported-networks
  • https://github.com/Global-Travel-Rule
  • https://github.com/Global-Travel-Rule/IVMS101-Protocols
  • https://github.com/Global-Travel-Rule/travel-rule-protocols

Internal linkages

• For the stronger workflow-control-plane read, go to notabene.
• For the sharper transport and directory baseline, go to trisa.

Control surface

• GTR matters because it decides which counterparties are recognized, how self-hosted wallets get verified, what payloads move between firms, and which checks block release before settlement.

• The open artifacts help implementation. The real leverage still sits with the vendor-run workflow, network access, and verification defaults.

• Last reviewed: 2026-06-15 UTC