MoonKeyDocumentation
Flagship scope

Universal ecosystem wallets

One verified identity and wallet namespace across multiple approved applications.

Foundation implemented
Pre-alpha documentation boundary

Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.

Examples
Code example format

Resolution invariant#

The same credential proof inside the same entitled environment and ecosystem resolves to the same ecosystem user and wallet identity across approved applications and domains. An unrelated ecosystem resolves a distinct identity and wallet.

Invariant
verified identity + environment + ecosystem
  → ecosystem user
  → wallet namespace
  → wallet identity

Entitlement boundary#

Ecosystem scope requires both stable capability keys at configuration, session issuance, resolution, provisioning, policy, and signer coordination. The dashboard cannot grant the capability.

Required capabilities
wallet_scope.ecosystem
ecosystem.multi_app

Application authority#

Sharing a wallet never means sharing unlimited authority. Each app retains its own origin, session, policy, risk, assurance, and revocation context.

  • App A can view only
  • App B can sign approved swaps
  • App C can interact with NFTs
  • Revoking one app preserves the wallet
Implementation status

Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.

Engineering status

Command center

Search page titles and navigate to a console page or documentation article.