Skip to content
Plentropy
Step 6 of 6
Contents

Step 6 of 6 · 7 min

Choose a setup you can recover

Build from a defensible seed and add only the protections that address a real threat without making recovery fragile.

Canonical scientific claim: A plentiful setup uses a defensible generator and enough seed entropy, then adds only the backup, passphrase, or distributed-control measures that address the user's actual threats and remain recoverable.

Choose a trustworthy way to create the wallet, protect more than one durable backup, and add advanced parts only when you can explain and rehearse them.

Choose the level of detail

Safety note: Use the original wallet's verified documentation for any real setup or recovery. Never enter existing secrets into Plentropy, and rehearse only through trusted offline tools.

The safest-looking setup can still fail if its owner cannot recover it under stress.

Build in this order

1. Name the threats

Consider blind guessing, backup theft, physical loss, malicious devices, coercion, and the people who may need to recover the wallet later. A control that does not change one of those paths is probably decoration.

2. Start from a defensible generator

Use a well-understood wallet or signing device and its documented process. If manual entropy is part of the plan, use only a vetted device-specific method. Do not invent seed words, transform a favorite sentence, or use an online generator.

3. Accept enough entropy

A correctly generated 12-word BIP39 backup carries 128 entropy bits. A 24-word backup carries 256. Choose within the wallet’s supported process, remembering that format and generation quality matter before length.

4. Make loss survivable

Keep the required number of durable copies in independent locations. Independence matters: two cards in one envelope do not protect against the same fire or theft.

5. Preserve the recovery map

Record the wallet product or format, whether a passphrase or threshold scheme is required, and the public policy information needed to locate accounts. This metadata should help recovery without revealing the spending secret by itself.

6. Rehearse before relying on it

Verify the backup through the wallet’s trusted recovery-check procedure before receiving meaningful funds. A rehearsal should prove that the recorded material produces the expected public wallet information without exposing the secret to a general-purpose website.

Add advanced mechanisms only for named reasons

  • BIP39 passphrase: helps after mnemonic disclosure, but creates an exact additional recovery secret.
  • SLIP39: distributes recovery among threshold shares, but uses a different backup format.
  • Multisig: distributes signing authority across independent keys and devices; recovery also needs the wallet policy.
  • BIP85: derives several entropy outputs from one root; fewer root backups mean greater dependence on that root.
  • Electrum seed: follows Electrum’s own versioned format, not BIP39 merely because it uses words.
  • BIP93 codex32: promising advanced context whose BIP status remains draft.

The stopping rule

For every added component, answer three questions:

  1. Which specific failure does it reduce?
  2. Which new failure does it introduce?
  3. Can the intended recoverer still perform the complete process without memory, guesswork, or one unavailable vendor?

Stop when guessing is comfortably irrelevant and the remaining arrangement is private, durable, understandable, and rehearsable. That is plenty.

Evidence reviewed 2026-08-06

Test the tradeoffs