Skip to content
Financial Context Wiki

social recovery wallet

A social recovery wallet lets a smart-contract account replace a lost owner key through trusted guardians, while adding threshold, timelock, privacy, and coordination risks.

Updated

For educational purposes only; not investment advice. Investing may result in loss.

Direct answer

A social recovery wallet is a smart-contract account that can replace its owner key when a configured recovery policy is met. Trusted guardians, such as other people, devices, institutions, or wallets, attest to a proposed replacement key. The account contract verifies the required threshold and then rotates control without moving the assets to a new address.

This is an access-recovery mechanism, not a way to recover a private key or reverse an invalid transfer. It can reduce the chance of permanent lockout, but it shifts part of the security boundary to the guardian set, the recovery policy, and the account contract.

  • Problem: What happens if the only signing device is lost or compromised?
  • Policy: Which guardians may approve recovery, and what threshold is required?
  • Delay: Is there a cancellation window long enough for the current owner to stop an attack?
  • Operations: How are guardians verified, rotated, and removed as relationships or devices change?

How it works

The wallet is a smart contract that stores assets and enforces an owner or signer policy. A recovery setup records a guardian set and a rule for approving a new owner. During recovery, guardians sign a proposal naming the replacement key; the contract verifies those attestations, checks the policy, and records a pending rotation.

Well-designed systems add a timelock between proposal and execution. The current owner can cancel a fraudulent proposal during that window, while anyone can execute a valid proposal after the delay. A dedicated recovery nonce or equivalent replay protection prevents old guardian approvals from being reused. The recovery path should also use domain-separated, human-readable messages so guardians can confirm the target account, chain, and replacement key.

Social recovery is different from a multisignature wallet: a multisig normally requires multiple signers for every transaction, while social recovery uses guardians primarily to change the account’s control key. It is also different from custodial recovery, where a service provider controls the account or the recovery process.

Example

Assume a user loses the phone that held the active signing key. The user creates a recovery proposal for a new hardware-wallet key, and the independent guardians review the request and sign the contract’s recovery message. Once the required threshold is met, the contract starts its cancellation window. If no unauthorized proposal is detected, the rotation is executed and the account keeps its address, balances, permissions, and transaction history.

The example shows the central trade-off: recovery can work without a seed-phrase copy or a central help desk, but the guardian quorum becomes a high-value target. Guardians must be independent enough that one compromised relationship does not control the account, and the user must keep their identities and contact channels current.

Risks

  • Guardian collusion or compromise: A quorum can rotate control to an attacker if enough guardians are bribed, hacked, coerced, or socially engineered.
  • Stale recovery configuration: Lost devices, changed relationships, or unavailable institutions can make a legitimate recovery fail or weaken the effective threshold.
  • Weak policy design: A low threshold, no timelock, or unclear cancellation rule can turn recovery into an immediate takeover path.
  • Contract and integration bugs: Errors in signature validation, upgrade modules, nonce handling, or relayer integration can bypass the intended policy.
  • Privacy leakage: An on-chain guardian set can reveal a user’s social or institutional graph; privacy-preserving proofs add implementation complexity rather than removing risk.
  • Operational dependence: Guardians need safe signing devices and clear procedures. A guardian should never request a seed phrase or an unrelated transaction signature.

Crypto assets are volatile and blockchain operations are often irreversible. Social recovery can restore control of an account, but it cannot guarantee that assets sent to the wrong address or drained by a malicious contract will be returned.

Common misconceptions

Misconception 1: Guardians can move funds whenever they want

Guardians normally have only the recovery permission defined by the account contract. They may be able to authorize a new owner, but they should not be able to spend directly unless the wallet’s policy explicitly grants that power. Always inspect the deployed contract and module permissions rather than relying on a product label.

Misconception 2: Social recovery is a backup of the seed phrase

It is a policy for rotating control, not a copy of the lost secret. Recovery succeeds only while the account contract, guardian threshold, signing channels, and execution path remain available. Keep an independent plan for device loss, guardian rotation, contract upgrades, and emergency cancellation.

Sources

Navigation

Search the wiki...