Damus
paulweaver34 profile picture
paulweaver34
@[email protected]
BIP-110 did not activate. The miners did not signal. Knut Svanholm wrote an honest retrospective landing on two explanations: capture, or insufficient economic weight.

Samson Mow read it and mostly agreed on the diagnosis, then made a claim I think is wrong: that nodes cannot and should not be able to influence the network.

A node that rejects an invalid block is influence. It’s the only kind that doesn’t need permission. Mempool policy failed because it depends on convention and buy-in. The supply cap has never been tested that way, because everyone already knows how that fight ends.

This piece works through where Mow is right (soft signals are cheap, that’s why thresholds are 95%), where the UASF/SegWit precedent complicates his “iatrogenic” charge, and a succession problem with Knots and Ocean that I don’t think anyone’s naming yet.

https://paulweaver34.substack.com/p/the-load-bearing-layer
61🤙1🫡1
Mischa · 5w
If the first block during mandatory signaling had been a BIP110 block, I think there was a real possibility the network would have followed it. Foundry wasn’t mining at the moment of the split, which is one reason the next block on both sides took so long. My speculation is that Foundry may initi...
Jack Spirko · 5w
"Samson Mow read it and mostly agreed on the diagnosis, then made a claim I think is wrong: that nodes cannot and should not be able to influence the network." But then cannot and that is not an opinion it is a fact. JFC have you people learned nothing?