Vana primary sources — 2026-05-11

Project status in this pass

• Official whitepaper materials surfaced clearly in this pass, including Vana’s whitepaper post and the linked PDF.
• The strongest mechanism detail came from the official whitepaper post plus Vana’s developer docs for Proof of Contribution and DLP deployment.
• The materials consistently frame Vana as a protocol for user-controlled data coordination and AI-data market formation, not merely as a storage product or generic AI chain.

Primary-source snapshots

1) Vana whitepaper post

• URL: https://www.vana.org/posts/vana-whitepaper
• Key excerpt/signals:
  • Vana describes itself as an open protocol for AI data sovereignty.
  • The post says users export data from platforms, hold it in personal servers, and join DataDAOs that negotiate with AI developers.
  • It defines Data Liquidity Pools as the coordination mechanism that turns non-fungible personal data into fungible data tokens.
  • It says AI buyers use VANA to purchase and burn DLP tokens, linking access demand to both network and dataset economics.
  • It says the top 16 DataDAOs receive emissions based on stake and governed performance metrics.
• Why it mattered:
  • This is the clearest source for Vana’s intended market structure and for the protocol’s real control surfaces: DLP tokenization, access pricing, staking competition, and emissions ranking.

2) Official whitepaper PDF

• URL: https://cdn.prod.website-files.com/662488d48afbf9b21e25c7d2/674e84d37254e5d1074b6c18_Vana_Whitepaper_Dec24.pdf
• Local copy:
  • ../whitepapers/vana-whitepaper.pdf
• Key excerpt/signals:
  • The PDF surfaced from Vana’s official whitepaper page and appears to be the formal technical/economic reference document for the protocol.
  • The PDF metadata identifies it as an internal editable copy of the Vana whitepaper.
• Why it mattered:
  • Even without a clean text extraction pass here, the official PDF is important to preserve because Vana presents it as the canonical deeper specification behind the public whitepaper post.

3) Proof of Contribution docs

• URL: https://docs.vana.org/data-applications/proof-of-contribution
• Key excerpt/signals:
  • Proof of Contribution verifies that data is real, unique, attributable, and reward-worthy.
  • Validation runs in a Trusted Execution Environment so raw data is not exposed during verification.
  • Each DLP can define its own scoring logic, including quality, uniqueness, ownership, authenticity, and model-influence-style weighting.
  • Attestations are recorded offchain-plus-onchain, and scores/metadata can drive token issuance.
• Why it mattered:
  • This page makes Vana’s real governance surface much clearer: whoever controls PoC rules controls what counts as valuable data, who gets rewarded, and what kinds of datasets become legible.

4) DLP quickstart docs

• URL: https://docs.vana.org/data-applications/dlp-quickstart
• Key excerpt/signals:
  • Vana provides a concrete deployment path for launching a Data Liquidity Pool, token contract, validation logic, refiner/schema layer, and contributor UI.
  • The quickstart treats DLPs as practical deployable components rather than only conceptual DAOs.
  • The manual path makes explicit that builders configure token contracts, DLP contracts, Proof-of-Contribution logic, refiners, and query-ready data flows.
• Why it mattered:
  • This confirms Vana is an operational builder stack with explicit module boundaries, which strengthens the case for cataloging it as reusable infrastructure.

Working conclusion

Vana is best understood as AI-data coordination infrastructure built around a split between private data custody and public market/governance rights. The decisive signals in this pass were the DLP-based tokenization model, custom Proof-of-Contribution scoring, TEE-based validation through the Satya network, and the stake-weighted emissions race that ranks DataDAOs and shapes which datasets gain power inside the network.