Cowrie Research

veriscope

3 min read

Veriscope

  • Name: Veriscope
  • URL: https://www.veriscope.network/
  • Category: Travel Rule interoperability infrastructure / VASP discovery-and-address-attribution network / proof-of-address-control compliance middleware
  • Summary: Veriscope is VASP-discovery and proof-of-address-control plumbing. The useful question here is simple: who controls the destination address, and how do counterparties exchange Travel Rule data before broadcast? That makes it a useful interoperability layer, not a settlement rail and not the main workflow anchor.
  • What it does:
    • Lets originator VASPs post attestations representing withdrawal or transfer requests to the Shyft Network without putting personally identifiable information on-chain
    • Gives beneficiary-side VASPs a way to detect attestations for addresses they control and respond with proofs of address control before sensitive data is exchanged
    • Separates the stack into Shyft Discover for entity-level VASP discovery and Veriscope Share for secure peer-to-peer exchange of encrypted IVMS and accept/reject decisions
    • Maintains VASP entity details, regulatory status, supported Travel Rule protocol endpoints, and transfer thresholds in the discovery layer
    • Supports a self-hosted deployment model where VASPs run the software stack themselves, including blockchain sync, web services, queues, and dashboard tooling
    • Positions itself as network- and token-agnostic infrastructure that works across multiple Travel Rule data-transmission protocols and across assets such as BTC, ETH, SOL, USDT-on-multiple-chains, and similar hosted-wallet flows
  • Key claims:
    • The Veriscope page says it provides “Entity level VASP Discovery & Sunrise Issue Resolution” that works with all Travel Rule protocols
    • The docs say Shyft Veriscope is a decentralized, enterprise-grade solution for VASPs to meet FATF Travel Rule requirements for virtual assets
    • The docs say the product is composed of Shyft Discover and Veriscope Share, with Discover solving address attribution / Know Your VASP and Share solving secure user-data transfer between VASPs before an onchain transaction occurs
    • The docs say no personally identifiable information is posted to the Shyft Network and that VASPs host the entire solution with no intermediary storage or servers involved
    • The discovery docs say Veriscope is protocol-agnostic, network-agnostic, and token-agnostic, and can work with all Travel Rule data-transmission protocols while avoiding end-user burden around identifying the beneficiary VASP
    • The discovery docs say VASP information includes entity details, regulatory status, protocol endpoints, and Travel Rule thresholds, and that each licensed entity in a group can respond independently for jurisdictional risk management
    • The docs say proofs of address control are used to demonstrate that a responding VASP actually controls the hosted destination address, reducing the risk of sensitive data being sent to the wrong counterparty
    • The architecture docs say the software package includes a Nethermind node, Nginx, NodeJS services, a Laravel/PHP application, Redis queues, Horizon monitoring, and the Veriscope web application
  • Whitepaper: No canonical standalone Veriscope whitepaper or litepaper surfaced in this pass. An official Shyft Network whitepaper is linked from the Veriscope docs and already saved locally as ../whitepapers/shyft-network-whitepaper-v4.1.pdf, but the clearest current operational sources of truth for Veriscope itself were the official product page and docs; see ../whitepapers/veriscope-primary-sources-2026-05-01.md.
  • Sources:

Internal linkages

Control surface

  • Veriscope matters because it shapes VASP discovery, address attribution, proofs of control, and pre-transfer data exchange.

  • The blockchain attestation layer is secondary. The leverage is in who gets recognized as the right counterparty before sensitive data is sent.

  • Last reviewed: 2026-06-13 UTC

Graph View

Backlinks