Yea he doesn't have social influence. Good point.
Want to address the code I linked or just toss more quotes around?
Again... ALL NODE POOLS DICTATE POLICY. that's literally how node pools work until StratumV2.
So you aren't angry that Ocean dictates policy (since the all so). You're angry that they changed a policy setting away from the default (literally something that core is designed to allow).
"80 bytes is standard policy on the network" -Adam Back
https://nitter.net/adam3us/status/1733409334577541162?s=20
"Samourai has no obligation of any kind to 'fix', they're using network standard..." -Adam Back
https://nitter.net/adam3us/status/1733409758508367972
"Luke often is correct, but sometimes only with a non-standard definition." -Adam Back
https://nitter.net/adam3us/status/1733098596122198306
Facts are stubborn things.
I post literal code from core, you post influencer quotes. Cool. Good work nostr:npub1x458tl7h9xcxa66vr4a8pg0h2qz96pnhwnfpcra0le9090uk5t5qw7armt
Attempting to change a default setting that is designed to be changed*
Ftfy
"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.
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
Per nostr:npub1x458tl7h9xcxa66vr4a8pg0h2qz96pnhwnfpcra0le9090uk5t5qw7armt : Core… has had 80 byte OP_RETURN for nearly a decade now. 85%+ miners have been set to 80 bytes for the same amount of time. Read the commit log. Read the bitcoin-dev mailing list.
https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h
It's a configurable value with a default! Look at the code. I feel like I'm taking crazy pills.
there is no "standard". it's literally a configurable setting. there is a default in core which is 80. and there is a default in knots which is 40. in both cases the user can set whatever they like.
I assumed when you said that you don't have to "accept my changes to the design" you were referring to Knots decision to include a different default value. As if altering an intentionally configurable value is "changing the design"
https://github.com/bitcoin/bitcoin/commit/8bbe257bac751859a272ddf52dc0328c1b5a1ede
MAX_OP_RETURN_RELAY has always been a configurable node setting in Core.
You all are freaking out about an alternative implementation having a different default value for an intentionally configurable variable?
Why?
No, that is absolutely not the point people are making. They are saying that a pool operator configuring their preferred MAX_OP_RETURN_RELAY value is somehow "an attack on Bitcoin". They are acting as if this setting is an ephemeral core parameter. It's literally designed to be and intended to be configurable.
Oh you mean the configurable node setting that has always been tweakable according to the node runners preference? Ya no shit you don't have to use the same setting... This debate is insane
You're free to use it how you like. That doesn't mean the design has to accommodate your use cases.
Dude... You're arguing over a configurable default...