SW
← All projectsSparrow

Sparrow Wallet

Desktop Bitcoin wallet focused on security, privacy, multisignature, and hardware signers.

BitcoinHardware integrationSoftware walletsNormal
Repository coverage

630 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

102security candidates447second-pass queue606AI analyses
181commits · 30 days
220commits · 60 days
411commits · 180 days
584commits · 365 days
Backfill bands
Aug 5 → Feb 6100 seen9 candidatesComplete
Feb 6 → Jun 6128 seen15 candidatesComplete
Jun 6 → Jul 67 seen1 candidatesComplete
Jul 6 → Aug 546 seen8 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

49/100 average clarity
0Strong · 80–100
55Adequate · 60–79
520Thin · 40–59
55Opaque · 0–39
3security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Craig Raw61398589949
doblon8313048
Michele Balistreri212048
nzb-tuxxx212060
nroktib111050
Liz Lightning202045
Aaron Leeb101060
PeterXMR101045
craigraw101060
Ian McKenzie101050
Jan Dvořák101050
Kevin Abramczyk101050
Analysis record

Published AI watches

Last scanned 2 minutes ago

Informational 18 AI analysisMessage 60 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

document building v2.5.3 to v2.5.6 with lenient dependency verification, as two pom files were later republished to maven central with additional metadata

This commit only updates documentation. It explains that when building older Sparrow Wallet releases (versions 2.5.3 through 2.5.6), two dependency files on Maven Central were later republished with extra descriptive metadata, causing a ha…

Dependency checksum mismatch in recorded verification metadataPOM-only republication of two Sparrow-published artifacts (hid4java, usb4java)Documentation instructs lenient verification for reproducible builds of older releases
6a83c9a5by Craig Raw+15−01 file
No security note in commit
Low 34 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

warn that a bip353 name resolved to a silent payment address for a different network on the send tab and in send to many, rather than reporting it has no address

