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.

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.

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.