> ## 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.

# VRC-20 data token standard

> The standard for dataset-bound, programmable data ownership tokens on Vana.

# VRC-20 data token standard

**VRC-20** is the standard for **data tokens** on Vana: tokens that represent ownership or attribution in a specific dataset or data liquidity pool (DLP). A **DLP can specify any currency** for access and rewards; when a pool uses VRC-20 tokens (as many DataDAOs do), builders typically burn VANA and the pool’s VRC-20 tokens to access the underlying data, and contributors earn VRC-20 for validated contributions.

## What makes VRC-20 different

Unlike generic ERC-20 tokens, VRC-20 tokens are **cryptographically tied to data** through [Proof of Contribution](/data-applications/proof-of-contribution) and DLP mechanics. When users contribute validated data to a Data Liquidity Pool, they receive VRC-20 tokens representing their stake. The tokens are:

* **Attribution-preserving** — Each token traces back to specific contributions and wallet addresses.
* **ERC-20 compatible** — Same interfaces as ERC-20, so they work with wallets, DEXs, and DeFi tooling.
* **Burned for access** — AI builders (and other consumers) must burn both VANA and the pool’s VRC-20 tokens to access the dataset, so value flows back to contributors.
* **Earned by contribution** — Issued only when data is validated by the pool’s Proof-of-Contribution logic.

That makes VRC-20 the standard for **programmable, liquid data ownership** on Vana: you can hold, transfer, or burn tokens; the link to the dataset and to contributions is enforced by the protocol and contracts.

**DeFi composability.** Because VRC-20 tokens are ERC-20 compatible, they can be used composably with decentralized finance applications—trading, lending, derivatives, and other programmable financial primitives—while remaining tied to data rights and contribution attestations on Vana.

## Specification and contracts

* **Specification:** The normative VRC-20 spec lives in the [Vana VRCs repository](https://github.com/vana-com/VRCs). Refer to it for full compliance and extension rules.
* **Reference implementation:** The ecosystem uses **DAT** (Data Access Token) contracts: ERC-20–compatible, upgradeable templates with optional extensions (voting, pausing, blocklisting). Deployments use **DATFactory**, which deploys DAT, DATVotes, and DATPausable as needed.

For **DAT template and factory** addresses (mainnet and Moksha testnet), see [Contract addresses](/data-applications/contract-addresses#dlp-template-contracts-dat). Other contract addresses and ABIs are in [Smart Contracts & Addresses](/network/smart-contracts-addresses). For deployment commands and parameters, use the official Vana deployment docs or block explorer ([vanascan.io](https://vanascan.io), [moksha.vanascan.io](https://moksha.vanascan.io)).