What version did you revert back to, if I may ask?
Login to reply
Replies (5)
This one. 🤙
I believe this is the newest version that is non-BIP110. There is a slightly newer one that says it doesn't have RDTS, but when I tried to install it, it would fail to initialize & told me to grab the RDTS version, so I just went 1 version back.
This one just runs:
1. Shut down your node.
2. Install "downgrade" in the same, existing Bitcoin directory.
3. Launch as normal.
It should go through block verification, then when it hits the chain split, it will throw out the conflicting blocks automatically & re-sync starting from block 961,631 so you won't have to download the whole chain again.
Takes 5 mins max. 🤙
https://bitcoinknots.org/files/29.x/29.3.knots20260210/
View quoted note →
This is the latest without #RDTS and I hope #Knots will survive as an alternative client somehow.
Unfortunately, this battle has been lost. Quo vadis bitcoin? Replicating the network effect with a fork would be almost impossible. So, is holding the status quo by running #Knots 29.3.0 20260507 (without #RDTS) the way forward in the meantime?
View quoted note →
Re-read the post you responded to. 💁♂️
That version failed out for me, wouldn't run & said I HAD to grab the RDTS version. 🤷♂️
No idea why. 🤙
Sorry, for the misunderstanding. If you previously run 20260508, you must first remove the config line "consensusrules=rdts" and then it should come up.
Ahhhh, PERFECT explanation. That makes total sense if the code flag was still in place from the prior install. 💁♂️
Thanks for the insight. 🤙