How It Works

Start by connecting your wallet — no signup, no email, just sign a message to prove ownership. ZDrive derives a unique encryption key from your wallet signature; this key never leaves your browser and is never stored anywhere, even by ZDrive. You're now authenticated for the session.

Type a prompt or upload a file. Your browser immediately encrypts everything with AES-256-GCM using your derived key. The encrypted blob and metadata (which model, which tier) go to the ZDrive worker. The worker never sees plaintext — only ciphertext plus metadata. It verifies your wallet signature, checks your credit balance, routes your request to an available inference provider, and streams back the encrypted response. Your browser decrypts the response locally. You see the result; the network saw only encrypted noise.

If you want to store your encrypted data permanently, the worker signs the ciphertext as an ANS-104 DataItem and uploads it to Arweave via Irys node2. The network confirms the upload and returns an Arweave transaction ID. That ciphertext is now immutable and globally retrievable — but only you can decrypt it because only you have the encryption key.

For inference, ZDrive routes your request through a fallback chain of TEE-backed providers. If the primary model is overloaded or unavailable, the worker silently retries the next option in the chain. You get a response header (X-Zdrive-Model-Used) telling you which model processed your query. Credits are consumed after successful inference, not before.

End-to-end flow