Damus
Steve ₿TC · 26w
Bitcoin is whatever node runners choose to run in open-source software, whether that’s Core, Knots, or another client. Any incompatible hardfork just creates another altcoin, no impact to Bitcoin. ...
Daire profile picture
I’m not sure it’s that simple

Knots is bitcoin core with some filters that don’t really work

Also if people run different versions of Bitcoin, it screws the lightning network

I’m not here to defend Core 30 but I don’t think we have a choice

🤷‍♂️
1❤️1
Jose Sammut · 26w
Depends on what "work" means. Not having random unencrypted data in my mempool is already working. Not relaying that data is already working. If it's returned to me in a confirmed state by miners, then the responsibility of that confirmation lies with them. Law enforcement / society will target the...
Jose Sammut · 26w
The easiest choise is Core 29, if you're not onboard with knots, and don't have a use case for a larger op return. Since I understand datacarriersize is essentially depricated now.
Steve ₿TC · 26w
Different implementations are non-partisan and perfectly fine as long as consensus rules match. Like you said, Knots is basically Core with extra relay options, and for Core/Knots team to deviate into hard-fork territory would be an insane move, and bad for Lightning. The good thing about Bitcoin ...