The ECDSA signer uses the Ownable Validator module to authorise transactions with standard Ethereum key pairs. It supports both single-owner and multisig (n/m threshold) configurations on the same account.Documentation Index
Fetch the complete documentation index at: https://docs.rhinestone.dev/llms.txt
Use this file to discover all available pages before exploring further.
Single owner
To create an account owned by a single ECDSA key:Multisig
The Ownable Validator supports n/m multisig with multiple owners and a configurable signature threshold. This is useful for shared accounts, treasury management, or any scenario where unilateral control is a risk.Setup
Pass multiple accounts and set a threshold. The threshold defines how many signatures are required to authorise a transaction.threshold is 1, meaning any single owner can sign.
Signing with a subset of owners
For m-of-n setups, specify which signers to use when sending a transaction:Provide at least as many signers as the threshold requires, or the transaction will fail validation.
Add a signer
Remove a signer
Change threshold
Get current owners
Enable in a separate transaction
If you need to enable the ECDSA module on an existing account rather than at creation time:Validator versions
The SDK ships with two Ownable Validator implementations. The default is the latest version, which supports EIP-712 legible signing — wallet prompts show structured typed data instead of an opaque hash — but accepts only raw 65-byte ECDSA signatures. The legacy validator (0x2483da3a338895199e5e538530213157e931bf06) does not support EIP-712 legibility, but it accepts ERC-1271 contract signatures, so you can use a smart account (e.g., a Safe) as an owner.
To use the legacy validator, pass its address as module: