WAGMI!

Shame on you for not just recommending running Core! This fork is clearly doomed and closing channels has a real cost!

thank you

Thanks nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0xc6zuv3n9cerydpwxgenzw34xsmnzvf0qgc43j. That’s great info. Now I understand why my channel was closed last night.

Good info. Thank you!

gg, nice write up and flow diagrams

Running Bitcoin core v26.0 Don’t Tread on Me.

My start9 just stopped working, do people have issues with the fan? Strange timing for a problem as been working for years.

'To be more like money we cut off our way to be used as daily money.' Congratulatiins. You are def the biggest retards in this space.

Well, isn't the lightning on the main chain unaffected? Lightning settles to the main chain, which keeps producing ~10-minute blocks with massive hash rate behind it. A starving minority fork doesn't disrupt that.

Signal enforcement splits more than chains. What specific actions should Lightning operators take now to protect channels?

As a normal lightning node runner. Just do nothing. And nothing happens to your node or funds!

Key concept IMO: "A miner extending the enforcing branch can never be reorged off it, but if that branch stays the minority they are burning real hashrate on a slow minority ledger whose coins the economic majority may not recognize. Immunity to reorg is not immunity to loss."

Nonsense. You made it sound like the chain will split in two more or less equall halves. While in fact it is 97% vs 3%. Knot nodes will be rejecting almost all the blocks and their chain will stall. Who cares to forfeit that worthless airdrop? If the chain were in fact to split close to 50/50, movin...