Skip to content

Commit 829f486

Browse files
committed
Added comparsion with competitors
1 parent 3d315e8 commit 829f486

2 files changed

Lines changed: 39 additions & 10 deletions

File tree

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
88

99
### Added
1010
- Benchmarks;
11+
- Comparsion with other solutions;
12+
13+
### Changed
14+
- Updated the overview;
1115

1216
## [2.0.0] - 2025-12-04
1317
### Added

docs/overview.mdx

Lines changed: 35 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,27 @@
11
---
2-
title: "What is Unforgettable Recovery?"
2+
title: "What is Unforgettable?"
33
slug: /
44
sidebar_label: Overview
55
---
66

77
import OutLink from "@site/src/components/OutLink";
88
import IdealImage from '@site/src/components/IdealImage';
99

10-
# What is Unforgettable Recovery?
10+
# What is Unforgettable?
1111

12-
**TL;DR:** Unforgettable Recovery uses account abstraction and visual keys to manage EVM wallets, so you never have to store or remember seed phrases.
12+
**TL;DR:** Unforgettable uses account abstraction and visual keys to manage EVM wallets, so you never have to store or remember seed phrases.
1313

14-
## Why Unforgettable Recovery?
14+
## Why Unforgettable?
1515

1616
- **No seed phrases:** Users authenticate leveraging visual memory (their face, a favorite object, etc.) instead of managing 12–24‑word phrases.
1717
- **Self-custodial and private:** The cryptographic secret is re-derived on the client device; only a public key and additional helping data are stored in the blockchain or on the app server. Raw biometrics or key material never leave the device.
18-
- **Multi‑factor auth:** Combine visuals (e.g., face + object) and add a short password or proof‑of‑work (PoW) step to reach the full 112‑bit security target.
18+
- **Multi‑factor auth:** Combine visuals (e.g., face + object), location and add a short password or proof‑of‑work (PoW) step to reach the full 112‑bit security target.
1919
- **Smooth onboarding:** First‑time users set up in seconds. Ideal for dApps that target mainstream audiences.
2020
- **Phishing‑resistant:** There is nothing to type or copy, eliminating most social‑engineering vectors.
2121

2222
## Tech overview
2323

24-
Unforgettable Recovery relies on a novel cryptographic primitive called **fuzzy extractors**, which convert “noisy” biometric/visual data into a stable, private key that can be reproduced from a close‑enough reading of the same object. Security is layered by combining factors (e.g., face + object) and strengthened further with a password or a proof-of-work challenge.
24+
Unforgettable relies on a novel cryptographic primitive called *fuzzy extractors*, which convert “noisy” biometric/visual data into a stable, private key that can be reproduced from a close‑enough reading of the same object. Security is layered by combining factors (e.g., face + object) and strengthened further with a password or a proof-of-work challenge.
2525

2626
### Security assumptions
2727

@@ -31,6 +31,7 @@ To achieve a 112‑bit security baseline, Unforgettable fuses ≈46 bits of en
3131
|-------------------|-----------------------|-------|
3232
| Face | ≈14-20 bits | FAR ≈ 2⁻²⁰–2⁻²¹ |
3333
| Generic object | ≈40 bits | Image distinguishing points |
34+
| Location | Up to 40 bits | 10-meter range accuracy required |
3435
| Face + object | ≈54 bits | Independent sources add up |
3536
| Password | ≈49 bits (8 chars) | ~6.12 bits per printable ASCII char |
3637
| PoW Challenge | ≈6 bits | 2⁶ space |
@@ -56,17 +57,17 @@ Once the smart-contract wallet is ready, all the user needs to do to restore acc
5657
- Make sure the annual fee was paid;
5758
- Derive the Unforgettable private key from the security challenges;
5859

59-
<IdealImage img={require('/img/recovering-wallet-flow.png')} alt="Unforgettable Recovery flow" />
60+
<IdealImage img={require('/img/recovering-wallet-flow.png')} alt="Unforgettable flow" />
6061

6162
## User flow
6263

63-
Example of Unforgettable Recovery flow is shown in the demo below:
64+
Example of Unforgettable flow is shown in the demo below:
6465

6566
<iframe
6667
width="560"
6768
height="315"
6869
src="https://www.youtube.com/embed/uZrqQsSihZE"
69-
title="YouTube Short - Unforgettable Recovery Demo"
70+
title="YouTube Short - Unforgettable Demo"
7071
frameborder="0"
7172
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
7273
allowfullscreen>
@@ -76,6 +77,30 @@ Example of Unforgettable Recovery flow is shown in the demo below:
7677

7778
The subscription is activated at setup, but the fee can be only charged when you actually invoke the recovery flow.
7879

