We built a local-first tool to break Bitcoin recovery plans before a real emergency — what are we missing?
Disclosure up front: ENTROPÍA is built by 12 Palabras, which is why I’m posting from this account. It’s free and open source; we’re not selling anything.
I kept seeing the same sentence: “I have the seed.” That answers one question, but not whether the passphrase is recoverable, wallet metadata survives, two backups share the same fire domain, the root email and password manager form a loop, or another person could follow the plan under stress.
ENTROPÍA uses aliases to map a Bitcoin wallet, devices, backup copies, email, security keys and trusted people. It then simulates phone loss, loss of the primary location, a missing security key, owner incapacity, possible seed exposure and root-email compromise. Each critical system is reported as available, blocked, unknown or compromised.
It never asks for a seed, passphrase, address, xpub or balance. The analysis runs in the browser, and an optional vault is encrypted locally.
The important limitation: it cannot prove that words written on metal are correct, that a device is genuine or that an off-site location is actually independent. A declared recovery path is not evidence; a controlled drill is.
The beta UI is currently in Spanish and the code is public: https://12palabras.github.io/
I’d genuinely like this model torn apart:
Which Bitcoin-specific failure mode is missing?
Is an aggregate summary without aliases or topology safe enough for asking for help, or would you still share nothing?
Would you use a browser-local tool for this, or only a downloadable offline build?
Please use a synthetic setup if you test it. Don’t post wallet data here.
[link] [comments]
from Bitcoin - The Currency of the Internet https://ift.tt/qATcuQ4
No comments