System Architecture
Morpheus uses a four-layer production design. The confidential boundary is narrow: only decryption, private fetch, private compute, NeoDID private flows, and attested result creation enter the TEE.
The Four Layers
1. On-Chain Interface
Neo N3 contracts own request submission, fee accounting, callback routing, and verifier-checked fulfillment.
2. Serverless Control Plane
Cloudflare Workers, Queues, and Workflows own ingress, validation, throttling, queueing, orchestration, and recovery.
3. Durable State
Supabase stores request records, relayer jobs, control-plane jobs, automation state, feed snapshots, and logs.
4. Confidential Execution
Role-split Oracle and DataFeed CVMs handle confidential execution only. Oracle serves request/response work; DataFeed serves publication only.
Runtime Roles
- Oracle CVM: request/response oracle, compute, NeoDID, confidential signing, and attested result generation.
- DataFeed CVM: isolated feed publication lane with higher operational priority.
- Shared topology: mainnet and testnet use the same Oracle and DataFeed CVMs and differ by path prefix and config.
Trust And Recovery Model
- Clients seal secrets before submission.
- Control plane and relayer never decrypt sealed payloads.
- Accepted jobs are persisted to Supabase-backed durable state.
- Queues and Workflows recover stale jobs instead of assuming single-pass success.
- Pricefeeds stay isolated so interactive bursts do not stall market updates.
Support Stance
Neo N3 is the active supported production path. Neo X artifacts remain in-repo only as archived reference material and should not be treated as the default integration path.