EXTENDED DOCUMENTATION

Async Privacy Request Spec

This spec still uses some legacy "oracle" naming because the active runtime routes and payload shapes have not been fully renamed yet. On Neo N3, the on-chain model is now a shared

text

miniapp-os + miniapps

kernel:

text
MorpheusOracle
is the kernel contract
built-in modules provide common fetch / compute / identity capabilities
text
OracleCallbackConsumer
is an optional external adapter, not the canonical callback surface
legacy
text
Request(...)
and
text
RequestFromCallback(...)
remain as compatibility shims

Canonical Network Registry

The canonical deployment registry lives in:

text
config/networks/mainnet.json
text
config/networks/testnet.json

Current Neo N3 anchors:

Item Mainnet Testnet

Oracle runtime API

text

https://oracle.meshmini.app/mainnet

text

https://oracle.meshmini.app/testnet

Oracle attestation explorer

text

https://cloud.phala.com/explorer/app_ddff154546fe22d15b65667156dd4b7c611e6093

text

https://cloud.phala.com/explorer/app_ddff154546fe22d15b65667156dd4b7c611e6093

Datafeed attestation explorer

text

https://cloud.phala.com/explorer/app_ac5b6886a2832df36e479294206611652400178f

text

https://cloud.phala.com/explorer/app_ac5b6886a2832df36e479294206611652400178f

text

MorpheusOracle

kernel

text

0x5b492098fc094c760402e01f7e0b631b939d2bea

via

text

oracle.morpheus.neo

text

0x4b882e94ed766807c4fd728768f972e13008ad52

text

OracleCallbackConsumer

opt.

text

0xe1226268f2fe08bea67fb29e1c8fda0d7c8e9844

text

0x8c506f224d82e67200f20d9d5361f767f0756e3b

text

MorpheusDataFeed

module

text

0x03013f49c42a14546c8bbe58f9d434c3517fccab

via

text

pricefeed.morpheus.neo

text

0x9bea75cf702f6afc09125aa6d22f082bfd2ee064

text

AbstractAccount

text

0x0268a387913b250166ddec032b03332690a1ef78

via

text

smartwallet.neo

text

aa.morpheus.neo

text

0xdbf38e7b2117186bf7a5e17ead702322c0c5b6f2

text

AA Web3AuthVerifier

text

0xf5c452cd4ba29dcdc47026383568c0d8b38d9272

text

0x7147f9a508594a7656a25f45d0a7a7dede7c227f

text

AA RecoveryVerifier

text

0x198b3a9cec9bccc2110d19bd929b10374a9d034d

text

recovery.smartwallet.neo

text

NeoDIDRegistry

text

0xb81f31ea81e279793b30411b82c2e82078b63105

via

text

neodid.morpheus.neo

unpublished in the shared registry

Interpretation rules:

