diff --git a/author_bio.html b/author_bio.html index 48976d1c..1d612714 100644 --- a/author_bio.html +++ b/author_bio.html @@ -9,5 +9,5 @@
As a bitcoin entrepreneur, Andreas has founded a number of Bitcoin businesses and launched several community open source projects. He serves as an advisor to several bitcoin and cryptocurrency companies. He is a widely published author of articles and blog posts on bitcoin, a permanent host on the popular Let’s Talk Bitcoin podcast, and a frequent speaker at technology and security conferences worldwide.
-David A. Harding is a technical writer focused on creating documentation for open source software. He is the coauthor of the Bitcoin Optech weekly newsletter (2018–2023), 21.co Bitcoin Computer tutorials (2015–2017), and Bitcoin.org developer documentation (2014–2015). He is also a Brink.dev grant committee member (2022–2023) and former board member (2020–2022).
+David A. Harding is a technical writer focused on creating documentation for open source software. He is the coauthor of the Bitcoin Optech weekly newsletter (2018–2023), 21.co Bitcoin Computer tutorials (2015–2017), and Bitcoin.org developer documentation (2014–2015). He is also a Brink.dev grant committee member (2022–2023) and former board member (2020–2022).
diff --git a/ch03_bitcoin-core.adoc b/ch03_bitcoin-core.adoc index a20af7db..38cca2b3 100644 --- a/ch03_bitcoin-core.adoc +++ b/ch03_bitcoin-core.adoc @@ -976,7 +976,7 @@ will demonstrate accessing Bitcoin Core from another program. Bitcoin Core's API is a JSON-RPC interface. JSON is a very convenient way to present data that both humans and programs can easily read. RPC stands for remote -procedure call, which means that we are calling procedures (functions) +[.keep-together]#procedure# call, which means that we are calling procedures (functions) that are remote (on the Bitcoin Core node) via a network protocol. In this case, the network protocol is HTTP. diff --git a/ch04_keys.adoc b/ch04_keys.adoc index 5ded89ad..8c0db91a 100644 --- a/ch04_keys.adoc +++ b/ch04_keys.adoc @@ -1337,16 +1337,19 @@ digest of that function in the witness program. For P2SH, the SHA256 digest was hashed again with RIPEMD-160, but that may not be secure in some cases; for details, see <For the example of a future segwit version, we simply use the highest possible segwit version number (16) and the smallest allowed witness -program (2 bytes) with a null value. +program (2 bytes) with a null value.
+++++ Now that we know the version number and the witness program, we can convert each of them into a bech32 address. Let's use the bech32m reference diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc index 5b601f84..4909896e 100644 --- a/ch07_authorization-authentication.adoc +++ b/ch07_authorization-authentication.adoc @@ -1184,7 +1184,7 @@ account directly after he gains access to the capital account's transaction records. <