vlayer

• Name: vlayer
• URL: https://www.vlayer.xyz/
• Category: verifiable data infrastructure / zk-and-MPC verification middleware / web-proof and onchain-proof platform
• Summary: vlayer is best cataloged as verifiable-data middleware that bridges web, email, historical onchain, and cross-chain data into application and smart-contract workflows. Its strongest current primary sources are not a single whitepaper but a layered docs surface: the homepage and docs frame vlayer around TLSNotary-based web proofs plus ZK and MPC, while the book explains a Prover/Verifier execution model for Solidity developers and the docs split the stack into server-side proving, client-side proving, and blockchain-oriented ZK proof compression. The result looks less like a narrow identity app and more like a general-purpose cryptographic verification substrate with both Web2 and Web3 integration paths.
• What it does:
  • Generates cryptographic web proofs from HTTPS requests and responses using TLSNotary-based proving infrastructure
  • Offers three main developer surfaces: server-side proving for token-authenticated APIs, client-side proving for cookie/session-authenticated resources, and ZK proving for blockchain use cases
  • Compresses web proofs into succinct zero-knowledge proofs using RISC Zero so verified data can be stored or checked onchain more efficiently
  • Exposes a Solidity-oriented Prover/Verifier architecture in which private inputs are handled offchain and public outputs plus proof verification land on EVM-compatible chains
  • Supports use cases such as account and asset verification, wallet recovery, identity and compliance checks, reputation proofs, social/account ownership proofs, historical-balance checks, and cross-chain proof-based logic
• Key claims:
  • The official docs say vlayer is powered by TLSNotary plus Zero Knowledge Proofs and Multi-Party Computation to verify private data without exposing sensitive information
  • The docs explicitly position server-side and client-side proving as general web-proof infrastructure for any application environment, while ZK proving is the blockchain-specific compression layer for onchain verification
  • The vlayer book says Prover contracts execute on vlayer zkEVM infrastructure while Verifier contracts validate proofs and execute on EVM-compatible chains, which is the clearest architectural clue for categorization
  • The Prover docs say inputs are private by default, proofs are not persisted by vlayer, and developers are responsible for tracking proof usage in their Verifier contracts
  • The public GitHub organization description also links a Veridise audit report, suggesting the team is exposing audit artifacts alongside product docs rather than relying on marketing copy alone
• Whitepaper: No canonical standalone vlayer whitepaper or litepaper was surfaced in this pass. The strongest primary sources were the official site, docs.vlayer.xyz, the vlayer book, and the public GitHub organization; see ../whitepapers/vlayer-primary-sources-2026-04-27.md.
• Sources:
  • https://www.vlayer.xyz/
  • https://docs.vlayer.xyz/
  • https://docs.vlayer.xyz/server-side/introduction
  • https://docs.vlayer.xyz/client-side/introduction
  • https://docs.vlayer.xyz/blockchain/introduction
  • https://book.vlayer.xyz/
  • https://book.vlayer.xyz/getting-started/how-it-works.html
  • https://book.vlayer.xyz/advanced/prover.html
  • https://book.vlayer.xyz/advanced/verifier.html
  • https://github.com/vlayer-xyz
• Last reviewed: 2026-04-27 UTC