sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-26 12:32:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

merge bitcoin#24310: docs / fixups from RBF and packages

Browse Source 
RBF and SegWit-specific changes have been excluded from this backport.

excludes:
- 5ae187f8761f5f85a1ef41d24f75afb7eecf366f
- d35a3cb3968d7584c7d5c42b121a80f34ea656bf
This commit is contained in:
Kittywhiskers Van Gogh 2024-12-20 11:18:31 +00:00
parent 8239d5fd0c
commit 537d3b3a14
No known key found for this signature in database
GPG Key ID: 30CD0C065E5C4AAD
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/policy/packages.md
View File

@ -47,3 +47,16 @@ test accepts):
* Packages must be child-with-unconfirmed-parents packages. This also means packages must contain at * Packages must be child-with-unconfirmed-parents packages. This also means packages must contain at
least 2 transactions. (#22674) least 2 transactions. (#22674)
* Transactions in the package that have the same txid as another transaction already in the mempool
will be removed from the package prior to submission ("deduplication").
- *Rationale*: Node operators are free to set their mempool policies however they please, nodes
may receive transactions in different orders, and malicious counterparties may try to take
advantage of policy differences to pin or delay propagation of transactions. As such, it's
possible for some package transaction(s) to already be in the mempool, and there is no need to
repeat validation for those transactions or double-count them in fees.
- *Rationale*: We want to prevent potential censorship vectors. We should not reject entire
packages because we already have one of the transactions. Also, if an attacker first broadcasts
a competing package, the honest package should still be considered for acceptance.