One connection, many fees.

A person connects their data once. Every time an approved app reads it, the app pays the network.

All network transactions

79.82Mtransactions

Running total or transactions per complete UTC day.

How reads generate fees

An app registers, an owner grants it access to data, and each read through that grant settles a fee.

Each step multiplies the one before it. One person can run several personal servers, one app can hold many grants, and every grant can be read against again and again.

Registered applications

212

Permission grants

702,296

Issued once, per application, per data source.

Personal servers

758,317

Scope reads

5,282,012

Settled, all time.

Where the fees go

Fees settle in USDC. Of each fee, 60% goes to stakers, 20% buys and burns VANA, and 20% funds ecosystem growth.

Fee allocation

60 / 20 / 20percent

Current allocation, as set out in VANA — The Asset Behind an Open Data Economy.

  • Stakers 60%
  • Buyback 20%
  • Treasury 20%

The 60% staker share includes operator commission. At 5% commission, 57% goes to delegators and 3% to operators.

How value flows through the network

Builders register applications, people grant them access to data, and applications pay the network each time they read it.

Registered applications

212apps

Apps get a registration ID when they join Vana mainnet.

Permission grants

702,296grants

An owner grants one app access to one data source.

The protocol is metered by reads

5,282,012reads

Each read against a grant settles a fee in USDC. Fee income adds up the amounts recorded for those settled reads.

How data compounds across applications

Data connected for one application can be granted to another. An application arriving later reaches connections that already exist, and a person arriving at a new application brings the permissions they already hold — so neither side starts from nothing.

Users with 3+ sources

1,090

Re-access rate

79%

Cross-app

13%

Reads per grant

7.52reads per grant

Cumulative settled reads divided by distinct permission grants issued.

Protocol and token economics

Understand the network and its token economics.

Staked VANA secures the network

VANA is credited to validators on the consensus layer — slashable, and redeemable on exit.

Delegated stake

814.85KVANA active

Daily active delegated VANA recorded at each capture.

Share of current supply
0.71%
Current supply
114,494,664 VANA

Rewards distributed

83,783.619VANA

VANA distributed to stakers, all time.

Staking pools

3

Plus the original pool, open for migration until 31 October.

Bonding period

5days

Time before newly staked VANA becomes reward-eligible.

Important information

This page is provided by the Vana Foundation for information only. Nothing on it is an offer to sell, a solicitation to buy, or a recommendation about VANA or any other digital asset, and nothing on it is investment, financial, tax or legal advice.

VANA is the token the Vana network runs on. It does not represent equity, ownership, or any claim on the Vana Foundation, OpenDataLabs or any other entity.

Network figures are drawn from onchain data and third-party sources. They may be delayed, incomplete or revised, and are provided without warranty of any kind. The burn simulator is illustrative only. Its outputs depend entirely on the inputs chosen and are not a forecast of network activity, token supply or price.

Fee allocations, staking parameters and other protocol settings shown are current as described in VANA — The Asset Behind an Open Data Economy, and may change. Staking involves risk, including the loss of some or all VANA staked by an operator, and staked tokens are subject to a bonding period.

Digital assets are volatile, and access to them may be restricted in some jurisdictions. You are responsible for complying with the laws that apply to you.