Replying to 1525d058...

Chris, you are either intentionally mid-representing this soft fork, or you aren’t remembering what orphan blocks are.

https://www.lightspark.com/glossary/orphan-block

Reorganizing a block happens often- that’s why we have the little 6-block circle indicator in Sparrow for example. You should be waiting about 6 confirmations to consider a transaction fully settled. That isn’t “F***ing with property” that’s how Bitcoin works.

Btw, guess what Foundry, Blackrock, Coinbase, etc, think about what CoreV30 does- by default making bitcoin an anonymous permanent data storage service -to their property?

Not to mention myself and any other decent Bitcoin node runner.

The decision here isn’t about voting thankfully. You are free to reject the soft fork, pin and persist on the CSAM chain and call it “the real Bitcoin” if you like, just like the B-cashers do with their hard fork.

https://fountain.fm/episode/WOslYaeXHkGPni8BznUK

nostr:nevent1qvzqqqpxquqzpzm0ttuld48qtds5l0jkmz8r07h5jj6d8wpw5c88kfr5fcyd8dxkrsxhwm

Ok I get the soft fork bit. But I don’t follow who makes the call and scans for the material and sets everything in motion when necessary.

Reply to this note

Please Login to reply.

Discussion

Who “made the call” to implement segwit or taproot or other soft forks?

How about the inflation bug?

The rabbit hole beckons to you brother