Solana SMS vs Embedded Wallet · OS-layer vs App-layer route contest
On this page
Wiki route
This entry sits under AI Agent payment protocols overview · a 7-protocol survey. Read it against Privy x AWS Bedrock AgentCore · Default-wallet positioning in the AI agent economy for peer / contrast context and payments index for the broader system / regulatory boundary.
Key facts
- Representative of the Embedded Wallet route: Privy + Coinbase CDP · provides in-dapp UX
- Representative of the SMS route: Solana Saga + Seeker · turns the wallet into a system service
- Root causes constraining Embedded Wallet: the iOS sandbox + Google Play 30% fees + browser push restrictions
- SMS circumvents the above 3 major constraints via the 3 of Seed Vault + MWA + dApp Store
- Coinbase Wallet is already MWA-compatible on Android (hybrid route)
- Stripe Tap to Pay leans toward the SMS paradigm (NFC at the system layer · on the merchant side)
Competitive structure of OS-layer wallets and embedded wallets
The Embedded Wallet hides the private key in iCloud / Google passkey sync to smooth the UX, but it gets bound to the OS provider (see ERC-4337 embedded wallet adoption map · Privy/Coinbase/Alchemy/Safe). SMS turns the wallet into an OS built-in service · any dapp invokes it via a system intent. The UI and signing prompt are controlled by the OS — phishing resistance is strong, but a hardware pre-install is required. The two routes are not mutually exclusive: Coinbase Wallet already runs a “dual-wielding” approach on Android — integrating into dapps as an embedded wallet while also implementing MWA so it can interoperate with Saga / Seeker. Over the medium-to-long term: the OS layer has a deeper moat (the system vendor’s decision-making power) · the App layer has broader reach (usable on any smartphone). If Samsung / Xiaomi / Google genuinely integrate a Seed Vault–style native keystore, embedded wallet vendors will be forced to support MWA in order to maintain compatibility across the Android long tail.
Origin & evolution
2018-2022 Early wallets were all in-app (MetaMask / Phantom). 2021-2023 embedded wallets rose (Magic Link / Privy / Web3Auth) · solving the onboarding pain point but still at the app layer. 2022 Solana proposed the SMS concept · betting on the OS layer. 2023 Saga launched, validating basic feasibility. 2024 Seeker was announced · showing that the SMS paradigm had gained community support. 2025 Stripe acquired Privy + Bridge, building a closed loop of embedded wallet and stablecoin merchants (Embedded Wallet · Fintech Eating Web3 in Reverse as a Trojan Horse (Stripe Five Layers)); in sync, Solana Mobile lobbied Samsung / Xiaomi for Seed Vault integration. 2026-05 AWS AgentCore chose Privy + Coinbase CDP by default — this is a significant win for the embedded route in AI agent scenarios — but SMS remains an independent battleground in consumer-side mobile payments (USDC as a general-purpose payment currency, see USD Stablecoin Interchange Market).
Related
- Wiki Index
- Solana Saga / Seeker · mobile-native wallet stack (SMS overview)
- Privy embedded wallet
- Privy x AWS AgentCore
- Embedded Wallet-Driven Fintech Disintermediation · Four-Player Structure
Sources
- Solana Mobile official documentation (Seed Vault / MWA / dApp Store · SMS route) — https://docs.solanamobile.com/
- Privy docs (representative of the embedded wallet route) — https://docs.privy.io/
- Coinbase Developer Platform (CDP Wallet · Android MWA hybrid) — https://docs.cdp.coinbase.com/
- Privy “Privy and Stripe: Bringing crypto to everyone” (Stripe acquisition · embedded × stablecoin closed loop) — https://privy.io/blog/announcing-our-acquisition-by-stripe