Cowrie Research

passkeys-foundation-primary-sources-2026-05-04

3 min read

Passkeys Foundation primary sources — 2026-05-04

Project status in this pass

  • No canonical standalone Passkeys Foundation whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official site plus the developer docs, quickstart guide, createWallet API reference, and FAQ.
  • The project is best understood as embedded-wallet and wallet-connectivity infrastructure for dapps rather than as a simple auth widget or single-chain wallet SDK.

Primary-source snapshots

1) Official homepage

  • URL: https://passkeys.foundation/
  • Key excerpt:
    • The homepage says Passkeys is “the elegant technology driving the next generation of crypto wallets.”
    • It highlights device-based authentication, multi-chain support, non-custodial design, and developer-friendly integration.
    • It also says the private key is never fully materialized in one place and describes partial-signature combination rather than full-key reconstruction.

2) Developer docs overview

  • URL: https://passkeys.foundation/docs
  • Key excerpt:
    • The docs call Passkeys Developer Kit a powerful SDK that helps application builders bridge the web2/web3 experience gap.
    • They describe a one-click embedded wallet that creates and accesses passkeys via a popup window instead of requiring a browser extension.
    • The docs position the product as embedded wallet infrastructure for desktop and mobile signing.

3) Quickstart guide

  • URL: https://passkeys.foundation/docs/quickstart
  • Key excerpt:
    • The quickstart says developers can integrate the embedded wallet in a few lines of code.
    • It shows createWallet being called with an app ID and supported chains, then wrapped with WalletProvider and a WalletWidget.
    • That is strong evidence that Passkeys is packaging a reusable integration layer rather than merely describing a wallet concept.

4) createWallet API reference

  • URL: https://passkeys.foundation/docs/api-reference/create-wallet
  • Key excerpt:
    • The reference says createWallet initializes the embedded wallet and exposes web3 providers to the page.
    • For EVM chains it returns an EIP-1193 provider and can announce through EIP-6963.
    • For Solana it returns a Phantom-like provider and can announce through Wallet Standard.
    • For Bitcoin it returns a Sats Connect v1 provider.
    • It also exposes a universal provider named “Passkeys Universal” for multi-chain dapps.

5) FAQ

  • URL: https://passkeys.foundation/docs/faq
  • Key excerpt:
    • The FAQ says integration should work with little to no code modification because Passkeys follows standards like EIP-1193.
    • It lists supported chains including Bitcoin, Ethereum, Solana, Base, Arbitrum One, Avalanche C-Chain, BNB Chain, Optimism, Mantle, and zkSync.
    • It says users can swap crypto and purchase crypto from inside the embedded wallet.
    • It also says the system is self-custodial because transactions require the user device’s involvement, the client key can only be decrypted and used by that device, and QR-based cloning can be used as a backup path where native passkey sync is weak.

Working conclusion

Passkeys Foundation is best cataloged as passkey-native embedded-wallet and multi-chain connectivity infrastructure. The deciding evidence in this pass was the combination of popup-based wallet creation, standards-aligned provider exposure across several chains, universal-provider support for multi-chain dapps, self-custodial MPC claims tied to mandatory user-device participation, and explicit backup/recovery UX built around passkey ecosystems rather than seed phrases.

Graph View