From e0d65f82119aa2b5f76ee39e71cb197c07875a27 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 14:28:55 +0000 Subject: [PATCH] Edited ch09_fees.adoc with Atlas code editor --- ch09_fees.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch09_fees.adoc b/ch09_fees.adoc index 45bea65a..fa7278fd 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -618,7 +618,7 @@ you intended. [[fee_sniping]] === Timelock Defense Against Fee Sniping -Fee sniping is a theoretical +Fee sniping ((("transaction fees", "fee sniping", id="transaction-fee-sniping")))((("fee sniping", id="fee-snipe")))((("timelocks", "fee sniping and", id="timelock-fee-snipe")))((("lock time", "fee sniping and", id="lock-time-fee-snipe")))is a theoretical attack scenario, where miners attempting to rewrite past blocks "snipe" higher-fee transactions from future blocks to maximize their profitability. @@ -663,5 +663,5 @@ other uses of the lock time field. As Bitcoin continues to mature, and as the subsidy continues to decline, fees become more and more important to Bitcoin users, both in their day-to-day use for getting transactions confirmed quickly and in -providing an incentive for miners to continue securing Bitcoin +providing an incentive for miners to continue securing((("transaction fees", "fee sniping", startref="transaction-fee-sniping")))((("fee sniping", startref="fee-snipe")))((("timelocks", "fee sniping and", startref="timelock-fee-snipe")))((("lock time", "fee sniping and", startref="lock-time-fee-snipe"))) Bitcoin transactions with new proof of work.