Attestation Payload Spec

This document explains what Morpheus currently stores in

attestation_hash

1. Current Hash Model

Today, Morpheus uses the following rule across Oracle, Compute, Feed, and VRF flows:

• text

  Copy

  attestation_hash == output_hash

• text

  Copy

  output_hash = sha256(stableStringify(canonical_result_payload))

• text

  Copy

  tee_attestation.report_data[0:32] == output_hash

Important:

• TDX
  text

  Copy

  report_data

  is 64 bytes.
• Morpheus uses the first 32 bytes as the application binding.
• The remaining 32 bytes are usually zero padding and must be ignored for app-level verification.

2. What Is The Canonical Payload?

The hash is not computed over the entire HTTP response body. It is computed over the canonical business payload for that execution path.

• Oracle fetch / smart-fetch:
  • text

    Copy

    { target_chain, target_chain_id, request_source, result, extracted_value, upstream_status }

• Compute builtin / script:
  • the compute result object returned by the worker, for example
    text

    Copy

    { runtime, function, result }

    or
    text

    Copy

    { runtime, entry_point, result }

• Pricefeed sync:
  • the canonical quote object, including
    text

    Copy

    feed_id

    ,
    text

    Copy

    pair

    ,
    text

    Copy

    display_symbol

    ,
    text

    Copy

    unit_label

    ,
    text

    Copy

    provider

    ,
    text

    Copy

    raw_price

    ,
    text

    Copy

    price_transform

    ,
    text

    Copy

    price_multiplier

    ,
    text

    Copy

    price

    ,
    text

    Copy

    decimals

    ,
    text

    Copy

    timestamp

    ,
    text

    Copy

    sources

• VRF:
  • text

    Copy

    { randomness }

3. How Users Verify

text

Copy

attestation_hash

A. Oracle / Compute callback verification

If your contract receives a callback result envelope like:

json
 Copy
{
  "version": "morpheus-result/v1",
  "request_type": "oracle",
  "success": true,
  "result": { "...": "..." },
  "verification": {
    "output_hash": "0x...",
    "attestation_hash": "0x...",
    "tee_attestation": {
      "app_id": "...",
      "compose_hash": "...",
      "report_data": "0x..."
    }
  }
}

verify it in this order:

1. Read
   text

   Copy

   verification.output_hash

   .
2. Read
   text

   Copy

   verification.attestation_hash

   .
3. Confirm they are equal.
4. Read
   text

   Copy

   verification.tee_attestation.report_data

   .
5. Take the first 32 bytes of
   text

   Copy

   report_data

   .
6. Confirm that first 32-byte prefix equals
   text

   Copy

   attestation_hash

   .
7. If you know the canonical result payload, compute
   text

   Copy

   sha256(stableStringify(payload))

   and confirm it also equals
   text

   Copy

   output_hash

   .
8. Optionally confirm
   text

   Copy

   app_id

   ,
   text

   Copy

   compose_hash

   , and
   text

   Copy

   instance_id

   against the published Morpheus deployment metadata.

B. Pricefeed on-chain verification

If you read a feed record from the on-chain datafeed contract:

json
 Copy
{
  "pair": "TWELVEDATA:NEO-USD",
  "roundId": 123,
  "price": 1234,
  "timestamp": 1710000000,
  "attestationHash": "0x..."
}

the chain only stores the compact

attestation_hash

To verify that hash:

1. Fetch the matching feed publication record from Morpheus operational logs / audit logs.
2. Rebuild the canonical quote payload for that exact publication.
3. Compute
   text

   Copy

   sha256(stableStringify(quote_payload))

   .
4. Confirm the computed hash equals the on-chain
   text

   Copy

   attestationHash

   .
5. If the publication log includes
   text

   Copy

   tee_attestation

   , confirm the first 32 bytes of
   text

   Copy

   report_data

   equal the same hash.

Without the off-chain publication record, you can verify chain consistency of the stored hash, but you cannot fully reconstruct the original TEE quote from the chain record alone.

4. Built-In Verifier

The web verifier is available at:

• text

  Copy

  /verifier

• text

  Copy

  /api/attestation/lookup

• text

  Copy

  /api/attestation/verify

It accepts:

• full worker responses
• compact callback envelopes
• raw
  text

  Copy

  tee_attestation

  objects
• stored attestation lookups by
  text

  Copy

  attestation_hash

• optional expected payload JSON
• optional expected
  text

  Copy

  output_hash

• optional expected or on-chain
  text

  Copy

  attestation_hash

