We did the update 1.0.0:26 but now it seems stuck in syncing or it looks like ti is downloading the complete blockchain. After 4 hours still just over 50%. Is this the right way. Appears to be another lost day in trying to set up our blake miners.
Besides this waiting we have another route with the Knots 29.4.1:4 versus Datum 0.4.1:17 but in this route my goldshell poolsettings don’t get green. Soomething with the ports but I am lost in the woods by now and go for a walk wirth the dog. Any suggestions are welkom
Yes, when you switch to mainnet it must do the IBD. It is a pruned node, so it won’t use up much disk space, but it still has to verify all blocks. Note that the “companion” stack is designed to be a second (pruned) node on your same server.
The other official route (where you update your main node with Retropex’s forks) worked fine in my case. You may need to step through everything to check for issues.
The first thing I’d check is to make sure Retropex’s Bitcoin Knots service is connecting to blake2b peers and syncing the new chain properly:
Install Retropex’s Mempool app. It will show up in your services as “Mempool Guide” with a different icon than the normal one. Configure it to use electrs for the indexer.
Stop electrs and start Mempool Guide (it will show a missing dependency but it should start
Give it a couple of minutes, then launch the UI.
Wait a few minutes for the cache to start populating. Once the blocks stop animating, make sure you are seeing blake2b blocks and that it isn’t stuck at the newspaper blocks from the BIP-110 chain
If it appears to be syncing blake2b blocks, then the next thing to check is the ASIC settings. Make sure you are using the correct port from Retropex’s Datum Gateway fork (not the port from my Datum Gateway fork) Make sure if your ASIC wants to have the “stratum+tcp://” prefix in the stratum settings that you have added that (or if it doesn’t want the prefix, make sure it is not there). This is ASIC-specific, so compare to what you entered when you were using my fork and it was working, to see whether your ASIC wants the prefix or not.