testnet example/demo contracts may differ from the shared optional callback adapter; always trust
text
config/networks/*.json
instead of older examples
blank / unpublished registry fields mean there is no shared stable publication yet, not that a temporary internal deployment never existed
text
UnifiedSmartWalletV3
is the canonical AA product/runtime label even if a raw deployed manifest string carries a historical or deployment-specific suffix
text
smartwallet.neo
is the canonical AA mainnet domain, while
text
aa.morpheus.neo
is an additional alias to the same clean AA address
AA verifier plugin addresses are deployment-specific and should not be inferred from the core AA contract hash

Architecture note:

Cloudflare control-plane ingress, queues, and workflows stay outside the TEE.
Supabase remains the durable source of truth for accepted jobs and recovery.
The Oracle CVM handles built-in confidential module execution for both mainnet and testnet.
The DataFeed CVM remains isolated for continuous shared resource publication.
network selection is path-based and payload-based, not CVM-based
route naming is still partly oracle-shaped, but the on-chain contract boundary is now kernel-oriented

Canonical Request Path

Client reads the Oracle public key.
Client encrypts a secret locally.
Contract calls
text
Request(requestType, payload, callbackContract, callbackMethod)
on
text
MorpheusOracle
, or uses the newer kernel registration path when available.
A kernel request event is emitted on-chain.
The relayer validates and persists the event, then forwards it to the correct built-in module lane.
The runtime executes fetch-only, private fetch, public compute, or private compute.

The relayer calls

text

FulfillRequest(requestId, success, result, error, verificationSignature)

The kernel stores the canonical inbox item.
If a callback adapter contract was configured, it receives the forwarded result as an optional integration surface.

NeoDID identity flows now also fit this same path when the request type is one of:

text
neodid_bind
text
neodid_action_ticket
text
neodid_recovery_ticket

Oracle Payload

json
{
  "url": "https://api.example.com/private",
  "method": "GET",
  "headers": {},
  "body": "",
  "json_path": "data.value",
  "encrypted_token": "<base64 ciphertext>",
  "encrypted_payload": "<base64 ciphertext>",
  "encrypted_params": "<base64 ciphertext>",
  "encrypted_payload_ref": "<uuid secret ref>",
  "encrypted_params_ref": "<uuid secret ref>",
  "token_header": "Authorization",
  "script": "function process(data) { return data.age > 80; }",
  "script_base64": "ZnVuY3Rpb24gcHJvY2VzcyhkYXRhKSB7IHJldHVybiBkYXRhLmFnZSA+IDgwOyB9",
  "script_ref": {
    "contract_hash": "<production-script-registry-hash>",
    "method": "getScript",
    "script_name": "age_gate"
  },
  "target_chain": "neo_n3"
}

For

text

neodid_recovery_ticket

, a typical on-chain payload is:

json
{
  "provider": "github",
  "network": "neo_n3",
  "aa_contract": "0x0268a387913b250166ddec032b03332690a1ef78",
  "verifier_contract": "0x198b3a9cec9bccc2110d19bd929b10374a9d034d",
  "account_id": "<aa-account-id>",
  "new_owner": "0x89b05cac00804648c666b47ecb1c57bc185821b7",
  "recovery_nonce": "7",
  "expires_at": "1735689600",
  "encrypted_params": "<encrypt({\"provider_uid\":\"github_uid_777\",\"oauth_code\":\"...\"})>"
}

For large Web3Auth JWT payloads, use the short-reference form instead of embedding the full ciphertext directly in the Oracle payload:

json
{
  "vault_account": "0x6d0656f6dd91469db1c90cc1e574380613f43738",
  "provider": "web3auth",
  "claim_type": "Web3Auth_PrimaryIdentity",
  "claim_value": "linked_social_root_oracle_ref",
  "encrypted_params_ref": "<secret_ref>"
}

Rules

text
encrypted_token
is the canonical encrypted auth-secret field for private fetches
if
text
encrypted_payload
decrypts to a JSON object, the worker treats it as a confidential payload patch and merges it before execution
text
encrypted_params
/
text
encrypted_input
are dedicated aliases for encrypted JSON patches that can carry secret headers, provider params, compute input, function names, or scripts
text
encrypted_payload_ref
/
text
encrypted_params_ref
are short references to ciphertext previously stored in
text
morpheus_encrypted_secrets
when a ref field is present, the worker loads the ciphertext from Supabase first, then decrypts the same X25519 envelope inside the TEE
text
script
and
text
script_base64
are interchangeable aliases
text
script_ref
lets the worker fetch the script body from a Neo N3 contract getter so the on-chain request only carries a small reference
text
callback_contract
and
text
callback_method
are on-chain request arguments, not JSON payload fields
kernel-native miniapp integrations may eventually bypass explicit callback adapters and read from the system inbox directly
text
target_chain
is currently
text
neo_n3
in the active supported path
confidential payload transport uses
text
X25519-HKDF-SHA256-AES-256-GCM
text
neodid_recovery_ticket
binds the signed ticket to
text
aa_contract
,
text
account_id
,
text
new_owner
,
text
recovery_nonce
, and
text
expires_at

Built-in Compute API

Use

text

POST /compute/execute

with one of:

json
{
  "mode": "builtin",
  "function": "zkp.public_signal_hash",
  "input": { "signals": ["1", "2", "3"] },
  "target_chain": "neo_n3"
}

json
{
  "mode": "script",
  "script": "function run(input) { return input.a + input.b; }",
  "entry_point": "run",
  "input": { "a": 2, "b": 3 },
  "target_chain": "neo_n3"
}

Confidential compute can be submitted by encrypting the full compute payload patch with the Oracle public key:

json
{
  "encrypted_payload": "<encrypt({\"mode\":\"builtin\",\"function\":\"math.modexp\",\"input\":{\"base\":\"2\",\"exponent\":\"10\",\"modulus\":\"17\"},\"target_chain\":\"neo_n3\"})>"
}

Built-in Providers

Requests may optionally specify a built-in provider via

text

provider

and

text

provider_params

Built-ins:

text
twelvedata
— direct market-data source with API key auth
text
binance-spot
— direct Binance spot ticker endpoint without aggregation
text
coinbase-spot
— direct Coinbase spot price endpoint without aggregation

text

provider

is omitted, callers may still use their own

text

url

plus encrypted secret payloads.

Worker Verification Envelope

The worker response may include a stable

text

verification

object:

json
{
  "verification": {
    "output_hash": "<sha256 of canonical result payload>",
    "attestation_hash": "<currently mirrors output_hash>",
    "signature": "<neo n3 signature or null>",
    "public_key": "<neo n3 public key or null>",
    "signer_address": "<optional neo n3 address>",
    "signer_script_hash": "<optional neo n3 script hash>",
    "tee_attestation": {
      "app_id": "...",
      "instance_id": "...",
      "compose_hash": "...",
      "quote": "0x...",
      "event_log": "...",
      "report_data": "0x..."
    }
  }
}

On-Chain Fulfillment Payload

The relayer normalizes successful worker output into a chain-ready result envelope before calling

text

fulfillRequest

json
{
  "version": "morpheus-result/v1",
  "request_type": "privacy_oracle",
  "fulfilled_at": "2026-03-09T00:00:00.000Z",
  "worker_status": 200,
  "success": true,
  "route": "/oracle/smart-fetch",
  "result": {
    "mode": "fetch+compute",
    "target_chain": "neo_n3",
    "result": true,
    "extracted_value": null
  },
  "verification": {
    "output_hash": "...",
    "attestation_hash": "...",
    "signature": "...",
    "public_key": "...",
    "signer_address": "...",
    "signer_script_hash": "...",
    "tee_attestation": {
      "app_id": "...",
      "instance_id": "...",
      "compose_hash": "...",
      "quote": "0x...",
      "event_log": "...",
      "report_data": "0x..."
    }
  }
}

This normalized JSON is UTF-8 encoded and passed as the

text

result

bytes of

text

FulfillRequest(...)

. The kernel stores that payload in its inbox even when no external callback adapter is used.

Result Interpretation

Miniapps and optional callback adapters should interpret the result payload as:

a UTF-8 JSON object
versioned by
text
version
with business payload under
text
result
with attestation/signature material under
text
verification

Verification

Use:

text
/api/attestation/verify
for server-side verification
text
/verifier
for the browser verifier UI

Runtime Limits

The active worker runtime now enforces:

request body limit at the HTTP ingress
script source size limit
registered-script fetch size limit
oracle programmable input size limit
compute input size limit
script / wasm result size limits
upstream Oracle / provider response size limits

Previous Relayer NextAttestation Spec

CURRENT DESIGNUPDATED FOR DUAL-CVM ARCHITECTURE

EDIT ON GITHUB