Beware anyone who tells you there’s an emergency situation and bitcoin needs an immediate fork. This isn’t the value overflow incident of 2010. There is absolutely no crisis.

Reply to this note

Please Login to reply.

Discussion

Lmao wow.

"soft fork with a chain split" um.... pretty sure that makes it a hard fork

Kratter has lost all credibility with me. #trainwreck

Yeah, Krapper is a bad actor.

He seems insistent on being just that.

They can fork off

Sick pedophile. People will learn the truth about you eventually.

I’m wary of anyone urging you to rush into action out of fear.

When everyone is a CSAM distributor, nobody is.

Will anybody tell me what the benefit is to increasing op return limit

It removes the incentive to embed arbitrary data in the most damaging ways.

Thank you

And also reduces mining centralization since it eliminates the premium some miners charged for getting around the previous op return limit

The only crisis is that there a lot of "Bitcoiners" out there who don't understand immutability and are actively attacking Bitcoin motivated by a purely theoretical moral panic.

nostr:nprofile1qy8hwumn8ghj7mn2w4khqtndv5hszythwden5te0dehhxarj9ekxzmny9uqzpprrqa5g5z0vzy5k06c9gnnc485gcj84qufv88k5j8ljkmaqrxhgkgzyc0 really should know better.

a fool additected to money is still a fool

Didnt the value overflow create more bitcoin? Only ever be 21.5 million btc

Yes! It accidentally produced 184.4 billion BTC across two outputs. The bug was patched in a few hours and the blocks were reorganized to remove the transaction history.

https://en.bitcoin.it/wiki/Value_overflow_incident

At this point I don't really like Core or Knots. I don't want excessive arbitrary data on chain, but I also don't like the doomsday alarmists who think they're gametheory experts at outsmarting states/corpos (who are already buying in to Bitcoin).

If you just think about it rationally for even 10 seconds you’ll come to the conclusion that you can’t stop people from embedding data on-chain, so the best path forward is option that does the least harm, and that’s what Core 30 provides.

I've never found a clear answer as to what fringe edge-case Core 30 fixes by greatly increasing the OP_RETURN filter. Of course, you can't stop people from embedding data on chain. However, I don't think the answer is to make it much much easier to do so (unless there is an explanation that has escaped me).

Op_return data is prunable. Utxo bloat is far worse for low powered nodes. The technical challenges of spamming the chain with a bunch of small op return vs one large one is minimal therefore a limitation op return is also pointless.

what is this all about?

A crisis is unavoidable, this dorks are hiding something.

If you want to eliminate CSAM feel free to run the node implementation of your choice.

These*

This guy lost the plot completely. Core v30 is shit but so is Knots. No need to rush anything