Skip to main content
The core protocol on Vana L1 is data portability: the ability to transact with data (consent, permissions, discovery). Below are the contract addresses for that protocol, plus staking and chain utilities. A major application built on top is DataDAOs — they use the DLP primitive and data-access contracts (QueryEngine, ComputeEngine, TeePool, etc.); we list those on a separate page: Contract addresses.

​
Block explorers

​
Contract addresses

Addresses are the same on Moksha and Mainnet. Each row links to the contract on the explorer. Data portability — Protocol reference describes these.
ContractAddressExplorer
DataPortabilityPermissions0xD54523048AdD05b4d734aFaE7C68324Ebb7373eFMoksha | Mainnet
DataPortabilityServers0x1483B1F634DBA75AeaE60da7f01A679aabd5ee2cMoksha | Mainnet
DataPortabilityGrantees0x8325C0A0948483EdA023A1A2Fd895e62C5131234Moksha | Mainnet
DataRegistry0x8C8788f98385F6ba1adD4234e551ABba0f82Cb7CMoksha | Mainnet
FeeRegistry0xb4FA18443E0FA6cdC0280D20b8cCDB2377D13Bf2Moksha | Mainnet
FeeRegistry holds the protocol’s data-portability fees. Do not hard-code fee amounts — read them onchain from FeeRegistry, since they are tunable and differ by environment (see Payments & fees). The DataPortabilityEscrow contract holds each app’s fee balance; its address is surfaced per app identity and network in Vana Account — see the Build a Vana App guide for funding escrow. Staking
ContractAddressExplorer
VanaPoolStaking0x641C18E2F286c86f96CE95C8ec1EB9fC0415Ca0eMoksha | Mainnet
VanaPoolEntity0x44f20490A82e1f1F1cC25Dd3BA8647034eDdce30Moksha | Mainnet
VanaPoolTreasury0x143BE72CF2541604A7691933CAccd6D9cC17c003Moksha | Mainnet
Chain
ContractAddressExplorer
Multicall30xD8d2dFca27E8797fd779F8547166A2d3B29d360EMoksha | Mainnet
Multisend0x8807e8BCDFbaA8c2761760f3FBA37F6f7F2C5b2dMoksha | Mainnet
For validator and node setup, see Validators.