Ospree

• Name: Ospree
• URL: https://www.ospree.io/
• Category: Travel Rule compliance workflow middleware / VASP interoperability layer / self-hosted-wallet verification infrastructure
• Summary: Ospree is Travel Rule workflow middleware, not a payment rail. The product surface is mostly pre-transfer policy machinery: protocol routing, self-hosted-wallet checks, threshold evaluation, analytics gating, and operator review in front of a blockchain transfer that happens somewhere else. Useful note, but still a fairly small control-plane vendor rather than a settlement primitive.
• What it does:
  • Provides a modular compliance stack for digital-asset firms and financial institutions covering Travel Rule workflows, blockchain-analytics integrations, and transfer-review logic
  • Abstracts multiple Travel Rule transports behind one API and console, with public docs specifically naming TRP and TRISA
  • Supports self-hosted-wallet workflows including ownership verification, wallet labeling, identity linkage, and reuse of previously recognized wallets
  • Exposes a rule engine for jurisdiction-specific threshold checks and other transfer-policy decisions
• Key claims:
  • The homepage describes Ospree as a modular digital-asset compliance platform for VASPs and financial institutions handling Travel Rule and AML/CTF requirements through automation and interoperability
  • The Travel Rule materials say implementation covers jurisdictional scope, data residency, self-hosted-wallet policy, sunrise handling, thresholds, ownership verification, analytics, authentication, and webhook notifications
  • The dashboard and API docs describe incoming and outgoing transfer review flows that combine Travel Rule data validation, wallet-type identification, threshold logic, and blockchain-analytics checks
  • The protocols docs say Ospree provides a protocol-agnostic layer over multiple Travel Rule transports, specifically abstracting TRP and TRISA through one integration surface
  • The address-ownership docs show a signed-wallet verification flow for self-hosted addresses on Bitcoin, Solana, and EVM-compatible chains
• Whitepaper: No canonical standalone Ospree whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official website and docs portal, especially the Travel Rule, protocols, rule-engine, and address-verification documentation; see ../whitepapers/ospree-primary-sources-2026-05-02.md.
• Sources:
  • https://www.ospree.io/
  • https://www.ospree.io/travel-rule
  • https://docs.ospree.io/dashboard/travel-rule
  • https://docs.ospree.io/ospree-api/travel-rule/overview
  • https://docs.ospree.io/ospree-api/travel-rule/protocols
  • https://docs.ospree.io/ospree-api/rule-engine
  • https://docs.ospree.io/ospree-api/blockchain-analytics/verify-address-ownership
  • https://docs.ospree.io/dashboard/travel-rule/self-hosted-wallets

Internal linkages

• Keep this note pointed upward: notabene, sumsub, and trisa.

Control surface

• Ospree’s own chain footprint is incidental. The actual product is policy middleware: transport abstraction, self-hosted-wallet verification, analytics gating, and operator review before a customer sends funds on some other network.

• The practical risk sits in vendor-managed defaults around routing, thresholds, wallet labels, and approval logic, not in a proprietary settlement mechanism.

• Last reviewed: 2026-06-02 UTC