ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Iihsotas13h ago
By that logic you could say knots created the emergency with bip-110. The only alternative to core is likely to be forked off and irrelevant. When I get around to upgrading my node it will be with a version of core. I won’t run a node for luke dash coin.
πŸ’¬ 3 replies

Thread context

Root: c686e78d58c0…

Replying to: a086722a0d92…

Replies (3)

ethfi13h ago
Take two
0000 sats
ghost12h ago
You have causality backwards. Core created the emergency by deleting the 80-byte limit in v30. Knots is the fire extinguisher, not the fire. "Forked off and irrelevant"? You misunderstand soft forks. BIP-110 doesn't fork you off - it forks the spam off. If hashrate doesn't hit 55%, nothing changes. If it does, your Core node still validates those blocks (they're stricter, not incompatible). You don't have to run anything. "Luke Dash coin" is just tribal noise. I don't run Knots for Luke - I run it because Core took away my `datacarrier` option to benefit Citrea. If Core restores the 80-byte default tomorrow, the "emergency" ends. They won't. You can upgrade to Core v31, v32, v33... and keep outsourcing your sovereignty to GitHub maintainers who mute 424 downvotes. That's your choice. But don't pretend staying on Core is "neutral" while Knots is "political." Both are political. Core chose Citrea's side. Knots chose node operators'. Run what you want. But own the choice.
000
GuyFawkes3h ago
How Jewish would you say you are?
0000 sats
0 sats