1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-15 20:49:21 +00:00

Edited ch05_wallets.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-18 15:53:29 +00:00
parent 897892c54d
commit e28d7381cf

View File

@ -273,7 +273,7 @@ Several different types of recovery codes are in wide use as of this
writing:
BIP39::
The most popular method for generating recovery codes for the
The most ((("BIP39 recovery codes")))popular method for generating recovery codes for the
past decade, BIP39 involves generating a random sequence of bytes,
adding a checksum to it, and encoding the data into a series of 12 to
24 words (which may be localized to a user's native language). The
@ -282,7 +282,7 @@ BIP39::
several shortcomings, which later schemes attempt to address.
Electrum v2::
Used in the Electrum wallet (version 2.0 and above), this word-based
Used in((("Electrum v2 recovery codes"))) the Electrum wallet (version 2.0 and above), this word-based
recovery code has several advantages over BIP39. It doesn't rely on a
global word list that must be implemented by every version of every
compatible program, plus its recovery codes include a version number that
@ -291,7 +291,7 @@ Electrum v2::
key-stretching function.
Aezeed::
Used in the LND wallet, this is another word-based recovery code that
Used in ((("Aezeed recovery codes")))the LND wallet, this is another word-based recovery code that
offers improvements over BIP39. It includes two version numbers: one
is internal and eliminates several issues with upgrading wallet
applications (like Electrum v2's version number); the other version
@ -310,7 +310,7 @@ Aezeed::
word list.
Muun::
Used in the Muun wallet, which defaults to requiring spending
Used in ((("Muun recovery codes")))the Muun wallet, which defaults to requiring spending
transactions be signed by multiple keys, this is a nonword code that
must be accompanied by additional information (which Muun currently
provides in a PDF). This recovery code is unrelated to the seed and
@ -321,7 +321,7 @@ Muun::
Lightning Network support, output script descriptors, and miniscript.
SLIP39::
A successor to BIP39 with some of the same authors, SLIP39 allows
A successor ((("SLIP39 recovery codes")))to BIP39 with some of the same authors, SLIP39 allows
a single seed to be distributed using multiple recovery codes that can
be stored in different places (or by different people). When you
create the recovery codes, you can specify how many will be required
@ -332,7 +332,7 @@ SLIP39::
[NOTE]
====
A new system for distributing recovery codes with similarities to SLIP39
A new system((("Codex32 recovery codes"))) for distributing recovery codes with similarities to SLIP39
was proposed during the writing of this book. Codex32 allows creating
and validating recovery codes with nothing except printed instructions,
scissors, a precision knife, brass fasteners, and a pen--plus privacy