Skip to main content
Choose multisig when one account needs several owners of the same signer type. Use it for shared control, treasury approvals, or a passkey-per-device setup.
  • A 1-of-n threshold lets any configured owner sign.
  • An m-of-n threshold requires at least m owners to sign.
Use multi-factor authentication instead when you need different validator types in one approval policy.
This threshold flow is EVM-only. A managed Solana Swig uses one configured viem secp256k1 or WebAuthn signer per handle. Multiple authority roles are independent permissions, not an m-of-n multisig, and Solana does not support this independent-owner assembly flow. See Solana support.

Configure the owner set

Pass every owner and the required threshold when you create the account.
The threshold defaults to one. Keep the complete owner set and threshold when reconstructing the account.

Select co-located signers

When the required keys are available in one environment, select them while preparing the transaction. This example executes calls without token delivery and requires configured gas sponsorship:
For passkeys, use kind: 'passkey' and provide the selected passkey accounts.

Collect signatures separately

When owners sign in different environments, prepare once, collect each contribution, and assemble them:
Every owner must sign the same prepared transaction. Transport the complete prepared artifact and returned owner contributions unchanged with a transport that preserves bigint values. Treat contributions as opaque; do not reconstruct their fields. Collect enough distinct owner signatures to meet the configured threshold; duplicate owners are rejected.

Manage the owner set

Use the ECDSA actions or passkey actions to add and remove owners or change the threshold after deployment.