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 48 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 queueddocument building v2.5.3 to v2.5.6 with lenient dependency verification, as two pom files were later republished to maven central with additional metadataby Craig Raw · 6a83c9a5 · Nov 22, 2026 · 1 fileMessage 60 · AdequateInformational 18Details
Commit message · Craig Raw

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

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 validationdocumentation-only discountsecond-pass: broader security terminology
AI analysis · Informational 18/100

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 harmless checksum mismatch. The documentation tells builders how to use a lenient verification mode and to confirm only those two POM files differ. There is no code change and no indication the JAR files or application behavior changed.

AI review queuedwarn 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 addressby Craig Raw · 08f32515 · Nov 21, 2026 · 3 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

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

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 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, testnet instead of mainnet). Previously, the wallet incorrectly told the user that no address was found. Now it clearly warns that the address belongs to a different network. This is a defensive fix that helps prevent users from accidentally sending funds to an incompatible address or being confused by misleading error text.

AI review queuedskip the keepalive ping while another request is awaiting its responseby Craig Raw · 4df18311 · Nov 21, 2026 · 3 filesMessage 50 · ThinLow 26Details
Commit message · Craig Raw

skip the keepalive ping while another request is awaiting its 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 pathsecond-pass: security-sensitive path
AI analysis · Low 26/100

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 pending request and waste a full synchronization cycle. The fix improves responsiveness and reduces wasted network round-trips, but it is not a direct fix for a remote exploit or data breach.

AI review queuedwait 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 onceby Craig Raw · 96d217cf · Nov 20, 2026 · 4 filesMessage 50 · ThinLow 38Details
Commit message · Craig Raw

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

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 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 halve the amount of data requested. The new behavior waits longer for a slow server instead of resending, only halves the data size when a request truly goes unanswered, and retries the keep-alive ping only once instead of five times. This is a robustness fix that reduces unnecessary load on servers and avoids degrading performance for slow but working servers. There is no direct evidence in the commit that this fixes a security vulnerability, but the change touches timeout and retry logic that could affect denial-of-service exposure and resource consumption.

AI review queuedreduce 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 900by Craig Raw · 86e52311 · Nov 20, 2026 · 17 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

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

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 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-relevant change here—no cryptography, networking, wallet logic, or data handling is modified.

AI review queuedcheck 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 tipby Craig Raw · f7357906 · Nov 20, 2026 · 2 filesMessage 50 · ThinModerate 61Details
Commit message · Craig Raw

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

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 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 the new tip, Sparrow could wrongly reject valid proofs as false. The fix makes Sparrow reconcile its stored block headers with the server's chain before marking a proof as failed. This reduces the chance of a server tricking the wallet into thinking a real transaction is unconfirmed or on the wrong chain, which could affect balance display or trust decisions.

AI review queueddecide whether a border wallets grid is hex from all of its cells rather than the selected onesby Craig Raw · 0d4f1482 · Nov 19, 2026 · 1 fileMessage 50 · ThinLow 33Details
Commit message · Craig Raw

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

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 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 pick cells that looked like ordinary decimal numbers, the app treated the whole grid as decimal and looked up the wrong BIP39 words, which could produce an incorrect wallet/seed. The fix now decides the grid type by examining all filled cells, so a hex grid is correctly recognized even when the selected cells contain only decimal-looking digits. This is a correctness/reliability fix with possible security implications for wallet recovery accuracy, but it is not an obvious remote-exploitable vulnerability.

AI review queuedleave qr codes that zbar can only return as transcoded text to the other scannersby Craig Raw · 0c28eafe · Nov 19, 2026 · 2 filesMessage 50 · ThinLow 43Details
Commit message · Craig Raw

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

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

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 ZBar's result when the content is plain printable text; otherwise it lets another scanner try. This could prevent wallet data from being misread when scanning QR codes containing binary or non-ASCII data.

AI review queuedsave the freeze status and labels of nested wallet outputs to the wallet that stores themby Craig Raw · 5c47c3a4 · Nov 19, 2026 · 11 filesMessage 50 · ThinLow 27Details
Commit message · Craig Raw

