Gloria Zhao
Gloria Zhao
We have pretty thorough documentation of our RBF policy in doc/policy/mempool-replacements.md. It enumerates each rule with several sentences of rationale. Also, each rule pretty much has its own function (3...
Part of #22290. In addition to allowing a child to pay for its parents within the package, also allow the child to pay for replacing the parent's conflicts. In particular,...
Please leave concept/approach feedback on the [mailing list thread](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020493.html) so that people can follow the discussion in one place. Feel free to leave a review comment if you find typos...
ML thread: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020493.html Supersedes #1324.
Opening as an alternative to #26933, as suggested in https://github.com/bitcoin/bitcoin/pull/26933#issuecomment-1412320818. Though they don't need to be mutually exclusive, e.g. we could both require individual transactions to meet minrelayfeerate and also...
This is part of #25038, which relaxes this for v3 transactions. Note that this still allows packages to bump transactions that are below the dynamic mempool minimum feerate, which means...
See #27463 for full project tracking. Please see #27742 for how this PR fits into the big picture. This PR is based on a more recent commit than that one....
This enables 1p1c packages to propagate in the "happy case" (i.e. not reliable if adversaries are actively attacking) and contains a lot of package relay-related code. See https://github.com/bitcoin/bitcoin/issues/27463 for overall...
See #27463 for overall package relay tracking. Delving Bitcoin discussion thread: https://delvingbitcoin.org/t/v3-transaction-policy-for-anti-pinning/340 Rationale: - There are various pinning problems with RBF and our general ancestor/descendant limits. These policies help mitigate...