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 47 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 queuedgive the transaction tab a copy of a wallet transaction, and leave locktimes and input sequences unchanged as the tab opensby Craig Raw · 44e7ee97 · Nov 19, 2026 · 4 filesMessage 50 · ThinModerate 61Details
Commit message · Craig Raw

give the transaction tab a copy of a wallet transaction, and leave locktimes and input sequences unchanged as the tab opens

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

This commit fixes a bug in the Sparrow Wallet desktop app where merely opening a transaction to view it could silently alter the wallet's stored copy of that transaction. Previously, the transaction tab shared the same in-memory object as the wallet, and the tab's user-interface setup code would overwrite locktime and input sequence values with defaults. The fix makes a defensive copy before opening the tab and only writes changes when the user actually interacts with the controls.

Security candidateopen the device signing dialog for a card keystore in a multisig wallet that also holds seed and watch only keystoresby Craig Raw · 3ef0d308 · Nov 19, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

open the device signing dialog for a card keystore in a multisig wallet that also holds seed and watch only keystores

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 19/100

This commit fixes a UI workflow bug in Sparrow Wallet. Previously, when signing a transaction with a multisig wallet that mixed a hardware card keystore, a software seed keystore, and a watch-only keystore, the device signing dialog would not open. The change ensures the dialog opens so the user can sign with the card device. It is a functional bug fix rather than a security vulnerability.

AI review queuedupgrade tern to v1.1.3 to point to rpcallowip when bitcoin core closes the rpc connection as the request is sentby Craig Raw · 5cc8e9b2 · Nov 19, 2026 · 4 filesMessage 50 · ThinLow 33Details
Commit message · Craig Raw

upgrade tern to v1.1.3 to point to rpcallowip when bitcoin core closes the rpc connection as the request is sent

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 updates a small internal library (tern) used by Sparrow Wallet to talk to Bitcoin Core. The change makes Sparrow show a clearer, more accurate error message when Bitcoin Core rejects or closes the remote-control (RPC) connection, specifically guiding users to check Bitcoin Core's rpcallowip setting. It also adds handling for a 'Connection reset' socket error. The patch is defensive and improves diagnostics rather than fixing a code-execution vulnerability.

AI review queuedomit bound values from wallet database error messages, and the entered text from the terminal descriptor import logby Craig Raw · 98173c6a · Nov 18, 2026 · 3 filesMessage 50 · ThinLow 49Details
Commit message · Craig Raw

omit bound values from wallet database error messages, and the entered text from the terminal descriptor import log

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

This commit removes sensitive information from two log/error locations: it stops H2 database error messages from including the actual data values involved in a failed SQL statement, and it stops terminal wallet logs from recording the exact text a user typed when importing a wallet descriptor. These changes reduce the risk that passwords, keys, or other private wallet data accidentally end up in application logs where they could be read by other users or attackers.

AI review queuedkeep the entered address for a payment when showing its cached payment instruction name in the send tab and send to manyby Craig Raw · 77132217 · Nov 18, 2026 · 3 filesMessage 50 · ThinLow 35Details
Commit message · Craig Raw

keep the entered address for a payment when showing its cached payment instruction name in the send tab and send to many

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 bug in the Sparrow Bitcoin wallet where a saved payment recipient could lose its actual Bitcoin address when reloaded. Previously, if a payment had a human-readable name (like an email-style payment alias) cached, the wallet would display only that name and discard the underlying address. The fix keeps both the name and the address, so the wallet sends funds to the correct destination instead of potentially resolving the name again to a different or stale address. There is no direct evidence this was exploited or treated as a security vulnerability by the project.

AI review queuedparse a multisig setup file line by line on newlines only, with case-insensitive labels, a strict policy value and no repeated policy or formatby Craig Raw · 7df6f358 · Nov 18, 2026 · 2 filesMessage 50 · ThinLow 40Details
Commit message · Craig Raw

parse a multisig setup file line by line on newlines only, with case-insensitive labels, a strict policy value and no repeated policy or format

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 tightens how Sparrow reads Coldcard multisig setup files. It now splits files only on newline characters, rejects hidden control characters, makes labels case-insensitive, enforces a strict 'N of M' policy format, and refuses files that repeat the policy or format lines. These changes reduce the chance that a maliciously crafted file could trick Sparrow into importing the wrong wallet configuration, but the commit itself is a hardening fix rather than a confirmed exploit patch.

AI review queuedimport a descriptor wrapped over several lines or followed by other text in a pdf, and refuse ec or duplicate keys in a scanned multisigby Craig Raw · 689f9fb0 · Nov 18, 2026 · 5 filesMessage 50 · ThinLow 46Details
Commit message · Craig Raw

import a descriptor wrapped over several lines or followed by other text in a pdf, and refuse ec or duplicate keys in a scanned multisig

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 two separate issues in Sparrow Wallet. First, it improves importing of Bitcoin wallet descriptors from PDF files so that descriptors split across multiple lines, or followed by extra text, are read correctly. Second, it makes QR code scanning of multisig wallet setups safer by rejecting raw EC (single-key) keys and duplicate extended public keys, which could otherwise lead to malformed or insecure wallet configurations.

AI review queuedmark a transaction tab height unverified when its proof cannot be obtained from a connected server, and fetch it again after the server changesby Craig Raw · 96735916 · Nov 18, 2026 · 6 filesMessage 50 · ThinLow 49Details
Commit message · Craig Raw

mark a transaction tab height unverified when its proof cannot be obtained from a connected server, and fetch it again after the server changes

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

This commit fixes how Sparrow Wallet handles transaction block-height information that a connected Electrum server reports but cannot prove with a cryptographic Merkle proof. Previously, if the server returned an empty or invalid proof, the wallet might still treat the reported height as verified. After the change, an unproven height is marked as 'server reported only' and the wallet re-fetches the proof when the server connection changes, rather than silently trusting the old value. This reduces the chance that a user is misled about whether a transaction is confirmed.

AI review queuedkeep a master wallet entry for a transaction otherwise held only by a paynym wallet, so history continues to syncby Craig Raw · 6e429598 · Nov 18, 2026 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · Craig Raw

keep a master wallet entry for a transaction otherwise held only by a paynym wallet, so history continues to sync

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100

This commit fixes a wallet-history synchronization bug in Sparrow Wallet that occurs when a master wallet and its nested BIP47 'paynym' wallet share a transaction. Previously, if the nested wallet learned about a transaction first, the master wallet might never record it, causing its balance and transaction history to stop updating correctly. The patch ensures the master wallet keeps its own copy of such transactions and only processes mempool entries that actually belong to the wallet being refreshed.

AI review queuedopen the wallet file that was validated, rejecting a wallet file with an empty nameby Craig Raw · 389ac270 · Nov 18, 2026 · 3 filesMessage 50 · ThinHigh 70Details
Commit message · Craig Raw

open the wallet file that was validated, rejecting a wallet file with an empty name

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 · High 70/100

This commit fixes a security bug in how Sparrow Wallet opens its H2 database files. Previously, the wallet validated one file but then opened a different file for the database connection, and it allowed wallet files with an empty name. A specially crafted wallet file with an empty name could trick the app into connecting to an attacker-controlled external H2 database, potentially leaking or manipulating wallet data. The patch makes sure the validated file is the one actually opened and rejects empty-named wallet files.

AI review queuedavoid an error labelling silent payment outputs from an open transaction tab before the wallet has fetched their transactionby Craig Raw · 6a1520c2 · Nov 18, 2026 · 1 fileMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

avoid an error labelling silent payment outputs from an open transaction tab before the wallet has fetched their transaction

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 is a small bug-fix patch that prevents the Sparrow Wallet app from crashing with a NullPointerException when a user labels a 'silent payment' output while the wallet hasn't yet finished loading the related transaction. It adds a simple null check before using a transaction object. There is no indication this is a security vulnerability or that it can be exploited by an attacker.

AI review queuedstop the external proxy status check while offline, and restart it on going onlineby Craig Raw · 5551284e · Nov 18, 2026 · 2 filesMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

stop the external proxy status check while offline, and restart it on going online

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 fixes a minor behavior issue in the Sparrow Wallet desktop app. When the user's internet connection was offline, the app would keep trying to check the status of an external Tor/proxy connection and could show confusing or incorrect status icons. The change simply pauses the proxy status check while offline and refreshes the Tor icon when the app comes back online. There is no direct evidence this is a security vulnerability, and no exploit path is described.

AI review queuedsave a bitcoin core server chosen or scanned that differs only in protocolby Craig Raw · 9eb7519e · Nov 18, 2026 · 1 fileMessage 50 · ThinInformational 23Details
Commit message · Craig Raw

save a bitcoin core server chosen or scanned that differs only in protocol

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 bug-fix commit in Sparrow Wallet's settings screen. When a user selected or scanned a Bitcoin Core server that was identical to the currently displayed one except for the protocol (for example, http vs https), the on-screen text fields did not change. Because Sparrow saves server settings only when those text fields change, the new protocol choice was silently lost. The fix explicitly saves the server configuration in that specific case. It is a data-loss/UX bug rather than a direct security vulnerability, though using the wrong protocol could indirectly affect connection security.

