A separate wallet for every app.
Use isolated wallet namespaces when each application should stand alone.
wal_Awal_Bwal_CEmbedded wallet infrastructure for the world you’re building. One identity across Solana and EVM. Every permission in your control.
wal_ECOSYSTEMSame wallet. Each app keeps its own permissions.
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.
Use isolated wallet namespaces when each application should stand alone.
wal_Awal_Bwal_CResolve one verified user to one entitled ecosystem namespace across domains.
wal_ECOSYSTEMEntitlements remain authoritative on the server. The interface explains access; it cannot grant it.
Explore the modelMoonKey separates authentication, policy, transaction understanding, and signing into explicit boundaries.
Review the security architectureUse one identity layer across app-scoped and premium ecosystem-scoped wallets. Chain details remain available when they matter.
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 };
}Composable surfaces for identity, wallets, permissions, transactions, recovery, and operations.
Email, passkeys, OAuth, OIDC, phone and external wallets resolve through separate credential records.
Solana and EVM first, with adapter seams for additional networks.
8fjQ…pM2z◇ EVM0x72…90E4App, chain, program, value, frequency and assurance become deterministic decisions.
Request IDs, lifecycle states, policy decisions, webhooks and redacted logs live in one operating surface.
Explore the foundation for your next ecosystem.