Today is the day and it and it appears my Umbrel Bitcoin Knots needs reindexing or something to work again on the legacy chain. My Knots is acting funny and even though it says 100% Synchronized it is not showing the latest blocks. I think it may not be functional. What do we need to do to get it running right on the core network again? Someone on Youtube said drop back to a previous verions then started inputting a bunch of command prompts which wen’t right over my (and other newbies) heads. Help please!
NOTE: I just got a bitcoin knots update as I was typing this. I updated it and if anything it’s worse. Someone must have has a fix for this knowing it was coming. I’d really like to support the network by continuing to run the node but the local mempool shows the last block my node processed was 961633 and the current block according to the public mempool is 961652. I think my Knots is in limbo. It ays 100% synched and I have peers etc. Bummer.
I had to drop back to Bitcoin Knots 29.3.knots20260507 to get past the block and resync. You will also need to run reconsider block against the last block in your queue and that will allow you to resync with the public mempool.
Thanks, Chuck. I have that version but I’m not sure how to do all the steps. I’m surprised Umbrel hasn’t sent a fix or instructions or something. I’m not a code geek and really only ran umbrel and knots to support the cause so to speak. My knots choked at block 961633 on the public mempool and I have no idea what needs to be done I just don’t know how to do it. I’ve sent a support request to Umbrel but haven’t heard back yet. Perhaps they don’t work on the weekends. I appreciate the insight though. I know I have to drop back and re-index. Just need a step by step to make sure I do it right.
Thanks. Actually changing the version to the above did the trick. I didn’t have to synch or reindex. The node just started running and within a half hour or so, was fully synched up with the public block chain. No reindex or even restart necessary. Thanks for your help. Problem Solved! For now anyway.
Not that anyone asked, but I switched to knots 07 a few days ago after i thought the 110 run was done/ But then saw a couple more blocks go thru today (Aug 13) so went back to 08 knots and took my whole 15THs back to 110. If you followed a trend back to 07 version like i did earlier this week, worth your time to check a mix of opinions on both sides and see who resonates with your thoughts. Good peeps on both sides.
I had to back up to 29.3.knots20260507 as well. My node also showed up as 100% sync’d but it just did not work, you might say it “acted funny”. Whatever was going on with Bitcoin Knots v29.4.knots20260508 Electrs, Public Pool and mempool did not work for 22 hours and when I backup to 29.3.knots20260507 it did a short 14 minute sync and everything started working again. I consider v29.4.knots20260508 fundamentally broke on my Umbrel setup. The 110 features are not something that matters to me however, running the latest version and keeping my lotto miner going does matter to me.