Attestation & Security

Remote Attestation is the cornerstone of Morpheus's trust model. It lets external observers validate that the response metadata came from the expected Phala TEE deployment and that the quote is bound to the reported output hash and on-chain attestation_hash.

The Evidence Layer

Every task executed by a Morpheus worker can be bundled with an Attestation Quote. The verifier focuses on the application-level fields that are available in the live result envelope:

• ✓
  app_id / compose_hashStable identifiers that let you confirm the response came from the expected Morpheus Phala deployment and compose bundle.
• ✓
  instance_idIdentifies the concrete worker instance that produced the quote, useful for operational forensics and replay analysis.
• ✓
  attestation_hash / report_dataMorpheus currently sets attestation_hash == output_hash. The verifier compares the first 32 bytes of TDX report_data against that hash.

Off-Chain Verification Flow

While on-chain contracts verify the worker signature, high-security applications should also perform off-chain verification:

1. Fetch the callback envelope or worker response, then read output_hash, attestation_hash, and tee_attestation.report_data.
2. Verify that attestation_hash == output_hash.
3. Verify that the first 32 bytes of report_data match that same hash.
4. Check app_id and compose_hash against the published Morpheus deployment metadata.
5. If you need full quote-chain validation, perform an additional platform-specific verification pass outside the built-in web verifier.

Trust Boundaries

By combining hardware isolation with cryptographic proof, Morpheus shifts the security boundary from "Trust the Operator" to "Trust the Code".