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

index cleanup

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

View File

@ -1836,7 +1836,7 @@ gives discount pricing to Eugenia.
// https://github.com/MakisChristou/vanitybech
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

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
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,
CHECKSEQUENCEVERIFY].

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
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
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).
[[rbf]]