OK, lunch! When Electrs Pruned is synced I will try again! Have a good day!
Because it hasn’t finished syncing and is still working on the SHA256 blocks (and I’d bet Knots hasn’t finished the IBD either, which was a few steps earlier in the process). Best bet:
- Stop Electrs Pruned
- Go back to the step that says “Wait for Knots (BLAKE2b) Companion to finish the IBD”, and continue with the process after the IBD finishes.
1 Like
No, Knots Companion had been running all the time so it is synced already, I re-started it today but it’as caugght up. So, it’s only the Electrs Pruned to sync (days)!!! The peculiar thing is that my rpc and username linked to my Bitcoin Knots v29.4.1.knots20260508 says it is connected: Connected to Cormorant 2.5.5 on protocol version 1.4
Batched RPC enabled.
Server Banner: Cormorant 2.5.5
/Satoshi:29.4.1/Knots:20260508/ but when I put off the settings it says NOT! Connection failed: Server Error (Announced block header at height 973181 does not meet its claimed proof of work target! (sever settings in blue, so that we can go there again!
Which Knots Companion? SHA256 or BLAKE2b?
1 Like
Maybe describe what you want your setup to be, and I’ll tell you want to change.
There are two possible setups:
- Main node is SHA256 and companion is BLAKE2b
- Main node is BLAKE2b and companion is SHA256
1 Like
" Bitcoin Knots (BLAKE2b) Companion 1.0.0:35"
of course, all the time since you updated every Companion. I am all updated on your Companions!
You explained that before. I want to mine Blake2b aka $XBT but I want to keep track of my old BTC sats via connected to my Craig Raw’s Sparrow from the past new version 2.5.5, I think now! So that I don’t lose track of the UTXOs and can move them when necessary either to the new XBT or do the Protection thing Replay! So that I accrue my old (new chain XBT) added to my newly bought XBT, which I plan to buy more of with USDC, as neaoxa.exchange accepts. I already set up my 2FA to withdraw it safely to my whatever new Sparroew (Blake2b) I use soon! I don’twnt to leave it at the NeoxEX too long; just buy and withdraw as we go along!
You are describing what you want to do. You can do that with either of the two configurations I mentioned. So I’ll just pick one for you.
- Main node is SHA256
- Companion is BLAKE2b
Do you agree? If so, we can continue with that end goal.
1 Like
Sounds good! (these guys want at least 20 characters reply! LUNCH. I am starving!
Sorry: You mean Bitcoin Knots (pre-rdts)? Bitcoin Knots (pre-RDTS) #knotsprerdts:29.3:27
Step 1: Go eat lunch
Step 2: Remove any of these apps if they are installed. If not installed, nothing to do on Step 2:
- Remove Bitcoin Knots (SHA256) Companion
- Remove Datum Gateway (SHA256) Companion
Step 3: Make sure these apps are installed. If already installed, nothing to do in Step 3:
- Install Bitcoin Knots (pre-RDTS)
- Install Bitcoin Knots (BLAKE2b) Companion
Step 4: Start these two apps. If already started, nothing to do in Step 4:
- Start Bitcoin Knots (pre-RDTS)
- Start Bitcoin Knots (BLAKE2b) Companion
Step 5: Wait for both of these apps to complete the IBD. If already completed for both, let me know and we can continue to Step 6:
- Wait for Bitcoin Knots (pre-RDTS) to complete the IBD
- Wait for Bitcoin Knots (BLAKE2b) Companion to complete the IBD
1 Like
" |[image]|Bitcoin Knots (BLAKE2b) Companion|Running|1.0.0:35|0Days
0Hours
55Minutes
5Seconds|
| — | — | — | — |
|[image]|Bitcoin Knots (pre-RDTS)|Running|#knotsprerdts:29.3:27|0Days
0Hours
55Minutes
7Seconds|"
Both already running and all updated for a long time now, only re-started fresh today!
So, Mary says LUNCH!!! Gracias. TTYL, Paul!
PS: I also meant both are synced and have been for ages!
PRE_RDTS:
"Status
*RPC *
The Bitcoin RPC Interface is ready
*Blockchain Sync *
Bitcoin is fully synced
*Index Sync *
All enabled indexes are up to date
*I2P *
Inbound and outbound connections
*Tor *
Inbound and outbound connections
*Clearnet *
Excluded by onlynet "
Bitcoin Knots (Blake2b) Companion:
" Health Checks
|Name|Status|
| — | — |
|RPC|The Bitcoin RPC Interface is ready|
|Chain|Following the BLAKE2b chain (973185)|
|Blockchain Sync|Bitcoin is fully synced|
|I2P|Inbound and outbound connections|
|Tor|Inbound and outbound connections|
|Clearnet|Outbound only. Publish an IP address to enable inbound.|
|RPC Proxy|The Bitcoin RPC Proxy is ready|
Uptime
0Days
0Hours
58Minutes
55S"
Perfect. Moving on:
Step 6: Make sure these apps are installed. If already installed, nothing to do in Step 6:
- Install Electrs Pruned
- Install Mempool Pruned
Step 7: Configure Electrs Pruned to point to the correct node:
- Actions & Config > Select Node > Bitcoin Knots (BLAKE2b) Companion
Step 8: Start Electrs Pruned
Step 9: Wait for Electrs Pruned to finish indexing.
I think this is where you are at currently (just double-check Step 7, since that will cost you time re-indexing again if it is wrong). Once the indexing is completed (probably a day or so), post back here, and we can continue. Make sure Bitcoin Knots Pre-RDTS is still running (from Step 4) since it will make the indexing go quicker (I have a little speed tweak in Electrs Pruned that indexes the common blocks before the chain split faster if there is a pre-RDTS full node running on the server)
1 Like
OK, lunch!!! LOL. Thanks a- plenty! Back ASA it’s ready. Electrs Pruned configured, fine!!!
Hey, that was Step 1!
1 Like
Howdy, Paul:
All synced, except Electrs Pruned keeps saying this:
" |Name|Status|
| — | — |
|Sync Progress|Fully synced|
|Electrum Server|Electrum server is ready and accepting connections|"
What shall we do nest? All your companions are updated but Tor on the Start9 0.4.0.1 fails to connect to the internet, so I salvaged my back up and kept the previous version, if that makes any difference!
Electrs Pruned also keeps saying:
"Status
*Sync Progress *
Electrs is not responding. It is likely busy indexing; this usually clears on its own. "
and it keeps goinfg ok and then back to the first message!
What’s going on? I kept my Electrs original for now as I don’t want to witch to Bitcoin Core from Knots (Pre-RDTS), is that ok?
Other than that, I noticed Dojo appeared in Augustr on the Start9 Registry Marketplace, but it depends on Bitcoin Core (v.31 or 32), so I keep it stoppef for now, as I am sticking to Knots (Pre-RDTS) and your Companions as well, which are all running except the Datum (Blake2b) Companion as it is not mining yet, because that’s what I wnt to learn how to get done! Please let me know where I am going wrong or right! Thanks.
PS: Also, I managed to link/connect your Sparrow (Blake2b) on the desktop with Electrs Pruned SSL onion, link though it is still alternating beteen on and off on the Start9 new version. But it did connect. Now I can create a wallet with secure entropy. For XBT.
Hi, Paul: What is happening regarding the soft-fork for Blake2b and the Knots update for it v. 29.4.2? Will you change your Balke2b Companion? How do we plebs mine now? Have a great day! We are wanting to participate on this XBT bitz.