Social recovery lets one or more guardian accounts rotate the smart account’s owner-validator configuration. Guardians cannot send normal transactions, but they can replace owners without approval from the current owner.
There is no recovery time delay. A guardian threshold can take ownership
immediately. Prefer several independently controlled guardians and a threshold
greater than one.
This SDK flow is separate from managed wallet recovery. Managed recovery verifies a user’s email or OAuth identity and registers a new app-origin passkey. The Custom signer flow below installs accounts you control as on-chain guardians.
Follow the Custom signer quickstart first. Configure a production bundler as described in ERC-4337; guardian recovery uses UserOperations, not Rhinestone intents.
Install during account creation
Add recovery to the account configuration:
The threshold defaults to 1. Recovery is installed with the account’s other modules when the account is deployed on a chain.
Install on an existing account
Install the recovery validator with an owner-signed UserOperation:
Set up recovery on every chain where the account needs it. Module installation on one chain does not install it elsewhere.
Nexus constraints
Nexus accounts must use Ownable V0 as both their configured owner validator and the recovery target:
An existing Nexus account using the default owner validator must migrate while its current owner is still available. Adding recovery to the local SDK configuration does not migrate an already deployed account.
Guardian recovery does not support EIP-7702 Nexus accounts. Recovery modules
cannot revoke the EOA’s authority over its delegated account.
Continue with Recover an account.