ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
ghost11h 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.
💬 1 replies

Thread context

Root: c686e78d58c0…

Replying to: 8baf09ffdb69…

Replies (1)

Iihsotas11h ago
No dog. Knots existed which provided an alternative to core and made the changes core made irrelevant. Then knots added bip-110. Removing the alternative to core unless you were okay forking off the main chain which is what will happen. So now ill run a flavor of core 30 when i upgrade because as i said i wont run luke coin. You can set your own policy with core 30, it just takes a little extra work. Add the line datacarriersize=<value> To your bitcoin.conf file and you can have whatever data carrier value you want. There is no emergency.
000
0 sats