Shrike Wallet Setup: Connect Your Start9 Node & Send Sats

Connecting your wallet to your own node means it asks your own server about your addresses and balances instead of a public one, which is incredibly important for privacy. This guide shows you how to connect Shrike, a wallet for Blake2b Bitcoin, to the Start9 node we set up in my last tutorial, and how to set it up properly with a strong passphrase. At the end, I show how to do the same thing on main chain Bitcoin using Sparrow Wallet.

https://youtu.be/4VjgM9B1hho

It covers disclaimers, downloading and verifying Shrike, connecting to your node, creating a strong random passphrase, creating and testing your wallet, and receiving and sending. There is also a copy-paste AI prompt that walks you through verifying your download for your operating system.

This is part of a tutorial series on decentralizing Bitcoin and using it as money.

Disclaimers

Given everything that has happened recently in Bitcoin, these are important. Please read before you continue:

  • Shrike is not official software. It’s an unofficial fork of Sparrow Wallet and isn’t affiliated with the Sparrow project.
  • It’s unaudited. In their own release notes, the developers describe it as unofficial, unaudited software provided as is, with no warranty and no liability, and say that you alone bear any loss of funds.
  • I can’t vouch for it. I don’t know the people behind it, and I can’t vouch for them or the code. I have no sponsors, nobody is paying me to talk about this. I’m actually using it myself.
  • Treat Blake2b funds as potentially lost. Any funds I receive in Blake2b Bitcoin, I consider potentially lost. Securing Bitcoin has become more uncertain than ever, and I think securing Blake2b Bitcoin is even more uncertain. Only use amounts you can afford to lose.
  • The Coldcard breach is unrelated to Blake2b. But it taught me not to trust anything when it comes to wallets. Blake2b is a new chain with unaudited software and a lot of uncertainty, so I expect I could lose anything I put there, and I treat it as a donation to the network.
  • This is not financial advice. What you decide to do is your responsibility.

If you need more context on what’s happening in Bitcoin right now, including the BIP110 soft fork and the Blake2b hard fork, I covered it in my previous videos.

What You Need

  • Your Blake2b Start9 node from my last tutorial, running Bitcoin Knots, Fulcrum, and Tor. Knots and Fulcrum both need to be fully synced.
  • A computer to run the wallet: Windows, Mac, or Linux.
  • Paper and a pen. You’ll write down your seed words and your passphrase, which should never be stored digitally.

Shrike does not exist on mobile, so any mobile apps claiming to be Shrike are probably a scam. Don’t use them.

Step 1: Download and Verify Shrike

  1. Go to Shrike’s release page: https://github.com/privkeyio/shrike/releases
  2. Download the install file for your computer.
  3. Also download the checksum file called SHA256SUMS, its signature file SHA256SUMS.asc, and the developer’s signing key file.

Which File to Download?

Your computerDownload this fileNotes
WindowsShrike-[version].msiInstaller. Not code-signed, so Windows may warn you.
Windows (no install)Shrike-[version].zipPortable version.
Mac with Apple Silicon (M1, M2, M3…)Shrike-[version]-arm64-unsigned.dmgNot notarized, so macOS will ask you to confirm opening it.
Mac with IntelShrike-[version]-x86_64-unsigned.dmgSame as above.
Linux, Debian/Ubuntu (Intel/AMD)shrike_[version]-1_amd64.deb
Linux, Debian/Ubuntu (ARM)shrike_[version]-1_arm64.deb
Other Linux (Intel/AMD)shrike-[version]-x86_64.tar.gz
Other Linux (ARM)shrike-[version]-aarch64.tar.gz
EveryoneSHA256SUMS, SHA256SUMS.asc, privkeyio-signing-key.ascNeeded to verify your download.

Verify Your Download

Please don’t skip verifying. This is a wallet that will hold your coins, so it’s important to make sure you have the right software. You’re checking two things: that the checksum file is signed by the developers’ key, and that your download matches the checksum.

In each command, replace [FILE_NAME] and [FILE_PATH] with your downloaded install file. There is an AI prompt a bit further down the page to help if you need more tailored guidance.

Verify on Linux

Open a terminal in the folder with your downloads and run:

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

Verify on Mac

Mac doesn’t include GPG, so install it first (for example with Homebrew: brew install gnupg). Then run:

gpg --import privkeyio-signing-key.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
grep "[FILE_NAME]" SHA256SUMS | shasum -a 256 -c

Verify on Windows

