Proof of Data
App
Open the app
Encrypt, query, verify, waitlist.
Encrypt your data
Encrypt a file in this browser to the TEE server's key.
402
Query the data
Price an AI query and pay it over x402 in USDG.
Verify the server
Check its Intel TDX proof against the onchain registry.
Private AI model
Trained on your data, pays you on every call. First training at 25 text uploads.
Join the waitlist
Uploads open in waves, in sign-up order.
Read
Protocol
Documentation
Dev log
X
Docs · How it works

The TEE server

Your data is opened and queried only inside an Intel TDX confidential machine on Phala Cloud. Its quote proves which code runs and which key your browser encrypts to.

Intel SGX Root CApinned in the verifierPCK certificatesigns the QE reportAttestation keysigns the quoteMRTD, RTMR0-2image hashreport_datasha256(key, signer)Registration stores the image hash, the quote hash, the signer and the encryption key onchain
What a TDX quote proves, and where each part is checked.

Why TDX

A TDX virtual machine runs with memory the host cannot read. Phala Cloud runs these VMs with dstack, which measures the image at boot. A small CVM (one vCPU, 2 GB) is enough for the query runner and for training the private AI model on CPU.

What the quote binds

  • The image: Proof of Data's image hash is keccak256(MRTD || RTMR0 || RTMR1 || RTMR2). The timelock keeps the list of allowed images.
  • The keys: the first 32 bytes of report_data are sha256(sealing key || signer address). The server makes both keys at boot and never exports them.
  • The chain: the operator registers the quote hash, the image hash, the signer and the encryption key in Enclaves, with its stake.

Checking it yourself

The verifier runs in your browser. It checks the quote's signature, the QE report, the PCK chain up to the pinned Intel SGX Root CA (SHA-256 44a0196b…74d3), the key binding, and the image and quote hashes against the registry. TCB status and revocation come from Intel's collateral and are checked by the operator's tooling at registration.

Status

The first TEE server is the next step. Its code is written and runs in a local simulation that builds a TDX quote byte for byte under a simulation root; the verifier refuses that quote against Intel's root, as it must.