Recovery Options (ZK Social Recovery)
Powered by Kohaku’s privacy-preserving recovery primitives
Account recovery is one of the hardest problems in self-custody. Traditional wallets force a trade-off:
Seed phrases → secure but easy to lose
Email/SMS recovery → convenient but centralized
Social recovery → useful but often privacy-leaking
Sanke takes a different approach by using zero-knowledge proofs to enable recovery without exposing your identity or your guardians.
How ZK Social Recovery Works
Kohaku introduces a recovery framework where the wallet can be restored through cryptographic proofs rather than trusted intermediaries.
A recovery request requires:
A set of pre-chosen guardians
Each guardian verifying the request locally
A zero-knowledge proof showing the required threshold approved
No guardian identity, wallet state, or approval path being revealed
The system learns only one thing: ➡️ “Enough valid guardians approved this recovery.” Nothing else.
This ensures that recovery remains:
✓ Private
Guardian addresses, approvals, or metadata never appear on-chain.
✓ Non-custodial
Guardians cannot move funds, only authorize a recovery event.
✓ Verifiable
All proofs are publicly checkable without revealing sensitive data.
When You’ll Use Recovery
Recovery options are available when:
You lose your device
You delete browser data
Your local password is forgotten
You reinstall the extension
Hardware fails or is replaced
Restoring your wallet simply requires:
Installing Sanke Wallet
Starting recovery flow
Notifying guardians
Proof is generated
Wallet is restored securely
No seed phrase exposure, no centralized servers, no recovery custodians.
Why Sanke Uses ZK Recovery
Most wallets force a trade-off between security and convenience. Sanke refuses that trade-off.
With Kohaku:
No server can “reset” your wallet
No company can restore access
No guardian is revealed or doxxed
No metadata leaks
No recovery is possible without your chosen threshold
This preserves the core principles of Web3:
self-custody, privacy, verifiability, and user sovereignty.
Last updated