AI review queuedselect the saved camera by its id before falling back to its name, so that a camera with the same name is not opened in its placeby Craig Raw · 1f3c2c50 · Nov 18, 2026 · 1 fileMessage 62 · AdequateInformational 23Details
Commit message · Craig Raw

select the saved camera by its id before falling back to its name, so that a camera with the same name is not opened in its place

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100

This commit fixes a webcam selection bug in Sparrow Wallet. Previously, if two cameras had the same name, the wallet might open the wrong camera. Now it first tries to match the saved camera by its unique ID, and only falls back to matching by name if no ID match is found. This is a correctness/usability fix rather than a clear-cut security vulnerability, though opening the wrong camera could have minor privacy implications.

AI review queuedreport the card status when a satochip extended key request does not succeed instead of parsing the responseby Craig Raw · 53c2e162 · Nov 18, 2026 · 2 filesMessage 50 · ThinLow 42Details
Commit message · Craig Raw

report the card status when a satochip extended key request does not succeed instead of parsing the response

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

This commit fixes a bug in how Sparrow Wallet reads responses from Satochip hardware cards when fetching an extended Bitcoin public key. Previously, if the card reported an error, the app would blindly try to interpret the error response as a valid key. Now it first checks whether the card signaled success, and if not, throws a clear error containing the card's status code. The change is defensive and improves error handling, but it is not obviously exploitable as a security vulnerability on its own.

AI review queuedfreeze and unfreeze the row whose menu was opened from the keyboard when it is not in the selection, and leave spent outputs in a selection unchangedby Craig Raw · e36312e4 · Nov 18, 2026 · 1 fileMessage 50 · ThinInformational 24Details
Commit message · Craig Raw

freeze and unfreeze the row whose menu was opened from the keyboard when it is not in the selection, and leave spent outputs in a selection unchanged

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 small user-interface bug in the Sparrow bitcoin wallet. When a user opened the right-click menu for a UTXO row using the keyboard (for example, to freeze or spend it), the wallet could apply the action to the wrong set of rows if the focused row was not part of the current selection. It also makes sure already-spent outputs are left alone when freezing or unfreezing a group selection. The change is a usability fix rather than a cryptographic or network security flaw.

AI review queuedapply hide amounts to the transaction hex on the input and output views in the light theme, and to unselected output values when an output is selectedby Craig Raw · d1a22668 · Nov 18, 2026 · 5 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

apply hide amounts to the transaction hex on the input and output views in the light theme, and to unselected output values when an output is selected

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

This commit is a UI polish fix for the 'hide amounts' privacy feature in Sparrow Wallet. It makes sure that when a user has chosen to hide transaction amounts, those amounts stay hidden in the transaction hex view and for unselected outputs. There is no security vulnerability here—just a consistency fix for on-screen display.

AI review queuedkeep the results of every other page when one page of a batched history, mempool, transaction, block header or block stats request returns an errorby Craig Raw · 4151ee9e · Nov 17, 2026 · 4 filesMessage 50 · ThinLow 36Details
Commit message · Craig Raw

keep the results of every other page when one page of a batched history, mempool, transaction, block header or block stats request returns an error

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

This commit fixes a bug in how Sparrow Wallet talks to Electrum servers when asking for wallet history, mempool, transactions, block headers, or block stats in large batches. Previously, if one 'page' of the batched request failed, the wallet would throw away all results from later pages. After the fix, it keeps the successful results from every page and only marks or drops the specific items that failed. This makes the wallet more reliable and prevents it from missing transactions or showing an incomplete wallet history when a server has a transient error.

AI review queuedomit the copy value actions from the transaction diagram context menus when amounts are hiddenby Craig Raw · 5242c529 · Nov 17, 2026 · 1 fileMessage 50 · ThinInformational 21Details
Commit message · Craig Raw

omit the copy value actions from the transaction diagram context menus when amounts are hidden

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

This commit removes the 'Copy Value' right-click menu options from transaction diagrams when the user has turned on the 'Hide amounts' privacy setting. Previously, even with amounts hidden on screen, a user could still right-click a transaction label and copy the exact value to the clipboard, which would leak the supposedly hidden amount. This is a minor privacy/UI consistency fix, not a remote attack.

AI review queuedrestart the stale tip warning clock only when the server announces a block it has not announced beforeby Craig Raw · efee1baa · Nov 17, 2026 · 3 filesMessage 50 · ThinModerate 51Details
Commit message · Craig Raw

