Cowrie Research

passkeys-foundation

5 min read

Passkeys Foundation

  • Name: Passkeys Foundation
  • URL: https://passkeys.foundation/
  • Category: embedded-wallet company / passkey-native signer-control-plane operator / multi-chain wallet-onboarding vendor
  • Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
  • Summary: Passkeys Foundation belongs as an entity note, not primarily as a protocol note. The useful question is who operates the embedded-wallet stack, decides which provider modes and chains are exposed by default, packages swap and on-ramp partners into the wallet shell, and defines backup / recovery workflow around passkey-based signing. The practical leverage sits in the company-run signer lifecycle: device-auth assumptions, MPC composition, popup and provider behavior, export / recovery options, and the app-facing integration defaults downstream teams inherit. The branding-versus-operator boundary is also worth keeping visible because the homepage footer currently says ©2026 Exodus Movement, Inc., which suggests the marketed Passkeys surface sits inside a named corporate operator rather than floating as a neutral standard.
  • What it does:
    • Provides an embedded wallet that dapps can integrate with a few lines of code through the Passkeys Developer Kit
    • Uses passkeys plus device-native authentication such as biometrics, system PINs, or device passwords to create and unlock wallets without seed-phrase-heavy onboarding
    • Exposes provider interfaces for EVM, Solana, Bitcoin, and a universal multichain provider, with standards-facing behavior aligned to EIP-1193, EIP-6963, Wallet Standard, Phantom-style Solana injection, and Sats Connect v1
    • Packages wallet-adjacent product surfaces including themeable embedded UI, in-wallet swaps, fiat on-ramp access, and multichain wallet connectivity into one app-facing integration shell
    • Defines backup, sync, QR-clone, recovery, and optional key-export workflow around the passkey-based wallet experience rather than leaving those flows entirely to external wallets
    • Markets the stack as self-custodial MPC-based wallet infrastructure while keeping the developer and user experience centered on app-embedded onboarding
  • Key claims:
    • The homepage markets Passkeys as technology for the next generation of crypto wallets, emphasizing biometric authentication, multichain support, non-custodial design, and easy dapp integration
    • The homepage says the private key is never fully materialized in one place and that partial signatures are combined without reconstructing the full key, which is the clearest top-level statement of the MPC-style signer model
    • The developer docs say Passkeys Developer Kit is an SDK for embedding a next-generation wallet directly into an application and explicitly contrast the popup-based flow with browser-extension onboarding
    • The createWallet API reference says the wallet can expose EIP-1193 and EIP-6963-aware EVM providers, Phantom-like Solana providers, Sats Connect v1 Bitcoin providers, and a universal provider named Passkeys Universal
    • The FAQ says Passkeys supports Bitcoin, Ethereum, Solana, Arbitrum One, Avalanche C-Chain, Base, BNB Chain, Optimism, Astar, Celo, Immutable, Kroma, Mantle, Moonbeam, Rari, and zkSync, while also saying additional EVM support can be configured through the sales team
    • The FAQ says users can swap crypto, including cross-chain swaps, and access fiat on-ramp providers directly from within the embedded wallet, which makes third-party liquidity and compliance partners part of the effective control surface
    • The FAQ says passkeys sync through platform backup providers where available, adds a QR-based clone path for environments like Windows where sync is weaker, and says users can export private keys through an advanced feature; those recovery and escape-hatch choices materially shape the real custody boundary
    • The FAQ says no transaction can occur without the user’s device involvement because the device holds the cryptographic material needed to decrypt and use the client key; that is important, but it still leaves the company with meaningful leverage over wallet UX, provider exposure, recovery design, and packaged service integrations
    • The homepage footer currently reads ©2026 Exodus Movement, Inc., which is a useful operator clue because it ties the marketed Passkeys product surface to a specific corporate boundary
  • Whitepaper: No canonical standalone company whitepaper surfaced in this pass. The clearest current primary materials were the official site, developer docs, API reference, and FAQ; the older source bundle at ../whitepapers/passkeys-foundation-primary-sources-2026-05-04.md still provides background context, but this note was refreshed directly from the live primary docs.
  • Sources:

Internal linkages

  • Project-layer alias: passkeys-foundation.
  • Broader corporate operator shell signaled by the live footer and docs adjacency: exodus.
  • Keep the best adjacent reads on embedded-wallet and signer-control-plane neighbors: turnkey, crossmint, and privy.
  • Reusable lens: wallet vendors that promise passkeys, embedded wallets, or one-click onboarding often deserve a company note when backup workflow, provider injection, partner composition, and recovery policy sit with one named operator.

Control surface

  • Practical leverage sits in provider exposure, chain-support defaults, popup and embedded-wallet behavior, swap and on-ramp partner composition, recovery and QR-clone workflow, key-export policy, and the app-integration defaults developers inherit.

  • The company also shapes what self-custody means in practice: which signing flows stay device-bound, how backup and migration are encouraged, how much recovery depends on platform vendors like Apple or Google, and what escape hatches exist when platform sync is weak.

  • The newer exodus company note is useful when the question is not only Passkeys as a signer-control plane but the broader wallet, docs, checkout, and distribution shell that now appears to package it.

  • Read Passkeys Foundation as a company-run wallet-onboarding and signer-control plane, not as a neutral protocol baseline.

  • Last reviewed: 2026-08-10 UTC

Graph View

Backlinks