From 30d48089db5632f9e3d74a948091eadba076d45a Mon Sep 17 00:00:00 2001 From: Clare Laylock Date: Thu, 2 Nov 2023 07:08:57 -0400 Subject: [PATCH] index cleanup --- ch04_keys.adoc | 2 +- ch07_authorization-authentication.adoc | 2 +- ch09_fees.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ch04_keys.adoc b/ch04_keys.adoc index 06525502..d9cdacdd 100644 --- a/ch04_keys.adoc +++ b/ch04_keys.adoc @@ -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 diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc index a55e8b64..030b41f0 100644 --- a/ch07_authorization-authentication.adoc +++ b/ch07_authorization-authentication.adoc @@ -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 <> and <>. -+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]. diff --git a/ch09_fees.adoc b/ch09_fees.adoc index 0d43cdf4..6eedacb1 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -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]]