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 19 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 queuedcompare multisig cosigner xpubs by public key and chain code when checking for duplicate keystoresby Craig Raw · 9e316f07 · Oct 12, 2026 · 2 filesMessage 50 · ThinLow 42Details
Commit message · Craig Raw

compare multisig cosigner xpubs by public key and chain code when checking for duplicate keystores

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 detects duplicate cosigner keys in multisig wallets. Previously it compared extended public keys (xpubs) using a full equality check, which may have treated xpubs with different metadata (such as different derivation paths or master fingerprints) as different even when they represented the same underlying public key. Now it compares only the raw public key and chain code. This could prevent a user from accidentally adding the same cosigner twice, or conversely could help catch cases where the same key is disguised with different xpub metadata. The commit itself does not explain whether this fixes a security bug or is just a robustness improvement.

AI review queuedignore a paynym search result that arrives after the search has changed, and stop enter replacing a pasted payment code search with its abbreviated displayby Craig Raw · 0340cdbe · Oct 5, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

ignore a paynym search result that arrives after the search has changed, and stop enter replacing a pasted payment code search with its abbreviated display

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 19/100

This commit fixes two minor user-interface timing glitches in Sparrow Wallet's PayNym (payment-code alias) search feature. First, it ignores a search result that arrives after the user has already typed something different. Second, it prevents pressing Enter from replacing a pasted full payment code with its shortened on-screen display. These are correctness/UX bugs, not direct theft-of-funds vulnerabilities, but in a wallet they could theoretically contribute to a user sending to the wrong recipient if the screen shows stale or truncated information.

AI review queuedrevalidate the send amount when payments are set from a uri opened externally or a spend event so insufficient and dust warnings showby Craig Raw · 8f47a8d1 · Oct 5, 2026 · 1 fileMessage 50 · ThinLow 27Details
Commit message · Craig Raw

revalidate the send amount when payments are set from a uri opened externally or a spend event so insufficient and dust warnings show

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 27/100

This commit fixes a UI bug in Sparrow Wallet's send form. When a payment amount was filled in automatically—such as when opening a Bitcoin payment link from another app or when triggered by a 'spend' event—the wallet did not re-run its amount checks. That meant warnings about sending too small an amount ('dust') or not having enough funds ('insufficient balance') might not appear. The fix adds a single call to revalidate the amount after auto-filling it, so the correct warnings are shown.

AI review queuedtake the bwt shutdown handle once across overlapping shutdowns, and do nothing in a shutdown that finds it takenby Craig Raw · a32e8653 · Oct 2, 2026 · 1 fileMessage 50 · ThinLow 29Details
Commit message · Craig Raw

take the bwt shutdown handle once across overlapping shutdowns, and do nothing in a shutdown that finds it taken

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 29/100

This commit fixes a race condition in how Sparrow Wallet shuts down its bundled Bitcoin Wallet Tracker (bwt) daemon. Previously, if two shutdown attempts overlapped, the same internal 'handle' could be used twice or cleared while still in use, which could crash the wallet or leave it in an inconsistent state. The fix makes the shutdown handle a one-time-use token and synchronizes access to it so only one shutdown can actually act.

AI review queuedalways rebuild the send transaction when a human readable name is pasted over the pay to addressby Craig Raw · 25db034c · Oct 2, 2026 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Craig Raw

always rebuild the send transaction when a human readable name is pasted over the pay to address

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 fixes a bug in Sparrow Wallet's 'Send' screen. Previously, if you pasted a human-readable payment name (like a DNS payment alias) over an already-filled recipient address, the wallet sometimes kept the old transaction details instead of rebuilding it for the new name. The change ensures the transaction is always recalculated after a name is pasted, so the wallet doesn't accidentally prepare a payment to the wrong recipient while the name is still resolving.

AI review queuedclear the max selection and revalidate the amount when a payment uri sets the send amountby Craig Raw · 4c085e00 · Oct 2, 2026 · 1 fileMessage 50 · ThinLow 32Details
Commit message · Craig Raw

clear the max selection and revalidate the amount when a payment uri sets the send amount

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 32/100

This commit fixes a UI bug in Sparrow Wallet's send screen. When a user clicked a Bitcoin payment link (a 'payment URI') that included a specific amount, the wallet could leave the 'send maximum' option turned on. That combination could lead to an incorrect or confusing transaction being prepared. The patch now clears the 'send maximum' setting and re-checks the amount whenever a payment URI supplies its own amount.

