Skip to main content
Your choice of signer determines how users authenticate. The right one depends on who your users are and whether they already have a wallet.

Native signers

Cryptographic primitives built into the SDK. No third-party provider required.

ECDSA

Standard Ethereum key pairs. Supports single-owner and multisig (n/m threshold). Best for server-side and agent wallets.

Passkey

Device biometrics via WebAuthn (Face ID, Touch ID). No seed phrases. Supports single-owner and multisig. Best for consumer apps.

Multi-factor

Combine multiple validators, e.g. require both an ECDSA key and a passkey. Best for high-security accounts.

Embedded wallet signers

Keys managed inside your app via secure enclave. Users authenticate with social login or email, with no browser extension or seed phrase needed. Use these when onboarding users who don’t already have a crypto wallet.

Privy

Social and email login with embedded wallets.

Dynamic

Multi-chain embedded wallets with social and email login.

Para

Embedded wallets with MPC key management.

Magic

Email and social login with non-custodial embedded wallets.

Turnkey

Programmatic wallet infrastructure for server-side and agent use cases.

Openfort

Embedded wallets with a gaming-first developer experience.

External wallet signers

Browser extensions and mobile wallets users already own, such as MetaMask, Coinbase Wallet, and any WalletConnect-compatible wallet. Use these for dApps serving existing Web3 users.

External wallets

Connect MetaMask, Coinbase Wallet, and WalletConnect-compatible wallets via Reown AppKit.