diff --git a/README.md b/README.md index 604201f..fbfed19 100644 --- a/README.md +++ b/README.md @@ -104,6 +104,7 @@ codex32 strings. Printable forms: - [codex32 recovery card](docs/user/recovery-card.html) +- [codex32 recovery card, 256-bit](docs/user/recovery-card-256.html) - [wallet-verification record](docs/user/wallet-verification-record.html) ## For developers and reviewers diff --git a/docs/user/guide.md b/docs/user/guide.md index 7be6bcf..83fcc71 100644 --- a/docs/user/guide.md +++ b/docs/user/guide.md @@ -58,7 +58,9 @@ You will need: - Bitcoin Core 32 or newer, with its local RPC server enabled and `bitcoin-cli` available on `PATH`; - codex32 installed using the [README instructions](../../README.md#install); -- one blank [codex32 recovery card](recovery-card.html) per secret or share; and +- one blank codex32 recovery card per secret or share: the + [standard card](recovery-card.html) for 48-character backups (128-bit), or + the [256-bit card](recovery-card-256.html) for 74 characters; and - a separately stored [wallet-verification record](wallet-verification-record.html). Before running `create` for a real wallet, have your blank cards, a pen, and diff --git a/docs/user/recovery-card-256.html b/docs/user/recovery-card-256.html new file mode 100644 index 0000000..5b73eee --- /dev/null +++ b/docs/user/recovery-card-256.html @@ -0,0 +1,72 @@ + + + + + codex32 recovery card: 74 characters + + + +

codex32 recovery card: 74 characters (256-bit)

+

+ PROTECTED RECOVERY MATERIAL — keep offline. Do not photograph, upload, or enter this + text into a website, chat, or network-connected device. +

+ +

Backup details

+
+
Threshold (shares needed):
+
Four-character identifier:
+
This share index:
+
Wallet policy: single-key / multisig / other:
+
Separate wallet record location(s):
+
+ +

Protected codex32 text — copy exactly, four characters per box

+
+ + + + + +
+

The last box holds two characters. For 128-bit seeds and shares (48 characters), + use the standard card.

+ +

Offline recovery

+
    +
  1. Collect the stated threshold of cards with the same identifier and text length.
  2. +
  3. On a reviewed offline computer, install the owner’s archived codex32 release.
  4. +
  5. Run codex32 check. It validates but does not suggest corrections.
  6. +
  7. Restore the wallet using its documented Bitcoin Core recovery workflow.
  8. +
  9. Use the separate wallet record to verify the restored wallet before signing.
  10. +
+ +

Manual fallback

+

+ Keep a versioned offline copy of the Codex32 Book Recovery Wheel and Translation + Worksheet, file 2023-03-07--bw.pdf, with the owner’s recovery kit. + Expected SHA-256: 0370ea863d2eae692408aeefa9b13c14283e520f45a00f7373ad933ccf418f2e. + Follow that archived document if compatible software is unavailable. +

+ + + diff --git a/docs/user/recovery-card.html b/docs/user/recovery-card.html index 361e153..ada48b1 100644 --- a/docs/user/recovery-card.html +++ b/docs/user/recovery-card.html @@ -2,26 +2,29 @@ - codex32 recovery card + codex32 recovery card: 48 characters -

codex32 recovery card

+

codex32 recovery card: 48 characters (128-bit)

PROTECTED RECOVERY MATERIAL — keep offline. Do not photograph, upload, or enter this text into a website, chat, or network-connected device. @@ -36,18 +39,14 @@

Backup details

Separate wallet record location(s):
-

Protected codex32 text — copy exactly in four-character groups

-
- - - - - - - - +

Protected codex32 text — copy exactly, four characters per box

+
+ + +
-

Leave unused boxes blank.

+

For 256-bit seeds and shares (74 characters), use the + 256-bit card.

Offline recovery

    @@ -65,6 +64,6 @@

    Manual fallback

    Expected SHA-256: 0370ea863d2eae692408aeefa9b13c14283e520f45a00f7373ad933ccf418f2e. Follow that archived document if compatible software is unavailable.

    - +