Skip to main content
A session-key multisig uses an ECDSA or passkey owner set with more than one account. Set threshold to the number of signatures required: Examples on this page use @rhinestone/sdk, where rhinestone is the RhinestoneSDK instance from Create a session with a custom setup.
threshold defaults to 1. Keep it between 1 and the number of configured accounts. The SDK’s standard session-key flow invokes the configured accounts while signing the transaction. It does not support collecting independent session-key owner signatures with assembleTransaction, so a distributed approval service must expose the configured viem account signing methods to the signing process.

Use weighted quorum

Use a deployed Quorum Signer validator when owners need different voting weights:
module must be the deployed Quorum Signer validator shared by the account’s session chains. thresholdWeight is the minimum combined weight required.

Combine different validator types

Use a multi-factor session owner when approval must span ECDSA and passkey validators:
The outer threshold counts validator factors. Each factor can also have its own account threshold. Quorum validators cannot be nested as multi-factor factors, and ENS owners are not supported for session keys.
A validator threshold limits who can use the session. It does not limit what the session can do. Add permissions and policies for least privilege.