save the freeze status and labels of nested wallet outputs to the wallet that stores 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 · Low 27/100

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 against the master wallet even if the coin actually belonged to a nested wallet. The patch makes sure the freeze status and label are saved to the wallet that truly owns the coin. It is a correctness and data-integrity fix rather than a remote hack, but it could affect which coins are spendable or how balances are displayed.

Security candidatekeep the encrypted master secret of imported slip39 shares, so that the wallet decrypts it with any passphrase as the shares doby Craig Raw · 9b998a78 · Nov 19, 2026 · 3 filesMessage 62 · AdequateModerate 58Details
Commit message · Craig Raw

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

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
access controlsigning or wallet path
AI analysis · Moderate 58/100

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 import time and stored the resulting master secret. That meant if the user later opened the wallet with a different passphrase, the wallet would derive the wrong keys. The change keeps the master secret in its encrypted form, so any passphrase works the same way the original SLIP39 shares do. This is a correctness fix for passphrase handling in SLIP39 wallets.

AI review queuedkeep the monospaced font of utxo addresses when the table is refreshedby Craig Raw · 868fa081 · Nov 19, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

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

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 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.

AI review queuedrefuse 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 editorby Craig Raw · 3d2fbac4 · Nov 19, 2026 · 10 filesMessage 50 · ThinLow 46Details
Commit message · Craig Raw

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

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 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 'receive' and 'change' chains used by most wallets. This is a defensive change: non-standard derivation paths could previously be accepted silently, which might let a malicious or malformed descriptor make Sparrow derive addresses the user didn't expect, potentially hiding funds or tricking the user into sending to attacker-controlled addresses.

AI review queuedapply the child derivations of keys in scanned output descriptors, and refuse those that do not derive on the standard chainsby Craig Raw · 6a000160 · Nov 19, 2026 · 3 filesMessage 50 · ThinModerate 58Details
Commit message · Craig Raw

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

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 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 generate receiving and change addresses. The fix applies those child derivations consistently and rejects descriptors whose derivation paths are not on the standard receive/change chains. This prevents a malicious or malformed descriptor from silently importing a wallet that derives addresses in an unexpected way, which could lead to funds being sent to addresses the user does not control or cannot easily recover.

Security candidaterefuse 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 descriptorby Craig Raw · 97742cab · Nov 19, 2026 · 8 filesMessage 55 · ThinModerate 60Details
Commit message · Craig Raw

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

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
secret or key materialsigning or wallet path
AI analysis · Moderate 60/100

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 now rejects xprvs in those places and, when scanning output descriptors, derives the public key from any private key instead of using the private key directly. This prevents private key material from being loaded into watch-only or multisig wallet setups where it does not belong.

AI review queuedlet the terminal user choose the script type when transactions are found for more than oneby Craig Raw · a18db115 · Nov 19, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

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

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 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 so the user can choose which script type to use. This is a usability fix that prevents the wrong wallet type from being selected automatically.

Security candidateuse 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 accountby Craig Raw · 002b1b58 · Nov 19, 2026 · 12 filesMessage 50 · ThinLow 33Details
Commit message · Craig Raw

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

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 33/100

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 using the older script-type defaults. The change is broad but mechanical: many import paths now pass the wallet's policy type into the derivation lookup. There is no direct evidence in the commit of a security vulnerability being fixed; it reads more like a correctness/consistency improvement for silent-payment support.

AI review queuedreplace control characters in cosigner labels of an imported multisig configuration, and size alerts to include blank linesby Craig Raw · c1d4feea · Nov 19, 2026 · 2 filesMessage 50 · ThinLow 37Details
Commit message · Craig Raw

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

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 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 dialog height calculation so blank lines are counted, avoiding dialogs that are too short to show their full message. These are defensive hardening changes rather than fixes for active remote attacks.

AI review queuedtruncate address, purpose node and keystore labels when updating a wallet, as a full save doesby Craig Raw · 0721ca98 · Nov 19, 2026 · 2 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

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

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 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 incremental update path did not. If a user set an unusually long label, the database update could fail or behave inconsistently, potentially blocking later wallet updates. The fix applies the same truncation routine during updates, and a new test confirms that a 300-character address label is safely reduced to 255 characters and does not prevent a second label from being saved.

