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 β†’

Replies (31)

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. πŸ€™
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. πŸ€™
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. πŸ€™
↑