arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-12-23 23:18:42 +00:00
Code Issues Releases Wiki Activity

Edited ch09_fees.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-19 14:16:46 +00:00
parent 69d139d501
commit b153d413ac
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch09_fees.adoc
View File

@ -412,7 +412,7 @@ which is addressed by ((("transaction fees", "fee bumping", "CPFP (child pays fo
=== Package Relay
Early versions of Bitcoin Core didn't place any limits on the number of
Early versions((("transaction fees", "package relay", id="transaction-fee-package-relay")))((("package relay", id="package-relay"))) of Bitcoin Core didn't place any limits on the number of
unconfirmed transactions they stored for later relay and mining in their
mempools (see <<mempool>>). Of course, computers have physical limits, whether
it's the memory (RAM) or disk space--it's not possible for a full node
@ -445,7 +445,7 @@ making it effectively impossible to estimate an appropriate fee rate.
If a presigned transaction pays a fee rate below the amount necessary to
get into a node's mempool, there's no way to fee bump it with a child.
If that prevents the transaction from confirming in time, an honest user
might lose money. Package relay is the solution for this critical
might lose money. Package relay is the solution for this ((("transaction fees", "package relay", startref="transaction-fee-package-relay")))((("package relay", startref="package-relay")))critical
problem.
[[transaction_pinning]]