145 sats \ 8 replies \ @oomahq 9 Dec 2023 \ parent \ on: On Ocean Mining Pool, Inscriptions and Luke bitcoin
You need to educate yourself about the differences between hard consensus rules and mempool policy. The latter is 100% in the hands of every individual node runner, pool operator, and soon every miner once Stratum v2 gains traction.
As the Samourai crew likes to say, "Route around Core".
Why launch a mining pool with the promise to "decentralize mining" only to cast a shadow over your own release by disbanding policy in #Bitcoin Core that's been standard for nearly 10 years?
Like it or not, Core made 80 byte OP_RETURN part of the network protocol a decade ago and any reduction of that constitutes a breaking change. Owness on Ocean.xyz to fess up and fix it.
Luke should also apologize for tanking Ocean.xyz's launch by sucking the air out of their "decentralization" marketing with his old OP_RETURN feud with Core.
Of course he and anyone else is free to fork, but the space is also free to come to a consensus as to whether it is good and proper or malicious and destructive.
reply
That's the part you don't understand, neither is Core any sort of official Bitcoin client, nor is there such a thing as a "standard mempool policy".
The 83 (not 80) OP_RETURN limit is not part of the "network protocol" by any stretch of the imagination, full stop.
It's mempool policy, and all mempool policy can be set at will by any individual node runner, who might also be a miner or not. It's just how Bitcoin works.
I have been dropping all unconfirmed transactions containing inscriptions since February from my personal node, for instance. 100% fair game.
People are just surprised because they're getting educated about some aspect of Bitcoin they didn't understand or know about.
reply
No, Oomah, you don't understand.
You are free to fork #Bitcoin but you are not free of the consequences of that fork.
#Bitcoin is a network where participants have implicit and explicit agreements. Mempool policy is a facet of that contract, and 80 bytes indeed has been standardized over a decade.
Luke can fork #Bitcoin.
Luke can make up his own op_return value.
Luke can undermine the Ocean.xyz launch.
And he has.
reply
Of course we can. It's you who still hasn't understood that those of us who are playing with our nodes' mempool policies aren't interested in any kind of fork.
We're staying. And you'll like it. Eventually.
reply
Mempool policy is a facet of that contract
I thought that's the whole point of Sv2... to move mempool policy out of core.
reply
Exactly, that's why it's so strange to see Ocean.xyz make their entire launch about kicking off ordinals and whirlpool when it should be about miner autonomy via Sv2.
reply
make their entire launch about kicking off ordinals and whirlpool
WTF are you even saying? their "entire" launch didn't mention whirlpool at all, as far as I understand.
Ordinals has the appearance of being a spam-attack problem now.
Miner centralization is a problem now.
People with an interest in whirlpool have had all the opportunity in the world to take advantage of that utility, and presumably they'll continue to do so until everybody trivially identifies and censors those transactions out of existence.
Samo's behavior is ugly and unnecessary. OCEAN is a hugely positive development. Whirlpool isn't as necessary as they would have their audience believe.
reply
It's a startup. Sv2 is on their roadmap.
They even went live with an outdated version of Knots that didn't filter inscriptions.
reply