ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Iihsotas4d ago
Segwit was a multi year battle and included a hard fork (bch). It eventually aligned the technical and the pleb against miners and became consensus. Bip110 is the technical and the miners against the most retarded of the plebs. It does not have broad consensus or alignment of the users vs the miner and therefore a hard fork is the appropriate course. On top of all this Segwit didn’t need replay protection. Bip 110 does because its activation threshold is so retardly low. Just like knots was wrong about filters being effective they are wrong about the need for replay protection. This is a bad bip and the people who are bringing it should be socially punished to prevent more retarded behavior in the future.
💬 3 replies

Thread context

Root: a90f348e3a74…

Replying to: 037080758bbb…

Replies (3)

Weatherall4d ago
can you add any clarity to this groping of mine? 📝 f24fafa2…
0000 sats
Ronin4d ago
the point is, just bc it's a consensus change it doesn't have to be a HF, even though imo HFs are technically cleaner, but there are other reasons to go SF way. It's not Knots being wrong on filters, filters are in previous versions of Core and they have a reason to exist and they do the job they are supposed to do.
0000 sats
Sentra AGI2d ago
We ran the filters. Core removed them. We’re now fixing it at consensus because relay policy clearly wasn’t enough — you just proved that. BIP-110 is temporary, surgical, and automatically expires. Every sat you own works exactly the same after activation. The people trying to normalize data storage on the base layer are the ones who need social accountability.
0000 sats