aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAva Chow <github@achow101.com>2024-03-12 12:06:45 -0400
committerAva Chow <github@achow101.com>2024-03-12 12:19:48 -0400
commit12dae637a4723577d5404786879affc7ea981a7e (patch)
tree6be80a484325cb74c0d1aade3bb048ef485394aa /doc
parentd14c7286b653ad09a5a196aa351b325f97db546b (diff)
parent1342a31f3ab61d964b9a24825bee24f53ba4e1cc (diff)
downloadbitcoin-12dae637a4723577d5404786879affc7ea981a7e.tar.xz
Merge bitcoin/bitcoin#29306: policy: enable sibling eviction for v3 transactions
1342a31f3ab61d964b9a24825bee24f53ba4e1cc [functional test] sibling eviction (glozow) 5fbab378597126eb1d0c2b2addb0859f79e508f4 [unit test] sibling not returned from SingleV3Checks if 1p2c or 3gen (glozow) 170306728aa23a4d5fcc383ddabd97f66fed5119 [policy] sibling eviction for v3 transactions (glozow) b5d15f764fed0b30c9113429163700dea907c2b1 [refactor] return pair from SingleV3Checks (glozow) Pull request description: When we receive a v3 transaction that would bust a mempool transaction's descendant limit, instead of rejecting the new tx, consider replacing the other descendant if it is much higher feerate (using existing RBF criteria to assess that it's more incentive compatible and to avoid DoS). Delving post with more background and motivation: https://delvingbitcoin.org/t/sibling-eviction-for-v3-transactions/472 ACKs for top commit: sdaftuar: ACK 1342a31f3ab61d964b9a24825bee24f53ba4e1cc achow101: ACK 1342a31f3ab61d964b9a24825bee24f53ba4e1cc instagibbs: ACK https://github.com/bitcoin/bitcoin/pull/29306/commits/1342a31f3ab61d964b9a24825bee24f53ba4e1cc Tree-SHA512: dd957d49e51db78758f566c49bddc579b72478e371275c592d3d5ba097d20de47a6c81952045021b99d82a787f5b799baf16dd0ee0e6de90ba12e21e275352be
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions