Shrike 2.5.5-blake2b.21 - connects to a BLAKE2b Electrum server, and names itself

Everything in 2.5.5-blake2b.20, plus two changes. Signing is unchanged.

Connects to a BLAKE2b Electrum server

Since the BLAKE2b hardfork a header is 164 bytes and hashed differently, so the electrs build that indexes it declines any client below Electrum protocol 1.8. Shrike asked for 1.4.2 and was refused before a single header was fetched (#22). It now asks for 1.8.

Asking that high also changes what Fulcrum sends: at 1.6 a run of headers arrives as a list rather than one string. Both forms are read.

Names itself

Notifications, the name given to an Electrum server, and the Help links said Sparrow, which is a different project. They name this one now. The saved file format keeps its name, since that is what the files are.

No warranty

This is unofficial, unaudited software provided as is, with no warranty and no liability, under the same Apache 2.0 license it inherits. It is not a Sparrow release and is neither affiliated with nor supported by the Sparrow project, nor by any hardware wallet manufacturer. Using it is entirely at your own risk, and you alone bear any loss of funds.

Verifying this release

If you already have Shrike installed, download SHA256SUMS, SHA256SUMS.asc and your install file into one folder, then drag any of them onto Shrike, or open Tools > Verify Download.

Otherwise, with gpg, adding privkeyio-signing-key.asc to that folder:

gpg --import privkeyio-signing-key.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS

Look for Good signature from "Kyle Santiago <kyle@privkey.io>" on key A47D99B6DB0D715D40C59A2023AE8A8EA7E24E38, and OK for your file. The warning that the key is not certified is expected: it means only that you have not marked it trusted yourself.

The macOS builds are not notarized and the Windows installer is not Authenticode signed, so both warn on first run. Reproducible builds: see reproducible.md.