Shrike
Docs
Shrike documentation
These pages cover what is specific to Shrike. For everything Shrike inherits unchanged from Sparrow, upstream's own documentation applies.
Quick start
From a fresh download to a first send: stand up a node, connect it, mark your signers, check the send screen.
Connecting a node
Why the public servers are gone, and how to point Shrike at a Knots node or your own Electrum server.
Replay protection
What the opt-in signature hash does, how to mark a keystore, what a multisig quorum gets, and the Anyone Can Pay exception.
Hardware wallet firmware
Unofficial Coldcard, SeedSigner and Trezor builds that can sign with SIGHASH_UNIFIED, how to verify them, and what flashing one costs you.
Building and running
Recursive clone, Java and packaging requirements, running from source, command line options and the home folder.
FAQ
Coins held across activation, using Shrike beside Sparrow, hardware wallet support, and where to report an issue.
From Sparrow's documentation #
Most of the wallet is upstream's work and behaves as it does there, so rather than restate it, Sparrow's documentation is worth reading alongside these pages. It covers wallet creation, hardware wallets, the transaction editor, airgapped workflows, privacy and server performance.
Two differences run through all of it, so keep them in mind wherever you are reading:
- Shrike offers no public servers. Anywhere upstream assumes you can pick one, that option does not exist here. Your own node, or your own Electrum server in front of it, is the only arrangement. See connecting a node.
- Signing has to opt in. A device on stock firmware still signs, but produces signatures with no replay protection. See replay protection and hardware wallet firmware.
In the repository #
Some material is kept next to the code rather than here, because it is checked against the code on every change: