Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usewraith.xyz/llms.txt

Use this file to discover all available pages before exploring further.

Wraith runs inside Trusted Execution Environment (TEE) hardware. Agent private keys are derived deterministically inside Intel TDX enclaves and never stored on disk or exported without authorization.

​
What Is a TEE?

A TEE is a hardware-isolated compute environment. Code and data inside the enclave are protected from the host operating system, hypervisor, and even the hardware operator. Intel TDX (Trust Domain Extensions) provides:
  • Memory encryption — data in enclave memory is encrypted at the hardware level
  • Code integrity — the enclave can prove it’s running specific, unmodified code
  • Remote attestation — clients can verify the enclave’s identity and integrity remotely
Wraith uses Phala Network for TEE deployment, which provides the DStack SDK for deterministic key derivation.

​
Key Derivation

Agent keys are derived deterministically from the TEE’s hardware root secret. They are never stored — re-derived on demand for every operation.

​
Derivation Path

Key Derivation The path includes the chain identifier to prevent key collision. The same agent gets different keys on different chains.

​
Implementation

class TeeService {
  async deriveAgentPrivateKey(agentId: string, chain: string): Promise<Uint8Array> {
    // DStack derives key from hardware root secret + path
    const raw = await dstack.getKey(`wraith/agent/${agentId}/${chain}`);
    return sha256(raw);
  }

  async deriveAgentKeypair(agentId: string, chain: string) {
    const connector = this.chainRegistry.get(chain);
    const seed = await this.deriveAgentPrivateKey(agentId, chain);
    return connector.deriveKeys(seed);
  }
}

​
Per-Chain Key Derivation

The chain connector determines how the raw seed becomes usable keys:
ChainCurveFlow
EVMsecp256k1seed → SHA-256 → privateKeyToAccount → sign message → deriveStealthKeys → st:eth:0x...
Stellared25519seed → SHA-256 → ed25519 seed → sign message → deriveStealthKeys → st:xlm:...

​
Security Properties

​
Keys Are Never Stored

Every time an operation needs agent keys (sending a payment, scanning, withdrawing), the keys are re-derived from the TEE root secret. No private key material touches disk. 
// Every chat message re-derives keys
async chat(agentId: string, message: string) {
  const agent = await this.db.agents.findOneBy({ id: agentId });
  const stealthKeys = await this.tee.deriveAgentKeypair(agent.id, agent.chain);
  // Use keys for this operation, then they're garbage collected
}

​
Wallet Ownership Verification

Agent creation requires an EIP-191 signature (EVM) or ed25519 signature (Stellar) from the owner wallet. This proves the creator controls the wallet without revealing any private key. 
// Verification flow
const recoveredAddress = recoverMessageAddress({
  message: body.message,
  signature: body.signature,
});
if (recoveredAddress !== body.wallet) {
  throw new UnauthorizedException("Signature does not match wallet");
}

​
Key Export

Exporting an agent’s private key requires a fresh wallet signature: 
import { Wraith, Chain } from "@wraith-protocol/sdk";

const wraith = new Wraith({ apiKey: "wraith_..." });
const agent = await wraith.getAgentByName("alice");

// Requires fresh wallet signature
const sig = await wallet.signMessage("Export private key for agent " + agent.info.id);
const { secret } = await agent.exportKey(sig, "Export private key for agent " + agent.info.id);
The TEE verifies the signature matches the owner wallet before releasing the key. Without the wallet, nobody — including Wraith — can export the key.

​
Remote Attestation

Clients can verify the TEE is running authentic, unmodified code: 
// GET /tee/attest/{agentId}
const attestation = await fetch(`${baseUrl}/tee/attest/${agentId}`);
// Returns cryptographic proof of code integrity
This proves:
  • The code inside the TEE matches the published source
  • Keys were derived by the legitimate Wraith software
  • No unauthorized modifications have been made

​
Privacy Properties

​
Stealth Addresses

Every payment goes to a fresh one-time stealth address. On-chain observers see random addresses with no link to the sender or receiver. Stealth Address Privacy

​
View Tags

View tags enable efficient scanning. Each announcement includes a 1-byte tag derived from the shared secret. The recipient can reject ~255/256 non-matching announcements by checking just the tag — without computing the full stealth address.

​
AI Privacy Guardian

The agent proactively monitors for privacy risks:
  • Timing analysis — warns if transactions happen too close together
  • Amount patterns — flags identical payment amounts
  • Address correlation — warns about withdrawing to a known wallet
  • Consolidation risk — alerts when too many stealth addresses are unspent
await agent.chat("withdraw all to 0xMyMainWallet");
// "Privacy concern — withdrawing all stealth addresses to a single
//  known wallet links every payment to your identity..."

​
Deployment

​
Docker

docker buildx build --platform linux/amd64 \
  -t wraith-tee:latest \
  --push \
  -f packages/tee/Dockerfile .
The container must target linux/amd64 for TEE hardware compatibility.

​
Environment Variables

VariableDescription
DATABASE_URLPostgreSQL connection string
GEMINI_API_KEYDefault AI model key
DEPLOYER_KEYKey for deploying contracts / funding agents
CHAIN_IDTarget chain ID
RPC_URLChain RPC endpoint

​
Deploy to Phala

phala deploy --cvm-id <app_id> -c docker-compose.yml
The DStack socket (/var/run/dstack.sock) connects the container to the TEE hardware for key derivation.