Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vana.org/llms.txt

Use this file to discover all available pages before exploring further.

Vana L1 is an EVM-compatible blockchain purpose-built for data portability. It serves as the source of truth for protocol state: registrations, grants, file records, and schemas are recorded onchain and can be independently verified. Nobody — not even Vana core contributors — can modify data permissions; only the data owner can create or revoke grants. That gives the owner of the data full control and a cryptographic guarantee: consent is enforced by the chain, not by any central party. Private data is never written to the chain; the blockchain state is what gates access to data — it defines who can access what.

​
What’s onchain

CategoryWhat’s recorded
Personal ServersServer registration and URL (via DataPortabilityServers). Users can run desktop-bundled, ODL Cloud, or self-hosted; the server identity is onchain.
BuildersApp registration: address, public key, app URL (via DataPortabilityGrantees).
GrantsPermissions linking a user and a builder to specific scopes (via DataPortabilityPermissions). Create, revoke, and verify consent onchain.
File recordsDataRegistry entries: fileId, URL to encrypted blob, schemaId, permissions. Points to data in storage backends; the data itself stays off-chain.
SchemasSchema registry (DataRefinerRegistry): schemaId → schema definition (e.g. IPFS CID/URL) for resolving scope and validating structure.
This gives you verifiability: anyone can check that a grant exists, that a builder is registered, or that a file record was registered, without trusting a single API. The Data Portability RPC (Gateway) provides fast reads and writes with eventual chain consistency so builders get low-latency access while the chain remains the authority.

​
What’s not onchain

  • User data — Actual data files are encrypted and stored in the user’s chosen backend (hosted storage, Google Drive, Dropbox, IPFS). Only pointers and metadata are onchain.
  • Decrypted content — Nothing that could reveal user data is written to the chain.

​
Networks

NetworkPurposeRPC URLChain IDExplorer
MainnetProduction — data portability protocol and Data Applicationshttps://rpc.vana.org(see explorer)vanascan.io
Moksha TestnetDevelopment and testinghttps://rpc.moksha.vana.org14800moksha.vanascan.io
Get testnet VANA from the Vana Faucet.

​
Add Moksha to your wallet

In MetaMask, Rabby, or another EVM wallet, add a network with:
FieldValue
Network nameVana Moksha
RPC URLhttps://rpc.moksha.vana.org
Chain ID14800
Currency symbolVANA

​
Availability and resilience

Vana L1 is a proof-of-stake chain designed for high availability with active validators securing the network. See Validators for consensus details. The Data Portability RPC (Gateway) provides a caching and relay layer between protocol participants and the chain:
  • Reads (grant verification, registration lookup, file records) use cached state with low-latency responses.
  • Writes (grant creation, registration) are submitted by the Gateway and confirmed on-chain asynchronously.
The Gateway maintains eventual consistency with the chain — reads reflect the latest confirmed state with minimal delay. If the chain experiences temporary congestion, the Gateway continues serving cached reads. New writes queue and confirm when the chain catches up. This architecture means builders experience consistent, low-latency API responses regardless of chain conditions. The chain remains the authoritative source of truth; the Gateway ensures that protocol operations are not blocked by transient network issues.
Smart Contracts & Addresses — contract addresses and chain operations. Validators — consensus and validator info.