Premium capability

One user wallet across every approved app.

Give verified users continuity across independent applications and domains—without giving every application the same authority.

Scope resolverOne entitled namespace
Wallet scope model
Identity-bound routeApp-specific authoritySame verified user + same entitled ecosystem = same wallet
Shared identity, isolated permission

The wallet is common. Authority is not.

Each app receives a policy-bound context evaluated again for every sensitive action.

Example permissions for each application in an ecosystem
ApplicationViewSignSendSwapNFT
MoonHoldAllowedAllowedDeniedDeniedDenied
MoonSwapAllowedAllowedAllowedAllowedDenied
MoonMarketAllowedAllowedAllowedAllowedDenied
MoonSeumAllowedAllowedAllowedDeniedAllowed
Configure deliberately

From ecosystem definition to controlled launch.

The setup flow keeps commercial access, trusted applications, domains and security choices distinct.

  1. 01Ecosystem details
  2. 02Add applications
  3. 03Verify domains
  4. 04Wallet scope
  5. 05Authentication
  6. 06Permissions
  7. 07Review
  8. 08Launch
Server-side entitlement required

The setup interface can request ecosystem scope, but `wallet_scope.ecosystem` and `ecosystem.multi_app` must both be active at every enforcing service.

The next chapter is yours

Build a world.
We’ll connect it.

Explore the foundation for your next ecosystem.