Install GPG for Windows (Gpg4win), then open PowerShell in the folder with your downloads and run:

gpg --import privkeyio-signing-key.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
Get-FileHash "[FILE_PATH]" -Algorithm SHA256

Windows prints the hash but doesn’t say OK. Open SHA256SUMS in a text editor and compare the hash next to your file’s name, character by character.

What You’re Looking For

  • A message saying Good signature for the developers’ key.
  • OK next to your file name (or an exact hash match on Windows).

GPG will probably warn that the key is not certified. That’s expected. It only means you haven’t marked the key as trusted yourself. I’d also compare the key’s fingerprint with the one the developers publish in more than one place.

If anything doesn’t match, stop. Delete the file and download it again from the official source.

If you’re still not sure what to do, use this prompt with Claude or any AI:

AI Prompt: Verify My Shrike Download

I downloaded Shrike Wallet, an unofficial fork of Sparrow Wallet for the Blake2b Bitcoin chain, and I want to verify the download before I install it. I have the install file, SHA256SUMS, SHA256SUMS.asc, and the developer's signing key file.
Ask me my operating system first, then interview me one question at a time:
1. Ask whether I already have GPG installed. If not, tell me how to install it for my system.
2. Give me the exact commands to import the signing key, verify the signature on SHA256SUMS, and check my install file against SHA256SUMS.
3. Ask me for the key fingerprint shown on the developer's official pages. Tell me to compare it with what GPG shows, and to check more than one source.
4. Explain what a good result looks like and what the GPG warning that the key is not certified means.
5. If the result is bad, tell me to stop and delete the file.
Never tell me to bypass security warnings until verification has passed. If you don't know a step for Shrike specifically, say so and ask me what I see on my screen instead of guessing. I've never done this before. Explain anything technical in plain language.

Step 2: Install & Open Shrike

Once you’re sure the software is genuine, install it and open it.

  • Linux: install the package for your system.
  • Mac: the app isn’t signed or notarized, so macOS may say it’s damaged or from an unidentified developer. That means it’s unsigned, not that the download is bad. Only get past this warning after you’ve verified your download.
  • Windows: the installer isn’t signed either, so Windows SmartScreen will warn you.

Step 3: Connect Shrike to Your Start9 Node

The first time you open Shrike, you’ll see a welcome screen. Click Next through the introduction. You’ll then be offered two ways to connect: a Bitcoin Knots node or a private Electrum server. We’ll use Fulcrum, our Electrum server, on the Blake2b node.

When your wallet is connected to your own node, it asks your own server about your addresses and balances instead of a public server. That’s incredibly important for privacy, and I always recommend it, even with Sparrow on the main chain. With Shrike, it isn’t optional anyway, because it doesn’t offer public servers.

  1. In StartOS, go to Fulcrum and click Interfaces.
  2. You’ll see the addresses you can connect to. You have two ways to connect.

At home: the local address

  • Use the local address that StartOS shows next to Fulcrum. It’s the fastest way.
  • Enter that address along with the port shown next to it, usually 50002 for a secure SSL connection.
  • Check the SSL option. I’d avoid the plain connection even at home, because it isn’t encrypted.

Away from home, or over Tor you can use the onion address

  • Use the onion address instead.
  • Tor has to be running on your computer. Tor Browser uses port 9150, and the Tor background service uses port 9050.
  • In Shrike, turn on the proxy option and enter that port. The node’s own port is the one shown next to the onion address.

Then click Test Connection. It may ask you to trust your node’s certificate. Since it’s your own node, you can accept.

When it says connected, close the window and look at the connection indicator in the bottom right corner.

If the Connection Fails

Check these:

  1. Has Fulcrum finished syncing on your node?
  2. Are you connecting to your Blake2b node, running the Blake2b version of Knots? Make sure you are not trying to connect a main chain node running Fulcrum.
  3. Did you copy the address exactly? Do you have the correct port?

Step 4: Create a Strong Passphrase

Before we create the wallet, we need to talk about passphrases. This may be the most important part of the guide, so please don’t skip it.

Your seed words control your coins. A passphrase is an extra secret that gets added on top. It creates a completely different wallet from the same seed words, so someone with only your seed words can’t reach your coins.

Why I’m Insisting on This

You’ve probably heard about the Coldcard breach. A bug in Coldcard’s firmware made some devices generate seeds with far less randomness than intended, and attackers have drained well over $100 million worth of Bitcoin. As far as I know, that bug doesn’t affect Shrike or Sparrow Wallet, but it shows why we shouldn’t trust one source of randomness blindly.

Shrike is built on Sparrow’s code. As far as I know, Sparrow gets its randomness from the operating system, which is a standard approach. But Shrike is unaudited, so I don’t want my coins protected by only one source of randomness. That’s why I add a strong, truly random passphrase.

Make It Random

The keyword here is random. Don’t pick a phrase or a sentence you can remember. The best approach is to use dice or a separate tool.

Most people don’t have casino-grade dice, so you can use KeePassXC. It’s free, open source, and works offline.

  1. Download it from the official KeePassXC site and verify the download, just like we did with Shrike.
  2. Ideally, disconnect your computer from the internet.
  3. Open Tools, then Password Generator, and click the Passphrase tab.
  4. Choose the EFF large word list (also called the long word list). It has 7,776 words.
  5. Drag the word count slider to 8 or more.

How many words? Each word from this list adds about 13 bits of randomness. Eight words is about 103 bits, which I’d consider the minimum. Seed phrases are designed to carry 128 bits, and ten words gets you to about 129 bits. If you want to match that standard, use ten.

Optional: Add Your Own Physical Randomness

If you have dice, or a deck of playing cards, you can add one more word so that your passphrase doesn’t rely on a single source of randomness.

With dice:

  1. Roll five casino-grade dice and read them in order (for example, left to right) as one five-digit number. For example, 4, 2, 6, 1, 3 makes 42613.
  2. Find that number in a numbered diceware list, such as the EFF large word list.
  3. Add that word to the end of your passphrase as an eleventh word.

With playing cards: use the deck like a six-sided die.

  1. Draw one card. If it’s an Ace through 6, write down its number (Ace is 1). If it’s anything else, put it back and draw again.
  2. Put the card back and reshuffle the whole deck before every draw.
  3. Repeat until you have five numbers, then look up the five-digit number as above.

Cards are less proven than dice for this, so treat them as an extra on top of KeePassXC, not a replacement. And don’t try to make your passphrase stronger by capitalizing letters or adding numbers you choose yourself. Adding another random word is stronger.

Rules for Your Passphrase

  • Write it down on paper.
  • Store it separately from your seed words.
  • Never photograph it, email it, or save it in the cloud.
  • It’s case sensitive and spaces matter, so write it down exactly the way you want it.
  • If you lose it, you lose your funds. No one can recover them for you.

Step 5: Create Your Wallet

  1. Click File, then New Wallet, and give it a name.
  2. Click Create Wallet.
  3. Choose Single Signature as the policy type. Leave the script type on the default unless you know why you’re changing it.
  4. Choose New or Imported Software Wallet.
  5. Let Shrike generate 12 or 24 words by clicking Generate New.
  6. Write your words down on paper, in order, exactly as you see them on screen.
  7. Type in your passphrase very carefully, exactly as you want to save it, with spaces and capitals if you added them.
  8. Confirm the words you wrote down. You’ll need to re-enter all of them, in order.
  9. Re-type your passphrase very carefully.

Don’t copy and paste any of this from a computer connected to the internet.

Once the keystore is created, you’ll see a master fingerprint and your xpub. Write this down. It’s different from your passphrase, but it’s very important, and in a moment I’ll show you why.

You can also add a password to the wallet, but it only encrypts the wallet file on your computer. The passphrase is different, because it’s part of your keys.

Step 6: Test Your Backup Before You Fund the Wallet

Before you put any coins in this wallet, test your backup.

  1. Write down your first receive address on paper.
  2. Close the wallet and delete it from Shrike.
  3. Recreate it fully from your seed words and your passphrase.
  4. Check that the keystore’s master fingerprint is identical, and that the first address matches what you wrote down.

If you purposely make a typo in the passphrase, you don’t get an error message. You get a different keystore and different wallet addresses. Any small difference creates a brand new wallet. That’s why it’s so important to test your backup first and make sure your keystore matches.

Step 7: Receive Bitcoin

Click the Receive tab and you’ll see an address. Add a label so you remember where it came from.

A Blake2b address looks exactly like a regular Bitcoin address, so be careful to specify that it’s a Blake2b address when you share it. Never send main chain Bitcoin to this wallet by mistake, and always double check which chain you’re on. Remember, only use amounts you can afford to lose.

Step 8: Send & Replay Protection

To send, click the Send tab, enter an address and an amount, and choose your fee.

On this screen, Shrike also tells you whether a transaction is replay protected. That matters because Blake2b split off from main chain Bitcoin, so a normal transaction could, in theory, be copied onto the other chain. That’s called a replay. Shrike signs with a special opt-in signature that prevents this problem, and it reports the result on screen. Be sure to leave it on.

Moving Existing Blake2b Coins: The Risk

To move your existing Blake2b Bitcoin, you have to enter your existing seed words into Shrike, because the same keys control your coins on both chains. Even if you send those coins to a brand new wallet afterward, your old seed was exposed to the software.

Shrike is unaudited, so if anything is wrong with it, you could lose not only your Blake2b coins, but also the main chain Bitcoin controlled by that same seed. A strong passphrase protects you from weak randomness, but it doesn’t protect you from a flaw in the wallet itself.

So if you decide to access Blake2b Bitcoin that comes from an older main chain wallet, only do it with amounts you can afford to lose, and use a brand new seed phrase for anything new.

Main Chain: Sparrow Wallet

If you want to do the same thing on main chain Bitcoin, Sparrow Wallet is the original software that Shrike is forked from. The steps are almost identical.

  1. Download Sparrow from its official website and verify the download.
  2. You can tell the two apps apart by color: Shrike is red and Sparrow is blue. Do any main chain activity in the blue app.
  3. Connect Sparrow to Fulcrum on your main chain node, following the same steps as above. Be careful: Sparrow connects to a public Electrum server by default, which is not private. Switch it to your own server.
  4. Create a separate wallet with its own seed words and its own strong passphrase.

You can have both apps installed on the same computer. On Debian Linux, at least, Shrike installs alongside Sparrow with its own settings folder. Just make sure each wallet connects to the correct node.

What’s Next

In the next videos, I’ll cover mining and e-commerce.

Frequently Asked Questions

Is Shrike Wallet Official or Safe?

No. Shrike is an unofficial fork of Sparrow Wallet and isn’t affiliated with the Sparrow project. Its own release notes describe it as unofficial, unaudited software provided as is, with no warranty and no liability. I don’t know the people behind it, so I can’t vouch for them or the code. Only use amounts you can afford to lose.

Why Do I Need to Run My Own Node for Shrike?

Shrike doesn’t offer public servers, so you have to connect it to your own node. That also protects your privacy, because your wallet asks your own server about your addresses and balances instead of a public one.

What Is a Passphrase, and Why Do I Need One?

A passphrase is an extra secret added on top of your seed words. The same seed words with a different passphrase create a completely different wallet. A strong random passphrase protects you if your seed was generated with weak randomness, but it doesn’t protect you from a flaw in the wallet itself.

How Many Words Should My Passphrase Have?

At least eight words from the EFF large word list, which is about 103 bits. If you want to match the 128-bit standard that seed phrases are designed for, use ten words, which is about 129 bits.

What’s the Difference Between My Passphrase and My Wallet Password?

The wallet password only encrypts the wallet file on your computer. The passphrase is part of your keys, so a different passphrase creates a different wallet.

What Happens If I Mistype My Passphrase?

You don’t get an error. You get a different keystore and different, empty wallet addresses. That’s why you should test your backup before you put in any coins and check that the master fingerprint matches.

Is the EFF Large Word List the Same as the Long Word List?

Yes. Both names refer to the same 7,776-word list.

What Is Replay Protection?

Blake2b split off from main chain Bitcoin, so a normal transaction could in theory be copied onto the other chain. Shrike signs with a special opt-in signature that prevents this, and it tells you on the send screen whether each transaction is replay protected.

Can I Use Shrike on My Phone?

No. Shrike doesn’t exist on mobile, so any mobile app claiming to be Shrike is probably a scam.

Can I Use the Same Seed on Both Chains?

The same keys control your coins on both chains, which is the problem. Because Shrike is unaudited, I’d create a brand new seed phrase and passphrase for anything new, and only move older coins if you can afford to lose them.

Daniella Liberati is the author of Beyond Money: Regaining Sovereignty, Rediscovering Humanity (foreword by Jeff Booth). She holds degrees in Economics, Corporate Law, English, and Teaching, and has spent over fifteen years working across technology and digital marketing. She is Bitcoin only with no sponsors or advertisers. You can find her work on this website as well as YouTube and Nostr.

Value For Value

The New Economy

I've never had sponsors and I don't run ads. My work is shared value for value, the peer-to-peer, no-middleman principle I write about in my book. If you find value in it, you're welcome to support it with a zap ⚡️

Thanks!

Zap Over Lightning⚡️


daniella@coinos.io