Hi Paul - Moving my question from Bitcion U to here.
I installed your SparrowBlake2b on Windows where I am running rc4 knots currently.
Can you please point me to the steps getting the two connected? Many thanks!
I’m happy to use start09 but didn’t see your Sparrow in your registry.
Thanks again for all of the help!
Sparrow isn’t run on the server, you run it on Windows, etc like you have. Then it connects typically to an indexer (Electrs Pruned in this case) running on the server via Tor.
You are trying to connect it directly to the Knots RPC on a native Windows installation. I’ve not done that before, but I assume it is the same as connecting normal Sparrow up to Core on Windows (see this guide here, for example)
Ah yes of course, I remember now. Thanks Paul!
Paul, could you please post the GitHub link for your SparrowBlake2b build? I’d like to install the Linux x86_64 version. Thanks!
I currently am only maintaining the “standalone” versions for Windows (the .zip file) and Linux (the .tar.gz files). If it becomes popular enough, I’ll expand that out. Note that on Mac, I don’t have an Apple signature, so it will try to convince you not to install it (you’ll have to jump through some hoops, unforutnately)
Hey Paul,
Just for clarification, as of 9/3/26, are you recommending that we run your version:
Sparrow (BLAKE2b) 2.5.5 with replay protection
or to run:
Shrike 2.5.5-blake2b.16 - report the protection a transaction actually has
I just want to make sure to run which ever is the most ironed out and up to date. Thank you
They are both forked from the same upstream version and should be current. Either should be good. I’ve only tested mine, but Shrike is more well known.
Thank you, I greatly appreciate your work!
Is the way that this works is to connect the pruned electrs that you provided to Sparrow (BLAKE2b) in the settings via the Tor address : 5002? I have Start9 4.0
Yes, that’s correct.
Excellent! Thank you
Thank you so much Paul!
Installed Sparrow (Blake2b) 2.5.5 a couple of days ago because BTC Knots (Blake2b) companion IBD on my node was taking a long time [4 days]
Used BTC-B2b Addr from Sparrow and mined from https://b.pyblock.xyz:8443/rentals.php (hit a couple of blocks) → Paid w/ Lightning from LND as well as from River (FYI @ River send BTC + LN Invoice works). Very simple (when rentals are available from Pyblock)
Now have Bitcoin Knots (BLAKE2b) companion past IBD, and Electrs Pruned (12hrs → read instructions folks to start indexing early) going now
Just added Mempool Pruned → can independently anonymously verify that above BTCb2 are there agreeing with Sparrow (Blake2b).
Also, have a Goldshell-HSBox w/ your Datum Gateway (Blake2b) Companion going 0.5TH/s (pre-verified on testnet4 and working as expected)
… thank you so much for all you do. No way I could have done this without you and this community. Cheers!
When I try connecting the latest version of Shrike (Shrike 2.5.5-blake2b.17 - the unified opt-in signature hash on Trezor) with the latest version of Electrs Pruned (0.11.1:36) I am getting the following error.
This happens both on Tor TCP as well as Tor SSL. Any thoughts on how to fix this?
Could not connect:
unsupported request Single(“1.4”) by Sparrow: this chain uses 164-byte block headers with a BLAKE2b block hash, which a client below protocol 1.8 cannot read. Refusing rather than serving headers it would misinterpret.
Thank you for letting me know. Electrs Pruned is still syncing for me. I hadn’t gotten to that point yet.
Hopefully there will be a fix for this soon.
Is there a way to run a full Knots node and a pruned pre-rdts node and use elctrs, sparrow and mempool for both? I would rather not run a full pre-rdts node. I know you are busy, but if there was a pruned Fulcrum maybe you could point one indexer to each node then point the versions of sparrow to the appropriate indexer. Is that possible?
This is in the works. Last piece is the SHA256 version of the Datum Gateway companion. Should have it up later today. I’ll post an update when it is ready.
That’s awesome. Thank you for all of your hard work Paul.