vlayer-primary-sources-2026-04-27

vlayer primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

• Official site: https://www.vlayer.xyz/
• Docs root: https://docs.vlayer.xyz/
• vlayer book: https://book.vlayer.xyz/
• GitHub org: https://github.com/vlayer-xyz

What the official materials say

1) Homepage / current framing

• URL: https://www.vlayer.xyz/
• Key takeaways:
  • The homepage frames vlayer as “the verifiable data infrastructure” and explicitly separates the protocol layer from the business/application layer built on top of it.
  • It says developers can extract, verify, and integrate real-world data into Ethereum smart contracts using ZKPs and MPC.
  • The most important categorization clue is that the homepage spans multiple data domains — web, email, historical onchain state, and cross-chain activity — instead of a single verification niche.

2) Docs root / proof-stack overview

• URL: https://docs.vlayer.xyz/
• Key takeaways:
  • The docs say vlayer is powered by TLSNotary and uses ZKPs plus MPC to verify private data without exposing sensitive information.
  • They define web proofs as cryptographically signed attestations of TLS transcripts.
  • The docs split the product into three developer APIs: server-side proving, client-side proving, and blockchain-oriented ZK proving.
  • The docs also distinguish their operating niches clearly: token-authenticated API proving, cookie/session-based client-side proving via Vouch, and compressed onchain verification via RISC Zero.

3) Server-side proving

• URL: https://docs.vlayer.xyz/server-side/introduction
• Key takeaways:
  • Server-side proving is presented as a REST API for generating and verifying web proofs using TLSNotary.
  • The two core endpoints are /prove for notarizing a request and returning a web proof, and /verify for validating a web proof and returning the parsed HTTP transcript.
  • The examples emphasize proving API responses and service interactions without exposing credentials or raw data.
  • The docs explicitly warn that this API is still under development, which is worth preserving in the catalog.

4) Client-side proving / Vouch path

• URL: https://docs.vlayer.xyz/client-side/introduction
• Key takeaways:
  • Client-side proving is routed through Vouch, a user-facing proving service built on top of vlayer.
  • The docs say this path is appropriate when the proof must be generated from a user’s browser or mobile device using cookies or other session-bound credentials.
  • This is a strong clue that the protocol and the end-user verification product should be treated as related but distinct library entries.

5) ZK proving / blockchain path

• URL: https://docs.vlayer.xyz/blockchain/introduction
• Key takeaways:
  • ZK Prover Server is presented as a REST API that compresses web proofs into ZK proofs.
  • The docs say the service uses RISC Zero and returns a ZK proof plus ABI-encoded public outputs for blockchain integration.
  • Example use cases include proving exchange balances, trading activity, RWAs, government-ID attributes, GitHub contributions, and domain ownership onchain.
  • This supports categorizing vlayer as general proof middleware rather than as a single identity or KYC product.

6) vlayer book / execution model

• URLs:
  • https://book.vlayer.xyz/getting-started/how-it-works.html
  • https://book.vlayer.xyz/advanced/prover.html
  • https://book.vlayer.xyz/advanced/verifier.html
• Key takeaways:
  • The vlayer book gives the clearest low-level model: Prover contracts execute offchain on vlayer zkEVM infrastructure, while Verifier contracts validate proofs and execute on EVM-compatible chains.
  • Inputs to Prover functions are private by default, while returned values become public inputs used for verification.
  • The docs also say proofs are not persisted by vlayer and must be tracked by the developer’s Verifier logic.
  • This makes vlayer look like application-facing proof middleware and execution infrastructure, not just a verification SDK.

7) GitHub organization / ecosystem and audit signal

• URL: https://github.com/vlayer-xyz
• Key takeaways:
  • The GitHub org description reiterates the split between web proofs, client-side proving, and ZK proving.
  • It also points to practical example repos and to Vouch as a separate proving application.
  • The org links a public Veridise audit report, which is a useful signal that the team is publishing security artifacts alongside the product surface.

Whitepaper / technical-doc status

• No canonical standalone vlayer whitepaper or litepaper was found in this pass.
• The strongest source of truth is distributed across the official site, docs.vlayer.xyz, the vlayer book, and the GitHub org.
• In practice, the docs are more useful than a missing whitepaper because they expose the actual proof modes, execution model, and product boundaries.

Research notes

• Best current category for the library: verifiable data infrastructure / zk-and-MPC verification middleware / web-proof and onchain-proof platform.
• Key categorization insight: vlayer should be treated as the protocol and middleware layer, not collapsed into the Vouch application built on top of it.
• Another useful note for future scouting: the explicit separation between server-side proving, client-side proving, and blockchain proving makes vlayer a good reference pattern for projects that span both Web2 data verification and onchain settlement or enforcement.