Thread by @BitcoinErrorLog

After weeks of arguing and consideration, I am now confident I can refute all arguments for a full-RBF regime, and that we should protect first-seen mempool policy from being subverted by keeping the existing environment intact.

1/5

My arguments include clear rationale that consider miners, incentive compatibility, maximization of fees per block, priority competition, utility for merchants, intelligent doublespend risk mitigation, protection of the user space, optimal culture of development of Bitcoin,

2/5

and optimizartion of Bitcoin adoption, utility, and activity.

What I do not know is the best path to communicating these learnings to Core, and best process for civilly halting the damage of the full-RBF regime.

3/5

So, I need your help. I need to learn a best strategy for helping Bitcoin thrive and protecting the current consensus environment, for creating pull requests or documentation or specification as necessary, and ultimately how to be heard and truly considered within Core.

4/5

Please read the above and let me know any advice you have or ways that you can help.

Please share this with any relevant engineers, merchants, miners, or users that can help.

Thank you for your consideration.

5/5

@murchandamus @glozow @ziggamon @esneider