80+
## Comparison with other wallet approaches
81+
82+
Unforgettable fits into the “smart account + just‑in‑time key derivation” category. Below is a practical comparison against common alternatives.
83+
84+
| Dimension | MPC wallet | Smart account + MPC signer | Smart account + passkeys (WebAuthn) | Unforgettable (smart account + fuzzy extractor) |
85+
|---|---|---|---|---|
86+
| **What it is** | Key is split into shares; multiple parties/devices must co-sign each transaction | Funds in a smart-contract wallet; multiple parties/devices must co-sign each transaction | Funds in a smart-contract wallet; authorization uses passkeys/WebAuthn-derived signing keys | Funds in a smart-contract wallet; signing key is derived on demand from biometrics/visual keys/location via fuzzy extractor (JIT keys) |
87+
| **Self-custody / regulatory risk** | **Medium–High** (signers can be seen as custodians) | **Medium–High** (signers can be seen as custodians) | **Low–Medium** (platform doesn’t control the key, but “soft custody” concerns may exist depending on the passkey provider model) | **Low** (user is the end key owner; platform never holds end keys/shares, only helper + policy metadata) |
88+
| **Key storage & risk** | **Medium–High**: shares stored on MPC provider infra (often in TEE). Risks: collusion, DoS | **Medium–High**: shares stored on MPC provider infra (often in TEE). Risks: collusion, DoS | **Low–Medium**: key stored on device; optionally synced. Risks: device loss/theft; ecosystem DoS/collusion if synced | **Low–Medium**: no end-key storage (JIT). Risks: spoofing attempts; platform availability/DoS |
89+
| **Recovery** | Depends on MPC providers | Depends on MPC providers | Device control (for local keys); if cloud-synced, relies on provider liveness | Relies on deterministic re-derivation; optional on-chain guardians/timelocks as safety nets |
90+
| **Cost assumptions** | Platform fee + per-signing/per-wallet costs; expensive at consumer scale | Platform fee + per-signing/per-wallet costs; expensive at consumer scale | Smart-account gas + bundler/paymaster ops; generally cheaper than MPC | Smart-account gas + bundler/paymaster ops + small helper-data storage; generally cheaper than MPC |
91+
| **Interoperability** | **High**: most dApps work out of the box | **Medium**: needs bundler/paymaster; usually per-chain deployments/modules | **Medium**: needs bundler/paymaster; usually per-chain deployments/modules | **High**: can produce standard keys/signatures and/or use smart-account policies; easier multi-chain (smart-account deployments still need bundler/paymaster infra) |
92+
| **Portability** | **Medium**: broad device/OS support, but hard to migrate | **Medium**: broad device/OS support, but hard to migrate | **Low–Medium**: often hard/impossible to switch passkey provider or attach passkeys to a different account | **Medium–High**: re-derive on any device; optional advanced export; avoids cloud lock-in |
93+
| **Sanctions / screening / abuse controls** | **High**: centralized controls (screening/limits), can increase custody-like perception | **High**: centralized controls (screening/limits), can increase custody-like perception | **Medium**: on-chain allowlists possible; depends on whether users can transact outside the app | **Medium–High**: screen at initiation; smart-account rules can enforce on-chain limits/allowlists while remaining non-custodial |
94+
95+
\* For smart-account approaches, availability/DoS risk can be reduced with extended on-chain emergency recovery functions (e.g., locktimes, guardians/social recovery).
96+
97+
Key takeaways:
98+
99+
- **MPC-based approaches** can feel seamless, but introduce higher custody/regulatory risk (signers can be viewed as custodians) and higher costs at consumer scale.
100+
- **Passkey-based smart accounts** reduce custody risk, but often trade off portability (provider/device lock-in) and can inherit ecosystem availability/DoS risks.
101+
- **Unforgettable** avoids storing end keys (keys are derived on demand) and aims for low custody risk, with optional on-chain safety nets (e.g., guardians/timelocks) where needed.
102+
103+
79104
## Conclusion
80105

81-
Unforgettable Recovery offers an alternative to seed phrases with visual keys derived via fuzzy extractors, combining factors (face + object) with a short password and a PoW challenge to reach a ≥ 112-bit security baseline without exposing biometric data. Built on account abstraction, it enables fast onboarding and straightforward recovery of EVM smart-contract wallets while remaining self-custodial, private and phishing-resistant.
106+
Unforgettable offers an alternative to seed phrases with visual keys derived via fuzzy extractors, combining factors (face + object) with a short password and a PoW challenge to reach a ≥ 112-bit security baseline without exposing biometric data. Built on account abstraction, it enables fast onboarding and straightforward recovery of EVM smart-contract wallets while remaining self-custodial, private and phishing-resistant.

0 commit comments

Comments
 (0)