Skip to main content
Vana is an open, decentralized protocol for data sovereignty: users keep control of their personal data and grant applications access with verifiable, revocable consent. The Vana network is the EVM-compatible layer-1 that runs this protocol—registrations, grants, file records, and permissions are recorded onchain so that nobody but the data owner can change who has access. The $VANA token is the native token of that network. It pays for transaction fees (including every data portability action—grants, file records, builder and Personal Server registration), secures the chain through validator staking, and is used in governance. It also serves as the default means of payment and the main trading pair for data applications built on the protocol, such as DataDAOs and other DLPs. Tokenomics are designed to align incentives across validators, stakers, application builders, and the community, with a fixed supply and allocations focused on long-term sustainability and decentralized participation.

Token overview

CategoryValue
Ticker$VANA
Total supply120,000,000 $VANA
% to Community66.9%
Float25.1%
Token standardVana L1: native $VANA; wrapped version as ERC-20 on Ethereum

Token utility

$VANA is the native token of the Vana network, powering its ecosystem and supporting secure, decentralized data transactions. It plays a central role in the network’s multi-token ecosystem through the following use cases:

Network security

Validators stake $VANA to secure the blockchain, ensuring reliable transaction validation and operational stability. Validators receive staking rewards for their role in maintaining the network’s integrity.

Transaction fees

A fee is charged on all data transactions on the network, including data portability transactions (creating or revoking grants, registering file records, updating Personal Server or builder registration) as well as smart contract executions and interactions with any data application, including DataDAOs. $VANA is used to pay these fees, establishing it as the medium of exchange for activities across the protocol and the broader ecosystem.

Data validators staking

Users stake $VANA in Data Validators and earn emissions for supporting the network in adding more valuable data capital to the ecosystem.

Default data access currency

DLPs can specify any currency for access; DataDAOs in the Vana ecosystem typically use $VANA by default. Access tokens can be swapped as desired by the buyer, seller, or agent. They unlock datasets for use in applications by researchers, developers, and businesses.

Trading pair

$VANA serves as the primary trading pair for all tokens issued by DataDAOs, facilitating exchange and interoperability across the ecosystem.

Governance

$VANA holders participate in the decentralized governance of the Vana network, voting on proposals and influencing key decisions. Governance of the treasury will expand to network stakeholders and contributors through the Vana DAO, ensuring a fair and inclusive approach to managing the ecosystem—expanding the scope of decision-making so participants can shape the network’s direction and manage key parameters, such as reward structures and emissions.

Data token ecosystem

The Vana network supports a dynamic ecosystem where DataDAOs can issue their own tokens tied to specific datasets or rights. $VANA serves as the foundational token that interconnects these activities, fostering collaboration and enabling a robust data economy.

Token role in data portability

The VANA token secures the network and pays for chain operations. Data portability operations — registration, grants, file records — are submitted through the Gateway, which handles chain interaction and gas on behalf of protocol participants. The token powers the infrastructure layer (validators, staking, governance) while data portability flows (consent, data access, revocation) operate through signed HTTP requests relayed by the Gateway. Builders and users interact with the protocol through standard HTTP APIs; the Gateway submits the corresponding chain transactions.
Data portability protocol operations use signature relay through the Gateway. The token secures the underlying chain; the Gateway abstracts chain interaction from the data portability flow. Builders do not need to hold, manage, or transact in VANA to integrate with the data portability protocol.

Supply and distribution

The total supply of VANA is capped at 120 million tokens, distributed as follows: VANA token allocation
CategoryAllocation% supply at TGELock-up (months)Unlock (months)Fully unlocked (months)
Core Contributors18.8%0.00%134860
Community44.0%20.3%03636
Investors14.2%0.00%133648
Ecosystem22.9%4.8%04848
Community and Ecosystem unlocks are non-linear. A full detailed unlock schedule is available on Vana’s CoinMarketCap page.

Community

The Community allocation focuses on fostering participation and rewarding contributors. This includes rewards for high-quality data contributions to DataDAOs, airdrops to early adopters, and support to developers building on Vana. Future incentives will ensure sustained engagement and community alignment with Vana’s vision.

Ecosystem

The Ecosystem allocation supports sustainability of the protocol through grants and rewards that drive long-term growth. Grants are allocated to activities including DataDAO bootstrapping, support for new DataDAO tokens, network partnerships, and block rewards to incentivize network decentralization, innovation, and adoption.

Investors

Early supporters with a 4-year vest (1-year cliff plus 3-year unlock).

Core contributors

The team that has built Vana from concept to reality and continues to support protocol development. All tokens in the Core Contributors allocation are subject to a 5-year vest (1-year cliff and 4-year unlock).

VANA token address

VANA is the native token of Vana mainnet, so there is no token contract address on the Vana L1.
NetworkContract address
Vana mainnetNative gas token (no contract)

VANA across chains

VANA is also available as an ERC-20 token on other chains, following the OFT (Omnichain Fungible Token) standard. Same contract address on each chain:
NetworkContract addressExplorer
Ethereum0x7ff7fa94b8b66ef313f7970d4eebd2cb3103a2c0Etherscan
Base0x7ff7fa94b8b66ef313f7970d4eebd2cb3103a2c0Basescan
Arbitrum0x7ff7fa94b8b66ef313f7970d4eebd2cb3103a2c0Arbiscan
BNB Smart Chain0x7ff7fa94b8b66ef313f7970d4eebd2cb3103a2c0BscScan
Optimism0x7ff7fa94b8b66ef313f7970d4eebd2cb3103a2c0Optimistic Etherscan
Polygon0x7ff7fa94b8b66ef313f7970d4eebd2cb3103a2c0PolygonScan
Other tokens named $VANA may exist and are not associated with Vana. Always verify the contract address before interacting.

Relevant tokens on Vana mainnet

TokenContract address
USDC.e0xF1815bd50389c46847f0Bda824eC8da914045D14
Vana OFT0x7FF7Fa94b8b66Ef313f7970d4EEbd2CB3103a2C0
Wrapped ETH0x2F6F07CDcf3588944Bf4C42aC74ff24bF56e7590
Wrapped Vana0x00EDdD9621Fb08436d0331c149D1690909a5906d
USDT0x88853D410299BCBfE5fCC9Eef93c03115E908279