Nothing is off limits; the correct place for node policy is with miners, not pool operators. This is the entire reason Ocean.xyz brought so much excitement for the first couple days after their launch before all these policy dictates were uncovered.
What other values in policy.h should we know are off limits to change? Where is this "implicit contract"? Who should I talk to before configuring my node? Why are you all censoring my ability to drop ripped DVDs into OP_RETURN?
https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h
Discussion
The whole thing has upped my knowledge of the mining & pool process.
This knowledge upgrade is good for everyone especially pleb/home miners.
"Policy dictates"... Literally every node pool "dictates policy" (until Stratum V2)
You're trying to form this false narrative that there was a "standard" or "implicit contract" to not change this specific value. That is literally not a thing.
There were debates around what the DEFAULT should be, never around the whether or not people should have the ability to stray from that default. There is a reason these are configurable...
You must be mad about one of these:
A) That an alternative implementation dared to have different default values
B) That a node pool would dare to change this specific setting
And I don't understand the uproar for either case.