forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
, bitcoin#23804, bitcoin#24310, bitcoin#24537, bitcoin#24582, bitcoin#24404, bitcoin#25013, bitcoin#25029, bitcoin#25254, bitcoin#25388 (mempool backports) 578be36 merge bitcoin#25388: move policy constants to policy (Kittywhiskers Van Gogh) aca2c0d merge bitcoin#25254: Move minRelayTxFee to policy/settings (Kittywhiskers Van Gogh) 1d82dd8 merge bitcoin#25029: Move fee estimation RPCs to separate file (Kittywhiskers Van Gogh) ad94a30 merge bitcoin#25013: Remove cs_main from verifymessage, move msg utils to new file (Kittywhiskers Van Gogh) 8e42b12 merge bitcoin#24404: Remove confusing P1008R1 violation in ATMPArgs (Kittywhiskers Van Gogh) 006370d merge bitcoin#24582: Move txoutproof RPCs to txoutproof.cpp (Kittywhiskers Van Gogh) dfa4772 merge bitcoin#24537: Split mempool RPCs from blockchain.cpp (Kittywhiskers Van Gogh) 537d3b3 merge bitcoin#24310: docs / fixups from RBF and packages (Kittywhiskers Van Gogh) 8239d5f merge bitcoin#23804: followups for de-duplication of packages (Kittywhiskers Van Gogh) 71b2623 merge bitcoin#22674: mempool validation and submission for packages of 1 child + parents (Kittywhiskers Van Gogh) 8392d23 merge bitcoin#23381: refactoring for package submission (Kittywhiskers Van Gogh) d3c0059 merge bitcoin#22689: deprecate top-level fee fields in getmempool RPCs (Kittywhiskers Van Gogh) Pull request description: ## Additional Information * [bitcoin#23694](bitcoin#23694) (backported in [dash#6256](#6256)) was backported before [bitcoin#22689](bitcoin#22689) and therefore, the formatting changes in the former were not incorporated in the backport. This has been resolved by accommodating them in the latter. * The fields deprecated in [bitcoin#22689](bitcoin#22689) were originally deprecated in [bitcoin#12240](bitcoin#12240) but not gated behind runtime arguments, the backport does so. * This pull request includes multiple backports that include code specific to RBF (BIP 125) and SegWit, which have been removed due to Dash Core not supporting them, comments and documentation (like `doc/policy/packages.md`) have been amended to reflect this accordingly. * When backporting [bitcoin#22674](bitcoin#22674), a new constructor was introduced for submitting `MEMPOOL_ENTRY` `ResultType`, upstream this can be done trivially as it uses function overloading ([source](https://github.com/bitcoin/bitcoin/pull/22674/files#diff-d3c243938494b10666b44404a27af7d84b44a72b85a27431e0c89e181462ca6eR198-R204)) but as Dash Core doesn't accept `replaced_txns`, there is no opportunity to differentiate arguments. * This was resolved by accepting `ResultType` as an argument but always passing `MEMPOOL_ENTRY` as the argument ([source](71b2623#diff-d3c243938494b10666b44404a27af7d84b44a72b85a27431e0c89e181462ca6eR232-R242)) * Unit tests like `package_witness_swap_tests` (introduced in [bitcoin#23804](bitcoin#23804)) have been omitted due to functionality tested not being implemented in Dash Core. Subsequent backports that include modifications to these tests have mirrored similar omissions. ## Breaking Changes * The top-level fee fields `fee`, `modifiedfee`, `ancestorfees` and `descendantfees` returned by RPCs `getmempoolentry`,`getrawmempool(verbose=true)`, `getmempoolancestors(verbose=true)` and `getmempooldescendants(verbose=true)` are deprecated and will be removed in the next major version (use `-deprecated=fees` if needed in this version). The same fee fields can be accessed through the `fees` object in the result. **WARNING: deprecated fields `ancestorfees` and `descendantfees` are denominated in sats, whereas all fields in the `fees` object are denominated in DASH.** ## Checklist - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have added or updated relevant unit/integration/functional/e2e tests - [x] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ ACKs for top commit: UdjinM6: utACK 578be36 PastaPastaPasta: utACK 578be36 Tree-SHA512: 38a62ec826f91c349269373463dd47f662cdc14dbb3c82cb5c56e779f22a2623fdce055018f15bcf6b5da029312dbcce0925545650c0eae8e3f5177812b68321
- Loading branch information
Showing
43 changed files
with
2,055 additions
and
1,151 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# Transaction Relay Policy | ||
|
||
Policy is a set of validation rules, in addition to consensus, enforced for unconfirmed | ||
transactions. | ||
|
||
This documentation is not an exhaustive list of all policy rules. | ||
|
||
- [Packages](packages.md) | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
# Package Mempool Accept | ||
|
||
## Definitions | ||
|
||
A **package** is an ordered list of transactions, representable by a connected Directed Acyclic | ||
Graph (a directed edge exists between a transaction that spends the output of another transaction). | ||
|
||
For every transaction `t` in a **topologically sorted** package, if any of its parents are present | ||
in the package, they appear somewhere in the list before `t`. | ||
|
||
A **child-with-unconfirmed-parents** package is a topologically sorted package that consists of | ||
exactly one child and all of its unconfirmed parents (no other transactions may be present). | ||
The last transaction in the package is the child, and its package can be canonically defined based | ||
on the current state: each of its inputs must be available in the UTXO set as of the current chain | ||
tip or some preceding transaction in the package. | ||
|
||
## Package Mempool Acceptance Rules | ||
|
||
The following rules are enforced for all packages: | ||
|
||
* Packages cannot exceed `MAX_PACKAGE_COUNT=25` count and `MAX_PACKAGE_SIZE=101KvB` total size | ||
(#20833) | ||
|
||
- *Rationale*: This is already enforced as mempool ancestor/descendant limits. If | ||
transactions in a package are all related, exceeding this limit would mean that the package | ||
can either be split up or it wouldn't pass individual mempool policy. | ||
|
||
- Note that, if these mempool limits change, package limits should be reconsidered. Users may | ||
also configure their mempool limits differently. | ||
|
||
* Packages must be topologically sorted. (#20833) | ||
|
||
* Packages cannot have conflicting transactions, i.e. no two transactions in a package can spend | ||
the same inputs. Packages cannot have duplicate transactions. (#20833) | ||
|
||
* No transaction in a package can conflict with a mempool transaction. | ||
|
||
* When packages are evaluated against ancestor/descendant limits, the union of all transactions' | ||
descendants and ancestors is considered. (#21800) | ||
|
||
- *Rationale*: This is essentially a "worst case" heuristic intended for packages that are | ||
heavily connected, i.e. some transaction in the package is the ancestor or descendant of all | ||
the other transactions. | ||
|
||
The following rules are only enforced for packages to be submitted to the mempool (not enforced for | ||
test accepts): | ||
|
||
* Packages must be child-with-unconfirmed-parents packages. This also means packages must contain at | ||
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
Updated RPCs | ||
------------ | ||
|
||
- The top-level fee fields `fee`, `modifiedfee`, `ancestorfees` and `descendantfees` | ||
returned by RPCs `getmempoolentry`,`getrawmempool(verbose=true)`, | ||
`getmempoolancestors(verbose=true)` and `getmempooldescendants(verbose=true)` | ||
are deprecated and will be removed in the next major version (use | ||
`-deprecated=fees` if needed in this version). The same fee fields can be accessed | ||
through the `fees` object in the result. WARNING: deprecated | ||
fields `ancestorfees` and `descendantfees` are denominated in sats, whereas all | ||
fields in the `fees` object are denominated in DASH. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.