This commit improves user-facing error messages in the Sparrow Wallet when a BIP353 human-readable name (like a DNS-based Bitcoin payment alias) resolves to a silent payment address meant for a different Bitcoin network (for example, testn…

BIP353 DNS payment resolutionsilent payment address network mismatchuser-facing warning improvement
08f32515by Craig Raw+6−13 files
No security note in commit
Low 26 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

skip the keepalive ping while another request is awaiting its response

This change stops Sparrow Wallet from sending unnecessary 'are you still there?' keepalive pings when another request is already waiting for an answer. On some Electrum server backends (notably electrs), a ping would queue up behind the pe…

Avoidance of redundant keepalive pings that could delay synchronizationNew transport-level predicate exposing in-flight request stateUnit test added to assert correct pending-request lifecycle
4df18311by Craig Raw+50−13 files
No security note in commit
Low 38 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

wait for a slow electrum server response instead of resending the request, halving batch page sizes only after a request goes unanswered, and retry the keepalive ping once

This commit changes how the Trezor hardware wallet app talks to Bitcoin servers when responses are slow. Previously, the app would quickly resend a request if it didn't get an answer in time, and each timeout would double the wait and halv…

Change to timeout/retry logic that could affect denial-of-service resilienceReduction in retry count for keep-alive pings from 5 to 2Avoidance of duplicate request sending to slow servers, reducing amplification
96d217cfby Craig Raw+84−194 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

reduce the minimum window width to 750, fitting the send tab, transaction diagram and transaction tab views to narrow windows and narrowing the wallet menu and transaction tree below 900

This commit is a user-interface layout tweak for the Sparrow Wallet desktop app. It makes the main window usable at narrower widths by shrinking minimum sizes, wrapping labels, and making diagrams and menus responsive. There is no security…

86e52311by Craig Raw+117−4717 files
No security note in commit
Moderate 61 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

check a proof that does not reconstruct against the server chain before reporting it, as a server can report a transaction on a branch before announcing its tip

This commit fixes a bug in how Sparrow Wallet checks Bitcoin transaction proofs from an Electrum server. Previously, if a server had switched to a different blockchain branch (for example due to a reorganization) but had not yet announced …

Merkle proof verification bypass/relaxation under reorganization windowServer-side blockchain state synchronization before proof validationRisk of false-negative proof rejection leading to incorrect transaction confirmation status
f7357906by Craig Raw+91−22 files
No security note in commit
Low 33 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

decide whether a border wallets grid is hex from all of its cells rather than the selected ones

This commit fixes a bug in Sparrow Wallet's 'Border Wallets' feature. Previously, the app guessed whether a grid of seed-word abbreviations was hexadecimal (base-16) by looking only at the cells the user selected. If a user happened to pic…

Incorrect input classification leading to wrong BIP39 word derivationWallet seed/recovery correctness issueUI dialog parsing bug in mnemonic grid import
0d4f1482by Craig Raw+9−61 file
No security note in commit
Low 43 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

leave qr codes that zbar can only return as transcoded text to the other scanners

This commit fixes a bug in how Sparrow Wallet reads QR codes using the ZBar scanner. ZBar converts binary QR code data into text and silently stops at the first null byte, which can corrupt non-text data. The fix makes Sparrow only trust Z…

Data integrity issue in QR code parsingReliance on lossy text conversion for binary dataSilent truncation at NUL byte
0c28eafeby Craig Raw+25−12 files
No security note in commit
Low 27 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

save the freeze status and labels of nested wallet outputs to the wallet that stores them

This commit fixes a bookkeeping bug in Sparrow Wallet for users who have a main wallet with nested sub-wallets (for example, PayNym-style wallets). Previously, when you froze an unspent coin or changed its label, the change was recorded ag…

State-persistence bug: freeze/label changes for nested-wallet UTXOs were saved to the wrong walletUI/event routing now keyed by owning wallet rather than display walletNew unit tests added to assert correct ownership semantics
5c47c3a4by Craig Raw+116−2611 files
No security note in commit
Moderate 58 AI analysisMessage 62 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

keep the encrypted master secret of imported slip39 shares, so that the wallet decrypts it with any passphrase as the shares do

This commit fixes how Sparrow Wallet stores the backup/recovery seed when a user imports a wallet using SLIP39 shares (a type of multi-share mnemonic backup). Previously, the wallet decrypted the shares with the passphrase entered at impor…

SLIP39 passphrase handling changed from one-time decryption to persistent encrypted master secretStored seed now derives correct keys regardless of which passphrase is later usedNew unit test explicitly checks passphrase-variant key derivation parity
9b998a78by Craig Raw+47−43 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

keep the monospaced font of utxo addresses when the table is refreshed

This is a minor user-interface bug fix. It ensures that Bitcoin addresses in the wallet's UTXO list keep their fixed-width (monospaced) font after the table is refreshed. There is no security issue here.

868fa081by Craig Raw+2−11 file
No security note in commit
Low 46 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

refuse descriptors that do not derive on the standard receive and change chains when importing a wallet or keystore, and warn of them in the descriptor editor

This commit tightens how Sparrow Wallet handles Bitcoin output descriptors imported from files, hardware wallets, QR codes, and the descriptor editor. It now rejects (or warns about) descriptors whose key paths don't follow the standard 'r…

New validation of BIP32 derivation paths on all descriptor import pathsRejection of descriptors with non-standard receive/change chains during wallet/keystore importWarning (but not rejection) retained for descriptor editor where user can amend the descriptor
3d2fbac4by Craig Raw+23−910 files
No security note in commit
Moderate 58 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

apply the child derivations of keys in scanned output descriptors, and refuse those that do not derive on the standard chains

This commit changes how Sparrow Wallet handles QR code and file imports of Bitcoin wallet descriptors. Previously, when scanning a descriptor from a QR code, the wallet might ignore or mishandle 'child derivation' paths that tell it how to…

Input validation added for scanned output descriptor child derivationsRejection of non-standard child derivation chainsConsistent application of child derivations between QR/file import and text descriptor parsing
6a000160by Craig Raw+290−403 files
No security note in commit
Moderate 60 AI analysisMessage 55 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

refuse an extended private key in place of an xpub in imported wallet files, and use the public key of a private hdkey in a scanned output descriptor

This commit fixes a security issue in Sparrow Wallet where wallet import files or QR scans that were supposed to contain only public extended keys (xpubs) could accidentally or maliciously contain private extended keys (xprvs). The wallet …

Rejection of extended private keys where extended public keys are expectedPublic-key derivation from private HD keys in scanned output descriptorsAddition of defensive validation helper across multiple wallet import formats
97742cabby Craig Raw+52−298 files
Vendor flagged security relevance
Informational 19 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

let the terminal user choose the script type when transactions are found for more than one

This change improves the Sparrow Wallet terminal (command-line) interface. Previously, if the wallet discovery process found transactions matching more than one Bitcoin script type, it would silently pick the first one. Now it shows a menu…

Behavioral fix: prevents silent selection of first discovered wallet script typeUser-choice dialog added in terminal wallet creation flowNo cryptographic, network, or input-validation changes observed
a18db115by Craig Raw+18−41 file
No security note in commit
Low 33 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

use the bip352 derivation for silent payment wallets imported from a mnemonic or device, created in the terminal, scanned from a seedqr or added at another account

This commit changes how Sparrow Wallet picks the derivation path when creating or importing wallets. It makes the wallet choose BIP-352 (silent payments) paths when the wallet policy is a single-key silent-payment wallet, instead of always…

Derivation-path selection now depends on policy type, which can change wallet fingerprint/address generation for silent-payment walletsBroad surface area (12 files) increases risk of an import path being missed or behaving differentlySubmodule bump (drongo) likely contains the actual ScriptType.getDefaultDerivation(PolicyType) implementation, but its diff is not supplied
002b1b58by Craig Raw+41−3012 files
No security note in commit
Low 37 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

replace control characters in cosigner labels of an imported multisig configuration, and size alerts to include blank lines

This commit makes two small UI fixes in Sparrow Wallet. First, it strips hidden control characters from cosigner labels when importing a shared multisig wallet setup, preventing odd or misleading label display. Second, it fixes alert dialo…

Sanitization of user-supplied labels (control/format characters replaced)UI dialog sizing fix to prevent content clippingNo explicit security framing in commit message or diff
c1d4feeaby Craig Raw+3−12 files
No security note in commit
Low 34 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

truncate address, purpose node and keystore labels when updating a wallet, as a full save does

This commit fixes a bug where Sparrow Wallet's database update path failed to shorten (truncate) long labels for wallet addresses, purpose nodes, and keystores before saving them. The full save path already did this truncation, but the inc…

Data-integrity bug: inconsistent truncation between full save and incremental updatePotential denial-of-service against local wallet state via overly long labelsRegression test added to prevent future recurrence
0721ca98by Craig Raw+50−52 files
No security note in commit
Low 32 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

refuse the bwt fallback for bitcoin core over https and ignore the legacy wallet setting for it

This commit changes Sparrow Wallet so that when it connects to a Bitcoin Core node over HTTPS, it no longer falls back to an older 'BWT' connection method and no longer tries to use legacy Bitcoin Core wallets. The change appears to be a h…

Disables legacy wallet handling for HTTPS Bitcoin Core connectionsRemoves BWT fallback for HTTPS Bitcoin Core connectionsForces Bitcoin Core v24+ requirement for HTTPS connections
b935568aby Craig Raw+8−22 files
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

check rsa server certificates against the ca trust store for the key exchange in use

This one-line change fixes how Sparrow Wallet checks a Bitcoin server’s TLS certificate. Previously, when the server used an RSA certificate, the app told Java’s certificate validator to expect an old-style RSA key exchange ("RSA"). That w…

TLS certificate validation logic changedX509TrustManager.checkServerTrusted authType correctedPotential for certificate acceptance/rejection mismatch before fix
1071ed7cby Craig Raw+1−11 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedisolate a malformed card response to the card that caused itby Craig Raw · 4989a881 · Aug 21, 2026 · 2 filesMessage 50 · ThinLow 35Details
Commit message · Craig Raw

isolate a malformed card response to the card that caused it

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100

This commit adds broader error handling when reading hardware cards during wallet import. Previously, an unexpected or malformed response from a card could throw an unhandled exception and potentially crash or disrupt the import process for other cards. The change catches any runtime exception, logs it, and limits the failure to the specific card that caused it. It is a defensive hardening fix rather than a clear-cut vulnerability patch.

AI review queuedfail rather than loop indefinitely on an unsuccessful card wait or repeated secure channel resetsby Craig Raw · 3e53f193 · Aug 21, 2026 · 3 filesMessage 50 · ThinLow 48Details
Commit message · Craig Raw

fail rather than loop indefinitely on an unsuccessful card wait or repeated secure channel resets

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 48/100

This commit fixes two situations where Sparrow Wallet could get stuck in an endless loop while talking to a hardware card (Coldcard/Satochip). Previously, if the card refused a 'wait' request or repeatedly rejected the secure channel setup, the software would retry forever. Now it throws an error or stops after three retries. This is a reliability/DoS fix rather than a direct theft-of-funds bug, but an attacker who can make the card misbehave could freeze the wallet interface.

AI review queuedbound the bitcoin core rpc connect and read timeouts, exempting the methods that rescan synchronouslyby Craig Raw · e49b6a4a · Aug 21, 2026 · 2 filesMessage 50 · ThinModerate 62Details
Commit message · Craig Raw

bound the bitcoin core rpc connect and read timeouts, exempting the methods that rescan synchronously

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 62/100

This commit fixes a bug where Sparrow Wallet's connection to a Bitcoin Core node could hang forever if the node accepted the connection but never replied. The patch adds sensible time limits for making and reading connections, while carefully allowing very long waits only for two specific Bitcoin Core operations that legitimately take hours. Without the fix, a user connecting to a slow, stuck, or maliciously unresponsive node could have their wallet interface freeze indefinitely.

AI review queuedbound the electrum read timeout across the wait for a response, not just acquiring the read lockby Craig Raw · 5b10debd · Aug 21, 2026 · 2 filesMessage 50 · ThinModerate 51Details
Commit message · Craig Raw

bound the electrum read timeout across the wait for a response, not just acquiring the read lock

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 51/100

This commit fixes a bug in Sparrow Wallet's connection to Electrum servers. Previously, when waiting for a server reply, the timeout only applied to acquiring an internal lock, not to the actual wait for data. A server that accepted a request but never answered could cause the wallet to hang forever instead of timing out. The patch makes the timeout cover the entire wait and adds tests to prove the hang is gone and that the connection can recover on the next request.

AI review queuedonly apply dns payment resolutions matching the currently entered recipientby Craig Raw · 185e0e8b · Aug 21, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

only apply dns payment resolutions matching the currently entered recipient

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This commit fixes a race condition in Sparrow Wallet's payment screen. When a user types a human-readable payment name (like a DNS-based address), every keystroke that forms a valid name triggers a slow background lookup. If the user keeps typing or changes the recipient, an older lookup could finish later and overwrite the current recipient address with the wrong one. The fix checks that the lookup result still matches what the user has actually typed before applying it.

AI review queuedimprove randomization for utxo selection, input and output shuffling, and anti-fee-snipingby Craig Raw · bf0daae6 · Aug 21, 2026 · 3 filesMessage 50 · ThinModerate 51Details
Commit message · Craig Raw

improve randomization for utxo selection, input and output shuffling, and anti-fee-sniping

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 51/100

This commit replaces ordinary shuffling with a cryptographically secure random number generator when selecting which coins (UTXOs) to use in Bitcoin transactions and when ordering transaction inputs and outputs. The change makes it harder for an observer to guess or reproduce the wallet's choices, which can reduce privacy risks and certain fee-sniping attacks. The actual security improvement depends on code inside the updated 'drongo' submodule that is not shown in the diff.

AI review queuedwarn before creating a keystore from a scanned seed with an invalid checksumby Craig Raw · fdd1875a · Aug 21, 2026 · 1 fileMessage 50 · ThinLow 44Details
Commit message · Craig Raw

warn before creating a keystore from a scanned seed with an invalid checksum

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 44/100

This change adds a warning when a user scans a QR code containing a seed phrase whose checksum is invalid. Previously, Sparrow would silently create a wallet keystore from the bad seed. With a bad checksum, other wallets will reject the same seed words, so any bitcoin sent to that wallet could become unrecoverable from the backup. The patch asks the user to confirm before proceeding.

AI review queuedcatch any parse failure when opening pasted or server-fetched transactionsby Craig Raw · 4caa02d3 · Aug 21, 2026 · 3 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

catch any parse failure when opening pasted or server-fetched transactions

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100

This commit hardens Sparrow Wallet so that unexpected failures while reading pasted transactions or transactions fetched from Electrum servers are caught and handled gracefully, instead of crashing the application. It also updates the 'drongo' subproject, which likely contains related parsing code. The change is defensive and improves robustness, but the commit message does not frame it as a security fix.

AI review queuedrelease the reference to the derived encryption key when clearing a loaded walletby Craig Raw · 4b373714 · Aug 20, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · Craig Raw

release the reference to the derived encryption key when clearing a loaded wallet

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100

This commit fixes a cleanup step in Sparrow Wallet. When a wallet is unloaded, the code now explicitly drops its reference to the derived encryption key, which may help the Java garbage collector reclaim the key material sooner and reduces the window in which a sensitive key could linger in memory. The change is defensive and small, but it does not by itself prove an exploitable vulnerability.

AI review queuedstrip only the trailing extension when deriving the h2 database nameby Craig Raw · bad92ba6 · Aug 20, 2026 · 2 filesMessage 50 · ThinModerate 60Details
Commit message · Craig Raw

strip only the trailing extension when deriving the h2 database name

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100

This commit fixes a bug in how Sparrow Wallet names its internal H2 database files. Previously, the app stripped every occurrence of the wallet file extension from the full file path, not just the trailing one. That meant a wallet file named something like 'backup.mv.db2.mv.db' would accidentally write its database data to a different file ('backup2') instead of the file Sparrow was tracking. The fix removes only the final extension. The bug could cause wallet data to be written to or read from the wrong file, potentially leading to data loss, confusion, or cross-wallet contamination, though direct theft of funds is not evident from the change.

AI review queuedignore the results of superseded download verificationsby Craig Raw · abd9de2d · Aug 20, 2026 · 2 filesMessage 50 · ThinLow 41Details
Commit message · Craig Raw

ignore the results of superseded download verifications

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 41/100

This commit fixes a timing bug in Sparrow Wallet's download verification dialog. Previously, if a user started a new file verification while an earlier one was still running, the old verification could finish later and overwrite the new results on screen. That could briefly show a wrong file as 'verified' or 'matched.' The fix adds a counter so results from an outdated verification are ignored, and it cancels any running checks before starting a new one.

AI review queuedconfirm the imported quorum and cosigners before completing an incomplete multisig walletby Craig Raw · 54926b5f · Aug 20, 2026 · 2 filesMessage 50 · ThinLow 44Details
Commit message · Craig Raw

confirm the imported quorum and cosigners before completing an incomplete multisig wallet

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 44/100

This commit adds a confirmation step when completing an unfinished multi-signature (multisig) Bitcoin wallet by importing a coordinator's configuration. Before the change, Sparrow would silently replace the user's local cosigner list and signing rules with whatever the imported file contained. After the change, the user must review and approve the required number of signatures (quorum), the list of cosigners, and which of their own keys are included before the wallet is updated. This reduces the risk that a malicious or incorrect import could trick the user into a wallet they cannot truly control or co-sign.

AI review queuedreport failed bitcoin core descriptor imports instead of only logging themby Craig Raw · 73c06c32 · Aug 20, 2026 · 4 filesMessage 50 · ThinInformational 20Details
Commit message · Craig Raw

report failed bitcoin core descriptor imports instead of only logging them

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit changes Sparrow Wallet so that when it fails to import Bitcoin Core wallet descriptors, the user is shown a clear error dialog or terminal message instead of the failure being hidden in logs. Previously, descriptor import failures were only logged, which could leave users unaware that their transaction history or balances might be incomplete. The change improves visibility and reliability but does not introduce or fix a traditional security vulnerability.

AI review queuedrange check the server supplied minimum relay feeby Craig Raw · 7faa65fc · Aug 20, 2026 · 1 fileMessage 45 · ThinModerate 50Details
Commit message · Craig Raw

range check the server supplied minimum relay fee

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 50/100

This commit adds a safety check on a fee rate value that a Bitcoin server sends to the Sparrow Wallet app. Before, the app would trust and use whatever number the server provided for the minimum relay fee. Now, if that number is negative or unreasonably high, the app ignores it and falls back to a safe built-in default. This protects users from a malicious or buggy server tricking the wallet into using bad fee rates that could delay, overpay, or otherwise mishandle transactions.

AI review queuedwarn when a bitcoin core node is neither local nor onionby Craig Raw · ad61007d · Aug 20, 2026 · 5 filesMessage 50 · ThinLow 47Details
Commit message · Craig Raw

warn when a bitcoin core node is neither local nor onion

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 47/100

This commit adds a warning to Sparrow Wallet when a user connects to a Bitcoin Core node that is neither on their own computer/local network nor a Tor onion address. Previously, users could unknowingly route Bitcoin Core RPC traffic over the public internet, exposing their wallet data and RPC credentials. The change also improves how Sparrow decides whether an address is 'local' and fixes a UI bug where settings panes were recreated each time they were opened. It is a defensive hardening change rather than a fix for an active exploit.

AI review queuedretain the existing wallet encryption when a password change is cancelledby Craig Raw · 194bd70f · Aug 20, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

retain the existing wallet encryption when a password change is cancelled

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This commit fixes a bug in Sparrow Wallet where cancelling a password change could leave the wallet unencrypted in memory for the rest of the session. Previously, the software decrypted the wallet to prepare for a new password, but if the user cancelled, it never re-encrypted it. Now it re-encrypts with the existing key when the change is abandoned. This is a security fix for a local, user-interactive edge case.

AI review queuedskip malformed silent payment entries rather than aborting the scan batchby Craig Raw · 1e660ad2 · Aug 19, 2026 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Craig Raw

skip malformed silent payment entries rather than aborting the scan batch

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 42/100

This commit changes how Sparrow Wallet handles data received from an Electrum server about silent payments. Previously, if one entry in a batch was malformed, the entire scan batch would abort. Now, the wallet logs a warning and skips only the bad entry. This makes the wallet more resilient to bad server data, but also means a malicious or buggy server could silently feed malformed entries and have them ignored rather than trigger a visible failure. There is no direct evidence in the commit that this is exploitable to steal funds, but it removes a fail-stop behavior.

AI review queuedhandle an absent final scriptsig or witness when restoring the original payjoin inputsby Craig Raw · c60a6ddd · Aug 19, 2026 · 1 fileMessage 50 · ThinLow 40Details
Commit message · Craig Raw

handle an absent final scriptsig or witness when restoring the original payjoin inputs

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 40/100

This commit fixes a crash in Sparrow Wallet's Payjoin feature. When receiving a Payjoin proposal, the wallet tries to restore original payment input details. Previously, if the original PSBT input lacked a final script signature or final witness, the code would throw a NullPointerException and crash. The patch now safely handles those missing fields by setting the restored values to null instead of crashing.

AI review queueddisable the proxy setting when no proxy server is configuredby Craig Raw · 571e4c94 · Aug 19, 2026 · 2 filesMessage 50 · ThinLow 38Details
Commit message · Craig Raw

disable the proxy setting when no proxy server is configured

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 38/100

This commit tightens how Sparrow Wallet handles its proxy setting. Previously, a user could enable 'use proxy' even if no proxy server was actually configured, or the app could save an empty/whitespace proxy server value. The change now disables the proxy setting automatically when no valid proxy server is configured, trims whitespace from the proxy host, and treats blank host values as invalid. This is a defensive hardening fix that prevents the wallet from accidentally running without the privacy/protection the user expected from a proxy.

AI review queueddetect legacy multisig descriptors case insensitively when warning about key sortingby Craig Raw · e0ee957c · Aug 19, 2026 · 3 filesMessage 50 · ThinInformational 24Details
Commit message · Craig Raw

detect legacy multisig descriptors case insensitively when warning about key sorting

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This commit fixes a minor user-facing bug in Sparrow Wallet where the app failed to recognize legacy multisig wallet descriptors if they used uppercase letters (for example, 'MULTI(' instead of 'multi('). As a result, Sparrow would not show its usual warning that it only supports BIP67-compatible sorted multisig wallets, and it would not automatically sort the public keys. The change makes the detection case-insensitive by using a regular expression pattern instead of a simple lowercase string check. This is a usability and correctness fix rather than a serious security vulnerability.

AI review queuedimprove max cosigner ui handling in settingsby Craig Raw · b99b880c · Aug 10, 2026 · 4 filesMessage 45 · ThinLow 27Details
Commit message · Craig Raw

improve max cosigner ui handling in settings

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 27/100

This commit tightens wallet validation in Sparrow Wallet. It replaces a simple validity check with a more detailed one that reports specific problems, and it prevents users from creating or loading wallets whose number of cosigners exceeds what the chosen Bitcoin script type supports. It also fixes UI slider behavior so the maximum cosigner count stays within allowed limits when the script type changes. The changes are defensive: they catch misconfigurations earlier and give clearer error messages, which reduces the chance of accidentally using an invalid or unsupported wallet.

AI review queuedresolve bip353 hrns over tcp via the socks proxy when one is configuredby Craig Raw · d9ad0618 · Aug 10, 2026 · 4 filesMessage 50 · ThinLow 38Details
Commit message · Craig Raw

resolve bip353 hrns over tcp via the socks proxy when one is configured

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 38/100

This commit changes Sparrow Wallet so that BIP353 human-readable payment names (like a Bitcoin email address) are resolved through the user's configured SOCKS proxy instead of directly over the internet. It also updates a related database field from seconds to milliseconds for storing key/seed creation times. The main security angle is privacy: without the proxy, DNS-style lookups for payment recipients could leak the recipient name and the user's IP address to DNS servers or observers. The change routes that traffic through Tor or another proxy if one is set. The database rename is a code-quality change and does not appear to be a security fix by itself.

AI review queuedclose remaining local dns resolution gaps when classifying hostnames and connecting via torby Craig Raw · 03222f20 · Aug 6, 2026 · 3 filesMessage 50 · ThinModerate 65Details
Commit message · Craig Raw

close remaining local dns resolution gaps when classifying hostnames and connecting via tor

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 65/100

This commit fixes privacy gaps in Sparrow Wallet when it connects through Tor or another proxy. Previously, the app could accidentally ask the computer's normal DNS resolver to translate server names, which could reveal which Bitcoin servers a user was trying to reach. It also could connect to local-network addresses directly even when a proxy was on, potentially bypassing Tor. The patch makes the app treat unknown hostnames as remote when a proxy is active and avoid resolving them locally, and it ensures Tor connections use the proxy for name resolution rather than the local system.

AI review queuedavoid deleting the backups of same-prefixed walletsby Craig Raw · b6ed4ba7 · Aug 5, 2026 · 2 filesMessage 50 · ThinLow 48Details
Commit message · Craig Raw

avoid deleting the backups of same-prefixed wallets

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 48/100

This commit fixes a bug in how Sparrow Wallet finds and deletes old wallet backups. Previously, the backup cleanup logic used loose pattern matching that could accidentally treat backups of one wallet as if they belonged to another wallet with a similar name. For example, a wallet named 'Savings' might incorrectly match backup files for 'SavingsX' or 'Savings.old'. The result could be that backups of a different wallet get deleted, or that cleanup of the intended wallet's backups fails. The patch replaces the loose prefix-and-date check with a strict regular expression that requires an exact wallet name, a complete 14-digit timestamp, and a matching file extension. New unit tests confirm that only correctly named backups are selected.

AI review queuedverify proof of work on chain tips and warn when a tip goes staleby Craig Raw · 5ccc4902 · Aug 5, 2026 · 5 filesMessage 60 · AdequateModerate 62Details
Commit message · Craig Raw

verify proof of work on chain tips and warn when a tip goes stale

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 62/100

This commit adds safety checks to the Bitcoin wallet Sparrow when it receives block-chain tip announcements from an Electrum server. It now verifies that the announced block header is properly formatted, not timestamped too far in the future, and meets the proof-of-work target encoded in the header itself. It also warns the user if the server stops sending new blocks for more than two hours, which can indicate a stale or malicious server. These changes reduce the risk of a hostile or malfunctioning server misleading the wallet about the state of the Bitcoin network.