AI review queuedleave the wallet file encryption unchanged in a queued update where the storage key has changed since it was queuedby Craig Raw · 8b440c44 · Oct 2, 2026 · 3 filesMessage 50 · ThinModerate 58Details
Commit message · Craig Raw

leave the wallet file encryption unchanged in a queued update where the storage key has changed since it was queued

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 58/100

This commit fixes a bug in Sparrow Wallet where a background save of a wallet file could use the wrong encryption password. If a user added or removed a wallet password while another save was still waiting in a queue, the queued save could later encrypt or decrypt the file with the old setting, potentially leaving the wallet file unencrypted when it should be encrypted, or encrypted with a password the user no longer expects. The fix makes the queued save check the current encryption key before deciding whether to change the file's encryption.

AI review queuedcormorant: replace a transaction entry moved within its block, hold entries sharing a block position, and stop relisting unconfirmed entries as updatesby Craig Raw · a185c91d · Oct 2, 2026 · 3 filesMessage 50 · ThinLow 33Details
Commit message · Craig Raw

cormorant: replace a transaction entry moved within its block, hold entries sharing a block position, and stop relisting unconfirmed entries as updates

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 33/100

This commit fixes bookkeeping bugs in how Sparrow Wallet tracks Bitcoin transactions when they move around in a block or sit unconfirmed. Before the fix, the wallet could report the same transaction as a new 'update' every time it was polled, even though nothing had changed. In rare cases after a blockchain reorganization, a transaction that changed position in a block might not be recorded correctly, or two transactions sharing the same temporary position could be handled wrong. The patch makes the wallet store entries more carefully and adds tests for these scenarios. There is no direct evidence this is exploitable by an attacker, but it could cause incorrect wallet state or missed notifications.

AI review queuedstop a terminal server test left with back or done, and leave services stopped when tor starts after going offlineby Craig Raw · ea696edb · Oct 2, 2026 · 2 filesMessage 60 · AdequateLow 34Details
Commit message · Craig Raw

stop a terminal server test left with back or done, and leave services stopped when tor starts after going offline

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 · Low 34/100

This commit fixes two reliability bugs in the Sparrow Wallet desktop app. First, it prevents a server-connection test from continuing to run in the background after the user leaves the test screen, which could otherwise connect to the wrong server or interfere with later settings. Second, it stops the wallet from automatically restarting network services when the Tor privacy tool comes back online if the user has intentionally gone offline. These are stability and privacy fixes rather than remote-hack vulnerabilities.

AI review queuedmatch the amounts in rbf insufficient fee broadcast errors without backtrackingby Craig Raw · 3f36bccf · Oct 1, 2026 · 1 fileMessage 50 · ThinInformational 16Details
Commit message · Craig Raw

match the amounts in rbf insufficient fee broadcast errors without backtracking

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 16/100

This commit tightens two text-parsing regular expressions in Sparrow Wallet that read error messages returned by Bitcoin nodes when a Replace-By-Fee (RBF) transaction is rejected for an insufficient fee. The change prevents the regex from backtracking into earlier digits in the error string, which could previously cause the wallet to extract the wrong fee amounts and display misleading guidance to the user. It is a robustness fix for user-facing diagnostics, not a cryptographic or network vulnerability.

AI review queuedreplace a server alias with its host when the ssl switch differs from the aliased server, and keep the alias when opening server settingsby Craig Raw · e6efcef3 · Oct 1, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · Craig Raw

replace a server alias with its host when the ssl switch differs from the aliased server, and keep the alias when opening server settings

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 · Low 35/100

This commit fixes a UI bug in Sparrow Wallet's server settings. When a user had saved a server under a friendly nickname (alias) and then changed the SSL/TLS switch or port, the wallet could end up trying to connect to the wrong server because the alias still pointed to the original protocol or port. The change makes the alias resolve to the actual server host when the connection protocol or port no longer matches the saved alias, preventing accidental misconnections.

AI review queuedremove incomplete transaction entries before calculating the wallet balance and leave them out of the new transactions notificationby Craig Raw · 711ded46 · Oct 1, 2026 · 2 filesMessage 50 · ThinLow 46Details
Commit message · Craig Raw

remove incomplete transaction entries before calculating the wallet balance and leave them out of the new transactions notification

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 46/100

This commit fixes a bug in the Sparrow Bitcoin wallet where the wallet could temporarily report an incorrect balance and send misleading 'new transaction' notifications. The problem happened when a transaction moving funds between two of the user's own addresses was partially known to the wallet—specifically, when the receiving side was seen before the spending side. Before this fix, the wallet would count the incoming money as new funds and notify the user, even though no actual new money had arrived. The fix delays both balance updates and notifications until the full transaction picture is available.

