It is not. Configuration is HOW you know what consensus is.
Example:
If I give you the Option to choose between the colors red, white, and blue.
Then 20% choose white
10% choose blue
70% choose red
The overwhelming consensus is that red is the prominent color. But that doesn't mean you'll NEVER see blue or white.
But if I say:
"Here is your option, the color red."
You will never see blue or white no matter what people prefer.
Removing configuration is removing choice.
Configuration is not consensus. I can config whatever I want and consensus valid txs will still be in my bloclchain data and UTXO set
You are misunderstanding consensus in this context. Consensus is not something that will "still be in my blockchain data and utxo set" the nodes dictate valid. Miners offer candidates based on the CONSENSUS of the nodes they pull the previous transaction blocks from. Which is determined by the CONFIGURED ruleset.
I speak of technical context, the only one that matters for creating a timechain entry.
Also, miners get tx'snout of band all the time, you cannot prevent that and long term incentives will only increase private mempool usage. MARA's slipstream offers whatbstarted at TG DM's as a service with a UI.
If spammers pay the fee, spammers get in the block. This is economic reality. Policy or configuration changes won't change this incentive. It's called censorship resistance.
if every node policy is useless why do they exist?
Legacy script problems from what I can tell. Or
Otherwise we deduce it from code and comments.
"Standardness rules exist for three main reasons. The first is as DoS protection. Your peers on the P2P network are not identified and some transactions are more expensive than others to process. An asymmetry between the cost of sending you an unconfirmed transaction (which is very small) and the cost for you to process it creates a DoS vector. Another reason for standardness rules is to provide upgrade hooks for soft forks. Invalidating a type of transactions in a soft fork that was already non-standard for a while gives more guarantees that a non-upgraded miner won’t include a newly-invalid transaction in a block, making soft forks significantly safer to roll out. Finally, standardness rules have also been used as a way to nudge behaviour toward a less harmful approach, or to mildly deter certain activities. For instance by standardizing OP_RETURN outputs, or discouraging data storage back when blocks were not full."
Obviously you aren't reading what I write so, good luck with your spam. I will run the code I want to with filters.
And your UTXO set will continue to bloat as spammers fill the chain. Won't be me spamming but it will bloat nonetheless.
