Veriscope primary sources — 2026-05-01

Project status in this pass

  • No canonical standalone Veriscope whitepaper or litepaper surfaced.
  • The clearest current source of truth was the official Veriscope product page plus the first-party docs corpus under docs.veriscope.network.
  • The docs also link an official Shyft Network whitepaper, but the docs are more useful for recovering the actual Veriscope operating model.

Primary-source snapshots

1) Official Veriscope page

  • URL: https://www.veriscope.network/
  • Key excerpts/signals:
    • Says Veriscope provides “Entity level VASP Discovery & Sunrise Issue Resolution” that works with all Travel Rule protocols.
    • Frames the product as quick to install and easy to use.
  • Why it mattered:
    • This is the clearest top-level signal that Veriscope wants to be understood as a protocol-spanning VASP discovery layer, not only as a single-protocol relay.

2) Docs index / overview

  • URL: https://docs.veriscope.network/docs/latest/index.html
  • Key excerpts/signals:
    • Says Shyft Veriscope is a decentralized, enterprise-grade solution for VASPs to meet FATF Travel Rule requirements.
    • Splits the system into Shyft Discover and Veriscope Share.
    • Says Discover solves destination-wallet attribution / Know Your VASP and Share solves secure transfer of user data between VASPs before an onchain transaction occurs.
    • Says no intermediary storage or servers are involved and that VASPs host the entire solution.
  • Why it mattered:
    • This page is the cleanest first-party statement of the product decomposition and self-hosted trust model.

3) Discovery layer docs

  • URL: https://docs.veriscope.network/docs/latest/learn/discover.html
  • Key excerpts/signals:
    • Says Shyft Discover is a universal, protocol-agnostic infrastructure for determining who controls a hosted wallet address without changing the end-user experience.
    • Says originator VASPs post attestations to the blockchain-based Shyft Network and beneficiary-side VASPs listen for addresses they control.
    • Says VASP information includes entity details, regulatory status, protocol endpoints, and Travel Rule thresholds.
    • Says the system is network- and token-agnostic and can work with all Travel Rule data-transmission protocols.
    • Explicitly contrasts the approach with user-facing identifier schemes such as LNURLs, PayStrings, and VASP codes.
  • Why it mattered:
    • This is the strongest evidence that Veriscope is solving entity-level discovery and routing as infrastructure, not only payload exchange.

4) Attestations docs

  • URL: https://docs.veriscope.network/docs/latest/learn/attestations.html
  • Key excerpts/signals:
    • Says attestations are core to how the Shyft Network provides assurances around KYC data and sharing methodologies.
    • Says confidential data stays private while only a pseudonymous attestation is published.
    • Says metadata is encrypted with a user-controlled key and that this makes social-engineering and data-mining attacks harder.
  • Why it mattered:
    • This clarifies that the onchain layer is being used for discovery and assurance signals rather than raw KYC disclosure.

5) Proof of Address Control docs

  • URL: https://docs.veriscope.network/docs/latest/learn/addressproofs.html
  • Key excerpts/signals:
    • Shows an address-type registry covering Bitcoin, Ethereum, Monero, Zcash, Litecoin, Dogecoin, Solana, BNB, Ripple, Cardano, Tron, Polygon, Polkadot, Avalanche, Cosmos, Near, Stellar, Liquid, and RSK variants.
  • Why it mattered:
    • The registry is a strong primary-source clue that address-verification coverage is intentionally broad and multi-chain.

6) Architecture docs

  • URL: https://docs.veriscope.network/docs/latest/learn/architecture.html
  • Key excerpts/signals:
    • Says the package includes a Nethermind node, Nginx, NodeJS, Laravel/PHP, Redis, Horizon, and the Veriscope web application.
  • Why it mattered:
    • This is the clearest first-party evidence that Veriscope is delivered as a substantial self-hosted operational stack rather than as a thin API wrapper.

Working conclusion

Veriscope is best cataloged as protocol-agnostic Travel Rule discovery-and-sharing infrastructure for VASPs. The strongest signals in this pass were the explicit split between Discover and Share, the use of attestations plus proofs of address control for pre-transfer counterparty identification, and the repeated emphasis that sensitive data remains off-chain while VASPs host the operating stack themselves.