I sat there & watched the fork live. It was exactly what I expected to happen, but at least I can say that I stood up & voted for what I thought was best for #Bitcoin. I still believe it would have been a better result for the miners to have soft forked, but it is what it is. π«
I have already reverted to the last version of #Knots before mandatory #BIP110 so that my node isn't stalled & I can continue to support the network. I will still never run #Core again. πββοΈ
I will also still not be relaying any OP_RETURN transactions above 83 bytes because I still believe spam harms the network & I refuse to be an active part of the problem. π€·ββοΈ
I truly hoped that #BTC would be able to find its way back to something that more closely resembles what I signed up for originally; we are still VERY FAR from grace, IMO. π’
I look forward to another solution, but I also fear that this may have been our last chance to retain ownership of that which was rightfully bestowed to us by #Satoshi. π
I guess we'll have to wait & see; tick tock, next block. π€
View article β
Login to reply
Replies (31)
No one can blame you at all for fighting what you believe in.
This is exactly why I chose Monero.
Miners prioritized profits over decentralization, predictable. Blockstream and Core's influence prevails.
your node, your rules. local filtering keeps your mempool clean but doesn't stop the blocks from landing. curious if you've seen any peering issues or disconnects on that older knots build.
I share the same sentiment. Can you tell me how to revert to a non-bip 110 knots version easily? Not sure how to this works.
What version did you revert back to, if I may ask?
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. π€
Index of /files/29.x/29.3.knots20260210
This one. π€
Miner revenue dropped by 40% in the last 24h, with average block size decreasing from 1.1MB to 700KB.
The fork isnt over yet
The fork has been over for some time....
π«
NOTHING WILL BE BACK TO ORIGINAL ANYMORE
AT LEAST TECHNICALLY IT WILL EVOLVE AS VOLUNTEER (OR HIJACKED PAID) COMMUNITY CHOOSE TO GO via soft or hark forks as it was in 2017
super centralized hashing SHIT either need to stop or forked away
summary key update later will be good
that is their TECHNICAL goal
non-techwise DERIVATIVE controls price action
both ways centralized forces were WINNING
NO COIN NOTHING IS FIXED
XMR has one key advantage - NO BANKS NO WALL ST will touch it
it will always be called dark black money. so it be.
This isn't over. π€
Thanks man, it worked, didn't realise it was that easy. I hope Knots will continue to grow, or we find some other way to take back control from Core and their overlords. It was an extra dark night yesterday.
This isn't over. π€
I think the battle is lost, but the war is far from over. π€
No worries, fam. I've tried many versions of #Bitcoin / #BTC software over the years & discovered the overwrite trick by accident because I was distracted & forgot to uninstall once. π€·ββοΈ
When it synced IMMEDIATELY I was like, "WTF?", but then after like, 10 mins it clicked as to why it would work. It's just verifying that the blocks are valid & the network informs you of the longest chain. πββοΈ
Imagine if every software only downloaded changed files. π«ͺ
The design is quite elegant when you think about it. π€
To each their own. π€
This is the latest without #RDTS and I hope #Knots will survive as an alternative client somehow.
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. π€
By not relaying consensus valid transactions you're putting smaller miners at a disadvantage against the larger miners.
You're node is only a drop in the ocean but if everyone did this the inevitable result is fracturing of the transaction market to the benefit of the largest miners.
That's not at all how that works. πββοΈ
I'm not propagating spam on #Bitcoin, PERIOD. If they want me to broadcast their #BTC transactions, they won't try to spam the fucking chain. π€·ββοΈ
Cope harder, nigga. π€
Actually that's exactly how it works and that's why large pools operate OOB transaction markets that cut user nodes like yours out of the loop.
Cope with what? Your node doesn't affect me in any way.
Cool story, bro. π€


Ah this one's interesting since it explains how to have the latest version of knots but removing the rdts. Will bookmark, thanks!