Switch to WaaP
If an application already ships an embedded wallet, the question is what changes for the user and what changes for the codebase.
What changes for the user. The wallet stops being scoped to one application. The same account works in the next app that supports it, so a user’s history, balances and reputation follow them rather than resetting. Keys are generated inside an attested enclave and never reach the device. Every signature passes a policy the user set.
What changes for the codebase. One SDK call to initialise, an EIP-1193 provider for EVM and the Wallet Standard interface for Sui. If the app already speaks to a wallet through either of those, most of the integration surface is unchanged.
Comparisons
| WaaP vs Privy | Trust model, account scope, pricing shape and feature-by-feature differences |
| Migrating from Privy | The migration itself: what to swap, in what order, and what to tell users |
Building for agents rather than an app? The agent-side comparisons are at WaaP vs Privy Server Wallets and WaaP vs Coinbase Agent Wallets.