AI review queuedrefuse the bwt fallback for bitcoin core over https and ignore the legacy wallet setting for itby Craig Raw · b935568a · Nov 19, 2026 · 2 filesMessage 50 · ThinLow 32Details
Commit message · Craig Raw

refuse the bwt fallback for bitcoin core over https and ignore the legacy wallet setting for 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 32/100

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 hardening step: HTTPS connections now require a newer Bitcoin Core version (v24+) that supports descriptor wallets, rather than silently using older, less secure wallet handling.

AI review queuedcheck rsa server certificates against the ca trust store for the key exchange in useby Craig Raw · 1071ed7c · Nov 19, 2026 · 1 fileMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

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

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 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 was the wrong label for modern TLS connections, which typically use ephemeral Diffie-Hellman with RSA ("ECDHE_RSA"). The mismatch could cause Java to reject valid certificates or, worse, accept weaker validation paths than intended. The fix makes the validation label match the actual key exchange in use, so certificates are checked correctly against the device’s trusted certificate authorities.

AI review queuedrequest historical rates from coingecko in whole utc daysby Craig Raw · 646a11dc · Nov 19, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

request historical rates from coingecko in whole utc days

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 changes how Sparrow Wallet asks CoinGecko for historical Bitcoin exchange rates. Previously it requested rates using raw timestamps, which could include partial days and a slightly wrong one-year cutoff. Now it rounds the request to whole UTC days and clamps the end date to the current time. This is a correctness/quality fix for price data used in wallet history and reporting; it is not a direct security vulnerability patch.

AI review queuedshow the remote bitcoin core node warning from the terminal server settingsby Craig Raw · 6ea7bca6 · Nov 19, 2026 · 3 filesMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

show the remote bitcoin core node warning from the terminal 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: security-sensitive path
AI analysis · Informational 17/100

This commit moves an existing user warning about connecting to a remote Bitcoin Core node into a shared helper, and now also displays that same warning in the terminal (command-line) version of Sparrow. It does not change how connections are made or fix a vulnerability. It only makes the warning appear in one additional place so terminal users see the same caution as desktop users.

AI review queuedwrap terminal alert lines after a line break in the text at the full widthby Craig Raw · 5316f484 · Nov 19, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

wrap terminal alert lines after a line break in the text at the full width

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 fixes a text-wrapping bug in the terminal version of Sparrow Wallet. Previously, if an alert message contained explicit line breaks (newlines), the wrapping logic counted the entire chunk after a newline as part of the current line length, causing later lines to be wrapped too early. The fix resets the line-length counter after each explicit newline so subsequent text uses the full available width. There is no security relevance in the commit or supplied references.

AI review queuedsync to the announced tip before serving a stored header when a reorg lengthens the chain, so a proof is not checked against a replaced blockby Craig Raw · 40310b05 · Nov 19, 2026 · 2 filesMessage 50 · ThinModerate 69Details
Commit message · Craig Raw

sync to the announced tip before serving a stored header when a reorg lengthens the chain, so a proof is not checked against a replaced block

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

This commit fixes a bug in how Sparrow Wallet verifies Bitcoin block headers during a blockchain reorganization (reorg). Previously, if a reorg made the chain longer, the wallet could serve an old, replaced block header to check a payment proof, instead of first syncing to the newly announced longer chain. This could let a malicious or mistaken server make a transaction proof look valid against the wrong block. The fix forces a sync to the announced tip before serving any stored header when the announced tip is newer or on a different branch than what is locally stored.

AI review queueddelete backups made before a password was added or changed from the terminal settingsby Craig Raw · 26e6705d · Nov 19, 2026 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Craig Raw

delete backups made before a password was added or changed from the terminal 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 42/100

This commit changes how Sparrow Wallet's terminal (command-line) version handles wallet backups when a password is added, changed, or removed. Previously, old unencrypted or differently-encrypted backups might have been kept on disk. After this change, the terminal version behaves like the desktop version: when a password is set or changed, backups made under the old password (or no password) are deleted. This reduces the risk that an attacker or another user could find an old, less-protected copy of the wallet and access its data.