Nostr Web Client

#Bitcoincore drama lately what are yall’s thoughts?

My personal opinion is that Bitcoins base layer will become increasingly expensive and arbitrary data will be priced out but it’s an open protocol that individuals can choose to use however they’d like.

I think that it should be used for monetary purposes but I’m not technical enough rly weigh in on expanding OPreturn vs adding arbitrary data elsewhere.

I just don’t want any significant changes to #Bitcoin bc it works perfectly as is.

With that being said, I’ve been rooting for a hard fork so I can dump the forked coins for more real BTC.

LMK what yall think.

#asknostr

Dikaios1517 8mo ago

I don't think anyone is suggesting a hard-fork on either side of the debate.

The differences here are not consensus breaking.

This whole thing is a fight about mempool policy. Some users want to be able to restrict the size of OP_RETURN data in transactions they allow into their mempool, which has always been a part of Bitcoin's mempool policy, though the default limit has changed a few times over the years.

Some users don't want mempools to be able to reject transactions on that basis at all.

Neither of those options constitutes a consensus change. Knots nodes will continue to accept blocks created from Core mempools, and Core nodes will continue to accept blocks created from Knots mempools.

Until someone wants to run a version of Bitcoin that will reject another version's blocks as invalid, this all seems like much ado about nothing. But then... I am over here running Knots, and absolutely no one else will be affected by that unless my miners happen to get really lucky and find a block. Then all those transactions that weren't in my mempool will be forced to wait... (checks notes) ... approximately 10 minutes until another block is found by another miner.

Reply to this note

Discussion