arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-04-17 23:59:09 +00:00
Code Issues Releases Wiki Activity

Merge 3c61d8e61b into 275c4eb8ea

Browse Source
This commit is contained in:
Gideon Bature 2025-01-16 14:35:02 +01:00 committed by GitHub
commit 4411b9a07b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ch04_keys.adoc
View File

@ -890,7 +890,7 @@ communicate his public key to her. Like that problem, where
public keys can be fairly large, the constraints Bob uses can also be
quite large—potentially thousands of bytes. That's not only thousands
of bytes that need to be communicated to Alice, but thousands of bytes
for which she needs to pay transaction fees every time she wants to spend money to Bob. However, the solution of using hash functions to create
for which she needs to pay transaction fees every time she wants to send money to Bob. However, the solution of using hash functions to create
small commitments to large amounts of data also applies here.
</p>
++++

2
ch05_wallets.adoc
View File

@ -218,7 +218,7 @@ network.
Public child key derivation can produce a linear sequence of keys
similar to the previously seen <<Type1_wallet>>, but modern wallet
applications use one more trick to provide a tree of keys instead a
applications use one more trick to provide a tree of keys instead of a
single sequence, as described in the((("wallets", "key generation", "public child key derivation", startref="wallet-keygen-public-child")))((("key generation", "public child key derivation", startref="keygen-public-child")))((("public child key derivation", startref="public-child-derive")))((("child key pair derivation", startref="child-key-pair"))) following section.
[[hd_wallets]]