Why social recovery looks safer than it is
Social recovery is often presented as a friendlier alternative to a seed phrase: if the key is lost, access can be restored through preselected guardians.
The catch is that this moves part of the security model out of cryptography and into human relationships, which creates a new class of attacks — from pressure on guardians to abuse of the recovery flow itself.
What the official specs actually say
ERC-7093 describes social recovery as a scheme with guardians, thresholds, and a policy verifier, and it explicitly treats recovery security as a design concern.
IPTF notes that setup quality depends on the user’s social graph, and that the dominant risk is often social engineering against the guardian set, plus lost or compromised guardians without any on-chain warning.
- Security depends on guardian selection, not just wallet code.
- Thresholds and timelocks reduce risk but do not eliminate it.
- Weak guardian sets turn recovery into an attack target.
Where the risk comes from
This is not necessarily a smart-contract bug. More often, it is a structural weakness of the model: an attacker only needs to persuade, trick, or compromise enough guardians.
Ethereum.org also frames wallet interfaces and authentication flows as a separate attack surface, and treats recovery-related flows as sensitive security paths.
- phishing and social engineering against guardians
- compromise of email, SIM, or other accounts involved in recovery
- misconfiguration: too-low thresholds or too-homogeneous guardians
The practical takeaway
Social recovery is useful, but it is not an automatic safety net. It only works well with disciplined setup, periodic guardian review, and a clear understanding that recovery itself is attack surface.
For users, the real question is not whether a wallet has recovery. It is which people, devices, or services can unlock that recovery — and how well they are protected.
- Prefer independent guardians.
- Avoid shared communication channels and single points of failure.
- Check timelock, cancellation, and guardian-change procedures.