Your first signed transaction
What you'll learn
- How a transaction travels from Sparrow to the device and back
- What to check on each review screen before you approve
- How to confirm the transaction on the signet network
This is the moment the whole build is for. You’ll send some of your signet coins and watch each step. Start with a one-input transaction: send part of the coins you got from the faucet.
You need: Sparrow on signet with your watch-only wallet, the device with your test seed loaded, and the computer’s webcam.
1. Build the transaction in Sparrow
Section titled “1. Build the transaction in Sparrow”- In Sparrow, open the Send tab.
- Enter a recipient address and an amount. For a first test, use one of your own receive addresses (from the Receive tab), so the coins come back to you.
- Create the transaction and finalise it for signing. Sparrow then offers ways to sign it. Choose to show it as a QR code, and set the QR density to its lowest.
Sparrow now shows an animated QR code: frames starting UR:CRYPTO-PSBT/.
2. Scan it with the device
Section titled “2. Scan it with the device”- On the device, open Sign PSBT. The scan screen shows a progress bar.
- Hold the camera board towards Sparrow’s QR code, so the code fills most of the camera’s view, and keep it steady.
The progress bar counts the pieces of the transaction recovered so far. Frames can be missed or caught twice; the decoder doesn’t need them all. In testing, a one-input transaction was complete in about 12 to 15 seconds of steady aiming.
3. Review every screen
Section titled “3. Review every screen”The device now checks the transaction on its own, as described in How it works, and shows you what it found.
One screen per recipient:
- the full address, split into groups of 4 characters, to compare with what you meant to pay
- the amount, in BTC and in sats
- if the address belongs to your own wallet, it says so (for example “to self, receive #1”), but only after the device has checked it
Then a summary:
- total sent, change back to you, the fee and the fee rate, and the number of inputs
- for a one-input transaction without the earlier transaction attached, a note that the fee wasn’t independently verified (see How it works for why that’s safe for one input)
- an extra warning screen if the fee is unusually high
Check each value against what you entered in Sparrow. If anything differs, reject.
4. Approve, or reject
Section titled “4. Approve, or reject”Reject is always the left button, and it’s the default. Approving takes a deliberate tap, then a second confirmation.
- If you reject, nothing is signed. The device wipes the transaction from memory and returns to the menu.
- If you approve, the device signs each input and checks every signature before showing anything.
5. Scan the signed transaction into Sparrow
Section titled “5. Scan the signed transaction into Sparrow”The device shows the signed transaction as an animated QR code (UR:CRYPTO-PSBT again).
- In Sparrow’s transaction window, choose to scan a QR code, and hold the device up to the webcam.
- If the webcam struggles, use the device’s density button. It switches between larger frames (fewer, denser) and smaller ones (more, easier to read). It starts at the easiest setting.
6. Broadcast and confirm
Section titled “6. Broadcast and confirm”- Sparrow shows the signed transaction. Check it, then broadcast it.
- Note the txid and look it up on a signet block explorer: [EXPLORER LINK]
- Wait for the first confirmation, when the transaction is included in a block.
When you’re done on the device, tap Done. It wipes the transaction from memory. Your seed stays loaded until you choose Wipe & lock, or the device locks itself after 5 minutes without a touch.
Spending more than one coin
Section titled “Spending more than one coin”A transaction with more than one input needs the earlier transactions that created each coin, so the device can check the amounts. Without them, it refuses, with a message that an input has no previous transaction. That is deliberate (see How it works).
In testing, Sparrow’s QR code left these earlier transactions out, although Sparrow’s saved transaction file included them. The cause is still unknown. The tested workaround was to save the transaction to a file in Sparrow and show that file as an animated QR code with a small tool from the firmware repository (tools/psbt_show, which needs Node.js). One multi-input transaction was signed and confirmed that way. See Known issues.
You did it
Section titled “You did it”The device has now done everything a signer has to do: read a transaction it didn’t trust, checked it independently, showed you the truth, and signed only after you approved. Two transactions signed by the tested build have confirmed on signet; yours can be next.