CodeVASP

• Name: CodeVASP
• URL: https://www.codevasp.com/
• Category: Travel Rule alliance network / member-routing workflow / unhosted-wallet verification sidecar
• Summary: CodeVASP is an alliance-run Travel Rule workflow stack. The useful surface is member admission, routing, and wallet-verification policy sitting in front of an ordinary transfer. Keep it as a secondary workflow note, not a neutral transport anchor.
• What it does:
  • Provides a Travel Rule protocol for VASP-to-VASP compliance messaging and routing
  • Offers developer documentation for Travel Rule integration, unhosted-wallet verification, and Uppsala wallet-screening integration
  • Exposes dashboard and client-status tooling for transaction tracking, due diligence, and trend monitoring
  • Supports wallet-address and TXID-based VASP discovery to improve routing and counterparty identification
  • Operates an alliance model with protocol interconnects and partner services spanning analytics, AML training, and regulatory support
• Key claims:
  • The homepage says CodeVASP was formed by Bithumb, Coinone, and Korbit to provide standardized Travel Rule compliance technology for VASPs under FATF-style regulatory pressure
  • The FAQ says CodeVASP supports both pre-transaction approval and post-transaction data-request flows, which is the clearest sign this is a workflow product rather than a single narrow transport primitive
  • The FAQ says CodeVASP does not store users’ personal data and that VASP-to-VASP communication is protected with end-to-end encryption
  • The developer docs show the real bundle: Travel Rule integration, unhosted-wallet verification, and Uppsala wallet-screening hooks rather than a clean isolated messaging layer
  • The services and alliances pages make the operator model plain: dashboarding, due diligence, wallet/TXID search, VASP risk assessment, training, and partner interconnects all sit inside the alliance wrapper
• Whitepaper: No canonical CodeVASP whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official homepage, developer documentation, services page, and alliances page; see ../whitepapers/codevasp-primary-sources-2026-05-01.md.
• Sources:
  • https://www.codevasp.com/
  • https://docs.codevasp.com/en/docs
  • https://www.codevasp.com/page-services
  • https://www.codevasp.com/page-alliances

Internal linkages

• Keep this note tight.
• Transport-and-directory baseline: trisa.
• Stronger workflow-control anchor: notabene.

Control surface

• The leverage sits in alliance admission, counterparty discovery, unhosted-wallet verification policy, routing defaults, and the dashboard-and-due-diligence wrapper around the protocol.

• Read CodeVASP as alliance middleware. The transfer itself is downstream; the real power is in who gets recognized, how counterparties are classified, and which checks block release.

• This is a lower-tier note and should spend its graph budget upward toward the transport and workflow anchors rather than validating peer vendor stacks sideways.

• Last reviewed: 2026-06-16 UTC