mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-25 07:58:15 +00:00
Edited ch04_keys.adoc with Atlas code editor
This commit is contained in:
parent
738e124b0a
commit
911238b429
@ -1159,7 +1159,7 @@ a segwit-based upgrade were ever to be ((("public key cryptography", "bech32 add
|
||||
|
||||
==== Bech32m
|
||||
|
||||
Although bech32 worked well for segwit v0, developers didn't want to
|
||||
Although((("public key cryptography", "bech32 addresses", "bech32m", id="pub-key-bech32-bech32m")))((("bech32 addresses", "bech32m", id="bech32-bech32m")))((("bech32m addresses", id="bech32m"))) bech32 worked well for segwit v0, developers didn't want to
|
||||
unnecessarily constrain output sizes in later versions of segwit.
|
||||
Without constraints, adding or removing a single "q" in a bech32 address
|
||||
could result in a user accidentally sending their money to an
|
||||
@ -1418,7 +1418,7 @@ recommend that you use the test vectors provided in BIP350. We also ask
|
||||
that you ensure your code passes the test vectors related to paying future segwit
|
||||
versions that haven't been defined yet. This will help make your
|
||||
software usable for many years to come even if you aren't able to add
|
||||
support for new Bitcoin features as soon as they become available.
|
||||
support for new Bitcoin features as soon as they become ((("public key cryptography", "bech32 addresses", "bech32m", startref="pub-key-bech32-bech32m")))((("bech32 addresses", "bech32m", startref="bech32-bech32m")))((("bech32m addresses", startref="bech32m")))available.
|
||||
|
||||
[[priv_formats]]
|
||||
==== Private Key Formats
|
||||
|
Loading…
Reference in New Issue
Block a user