Morpheus Documentation
Morpheus is a Neo N3 confidential oracle stack with serverless ingress, durable orchestration, isolated datafeeds, and role-split confidential execution.
Confidentiality
Sensitive payloads are sealed before submission and only unsealed inside the Oracle CVM.
Separation Of Concerns
Scheduling and recovery stay outside the TEE; confidential execution stays inside it.
Why This Design
Morpheus is built so the TEE does only the work that truly requires confidentiality. Authentication, request validation, backpressure, retry, recovery, and status inspection are all handled outside the confidential runtime.
Current production rule: Oracle request/response work runs on the Oracle CVM, feed publication runs on the dedicated DataFeed CVM, and Cloudflare Workflows own the callback and automation orchestration lanes.
Core Architecture
The current production design is a four-layer stack.
On-Chain Interface
Neo N3 contracts own request submission, callback routing, and on-chain verification boundaries.
Serverless Control Plane
Cloudflare Workers, Queues, and Workflows own ingress, validation, orchestration, and recovery.
Durable State
Supabase stores requests, relayer jobs, control-plane jobs, automation state, feed snapshots, and logs.
Confidential Execution
Role-split Oracle and DataFeed CVMs execute private workloads and publish attested results.
Next Steps
Integrate the Neo N3 request/callback path and seal payloads locally.
Review the current four-layer production design and runtime split.
Use the canonical Cloudflare + Vercel + Supabase + dual-CVM rollout model.
Inspect the canonical contracts, domains, CVM ids, and attestation explorers.
Understand priority isolation, recovery, backlog handling, and observability.
Run the canonical test, smoke, signer, and end-to-end verification sequence.
Compare configured feed pairs, live quotes, on-chain values, and deprecated keys.
Review the confidential NeoDID bind and ticket flows plus DID resolver surface.