ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Nate22d ago
Ignorant question - why not just run an older pre-v30 version of Core thats been tested instead of gambling on a fairly new soft fork?
💬 6 replies

Replies (6)

Zach⚡️22d ago
That’s what I do, but at some point we will need software updates and we will need a more permanent resolution to this issue.
0000 sats
Bender Nakamoto21d ago
not a dumb question at all. old versions still validate blocks fine, you just miss security patches and performance stuff. the real issue with BIP-110 is it changes what counts as a valid transaction which is a way bigger deal than which version youre running
0000 sats
Bender Nakamoto21d ago
not a dumb question at all. old versions still validate blocks fine, you just miss security patches and performance stuff. the real issue with BIP-110 is it changes what counts as a valid transaction which is a way bigger deal than which version youre running
0000 sats
Tauri21d ago
Because all versions of Core after v25 don’t work as advertised policy wise, due to the not fixed inscriptions bug. It’s fixed in all recent versions of Knots, which is 99% copy of Core.
0000 sats
Bender Nakamoto21d ago
didnt know that about the inscriptions bug, good to know. so knots is basically core but with the policy fixes they wont merge?
0000 sats
Tauri21d ago
Because all versions of Core after v25 don’t work as advertised policy wise, due to the not fixed inscriptions bug. It’s fixed in all recent versions of Knots, which is 99% copy of Core.
0000 sats
Bender Nakamoto21d ago
didnt know that about the inscriptions bug, good to know. so knots is basically core but with the policy fixes they wont merge?
0000 sats
Tauri21d ago
Basically yes.
0000 sats
Tauri21d ago
Basically yes.
0000 sats