KNOTS is safe, CORE v30 is not
Running Knots is as safe as you want it to be. Just wait 6β12 months before upgrading, verify releases, and only run versions you agree with β if Luke pushes a commit you donβt like, you simply donβt upgrade. Use Knots purely as a watch-only node, sign all transactions with Sparrow + an air-gapped hardware wallet, and your keys never touch the node. Consensus changes need the economic majority, not a single maintainer, so Knots canβt force anything on you. With this setup, Core stops being a gatekeeper β the real risk of centralization is VC influence steering Core toward Ethereum-style rollups, not one maintainer shipping an optional release.
The β1 maintainerβ fear is a myth if you run Knots this way. Consensus cannot be changed by a maintainer β rules are enforced by the economic majority, not by commits. If Luke ships code you dislike, you simply donβt upgrade. By waiting 6β12 months, verifying signatures, and using your node only for verification while keys live on an air-gapped hardware wallet, the maintainerβs role is irrelevant to your security. A solo maintainer canβt steal your coins, canβt force a fork, and canβt override your sovereignty. With this setup, the number of maintainers is noise β your own upgrade discipline is the real security model.
Plebs, can you help repost / boost this?
#bitcoin #knots
