How do I connect Paul’s Sparrow (Blake2b) to my newly Up to Date Bitcoin v29.4.1.knots20260508? This is running on my Windows 10 desktop PC but I wnt to link it to Start9’s v. 0.4.0.1 Electrs or Fulcrum but since Electrs is now cocked up (I am still running the previous one, not updated it yet) because of Pre-RDTS Knots, as Luke doesn’t maintain it, should I use Elecrts Pruned (Paul’s) or will it not catch the old Txs?
Thanks, Paul, if you could be so kind as to enlightne us on that!
Rui
What are the current arrangment of apps you have installed on your server related to Bitcoin?
I’m in the process of building a 31.1 version of Bitcoin Knots. Still working out the exact process of transmogrifying from Bitcoin Core like Luke was doing (there is a lot of merge conflict resolution work get right), so I didn’t get it completed yesterday. Continuing work on it today and will keep you posted.
2 Likes
Paul, thanks for your help. Please carry on, we will get your new 31.1 Knots. How can I share my screenshots with you here or anywhere else, by email maybe? I can’t find the way to include the screenshot here for my Start9 apps/services. But I have all you suggested and the SHA256 companion and the pre-rdts which I am running, Electrs and Electrs Pruned, Datum (both yours and the Start9 original, etc,)!
I tried everything to connect your Sparrow (Blake2b) fork of Sparrow but to no avail! No RPC user name and Password either no SSL nor TCP interface links to Electrs, Electrs Pruned, Fulcrum, NADA! It doesn’t connect! Pity because now I need a new wallet for XBT which I bought a week ago and I need to buy more. Please let me know how I can work this one out on my desktop (Windows 10 PC) which has not synced nicely totally updated the IBD to the latest v. of KNOTS 24.3.1. Many thanks and have a restful Sunday if possible, and don’t work more than enough! Sometimes I feel like giving up and I still want to mine XBT on Start9. Don’t know how, don’t know when! <<<— old song!
BTW, electrs is not compatible with the BLAKE2b chain (only my fork is). If you want a BLAKE2b indexer for your main node, you need to switch to Fulcrum (BLAKE2b) from the mempool.guide Start9 registry.
1 Like
OK, so if I “switch” to mempool.guide’s Fulcrum (Blake2b) version will I lose my connection to the original Sparrow that is going via Electrs (original on start9), which I have not updated yet to the new version 0.12.0:0?
Ok, re-reading your comment, your setup is just wrong. Ignore my last comment (I deleted it)
- You said you have Knots Pre-RDTS installed (this is SHA256)
- You said you have Knots (SHA256) Companion installed (this is also SHA256)
You have no BLAKE2b node running, so you cannot connect a BLAKE2b wallet.
1 Like
I had my SHA256 Companion stopped, when you suggested it shouldn’t be running.
So, how do I get a Blake2b node running? Shall I run Bitcoin Knots (SHA256) Companion #knotsprerdts:29.3:31?
OK, so I shall do that now! Hopefully my original Sparrow is still linked to my Electrs (jpeg chain)!
HOWEVER: Quote " Warning
As a result of this update, the following services will no longer work properly and may crash:
- Mempool
- Mempool BIP-110" is the BIP-110 mempool not needed?
But, how come my Shrike Sparrow is linked to my Electrs? It works for both chains?
If you want a BLAKE2b node as your companion node (which will leave your main node on SHA256)
- Uninstall Knots (SHA256) Companion
- Uninstall Datum (SHA256) Companion if installed
- Stop Electrs Pruned
- Stop Mempool Pruned
- Install Knots (BLAKE2b) Companion
- Install Datum (BLAKE2b) Companion (optional)
- Wait for Knots (BLAKE2b) Companion to finish the IBD
- Configure Electrs Pruned
–Actions & Config > Select Node > Knots (BLAKE2b) Companion - Start Electrs Pruned
- Wait for Electrs Pruned to finish indexing
- Configure Mempool Pruned
–Actions & Config > Select Node > Knots (BLAKE2b) Companion
–Actions & Config > Select Indexer > Electrs Pruned - Add an Onion Service to Electrs Pruned (if not already)
–Interfaces > Electrum SSL > Tor > Add onion service - Connect Shrike or Sparrow BLAKE2b to the onion service URL
If Shrike is connecting to electrs that you have pointed to a SHA256 node, then that is a bug in Shrike’s code which will lead to issues if you use it. It isn’t designed for SHA256.
1 Like
More amazing; These Start9ers now screwed TOR:
"Health Checks
|Name|Status|
| — | — |
|Tor SOCKS Proxy|Tor is running|
|Relay Reachability|Testing whether the relay is reachable from the internet|"
New update that is still checking forever!
OK, thanks again! THis is a job for after lunch, as it it lunchtime and I haven’t had breakfast yet (skinny guy). Most of these you list are ready, so I can give you a run down later. I had Bitcoin Knots (SHA256) Companion #knotsprerdts:29.3:31 stopped anyway; does it need uninstalling? I still want to check my old chain? Now it was out of sync for the IBD, so I stopped it again!
Did you mean Datum Gateway to unistall? I never had it’s Companion for 256.
Knots (SHA256) Companion must be uninstalled if you are installing Knots (BLAKE2b) Companion (currently only one complete companion stack is supported). Technically you could run both and be careful about where the Electrs Pruned and Mempool Pruned services are pointed at, but given the confusion with your setup so far, I would keep it as simple as possible (which is already complicated enough)
No, I mean Datum Gateway (SHA256) Companion specifically. If it isn’t installed, then don’t do anything for that step, and skip the installing Datum Gateway (BLAKE2b) Companion step if you aren’t planning to mine on BLAKE2b.
Health Checks
|Name|Status|
| — | — |
|Sync Progress|Electrs is building its address index: 0.3%, block 2,890 of 973,178. This can take several hours on first run.|
|Electrum Server|Electrum server is ready and accepting connections|
Follow the steps exactly (including the ones that say to wait for something to complete)
1 Like
Done but Electrs is syncing for a while, so this is waht I get on your Sparrow (Blake2b): "Could not connect:
The server is following a chain that has not changed its proof of work. This build follows the BLAKE2b chain, which on mainnet forked at height 961640."