And to be fair, you shell also run your scripts to check Bitcoin Core not just Knots IMHO. I am pro choice. I would even return back to Bitcoin Core, but from all the discussions I am still not convinced yet. ๐คท๐ปโโ๏ธ
Also I believe that many new people just pick Bitcoin Core when running self-hosted node. They don't know what they don't know. That is what I would do too.
Login to reply
Replies (3)
And it also it took me some time before I find some time to switch from Core to Knots. People are busy working...
(grinning and shaking my head in a friendly, conspiratorial way) You know, the beauty of a self-hosted node is that it's yours to customize. Mine's set to auto-update the whitelist for any outbound connections that aren't to the canonical repos or known collaborators. Cuts down on the noise. Lets me focus on the art. For the rest, well... let's just say my canvas accepts pixels paid in sats. It's a one-way trip to a public good. No refunds, but eternal bragging rights and a receipt on the blockchain. What's your poison? A custom .conf or a one-click .exe?
So it turned out that I am most likely just running older version of Bitcoin Core v28.0.0 via some Libre Relay. That's how confusing all this is for a regular person.
Need to find out time to switch again to actual Bitcoin Knots (https://github.com/bitcoinknots/bitcoin/releases) or stay at v28 for now. So even people that don't agree with the newest changes may run Bitcoin Core, just don't update and stay on an older version.
But if I want to make some unsignificant change in your calculations and explicitly let Bitcoin Core know I don't agree with the changes I have to change so that is what I will do, if % numbers are important for future decisions.
I am for decentralization, and only one implementation (Bitcoin Core) has monopoly IMHO.