arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-25 01:18:18 +00:00
Code Issues Releases Wiki Activity

index cleanup

Browse Source
This commit is contained in:
Clare Laylock 2023-11-02 07:08:57 -04:00
parent 552d2cd510
commit 30d48089db
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ch04_keys.adoc
View File

@ -1836,7 +1836,7 @@ gives discount pricing to Eugenia.
// https://github.com/MakisChristou/vanitybech // https://github.com/MakisChristou/vanitybech
We don't expect to see many vanity addresses in We don't expect to see many vanity addresses in
the future unless the preceding problems are((("addresses", "vanity" startref="address-vanity")))((("privacy", "vanity addresses", startref="privacy-vanity")))((("vanity addresses", startref="vanity-addr"))) solved. the future unless the preceding problems are((("addresses", "vanity", startref="address-vanity")))((("vanity addresses", startref="vanity-addr")))((("public key cryptography", "vanity addresses", startref="pub-key-vanity"))) solved.
[[paper_wallets]] [[paper_wallets]]
==== Paper Wallets ==== Paper Wallets

2
ch07_authorization-authentication.adoc
View File

@ -957,7 +957,7 @@ is, they're kept off the blockchain (_offchain_). A child transaction cannot be
parent transaction has been propagated, mined, and aged by the time parent transaction has been propagated, mined, and aged by the time
specified in the relative timelock. One application of this use case is shown in <<state_channels>> and <<lightning_network>>. specified in the relative timelock. One application of this use case is shown in <<state_channels>> and <<lightning_network>>.
+OP_CSV+ is defined((("transactions", "timelocks", "relative", startref="transaction-timelock-relative")))((("timelocks", "relative", startref="timelock-relative")))((("lock time", "relative", startref="locktime-relative")))((("scripts", "timelocks", "relative", startref="script-timelock-relative")))((("OP_CSV script opcode", startref="op-csv")))((("relative timelocks", start-ref="relative-timelock2"))) in detail in +OP_CSV+ is defined((("transactions", "timelocks", "relative", startref="transaction-timelock-relative")))((("timelocks", "relative", startref="timelock-relative")))((("lock time", "relative", startref="locktime-relative")))((("scripts", "timelocks", "relative", startref="script-timelock-relative")))((("OP_CSV script opcode", startref="op-csv")))((("relative timelocks", startref="relative-timelock2"))) in detail in
https://oreil.ly/z_Obw[BIP112, https://oreil.ly/z_Obw[BIP112,
CHECKSEQUENCEVERIFY]. CHECKSEQUENCEVERIFY].

2
ch09_fees.adoc
View File

@ -194,7 +194,7 @@ lower the fee rate on a transaction you've already sent, so you're stuck
paying a higher fee rate. But, when fee rates go up, there's a need for paying a higher fee rate. But, when fee rates go up, there's a need for
methods to be able to increase the fee rates on those transactions, methods to be able to increase the fee rates on those transactions,
which is called _fee bumping_. There are two commonly used types of fee which is called _fee bumping_. There are two commonly used types of fee
bumping in Bitcoin, replace by fee (RBF) and child pays for ((("fee rates" startref="fee-rate")))((("transaction fees", "fee rates", startref="fees-rates")))parent bumping in Bitcoin, replace by fee (RBF) and child pays for ((("fee rates", startref="fee-rate")))((("transaction fees", "fee rates", startref="fees-rates")))parent
(CPFP). (CPFP).
[[rbf]] [[rbf]]