Test webhook on PR #33
Draft
Conversation
This file contains hidden or 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
Effectively this is treating all transactions in txgraph as being in a cluster of size 1.
Preparatory commit to the rbf functional test, before changes are made to the rbf rules as part of cluster mempool.
Include an adjustment to mempool_tests.cpp due to the additional memory used by txgraph. Includes a temporary change to the mempool_ephemeral_dust.py functional test, due to validation checks being reordered. This change will revert once the RBF rules are changed in a later commit.
Rather than evicting the transactions with the lowest descendant feerate, instead evict transactions that have the lowest chunk feerate. Once mining is implemented based on choosing transactions with highest chunk feerate (see next commit), mining and eviction will be opposites, so that we will evict the transactions that would be mined last.
The addition of a cluster size limit makes the CPFP carveout rule useless, because carveout cannot be used to bypass the cluster size limit. Remove this policy rule and update tests to no longer rely on the behavior.
With a total ordering on mempool transactions, we are now able to calculate a transaction's mining score at all times. Use this to improve the RBF logic: - we no longer enforce a "no new unconfirmed parents" rule - we now require that the mempool's feerate diagram must improve in order to accept a replacement - the topology restrictions for conflicts in the package rbf setting have been eliminated Revert the temporary change to mempool_ephemeral_dust.py that were previously made due to RBF validation checks being reordered. Co-authored-by: Gregory Sanders <[email protected]>, glozow <[email protected]>
Previously, transaction batches were first sorted by ancestor count and then feerate, to ensure transactions are announced in a topologically valid order, while prioritizing higher feerate transactions. Ancestor count is a crude topological sort criteria, so replace this with linearization order so that the highest feerate transactions (as would be observed by the mining algorithm) are relayed before lower feerate ones, in a topologically valid way. This also fixes a test that only worked due to the ancestor-count-based sort order.
The mempool clusters and linearization permit sorting the mempool topologically without making use of ancestor counts (as long as the graph is not oversized). Co-authored-by: Pieter Wuille <[email protected]>
In preparation for removing ancestor data from CTxMemPoolEntry, recalculate the ancestor statistics on demand wherever needed.
The cluster limits should be sufficient. Co-Authored-By: Gregory Sanders <[email protected]>
Remove a reference to GetCountWithDescendants() in preparation for removing this function and the associated cached state from the mempool.
Repository owner
deleted a comment from
guix-builder
Oct 15, 2025
|
Guix build:
Hashes: |
Repository owner
deleted a comment from
guix-builder
Oct 15, 2025
Repository owner
deleted a comment from
guix-builder
Oct 15, 2025
Repository owner
deleted a comment from
guix-builder
Oct 15, 2025
github-actions
bot
force-pushed
the
master
branch
3 times, most recently
from
97ed557 to
e472e80
Compare
willcl-ark
force-pushed
the
master
branch
2 times, most recently
from
3108440 to
2370337
Compare
github-actions
bot
force-pushed
the
master
branch
2 times, most recently
from
a5d742e to
acc041c
Compare
willcl-ark
force-pushed
the
master
branch
2 times, most recently
from
37a6a6d to
4cdce02
Compare
github-actions
bot
force-pushed
the
master
branch
4 times, most recently
from
6a31544 to
acff675
Compare
willcl-ark
force-pushed
the
master
branch
9 times, most recently
from
ed138e2 to
2ccfcf2
Compare
willcl-ark
force-pushed
the
master
branch
3 times, most recently
from
425aeb2 to
9827b14
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test webhook on a pr