restart the stale tip warning clock only when the server announces a block it has not announced before

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 change fixes how Sparrow Wallet decides whether its connected Bitcoin server is still keeping up with the blockchain. Previously, any block announcement from the server—even a repeat of the same block—would reset the 'stale tip' timer, potentially hiding a server that had stopped following the chain. Now the timer only resets when the server announces a block with a new hash it hasn't announced before. This makes the stale-tip warning more reliable, which matters because a stale or malicious server could feed outdated or inconsistent transaction information to the wallet.

AI review queuedswitch the send amount and fee fields to btc when a btc amount below 1 is pasted into them in sats, and restore the default unit when the form is clearedby Craig Raw · 2971002a · Nov 17, 2026 · 3 filesMessage 50 · ThinInformational 21Details
Commit message · Craig Raw

switch the send amount and fee fields to btc when a btc amount below 1 is pasted into them in sats, and restore the default unit when the form is cleared

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

This commit changes how Sparrow Wallet handles pasted amounts in the send and fee fields. If a user has the wallet set to display amounts in satoshis (sats) and pastes a small Bitcoin amount written as BTC (for example, '0.001'), the wallet now automatically switches the field to BTC mode so the value is interpreted correctly. It also restores the default unit when the form is cleared. The change is a usability improvement to prevent users from accidentally sending the wrong amount because of unit confusion. There is no direct evidence in the commit of a security vulnerability or malicious behavior.

AI review queuedadd test coverage for multisig ur output descriptor exportsby Aaron Leeb · 46684fef · Nov 17, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Aaron Leeb

add test coverage for multisig ur output descriptor exports

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 · Informational 15/100

This commit only adds new automated tests that check how Sparrow Wallet exports multisig wallet descriptors in a standardized QR-code-friendly format (called 'UR'). It does not change any production code, so it cannot introduce a security vulnerability or fix one.

Security candidateinclude the non-witness utxo in psbts for jade keystores, and in the qr display when the psbt has more than one inputby Craig Raw · 0aaec9cf · Nov 17, 2026 · 1 fileMessage 50 · ThinLow 38Details
Commit message · Craig Raw

include the non-witness utxo in psbts for jade keystores, and in the qr display when the psbt has more than one input

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Low 38/100

This commit updates a submodule called 'drongo' inside the Sparrow Wallet project. The visible change is just a pointer to a newer version of that submodule. The commit message says the update is meant to include extra transaction data (the 'non-witness utxo') in PSBTs for Jade hardware wallets, and in QR codes when a PSBT has more than one input. That extra data helps a hardware wallet verify it is signing the right transaction, which can be a security-relevant improvement. However, the actual code changes are not shown in this diff, because only the submodule reference changed. We therefore cannot directly verify what was fixed or whether it closes a known vulnerability.

Security candidateaccept 64 byte sighash default taproot signatures when verifying bip322 messagesby Craig Raw · 8717f316 · Nov 17, 2026 · 1 fileMessage 50 · ThinLow 39Details
Commit message · Craig Raw

accept 64 byte sighash default taproot signatures when verifying bip322 messages

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialsigning boundary
AI analysis · Low 39/100

This commit updates a submodule called 'drongo' inside the Sparrow Wallet project. The stated purpose is to allow 64-byte default Taproot signatures when verifying BIP322 signed messages. BIP322 is a standard way to prove ownership of a Bitcoin address by signing a message. Without seeing the actual code changes inside the submodule, we cannot fully assess the security implications, but the change appears to be a compatibility/correctness fix for signature verification rather than an obvious vulnerability patch.

Security candidatewiden stored transactions to the consensus maximum size and skip larger ones fetched from the serverby Craig Raw · 485eddb6 · Nov 17, 2026 · 3 filesMessage 50 · ThinLow 49Details
Commit message · Craig Raw

widen stored transactions to the consensus maximum size and skip larger ones fetched from the server

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
consensus or confidential-proof validationsigning or wallet path
AI analysis · Low 49/100

This commit makes Sparrow Wallet better handle unusually large Bitcoin transactions. It widens the database column that stores raw transaction bytes from 1 MB to 4 MB (the largest size Bitcoin consensus allows), and tells the wallet to skip any transaction fetched from an Electrum server that is larger than that maximum. It also avoids treating a special 'unfetchable' placeholder transaction as a real transaction when building wallet history. The changes appear defensive: they prevent the wallet from crashing or misbehaving when it encounters oversized transactions, and stop a malicious or buggy server from feeding a response larger than a valid Bitcoin transaction.