pull down to refresh

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.
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