Meet Universal Ecosystem Wallets

One wallet.
Every app.
Entirely yours.

Embedded wallet infrastructure for the world you’re building. One identity across Solana and EVM. Every permission in your control.

App-scoped by default. Shared across approved apps on eligible plans.
THE MOONKEY ACCESS LAYER01 / ARCHITECTURE PREVIEW
One verified identity
Drag with a mouse or finger to rotate in any direction. Use arrow keys to rotate, Q and E to roll, or Shift for larger turns. Press Home, Enter or Space to reset. Automatic rotation follows the page animation preference.
Explore approved applications
Hero wallet scope
swap.moonsters.appwal_ECOSYSTEM

Same wallet. Each app keeps its own permissions.

ONE CONNECTED FOUNDATIONIdentityWalletsPermissions◎ Solana + ◇ EVM
01 / A world beyond a single app

Separate apps. Shared possibilities.

Start with a wallet for each application. Connect your ecosystem when you’re ready, with one wallet identity and explicit permissions for every approved app.

Entry tierApplication scope

A separate wallet for every app.

Use isolated wallet namespaces when each application should stand alone.

App Awal_A
App Bwal_B
App Cwal_C
Eligible plansUniversal ecosystem

The same wallet across approved apps.

Resolve one verified user to one entitled ecosystem namespace across domains.

App AApp BApp C
wal_ECOSYSTEM

Entitlements remain authoritative on the server. The interface explains access; it cannot grant it.

Explore the model
02 / Trust is in the architecture

Connected by design. Protected at every step.

MoonKey separates authentication, policy, transaction understanding, and signing into explicit boundaries.

Review the security architecture
01
ApplicationOrigin + audience
02
IdentityAssurance + session
03
PolicyEffective permissions
04
SimulationExact payload
05
SignerIsolated plane
No plaintext keysControl plane stores public metadata only
Default-deny authorityPermissions bind to each app and action
Portable by designRecovery, export and signer rotation paths
03 / Built for the builders

Your next big idea. A considered foundation.

Use one identity layer across app-scoped and premium ecosystem-scoped wallets. Chain details remain available when they matter.

  1. 01
    Register an applicationBind origins, environment and wallet scope.
  2. 02
    Configure authenticationEmail, passkey, social or enterprise.
  3. 03
    Resolve the walletMoonKey applies identity, scope and entitlement.
Open the developer experience
TypeScript
import { MoonKeyClient } from "@moonkey/sdk";

export async function readApplicationWallets(
  baseUrl: string,
  applicationId: string,
  getAccessToken: () => Promise<string>,
) {
  const moonkey = new MoonKeyClient({
    baseUrl,
    applicationId,
    getAccessToken,
  });
  const session = await moonkey.getSession();
  const wallets = await moonkey.listWallets();
  return { session, wallets };
}
Private workspace read SDK · endpoint activation required
04 / The complete picture

Everything connects here.

Composable surfaces for identity, wallets, permissions, transactions, recovery, and operations.

01 / Identity

Authentication without binding wallet ownership to one credential.

Email, passkeys, OAuth, OIDC, phone and external wallets resolve through separate credential records.

@◉G⌁OIDC
02 / Wallets

Chain-family accounts beneath one wallet identity.

Solana and EVM first, with adapter seams for additional networks.

◎ Solana8fjQ…pM2z◇ EVM0x72…90E4
03 / Policy

Readable rules bound to the payload being signed.

App, chain, program, value, frequency and assurance become deterministic decisions.

ALLOWApp = MoonSwapDaily spend < $5kotherwise → user approval
04 / Operate

Diagnostics built for the incident, not the screenshot.

Request IDs, lifecycle states, policy decisions, webhooks and redacted logs live in one operating surface.

API healthyAwaiting userPolicy denied
The next chapter is yours

Build a world.
We’ll connect it.

Explore the foundation for your next ecosystem.