• optional
  text

  Copy

  app_id

  ,
  text

  Copy

  compose_hash

  , and
  text

  Copy

  instance_id

The verifier returns:

• text

  Copy

  binding_ok

  • text

    Copy

    output_hash

    ,
    text

    Copy

    attestation_hash

    , and
    text

    Copy

    report_data

    prefix are consistent
• text

  Copy

  full_attestation_ok

  • same as above, plus a full quote and event log were attached

5. Scope

The built-in verifier is an application-level verifier.

It does:

• verify
  text

  Copy

  output_hash

• verify
  text

  Copy

  attestation_hash

• verify
  text

  Copy

  report_data

  first-32-byte binding
• verify
  text

  Copy

  app_id

  /
  text

  Copy

  compose_hash

  /
  text

  Copy

  instance_id

  when supplied

It does not:

• fully validate Intel / TDX certificate chains
• independently validate platform trust roots

6. Published Morpheus CVM Explorers

The current production topology is role-split, not network-split:

• Oracle request/response CVM:
  • text

    Copy

    oracle-morpheus-neo-r3e

  • app id
    text

    Copy

    ddff154546fe22d15b65667156dd4b7c611e6093

  • explorer
    text

    Copy

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

• DataFeed CVM:
  • text

    Copy

    datafeed-morpheus-neo-r3e

  • app id
    text

    Copy

    28294e89d490924b79c85cdee057ce55723b3d56

  • explorer
    text

    Copy

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

Both mainnet and testnet Oracle traffic now terminate at the Oracle CVM and differ only by the network selected in the request path or payload. Feed synchronization runs on the dedicated DataFeed CVM.

中文说明

1. 当前

text

Copy

attestation_hash

的含义

目前系统里：

• text

  Copy

  attestation_hash == output_hash

• text

  Copy

  output_hash = sha256(stableStringify(规范结果载荷))

• text

  Copy

  tee_attestation.report_data

  的前 32 字节等于这个 hash

注意：

• text

  Copy

  report_data

  总长度通常是 64 字节
• 真正要比对的是前 32 字节
• 后 32 字节一般是补零，不能拿整段直接和 32 字节 hash 比

2. 用户应该怎么验

Oracle / Compute 回调

拿到链上 callback 的

result

1. 读取
   text

   Copy

   verification.output_hash

2. 读取
   text

   Copy

   verification.attestation_hash

3. 确认两者相等
4. 读取
   text

   Copy

   verification.tee_attestation.report_data

5. 截取前 32 字节
6. 确认这个前缀等于
   text

   Copy

   attestation_hash

7. 如果你能拿到规范结果载荷，就自己重新做
   text

   Copy

   sha256(stableStringify(payload))

8. 确认算出来的值也等于
   text

   Copy

   output_hash

Pricefeed 链上记录

链上的 datafeed record 只保存了

attestation_hash

因此要验证它：

1. 从 Morpheus 的操作日志 / 审计日志里拿到对应那次发布的完整 quote 记录
2. 用同样的规范序列化方式重建 quote payload
3. 计算
   text

   Copy

   sha256(stableStringify(payload))

4. 和链上的
   text

   Copy

   attestation_hash

   比较
5. 如果日志里有
   text

   Copy

   tee_attestation

   ，再确认
   text

   Copy

   report_data

   前 32 字节也等于这个 hash

只看链上 record 本身，只能验证“链上存了什么 hash”，不能单独还原完整 TEE quote。

3. 前端 verifier 能做什么

/verifier

• 完整 worker 响应
• 链上 callback 的紧凑 envelope
• 原始
  text

  Copy

  tee_attestation

  JSON

并且支持额外输入：

• 期望的
  text

  Copy

  output_hash

• 期望的 / 链上的
  text

  Copy

  attestation_hash

• text

  Copy

  app_id

• text

  Copy

  compose_hash

• text

  Copy

  instance_id

4. 当前 verifier 的边界

当前 verifier 是“应用层验证”，不是完整的 TDX 证书链验证。

5. 当前公开的 Phala Explorer

当前生产拓扑是按角色拆分，不是按网络拆分：

• Oracle 请求/响应 CVM
  • 名称：
    text

    Copy

    oracle-morpheus-neo-r3e

  • app id：
    text

    Copy

    ddff154546fe22d15b65667156dd4b7c611e6093

  • explorer：
    text

    Copy

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

• DataFeed CVM
  • 名称：
    text

    Copy

    datafeed-morpheus-neo-r3e

  • app id：
    text

    Copy

    28294e89d490924b79c85cdee057ce55723b3d56

  • explorer：
    text

    Copy

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