Cowrie Research

metamask-embedded-wallets-primary-sources-2026-04-26

4 min read

MetaMask Embedded Wallets (formerly Web3Auth) primary-source snapshot

Fetched: 2026-04-26 UTC

1) Official website

Source: https://web3auth.io/

Selected excerpts from the official site:

Key Management SDKs with MPC and AA enabled

Non-custodial Infrastructure

Additional signals from the site:

  • The homepage is sparse, but it still signals the core product framing: key-management SDKs, MPC-enabled wallet infrastructure, and non-custodial onboarding
  • The public site remains under the Web3Auth domain even though the product is now branded as MetaMask Embedded Wallets in developer docs

2) Legacy docs introduction

Source: https://docs.web3auth.io/

Selected excerpts from the docs:

MetaMask Embedded Wallets (formerly Web3Auth) is a pluggable embedded wallet infrastructure that simplifies Web3 wallet integration and user onboarding.

Users enjoy seamless onboarding while maintaining full control of their non-custodial wallets

Additional signals from the docs:

  • The docs explicitly map the old and new brands, which is useful for tracing continuity across product, repo, and package surfaces
  • The introduction makes clear that the product is infrastructure for applications, not an end-user wallet brand on its own

3) MetaMask Embedded Wallets overview

Source: https://docs.metamask.io/embedded-wallets/

Selected excerpts from the MetaMask docs:

MetaMask Embedded Wallets (formerly Web3Auth) provides a pluggable embedded wallet infrastructure to simplify Web3 wallet integration and user onboarding.

MetaMask Embedded Wallets is not a wallet, but rather a wallet infrastructure that can be integrated into any application.

Additional signals from the docs:

  • The overview page is the clearest first-party statement of category: wallet infrastructure, not wallet product
  • The feature list centers authentication, distributed security, developer customization, and onboarding UX rather than speculative protocol claims
  • This framing makes the project more comparable to embedded-wallet/key-management vendors than to consumer wallets

4) Get-started page

Source: https://docs.metamask.io/embedded-wallets/get-started/

Selected excerpts from the docs:

Seamlessly provide your users with Web3 wallets using social logins they already know and trust.

Select the SDK for your framework or platform: React, Vue, JavaScript, Node.js, Android, iOS, React Native, Flutter, Unity, Unreal Engine

Additional signals from the docs:

  • The breadth of platform support is a major part of the product’s value proposition
  • The dashboard still lives at dashboard.web3auth.io, which confirms that the Web3Auth operational surface remains active even after MetaMask rebranding

5) Architecture page

Source: https://docs.metamask.io/embedded-wallets/architecture/

Selected excerpts from the docs:

The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plug and Play SDKs). Package names and APIs remain Web3Auth

The infrastructure is designed so that no single party holds the full private key.

Core kit (tKey) combines key shares to recreate the user’s signing key.

Additional signals from the docs:

  • The architecture page is the highest-signal source for the trust model, because it explains the SDK, login-provider, Embedded Wallets network, and key-share flow explicitly
  • The note about package names staying Web3Auth is important for catalog accuracy, since docs, code, and branding are split across two names
  • The key-share flow makes the product clearly about key-management and wallet infrastructure rather than simple OAuth login middleware

6) Public GitHub organizations

Source: https://github.com/Web3Auth Source: https://github.com/MetaMask

Selected excerpts from the GitHub surfaces:

MetaMask Embedded Wallets (formerly Web3Auth) is a pluggable wallet infrastructure that brings non-custodial social login wallets to any application.

private keys are split across multiple parties using Shamir Secret Sharing and MPC. No single party, including MetaMask, ever holds the full key.

built-in providers for EVM and Solana; export the private key for any other chain.

Additional signals from the repos/orgs:

  • The Web3Auth GitHub org remains the best high-signal source for package inventory, examples, SDK coverage, and current developer surface area
  • MetaMask’s org and docs provide the broader parent-brand context, but Web3Auth’s org still contains the most direct repository-level evidence about the product
  • The coexistence of the two org/doc surfaces strongly suggests this should be cataloged as an active rebranded product rather than as a deprecated legacy brand

Notes

  • This pass did not locate a classic whitepaper or litepaper from official MetaMask Embedded Wallets / Web3Auth sources.
  • MetaMask Embedded Wallets appears best categorized as embedded wallet infrastructure / authentication / non-custodial key-management SDK.
  • The strongest primary materials were the Web3Auth site, Web3Auth docs intro, MetaMask Embedded Wallets docs and architecture pages, and the public Web3Auth GitHub organization.

Graph View