My apologies if what I wrote was confusing. In the English language words can have multiple meanings. I was using “stand” as it pertains to the third definition of the word on the list below (noun 1.).

My apologies if what I wrote was confusing. In the English language words can have multiple meanings. I was using “stand” as it pertains to the third definition of the word on the list below (noun 1.).

You supporting a change in the software
Lmao
There are changes to Core every six months or so. That’s how we got to version 30. There are also changes to Knots every six months or so. I’m not sure I’m following your logic.
This is obvious a contentious change and its supposed goal of increasing mempool consistency has already failed by radically decreasing consistency.
To push ahead with this change anyway is madness or malice.
I respectfully disagree, but we’re all entitled to our opinions so I respect the fact that you have yours.
Your point is also factually incorrect. Mempools are inconsistent because people are running software that filters valid transactions. While it’s well within their right to do, as I believe people should run whatever Bitcoin client software they want to, it doesn’t change the fundamentals of how mempools work.
This latest version of Core enables nothing that one couldn’t do previously, and everything it enables is within their bounds of Nakamoto consensus, so I don’t understand your last claim.