diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2021-12-20 10:05:44 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2021-12-20 10:06:59 +0100 |
| commit | 23afc5f47ba155ba4dda842ff24546b7d27a411a (patch) | |
| tree | 97d1cfe6999bec49dc3a22bf13f9e58b978f80ca /.tx | |
| parent | d1dc6b895fe15a77d5a941775cae6250d0fc9390 (diff) | |
| parent | 82858bab64274506cfcd365a6588a1a9141fb22c (diff) | |
Merge bitcoin/bitcoin#23711: docs: RBF policy and mempool limit exemptions
82858bab64274506cfcd365a6588a1a9141fb22c [doc] CPFP carve out and single-conflict RBF exemption (glozow)
1fd49eb498c75a1d14193bb736d195a3dc75ae12 [doc] clarify RBF difference from BIP125 (glozow)
919ae8b8cdeccfc04026293153b876e27469a027 [doc] current rbf policy (glozow)
Pull request description:
Since RBF was first implemented and BIP125 was written, our code has changed, people have highlighted implementation differences, and some people have proposed further changes to it. Many people seem to support the idea of documenting our _current_ RBF policy as it stands today.
As the ancestor/descendant limit carve-out exemptions are very related to RBF, it seemed appropriate to group them with this PR.
Related to #22806 - it seems that these policies are the most confusing for people, or at least the most documentation-requested.
ACKs for top commit:
dunxen:
ACK 82858ba
t-bast:
ACK https://github.com/bitcoin/bitcoin/pull/23711/commits/82858bab64274506cfcd365a6588a1a9141fb22c, thanks @glozow!
darosior:
re-ACK 82858bab64274506cfcd365a6588a1a9141fb22c
ariard:
ACK 82858ba
Tree-SHA512: 5d296537cce3488c18179c0aa76c739ca02fdc424e5aa17129b4cdd0d057358f86bcc1e92a9857bd2c60495f834fe9d9406d1a9f8ac5cfc8f0f4f4c27ec4f8e1
Diffstat (limited to '.tx')
0 files changed, 0 insertions, 0 deletions