Phala Cloud Documentation — Private AI on TEE

This document is a work in progress. Test results will be populated as they become available.

Test Coverage

Tests are being conducted across the following scenarios. Results will be added as each test completes.

Category	Status	Notes
GCP CVM deployment	In progress
GCP KMS deployment + bootstrap	In progress
Nitro Enclave deployment	In progress
RA-TLS connection (GCP KMS → GCP workload)	In progress
RA-TLS connection (GCP KMS → Nitro workload)	In progress
getKey() key retrieval	In progress
On-chain measurement registration	In progress
On-chain measurement revocation	In progress
Governance flow (propose → approve → timelock → execute)	In progress
KMS bootstrap (Onboard → Finish)	In progress
Multi-node key replication	Planned

Component

Version

dstack-cloud

0.6.0-test

dstack OS

dstack-cloud-0.6.0

GCP zone

us-central1-a

AWS region

us-east-1

Blockchain

Base Sepolia (testnet)

Known Limitations

Limitation	Impact	Mitigation
KMS root key is single-point	If the KMS TEE is compromised, all keys are at risk	MPC distribution planned for future version
Nitro Enclaves are stateless	Workloads lose state on restart	Use GCP for persistent workloads; KMS runs on GCP only
Public RPC reliability	Testnet RPCs may return stale state	Use multiple RPC providers

Risk	Acceptance Criteria
TEE hardware side-channels	Accept residual risk. Monitor Intel/AWS advisories.
Smart contract vulnerabilities	Mitigate with audits. Re-audit after each contract change.

Risk

Acceptance Criteria

TEE hardware side-channels

Accept residual risk. Monitor Intel/AWS advisories.

Smart contract vulnerabilities

Mitigate with audits. Re-audit after each contract change.

E2E Test Report