SUPPORT

FAQ & Troubleshooting

Common questions about integration, security, and network operations.

Frequently Asked Questions

Q: What is the request fee for the Privacy Oracle?

The current fee is 0.01 GAS (or equivalent) per request. This covers the TEE computation time and the relayer's transaction costs for the on-chain callback.

Q: Which networks are currently supported?

Neo N3 Mainnet is the live production network today. Neo X interfaces and examples are available in the repository, but live Neo X mainnet contract publication is still pending.

Q: Do I need to run my own relayer?

No. The Morpheus Network operates a decentralized pool of relayers. However, for high-availability enterprise requirements, you can run a private relayer instance.

Q: Is the TEE code open source?

Yes. The worker, relayer, contracts, and frontend are open source. The public verifier checks application-level attestation consistency, and deeper quote-chain validation can be layered on top if required.

Error Codes

If your callback receives a failure status, refer to the table below to diagnose the issue.

CODENAMEDESCRIPTION
0x01INVALID_SIGNATUREThe callback signature does not match the configured Oracle Verifier Key. Ensure your contract is pointing to the correct Morpheus registry.
0x02INSUFFICIENT_FEEThe request fee was not prepaid correctly. On Neo N3, deposit or sponsor 0.01 GAS fee credit first. On Neo X, match the live requestFee() value.
0x03TEE_TIMEOUTThe request exceeded the configured execution timeout. The system should still finalize the request with a failure callback instead of dropping it.

Still having issues?

If you encounter an error not listed here, please provide your requestId and transactionHash to our support team.

OPEN ISSUE
Previous Attestation SpecNextExamples Portfolio
REVISION 1.0.2LAST UPDATED: 2026-03-11