Async Privacy Oracle Spec

Canonical Request Path

1. Client reads the Oracle public key.
2. Client encrypts a secret locally.
3. Contract calls
   text

   Request(requestType, payload, callbackContract, callbackMethod)

   on
   text

   MorpheusOracle

   or
   text

   MorpheusOracleX

   .
4. text

   OracleRequested

   is emitted on-chain.
5. Morpheus dispatcher validates the event and forwards it to the Phala worker.
6. Phala executes fetch-only, private fetch, public compute, or private compute.
7. Dispatcher calls
   text

   FulfillRequest(requestId, success, result, error)

   .
8. Callback executes in the consumer contract.

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>",
  "token_header": "Authorization",
  "script": "function process(data) { return data.age > 80; }",
  "script_base64": "ZnVuY3Rpb24gcHJvY2VzcyhkYXRhKSB7IHJldHVybiBkYXRhLmFnZSA+IDgwOyB9",
  "target_chain": "neo_x",
  "target_chain_id": "12227332"
}

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

  script

  and
  text

  script_base64

  are interchangeable aliases
• text

  callback_contract

  and
  text

  callback_method

  are on-chain request arguments, not JSON payload fields
• text

  target_chain

  may be
  text

  neo_n3

  or
  text

  neo_x

• confidential payload transport uses
  text

  X25519-HKDF-SHA256-AES-256-GCM

Built-in Compute API

Use

POST /compute/execute

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

or

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

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

provider

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

If

provider

url

Worker Verification Envelope

The worker response may include a stable

verification

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

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

result

FulfillRequest(...)

Callback Consumer Interpretation

Consumers should interpret the callback 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/demo

  for a prefilled example
• text

  /api/attestation/verify

  for server-side verification
• text

  /verifier

  for the browser verifier UI