1. Core's plan was always to roll out 80 byte OP_RETURN incrementally by starting with 40 to see if it broke anything and then ramping shortly up to the intended 80.
2. #Bitcoin Core, having finished that project, 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.
3. You admitted on Shitter/X that you went along with the Core team because you had your own fork where you can make any changes you'd like.
4. Now that Jack has invested in you to decentralize mining, you've cast a shadow over the launch by revolting against the implicit op_return contract in #Bitcoin Core which has been standardized by the network over the last decade.
5. Whirlpool transactions are trivial to detect and you could whitelist them no problem. This is about you kneecapping #Bitcoin fungibility while gaslighting the space about decentralization.
6. What's more centralized? The development process in bitcoin:master with a decade+ track record, ~1000 developers, and 20,000+ code reviews, or Knots, where one dude makes god commits daily, breaking critical aspects of #Bitcoin?
7. Until Ocean.xyz launches #StratumV2, you're just another gatekeeper. Ordinals ia going to run out of customers like every other shitcoin. We don't need to compromise Core just because you didn't get your way 10 years ago.
8. GFY.
Login to reply
Replies (9)
I agree with Laser. Censoring whirlpool transactions is pants over head retarded. I hate ordinals but let the shitcoin casino players run out of payday loan money.
Luke I bet knows all this and is prob so into himself he is high on his own farts.
View quoted note →
"implicit contract"... dafuq
💯🎯 @Laser
Funny. I was saying this on Shitter last year. Bitcoin fixes itself. We don’t need to interfere Luke. Just sounds more like he just doesn’t really get Bitcoin. Sorry, not sorry.
Well said! The minuscule hash rate of my 3 under-clocked space heaters will continue to point to Braiins pool.
By the way, apparently the 42 limit standard is his version, not cores. The standard he's talking about is his series of patches he has been advocating for merging to core for several years.
Not so much lying, as being zealous.
This distinction might be damage control though.
Bitcoin can't be coded itself
Set aside technical debate for a second and observe the npubs themselves. One pushes psyops ; the other is focused and speaks without trying to "one up" anyone. After noticing which is which, **_then_** consider the technicals.
1. Core's plan was always to roll out 80 byte OP_RETURN incrementally by starting with 40 to see if it broke anything and then ramping shortly up to the intended 80.
2. #Bitcoin Core, having finished that project, 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.
3. You admitted on Shitter/X that you went along with the Core team because you had your own fork where you can make any changes you'd like.
4. Now that Jack has invested in you to decentralize mining, you've cast a shadow over the launch by revolting against the implicit op_return contract in #Bitcoin Core which has been standardized by the network over the last decade.
5. Whirlpool transactions are trivial to detect and you could whitelist them no problem. This is about you kneecapping #Bitcoin fungibility while gaslighting the space about decentralization.
6. What's more centralized? The development process in bitcoin:master with a decade+ track record, ~1000 developers, and 20,000+ code reviews, or Knots, where one dude makes god commits daily, breaking critical aspects of #Bitcoin?
7. Until Ocean.xyz launches #StratumV2, you're just another gatekeeper. Ordinals ia going to run out of customers like every other shitcoin. We don't need to compromise Core just because you didn't get your way 10 years ago.
8. GFY.
View quoted note →