Proof of Data
App
Open the app
Seal, rent, verify, waitlist.
Seal a plate
Encrypt a file in this browser to the enclave key.
402
Rent a query
Quote an aggregate and pay it over x402 in USDG.
Verify the enclave
Check a TDX quote against the onchain registry.
The Armour
The model its uploaders own. Trains when the enclave is live.
Join the waitlist
Uploads open in waves, in sign-up order.
Read
Protocol
Documentation
Dev log
X
Docs · Operate

Operators and $POD

$POD is the bond behind every enclave. An operator stakes it to hold plates, earns from the queries it serves, and loses it if its enclave leaks.

100,000 $PODbondedrequestExit7 days, still slashableEnclave canary48 h caseReturned50% burn50% users
An operator's bond and what can happen to it.

The bond

Registering an enclave pulls 100,000 $POD from the operator into Enclaves. Leaving takes 7 days after requestExit, and the bond stays slashable during that time. An enclave canary that stands its case slashes the whole bond: 50% burned, 50% to the uploaders.

What an operator earns

5% of the revenue of every query its enclave serves, paid by the Meter at settlement and taken from the Armour's 15%. On day one the only operator is Proof of Data's own enclave.

The burn

15% of query revenue accrues in USDG in the Meter's burn reserve. Anyone may call burnBuy(minOut) once an hour after the $POD pool is set: it spends up to 0.5% of the pool's depth, buys $POD, sends it to the dead address and pays the caller 1%. Proof of Data's own services never call it.

Running an enclave

  1. Deploy the Proof of Data image on a Phala Cloud TDX CVM.
  2. Read its attestation: the quote, the sealing key and the signer.
  3. Check the image hash is on the allowlist (the timelock adds images).
  4. Approve 100,000 $POD and call Enclaves.register.