Cowrie Research

passkeys-foundation

3 min read

Passkeys Foundation

  • Name: Passkeys Foundation
  • URL: https://passkeys.foundation/
  • Category: embedded-wallet infrastructure / passkey authentication / multi-chain wallet connectivity
  • Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
  • Summary: Passkeys Foundation is a passkey-native embedded-wallet stack. The useful part is not passwordless onboarding; it is the packaged bundle of signer custody, provider shims, session defaults, and app-controlled wallet policy across Bitcoin, EVM chains, and Solana.
  • What it does:
    • Provides an embedded wallet that dapps can integrate with a few lines of code through @passkeys/core and @passkeys/react
    • Uses passkeys and device-native authentication such as biometrics, system PINs, or device passwords to create and unlock wallets without seed-phrase-heavy onboarding
    • Supports Bitcoin, Ethereum and other EVM chains, Solana, and a broader list of supported networks including Base, Arbitrum One, Avalanche C-Chain, BNB Chain, Optimism, Mantle, zkSync, and others
    • Exposes provider interfaces aligned with standards such as EIP-1193, EIP-6963, Wallet Standard, Phantom-style Solana behavior, and Sats Connect v1 for Bitcoin
    • Offers a universal provider intended to let one embedded-wallet connection work across a multi-chain dapp
    • Includes wallet-adjacent UX features such as in-wallet swaps, fiat on-ramp access, theme customization, and QR-based passkey cloning for backup on platforms with weaker native sync
  • Key claims:
    • The homepage says Passkeys is “the elegant technology driving the next generation of crypto wallets” and emphasizes device-based authentication, multi-chain support, non-custodial design, and developer-friendly integration
    • The homepage also claims the private key is never fully materialized in one place and that relevant parties produce partial signatures that are combined without reconstructing the full key
    • The developer docs frame Passkeys Developer Kit as an SDK that bridges the web2/web3 experience gap by embedding a next-generation wallet directly in the application, with popup-based wallet creation instead of requiring a browser extension
    • The quickstart guide shows dapps initializing the wallet with createWallet, choosing supported providers, wrapping the app with WalletProvider, and rendering a WalletWidget, which supports the “few lines of code” integration claim
    • The API reference says createWallet can expose EIP-1193/EIP-6963-compatible EVM providers, Phantom-like Solana providers, Sats Connect v1 Bitcoin providers, and a separate universal provider named “Passkeys Universal”
    • The FAQ says Passkeys is self-custodial because transactions cannot occur without the user device’s involvement, adds that passkeys are powered by MPC, and describes QR-based cloning as a backup path for platforms like Windows that do not yet sync passkeys well
  • Whitepaper: No canonical standalone Passkeys Foundation whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, the developer docs, the quickstart guide, the API reference, and the FAQ; see ../whitepapers/passkeys-foundation-primary-sources-2026-05-04.md.
  • Sources:

Internal linkages

  • Best upward comparisons: privy, turnkey, and eip-6963.
  • Do not spend more graph budget than that unless the point is explicitly wallet-provider standardization.

Control surface

  • The leverage sits in device-bound signing, recovery and clone paths, supported provider modes, session defaults, and which chains or wallet surfaces the SDK makes easiest to ship.

  • That is why this note belongs with embedded-wallet control planes, not with generic auth widgets.

  • Last reviewed: 2026-05-29 UTC

Graph View