# Vana Protocol Documentation > Vana is an open protocol for user-controlled data portability. Users store personal data in Personal Servers, grant third-party builders access via signed, scope-native permissions, pay protocol fees from an onchain escrow, and revoke access at any time. All consent is recorded onchain on Vana L1. The canonical documentation URL is https://docs.vana.org ## Build - [Build a Vana App](https://docs.vana.org/build-a-vana-app): The step-by-step builder guide to the Data Portability direct data flow — request user-approved data, read it from the user's Personal Server, and pay protocol fees from your app's escrow balance. Uses the @opendatalabs/vana-sdk (createDirectDataController, useDirectVanaConnect). Covers app identity, sources and scopes, funding escrow and checking fees (FeeRegistry), the example app, testing, and troubleshooting. ## Protocol Reference - [Data portability protocol](https://docs.vana.org/data-portability-protocol): Conceptual overview — programmable data ownership, Personal Servers, tokenized data rights, and how data flows through the protocol. - [Protocol — DP RPC](https://docs.vana.org/protocol-reference/dp-rpc): The protocol's read/write boundary (https://dp-rpc.vana.org) — the onchain primitives (identity, permissions, fees, PGE, schemas, files, DLP contracts), EIP-712 verification, and the L1 settlement path. - [Identity](https://docs.vana.org/protocol-reference/identity): Wallet-based identity for users, builders, and Personal Servers; app-identity/builder registration (DataPortabilityGrantees); app manifests; Personal Server registration (DataPortabilityServers); the Passport authentication abstraction. - [Personal Servers](https://docs.vana.org/protocol-reference/personal-servers): The user's access engine that stores data and serves authorized requests. Covers the REST API surface, Web3Signed authorization, grant verification and fee gating, forms (Desktop Full, Web Lite, and future user-controlled compute), reachability/tunneling, data sync, and local data hierarchy. - [Scopes & Schemas](https://docs.vana.org/protocol-reference/scopes-schemas): Scope taxonomy ({source}.{category}), the schema registry (DataRefinerRegistry), JSON data file format, data connectors, and how to define new scopes. - [Storage & Encryption](https://docs.vana.org/protocol-reference/storage-encryption): Key derivation (HKDF-SHA256 from wallet signature), OpenPGP password-based encryption, storage backends (Vana Storage, Google Drive, Dropbox, IPFS), the data sync model, and data deletion. - [Grants & Permissions](https://docs.vana.org/protocol-reference/grants-permissions): Scope-native EIP-712 grants (v2: grantor, granteeId, scopes, expiry), grant lifecycle (create, active, revoked, expired), verification and fee gating, the Connect flow (createAccessRequest → approve → poll → read), operation-scoped grants (design direction), and the onchain PermissionSet event. - [Payments & Fees](https://docs.vana.org/protocol-reference/payments-fees): The per-account escrow that funds and settles protocol fees (deposit/settle/withdraw, onchain events), fee model (registration and access fees), FeeRegistry, and the token vs USD rails. - [Encryption & PGE](https://docs.vana.org/protocol-reference/encryption-pge): Protocol-Governed Encryption — threshold key release on data access, with no single party holding the key (in active development). - [Provenance & Verifiability](https://docs.vana.org/protocol-reference/provenance): A protocol-level commitment that anchors a data point's provenance onchain (dataCommitment, metadataHash), with pluggable off-chain proofs (attestation today, zkTLS later). Coming soon. - [Full Specification](https://docs.vana.org/protocol-reference/full-specification): The complete normative Data Portability Protocol specification — protocol components, data formats, grants (v2), fees and escrow, operations, security model, error codes, and the Vana SDK. ## Applications - [Confidential compute](https://docs.vana.org/applications/confidential-compute): Privacy-preserving jobs over pooled data (the DataDAO model) inside a TEE network — an application on top of the protocol, not a requirement. - [Collection & apps](https://docs.vana.org/applications/collection-and-apps): How data enters the protocol — sources, connectors, collection paths — and the Vana apps that bundle a Personal Server. - [Agents](https://docs.vana.org/applications/agents): AI agents consume user data under the same grants, fees, and audit trail as any builder, over the Personal Server's MCP interface. - [Context Gateway](https://docs.vana.org/applications/context-gateway): ODL's optional, replaceable commercial layer on top of the protocol (OAuth/OIDC, USD billing) — distinct from the protocol's RPC gateway. ## Network - [Vana L1](https://docs.vana.org/network/vana-l1): EVM-compatible blockchain for data portability. Covers what is onchain (registrations, grants, file records, schemas), mainnet and Moksha testnet RPC URLs and chain IDs, and the Data Portability RPC. - [Validators](https://docs.vana.org/network/validators): L1 blockchain validators (Proof-of-Stake consensus, block production, hardware requirements) and Satya data validators (Trusted Execution Environments, Proof of Contribution, Intel TDX). - [Core Contracts](https://docs.vana.org/network/smart-contracts-addresses): Contract addresses for DataPortabilityPermissions, DataPortabilityServers, DataPortabilityGrantees, DataRegistry, FeeRegistry, staking contracts, and chain utilities. Addresses are the same on Moksha and Mainnet. - [VANA Token](https://docs.vana.org/network/vana-token): Token overview, utility (network security, transaction fees, staking, governance, data access currency), total supply (120M), distribution schedule, and ERC-20 contract addresses on Ethereum, Base, Arbitrum, BNB, Optimism, and Polygon. - [Staking & Bridging](https://docs.vana.org/network/staking-bridging): How to stake VANA at stake.vana.org, non-rebasing staking positions, rewards, and how to bridge assets (VANA, USDC.e, USDT, ETH/WETH) via Stargate and Jumper using LayerZero OFT standard. ## Resources - [Ecosystem](https://docs.vana.org/resources/ecosystem): Projects and applications built on Vana, including ecosystem partners (Stargate, Hyperlane, Quicknode, Chainstack, Gelato, The Graph, Goldsky, Safe, and others). - [Community & Discord](https://docs.vana.org/resources/community-discord): Join the Vana community on Discord and connect with other builders. - [Whitepaper](https://docs.vana.org/resources/whitepaper): The Vana whitepaper: "An Open Protocol for Data Sovereignty." - [Security & Audits](https://docs.vana.org/resources/security): Defense-in-depth security model (chain-level, server-level, encryption-level), audit reports from Nethermind and Hashlock, smart contract governance, and responsible disclosure policy. ## Deprecated URLs The following URLs are no longer valid. Do not link to them: - https://docs.vana.org/docs/how-vana-works — REMOVED. See https://docs.vana.org/ and https://docs.vana.org/protocol-reference/personal-servers instead. - https://docs.vana.org/docs/system-architecture — REMOVED. See https://docs.vana.org/protocol-reference/full-specification instead. - https://docs.vana.com/api — REMOVED. Old domain. There is no separate API reference; the protocol API is documented inline in the Protocol Reference pages. - The @opendatalabs/connect SDK is DEPRECATED — use @opendatalabs/vana-sdk (see the Build a Vana App guide). - Any URL under https://docs.vana.org/docs/* — REMOVED. The /docs/ prefix is no longer used. - Any URL under https://docs.vana.com/* — REMOVED. The docs.vana.com domain is deprecated; use docs.vana.org.