Universal ecosystem wallets
One verified identity and wallet namespace across multiple approved applications.
Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.
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.
verified identity + environment + ecosystem
→ ecosystem user
→ wallet namespace
→ wallet identityEntitlement boundary#
Ecosystem scope requires both stable capability keys at configuration, session issuance, resolution, provisioning, policy, and signer coordination. The dashboard cannot grant the capability.
wallet_scope.ecosystem
ecosystem.multi_appApplication 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
Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.