Skip to main content
Custom signer lets you build with Rhinestone smart accounts while choosing how users authenticate and authorize actions. Bring an existing wallet provider, connect an external wallet, or manage signing directly with ECDSA keys or passkeys. The Rhinestone SDK handles account creation and transaction orchestration, while your chosen signer supplies approvals. This lets you add smart-account capabilities without replacing your existing authentication experience.

​
Separate the signer from the account

A signer authorizes actions; the smart account holds assets and executes calls. For contract accounts, these have different addresses. You can configure a single owner, require multiple signatures, or combine validator types for multi-factor authentication. Choose based on where keys should live and who must approve an action. The account implementation is a separate choice. The SDK defaults to Nexus and supports alternatives including Safe and Kernel. Account creation computes a deterministic address; deployment happens when the account first transacts on each chain.

​
Extend account behavior

Smart accounts can support more than owner-approved transactions. Session keys let you delegate actions to separate session signers, with policies defining their authority. Guardian recovery lets configured guardians replace owners if access is lost. These capabilities require explicit configuration. Your application chooses the permissions and recovery authorities, protects signing credentials, and presents or validates actions before requesting approval.

​
Get started

Follow the quickstart for a complete account-to-transaction example, then adapt the signer and account configuration to your application.