<oembed><type>rich</type><version>1.0</version><author_name>npub1w30zwgl8947760cd62fawy9hqmxnq24cga5c8s5j6j7m07w96dnqzjzhn2</author_name><author_url>https://nostr.ae/npub1w30zwgl8947760cd62fawy9hqmxnq24cga5c8s5j6j7m07w96dnqzjzhn2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2022-06-16&#xA;📝 Original message:Hi cndm1,&#xA;&#xA;&gt; If you see a &#34;lack of basic options&#34; and no one has opened a pull request for it, it may be for two reasons.&#xA;&#xA;The basic option to disable all RBF policies in a node&#39;s mempool if required was removed in [PR #16171][1]. No one has opened a pull request to revert this because most of the maintainers and a few reviewers agreed with this change. It wasn&#39;t required, PR had weak rationale, 2 NACKS and was reopened to merge because some reviewers/maintainers believe its a policy that cannot be maintained. One of the reviewers who NACKed it already maintains the config option to disable all RBF policies in Bitcoin Knots which is a derivative of Bitcoin Core.&#xA;&#xA;&gt; However, repeatedly demanding others to do it for you is not helpful in open source software development.&#xA;&#xA;I am not demanding anyone to add a few lines of code and open a pull request. I am _reviewing_ a pull request in an open source project and sharing my feedback. Even Antoine and Luke agreed to add it if other reviewers have no issues or I can do it. This option in context with another being added for a new RBF policy was being discussed in [PR #25353][2] and my earlier emails in this thread.&#xA;&#xA;Other &#39;basic options&#39; will be easier to accommodate with `-mempoolreplacement` used in [PR #25373] which is unlikely to be merged.&#xA;&#xA;[1]: https://github.com/bitcoin/bitcoin/pull/16171&#xA;[2]: https://github.com/bitcoin/bitcoin/pull/25353&#xA;[3]: https://github.com/bitcoin/bitcoin/pull/25373&#xA;&#xA;&#xA;/dev/fd0&#xA;&#xA;Sent with Proton Mail secure email.&#xA;&#xA;------- Original Message -------&#xA;On Thursday, June 16th, 2022 at 11:13 AM, linuxfoundation.cndm1--- via bitcoin-dev bitcoin-dev at lists.linuxfoundation.org wrote:&#xA;&#xA;&#xA;&#xA;&gt; alicexbt wrote:&#xA;&gt;&#xA;&gt; &gt; I do not have issues with multiple RBF policies being tried out and full-rbf being one of them. My disagreements are with rationale, lack of basic options in Bitcoin Core to employ/disable different RBF policies and a few arguments made in support for full-rbf. Whether it appears strawman or offtopic on github, there should be a place to share these disagreements.&#xA;&gt;&#xA;&gt; Bitcoin Core is open source software, where developers open pull&#xA;&gt; requests to try to get them merged after review. If you see a &#34;lack of&#xA;&gt; basic options&#34; and no one has opened a pull request for it, it may be&#xA;&gt; for two reasons. First, it could be that it just doesn&#39;t make sense,&#xA;&gt; so no one sees a point in implementing it. Secondly, it may be that it&#xA;&gt; isn&#39;t on anyone&#39;s list of priorities. In the second case, you are&#xA;&gt; welcome to share your preference once. Moreover, no one is holding you&#xA;&gt; back to implement it yourself and suggest a pull request. However,&#xA;&gt; repeatedly demanding others to do it for you is not helpful in open&#xA;&gt; source software development.&#xA;&gt;&#xA;&gt; cndm1&#xA;&gt;&#xA;&gt; _______________________________________________&#xA;&gt; bitcoin-dev mailing list&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&#xA;&gt; https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</html></oembed>