1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-23 00:28:14 +00:00

Edited ch09_fees.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-19 14:10:04 +00:00
parent 5286877423
commit d140423aba

View File

@ -193,7 +193,7 @@ bumping in Bitcoin, replace by fee (RBF) and child pays for parent
[[rbf]] [[rbf]]
=== Replace By Fee (RBF) Fee Bumping === Replace By Fee (RBF) Fee Bumping
To increase the fee of a transaction using RBF fee bumping, you create To((("transaction fees", "fee bumping", "RBF (replace by fee)", id="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", id="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", id="rbf"))) increase the fee of a transaction using RBF fee bumping, you create
a conflicting version of the transaction that pays a higher fee. Two a conflicting version of the transaction that pays a higher fee. Two
or more transactions are considered to be _conflicting transactions_ if or more transactions are considered to be _conflicting transactions_ if
only one of them can be included in a valid blockchain, forcing a miner only one of them can be included in a valid blockchain, forcing a miner
@ -354,7 +354,7 @@ general, if you're the receiver of an unconfirmed transaction and you
want to make it confirm faster (or at all), you can't use an RBF fee want to make it confirm faster (or at all), you can't use an RBF fee
bump; you need some other method. bump; you need some other method.
There are additional problems with RBF that we'll explore in <<transaction_pinning>>. There are additional problems ((("transaction fees", "fee bumping", "RBF (replace by fee)", startref="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", startref="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", startref="rbf")))with RBF that we'll explore in <<transaction_pinning>>.
[[cpfp]] [[cpfp]]
=== Child Pays for Parent (CPFP) Fee Bumping === Child Pays for Parent (CPFP) Fee Bumping