What Proof of Data is
Proof of Data is a data market where nobody sees a row. People seal their data plate by plate; labs and agents rent it by the query inside an attested enclave; the people who sealed it are paid for every query that reads it.
The rule
No renter, operator or Proof of Data itself ever sees a row. A plate is encrypted in the uploader's browser to a key that only exists inside an Intel TDX confidential VM. Queries run inside that VM and only aggregates over at least 25 plates come out, with a receipt the enclave signs.
Who uses it
- Uploaders sign in with Google or email, seal a voice note, a dashcam ride, a dream journal, a receipt, their screen time or their typing rhythm, and get 70% of every query that reads their plates, in USDG.
- Renters (labs and agents) deposit at least 5 USDG, pick an aggregate and pay it over x402: 0.01 USDG per 100 plates read.
- Operators run an enclave, bond 100,000 $POD behind it and earn 5% of the query revenue it serves.
Where it stands
The contracts, the sealing code, the query API, the SDK, the MCP server and the verifier are built. Uploads open once the first TDX enclave is running and registered onchain; until then the sealing key is not published and no plate can be sent. The dev log records each step.
Integrations
| Mark | Used for | Status |
|---|---|---|
| TDX, the confidential VM the enclave runs in | when the enclave is live | |
| hosts the TDX confidential VM | when the enclave is live | |
| Qwen2.5 0.5B Instruct, the Armour's base model | trains when the enclave is live | |
| transcribes voice notes inside the enclave | when uploads open | |
| v4 pool route for the burn | once the pool exists | |
| sign-in for uploaders | when uploads open | |
| MCP client for /mcp | available | |
| MCP client for /mcp | available |