AI review queuedcheck stored transaction block hashes against the header store when a wallet is first fetchedby Craig Raw · ae0d1ff0 · Oct 1, 2026 · 2 filesMessage 50 · ThinModerate 68Details
Commit message · Craig Raw

check stored transaction block hashes against the header store when a wallet is first fetched

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 68/100

This commit fixes a gap in Sparrow Wallet's protection against Bitcoin blockchain reorganizations ('reorgs'). Previously, if a wallet was closed while a reorg happened, the wallet could reopen still believing an old, replaced block proved its transaction—because the server kept reporting the same block height. The change now compares stored transaction block hashes against the local header store when a wallet is first fetched, and re-proves any transaction whose recorded block no longer matches the chain. This prevents the wallet from displaying a transaction as confirmed when the proof is actually stale or invalid.

AI review queuedapply the wallet lock to label import, sweep and show paynym, and to password prompts and unlocks completing after the wallet was lockedby Craig Raw · 26a06c9e · Oct 1, 2026 · 8 filesMessage 50 · ThinLow 46Details
Commit message · Craig Raw

apply the wallet lock to label import, sweep and show paynym, and to password prompts and unlocks completing after the wallet was locked

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 · Low 46/100

This commit fixes a timing issue in the Sparrow Bitcoin wallet where a user could still perform sensitive actions on a wallet that had been locked while a password prompt or background unlock was in progress. The patch makes sure that if a wallet is locked before the password is entered or the unlock finishes, the action is cancelled or blocked. It also disables certain wallet features (label import, sweeping private keys, and showing a PayNym) when the wallet is locked. This is a defensive hardening fix rather than a remote-exploitable vulnerability.

AI review queueddetermine whether the wallet lock screen requires a password from the storage encryption key on each lock and unlockby Craig Raw · 17ab7f08 · Oct 1, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · Craig Raw

determine whether the wallet lock screen requires a password from the storage encryption key on each lock and unlock

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 · Low 35/100

This commit changes how Sparrow Wallet decides whether to show a password-protected lock screen. Previously, the app checked once when wallet settings changed and cached that result. Now it re-checks every time the wallet is locked or unlocked by looking directly at the storage encryption key. This is a defensive fix: it reduces the chance that the lock screen might be skipped or incorrectly shown if the wallet's encryption state changes without the app noticing.

AI review queuedskip recipient parsing of the send tab pay to field while it shows the name of a selected paynymby Craig Raw · 8b9074e0 · Oct 1, 2026 · 1 fileMessage 50 · ThinInformational 24Details
Commit message · Craig Raw

skip recipient parsing of the send tab pay to field while it shows the name of a selected paynym

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 UI bug in Sparrow Wallet's 'Send' tab. When a user selected a PayNym (a privacy-focused contact name), the wallet was still trying to parse that display name as if it were a Bitcoin address, payment code, or web address. This could trigger unnecessary network lookups, show confusing error dialogs, or in rare cases change the intended recipient. The fix simply skips all that parsing while the field is showing a PayNym name.

AI review queuedremove the redundant merkle proof flag from the cormorant server capabilityby Craig Raw · c2555d22 · Oct 1, 2026 · 2 filesMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

remove the redundant merkle proof flag from the cormorant server capability

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 17/100

This commit removes a special flag telling Sparrow not to request cryptographic transaction proofs when connected to a backend called 'cormorant'. The change makes cormorant behave like other local-node backends, which is described as removing a redundant distinction. It is a small cleanup with no obvious security bug being fixed.

AI review queueddisable the sign button in the sign message dialog while an encrypted wallet is decryptingby Craig Raw · 31de9cbc · Oct 1, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · Craig Raw

disable the sign button in the sign message dialog while an encrypted wallet is decrypting

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 user-interface timing issue in Sparrow Wallet's 'Sign Message' feature. When a user tried to sign a message with an encrypted wallet, the 'Sign' button stayed active while the wallet was still decrypting in the background. If the user clicked it again during that brief window, the app could attempt to sign twice or behave unexpectedly. The patch now disables the Sign button while decryption is in progress and re-enables it only when decryption finishes or fails.

AI review queuedturn the server toggle off and retry when the ping finds the server connection closedby Craig Raw · 4cefae3f · Sep 30, 2026 · 1 fileMessage 50 · ThinLow 25Details
Commit message · Craig Raw

