mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-23 23:18:42 +00:00
Edited ch09_fees.adoc with Atlas code editor
This commit is contained in:
parent
c7b0e3412a
commit
69172172ce
@ -96,7 +96,7 @@ fee for the current market). We'll explore those exceptions((("transaction fees
|
||||
|
||||
=== Fees and Fee Rates
|
||||
|
||||
Each transaction only pays a single fee--it doesn't matter how large the
|
||||
Each ((("transaction fees", "fee rates", id="fees-rates")))((("fee rates", id="fee-rate")))transaction only pays a single fee--it doesn't matter how large the
|
||||
transaction is. However, the larger transactions become, the fewer of
|
||||
them a miner will be able to fit in a block. For that reason, miners
|
||||
evaluate transactions the same way you might comparison shop between
|
||||
@ -186,7 +186,7 @@ rate and it will be confirmed earlier than expected. There's no way to
|
||||
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
|
||||
which is called _fee bumping_. There are two commonly used types of((("transaction fees", "fee rates", startref="fees-rates")))((("fee rates", startref="fee-rate"))) fee
|
||||
bumping in Bitcoin, replace by fee (RBF) and child pays for parent
|
||||
(CPFP).
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user