Networks & Contracts
Canonical mainnet and testnet publication status for Morpheus Oracle, DataFeed, NeoDID, and AA integration anchors. The selected runtime is mainnet, but this page shows both networks side-by-side so addresses and domains do not get mixed. Oracle and DataFeed CVMs are shared across both networks; the network boundary is path-driven and config-driven rather than VM-driven.
Source of truth: config/networks/mainnet.json and config/networks/testnet.json. The current role-split Phala launchers live in phala.request-hub.toml and phala.feed-hub.toml, while runtime selection happens through /mainnet/* and /testnet/*.
Interpretation rules:
OracleCallbackConsumeris the production callback sink contract configured in the network registry.Example consumerandFeed reader exampleare validation/demo contracts used by the published live probes.AA runtime labelis the canonical product name; raw manifest-name suffixes stay in low-level deployment logs only.- Oracle and DataFeed CVM ids intentionally match across mainnet and testnet rows.
- Mainnet AA ecosystem contracts are now also published under
smartwallet.neosubdomains for direct verifier / hook discovery. aa.morpheus.neois kept as a compatibility alias;smartwallet.neoremains the primary AA public domain.- Testnet AA currently has a published core hash but no NNS alias.
- Testnet NeoDIDRegistry remains unpublished in the canonical registry until a stable shared deployment is intentionally promoted.
Neo N3 remains the active supported runtime path. The live request fee is 0.01 GAS, the confidential payload transport is X25519-HKDF-SHA256-AES-256-GCM, and the public NeoDID service DID is did:morpheus:neo_n3:service:neodid.