metamask-embedded-wallets

MetaMask Embedded Wallets (formerly Web3Auth)

• Name: MetaMask Embedded Wallets (formerly Web3Auth)
• URL: https://web3auth.io/
• Category: hosted wallet-control plane / embedded auth and key-share middleware
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: MetaMask Embedded Wallets is hosted wallet ops for teams that want familiar login flows instead of seed-phrase discipline. The product note matters because the user-facing and integrator-facing surface is still distinct: hosted key-share, recovery, and identity plumbing wrapped as embedded wallet infrastructure. The broader operator boundary around MetaMask distribution, Embedded Wallets packaging, and adjacent developer infrastructure now lives in consensys.
• What it does:
  • Lets apps create embedded non-custodial wallets using OAuth, email, SMS, authenticator apps, or custom authentication flows
  • Provides SDKs across web, React, Vue, Node.js, Android, iOS, React Native, Flutter, Unity, and Unreal Engine
  • Supplies wallet infrastructure rather than a standalone end-user wallet, giving developers a cryptographic key provider they can use inside their own applications or wallet experiences
  • Uses distributed key-share and threshold-reconstruction infrastructure so no single party holds the entire private key, while still supporting account recovery flows
  • Supports EVM and Solana directly and can export private keys for use with other chains and custom integrations
• Key claims:
  • MetaMask’s docs say Embedded Wallets is “not a wallet” but wallet infrastructure that simplifies onboarding and key management for dapps and blockchain wallets
  • The docs say users maintain control of non-custodial wallets while the system removes direct seed-phrase management from the onboarding path
  • The architecture docs say the system combines OAuth login flows, an Embedded Wallets network, SDKs, and a threshold-key core kit (tKey) to reconstruct signing keys without any single party holding the full secret
  • The GitHub org says the product is chain-agnostic, includes built-in EVM and Solana providers, and spans web, mobile, gaming, and backend SDKs
  • The docs also say the infrastructure is built to handle millions of users with globally available, automatically scaling Kubernetes-based infrastructure
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were the official Web3Auth site, MetaMask Embedded Wallets docs, architecture/get-started pages, and the public Web3Auth GitHub organization; see ../whitepapers/metamask-embedded-wallets-primary-sources-2026-04-26.md.
• Sources:
  • https://web3auth.io/
  • https://docs.web3auth.io/
  • https://docs.metamask.io/embedded-wallets/
  • https://docs.metamask.io/embedded-wallets/get-started/
  • https://docs.metamask.io/embedded-wallets/architecture/
  • https://github.com/Web3Auth
  • https://github.com/MetaMask

Internal linkages

• Company / operator boundary for MetaMask distribution, Embedded Wallets packaging, and the broader wallet-plus-infrastructure shell: consensys.
• Keep the comparison set tight and upward: privy and turnkey.

Protocol / company boundary

• Keep this note on the embedded-wallet product surface: OAuth-style onboarding, threshold key-share reconstruction, recovery-factor composition, SDK ergonomics, and the specific middleware developers integrate.
• Use consensys when the sharper question is who packages MetaMask distribution, builder tooling, embedded-wallet infrastructure, and adjacent chain-access or protocol-client surfaces into one operating shell.
• That split matters because how do Embedded Wallets work? and which company controls the surrounding wallet-and-infrastructure bundle? are related but not identical questions.

Control surface

• At the product layer, the leverage sits in authentication-factor policy, threshold-key reconstruction, recovery handling, and provider defaults.

• When a vendor says it removed wallet friction, ask who now controls recovery factors, identity bindings, and the durable login path.

• For the wider distribution and platform shell around this product, read consensys.

• Read this as hosted login-and-key middleware, not a new account substrate.

• Last reviewed: 2026-08-07 UTC