turn the server toggle off and retry when the ping finds the server connection closed

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 25/100

This tiny change alters what happens when Sparrow Wallet's background ping notices the connection to an Electrum server has dropped. Previously the code simply closed the local connection. Now it throws an explicit 'connection lost' error, which the surrounding logic is designed to catch, flip the server toggle off, and retry. The intent appears to be a reliability fix: make the wallet recover automatically from a dropped server connection rather than silently staying in a broken state.

AI review queuedreplace the qr display density toggle with low, medium and high levels that produce the same qr code version for ur and bbqrby Craig Raw · 344895b3 · Sep 29, 2026 · 4 filesMessage 50 · ThinInformational 18Details
Commit message · Craig Raw

replace the qr display density toggle with low, medium and high levels that produce the same qr code version for ur and bbqr

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 18/100

This commit changes how Sparrow Wallet lets users pick QR code density when displaying animated QR codes. It replaces a two-option toggle (Normal/Low) with three levels (Low/Medium/High) and makes sure both supported QR formats (UR and BBQr) produce QR codes of the same physical size at each level. It also adds a test to verify that consistency. There is no security vulnerability visible in the change.

AI review queuedremove events no longer posted along with their subscribersby Craig Raw · ee2daf94 · Sep 28, 2026 · 11 filesMessage 50 · ThinInformational 12Details
Commit message · Craig Raw

remove events no longer posted along with their subscribers

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 12/100

This commit removes several unused event classes and their corresponding event listeners from the Sparrow Wallet codebase. It is a cleanup change: the events were no longer being posted anywhere, so the code that subscribed to them was dead code. There is no indication this change fixes or introduces a security vulnerability.

AI review queuedremove the terminal saving and loading dialogs and show an error when saving a new wallet or opening a wallet failsby Craig Raw · 78025f22 · Sep 28, 2026 · 3 filesMessage 50 · ThinLow 37Details
Commit message · Craig Raw

remove the terminal saving and loading dialogs and show an error when saving a new wallet or opening a wallet fails

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 37/100

This commit fixes several small but real bugs in Sparrow Wallet's terminal (command-line) interface. It prevents the app from crashing with a NullPointerException when an error message is missing, makes sure password memory is wiped even when wallet opening fails, and ensures loading/saving dialogs close properly when errors occur. These are reliability and minor security-hygiene fixes rather than a major vulnerability patch.

AI review queuedcompare rewritten keystore derivation paths when checking for a single derivation path in the terminal receive dialogby Craig Raw · 2ed6e385 · Sep 28, 2026 · 1 fileMessage 50 · ThinInformational 23Details
Commit message · Craig Raw

compare rewritten keystore derivation paths when checking for a single derivation path in the terminal receive dialog

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 23/100

This is a small UI consistency fix in Sparrow Wallet's terminal (command-line) receive dialog. It changes how the wallet checks whether all key storage locations (keystores) use the same derivation path. Previously the comparison used raw string paths, which could differ in format even when logically identical. Now it compares rewritten/normalized paths. The effect is mostly cosmetic: it determines whether the terminal receive screen shows one derivation path or multiple. There is no direct evidence this enables theft of funds or unauthorized transactions.

AI review queuedadd verification on additional satscard, tapsigner and satschip operationsby Craig Raw · 7c7086f0 · Sep 28, 2026 · 2 filesMessage 60 · AdequateLow 46Details
Commit message · Craig Raw

add verification on additional satscard, tapsigner and satschip operations

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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 46/100

This commit adds extra verification steps when Sparrow Wallet talks to certain physical Bitcoin cards (Satscard, Tapsigner, Satschip). It makes the wallet check the card's authenticity before performing sensitive operations like reading an address or loading the keystore. The change looks like a defensive hardening patch, but the commit message gives no details about what specific attack or failure it prevents.

AI review queuedcheck a paynym retrieved by payment code matches the requested codeby Craig Raw · b7fb756c · Sep 28, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

check a paynym retrieved by payment code matches the requested code

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 adds a safety check in Sparrow Wallet's PayNym feature. PayNyms are human-readable names linked to Bitcoin payment codes. Previously, when a user looked up a PayNym by its payment code, the wallet would trust whatever payment code the PayNym server returned. The fix verifies that the returned payment code actually matches the one requested, preventing a malicious or compromised server from silently substituting a different payment code. The UI now also displays the wallet's own payment code rather than the server-returned one.