Skip to main content
Choose an EVM signer based on where keys live, how users authenticate, and how many approvals a transaction requires. Configure smart account owners under evm.owners; plain EOAs use evm.eoa.

​
Solana authority scope

A managed Solana entry uses singular solana.owner: { type: 'ecdsa', account } for a viem secp256k1 account, or { type: 'passkey', account } for a WebAuthn account. It does not accept Ed25519 wallet keys, owner arrays, EVM multisig, or MFA configurations. Additional Swig roles carry explicit permissions, not approval thresholds. Use the common account recipe for independent or composite accounts and receiver-only destinations. Embedded or external Ethereum signers need the same secp256k1 signing capabilities; their Solana-wallet products are not interchangeable with these authorities. See Solana support for scope and environment limits.

​
Native signers

Use native signers when you want direct control without an embedded wallet provider.

ECDSA

Use standard Ethereum keys for server wallets, agents, existing wallet clients, and straightforward integrations.

Passkeys

Use WebAuthn and device biometrics for consumer onboarding without seed phrases.

Multisig

Require a threshold of ECDSA signatures or passkey signatures for shared control.

Multi-factor authentication

Combine different validator types, such as an ECDSA key and a passkey.

​
Managed and external signers

  • Choose an embedded wallet signer when users should sign in with email or social login and manage keys inside your app.
  • Choose an external wallet signer when users already have a browser or mobile wallet and expect to approve requests there.
A signer controls the account but is not the account itself. The signer address and smart account address are different unless you use an EOA or EIP-7702 account type.