EXTENDED DOCUMENTATION
Deployment
Environment Templates
- for bilingual variable explanations and operator guidance
Frontend
Deploy
to Vercel.Required env vars:
- or
- for the TwelveData built-in provider
- optional Coinbase spot provider requires no secret
- optional but recommended in production: or
- optional and recommended for scoped admin separation:
- optional datafeed defaults: ,
Phala Worker
Deploy
to Phala with:- or
- or
- or if direct worker calls should resolve project provider defaults
- (or compatible service key) for worker-side provider-config lookup
- optional for upstream fetch timeout (for example )
- optional for privacy Oracle script execution timeout
- optional for compute script execution timeout
- optional to derive worker and relayer signing keys from tappd/dstack when explicit keys are omitted
- optional to attach dstack quotes in worker responses
- optional to override the dstack endpoint (defaults to when mounted)
- optional / to override worker derived key paths
- optional / to override relayer derived key paths
- optional to control the wrapping-key path for stable Oracle X25519 transport key storage
- optional to control where the sealed Oracle transport key is persisted (default inside the shared CVM volume)
- web verifier API:
- demo verifier flow: and
Phala CVM Topology
Recommended first deployment:
- 1
- 2 containers inside it: +
Sizing guidance:
- → not recommended
- → recommended for testnet / MVP
- → recommended default for production
Deployment files:
Morpheus Relayer
Run
as the async bridge that watches events and calls back on-chain.Required env vars:
- or
- or
Optional:
Supabase
Apply, in order:
Optional:
Supabase Recording Model
Current persistence behavior:
- relayer runs and jobs are recorded in and
- web/API operations are recorded in
- encrypted request fields such as , , , and are stored directly as ciphertext in
- plaintext secret-like keys are redacted before operation-log persistence
- automation registrations are stored in
- automation queue attempts are stored in
Contracts
Build and deploy the Morpheus gateway contracts from
. Use and as the canonical address registry files.Core contracts:
- Neo N3: , ,
- Neo X: , ,
The intended logic is consistent across both chains:
- privacy oracle requests
- off-chain privacy compute through oracle/compute worker modules
- datafeed storage and updater-controlled publication
- automation registration, execution queueing, and callback fulfillment
Provider control-plane notes:
- built-in provider metadata lives in the worker provider registry
- project-level provider defaults live in Supabase
- the web dashboard can manage provider configs through
Optional On-Chain Key Publication
After the Phala worker is live, publish the active Oracle encryption key to your gateway contract:
REVISION 1.0.2LAST UPDATED: 2026-03-11