# Vana Build user-approved data flows with scoped permissions, Personal Servers and a programmable data-portability protocol. - Findings24: - 网站: - 价格: Freemium - 分类: 开发者工具 ## 什么是 Vana？ Vana is an open peer-to-peer network and software protocol for user-controlled data portability. People collect data through web or desktop connectors and approve which scopes an application may use. Developers request that access through Vana's API and SDK, then read approved data from the user's Personal Server. The Personal Server can run in a browser or the desktop app and synchronize encrypted data to cloud storage. An application presents a valid grant before receiving the permitted records. Core collection, storage, permissions and fee escrow are live; Protocol-Governed Encryption is still in progress, and pooled confidential compute remains on the roadmap. ## Vana 能做什么？ ### Scoped user consent An application requests specific data scopes. The user reviews the request and signs a wallet-based grant with an optional expiry; the Personal Server checks authorization before serving data. ### Personal Server data access Collect account data into a user-controlled environment and provide permitted records to connected applications. Cloud synchronization stores ciphertext; authorized recipients receive the data they requested. ### Developer integration Use the SDK with backend routes for access requests, approval-status checks and approved reads, plus an approval button in a React frontend. The same integration can be developed on testnet and deployed to mainnet. ### Revocation and usage settlement Revoke a grant to block future reads. Where the Personal Server charges fees, the application's escrow funds each configured access charge and settled reads are recorded onchain. ## 使用场景 ### Give an application selected context Authorize relevant account-data scopes instead of handing an app unrestricted access to the whole account. ### Build a data-aware service Add the request-approve-read flow to your existing application so it can receive user-approved context through a repeatable API. ### Review and change access Use grant scope, expiry and revocation controls to manage future access while accounting for data already delivered to recipients. ## 常见问题 ### How does a user approve access? The application creates an access request and opens Vana's approval surface. The user reviews the app, source and scopes, then signs the grant with a wallet. The application checks approval status and reads only the granted data from the Personal Server. ### What happens after I revoke a grant? Future reads fail when the Personal Server checks the revoked grant; the Context Gateway also stops serving it. Revocation does not erase copies a builder already received. Those copies are outside the grant and Vana's access log. ### Is all permission information private? No. The grantor, grantee, scopes and expiry of a grant are public onchain; the data records themselves are not. Current revocations are recorded through the DP RPC rather than written to the permissions contract, so contract status alone does not establish whether access was revoked. ### How are data-access fees paid? Charging is configured per Personal Server. A charging server requires each access fee to be paid from the application's escrow. Mainnet uses USDC.e; Moksha testnet uses native VANA. The optional hosted Context Gateway has separate USD billing. Noncharging-server reads are not recorded onchain. ### Which parts are available now? Collection, encrypted storage, core permissions, API access, Personal Servers and fee escrow are live. Protocol-Governed Encryption is in progress; provenance commitments, user-controlled compute and pooled confidential compute remain planned. ## 快速信息 - **Product type**: Open data-portability network and software protocol - **Primary users**: People controlling account data and developers integrating it - **Workflow**: Collect data, request scopes, approve a grant, read permitted records - **Control boundary**: Revocation blocks future access; recipient copies remain outside its control - **Network**: Vana mainnet and Moksha development testnet