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 55 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 queuedsave silent payments found by a scan when fetching their history fails, and load wallets whose silent payment indexes are not contiguousby Craig Raw · 9f29f57f · Nov 17, 2026 · 4 filesMessage 50 · ThinLow 42Details
Commit message · Craig Raw

save silent payments found by a scan when fetching their history fails, and load wallets whose silent payment indexes are not contiguous

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 two related bugs in Sparrow Wallet's handling of silent payments. Silent payments are a privacy-preserving way to receive Bitcoin where each payment uses a unique address derived by the sender. The wallet scans the blockchain to find payments made to it. The first bug meant that if the wallet found silent payments during a scan but then failed to fetch their transaction history, those newly found payments could be lost instead of saved. The second bug meant that wallets with silent payment indexes that were not sequential (which is normal for silent payments) could fail to load or refresh properly because the code tried to fill in missing indexes as if they were ordinary derived addresses. The fix ensures found silent payments are saved even when history fetching fails, and that the wallet does not try to force silent payment indexes to be contiguous.

AI review queuedtidy repository housekeeping filesby Craig Raw · 1ebbc57e · Nov 17, 2026 · 3 filesMessage 35 · OpaqueInformational 15Details
Commit message · Craig Raw

tidy repository housekeeping files

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit removes two leftover configuration files from the repository and makes a trivial formatting fix to the .gitignore file. One deleted file contained a local-only Trezor hardware-wallet pairing credential, and the other contained generic Sparrow wallet settings. There is no code change, no vulnerability fix, and no indication these files were ever shipped to users or exposed secrets in a harmful way.

AI review queuedskip a silent payments transaction the server cannot return when processing a subscription batch, and fetch it again on the next refreshby Craig Raw · 0615085d · Nov 17, 2026 · 2 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

skip a silent payments transaction the server cannot return when processing a subscription batch, and fetch it again on the next refresh

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 in how Sparrow Wallet handles Silent Payments transactions that the server cannot currently return (for example, because a transaction left the mempool before the wallet fetched it). Previously, such a missing transaction could stop the whole batch of Silent Payments updates from being processed, potentially causing later payments to be missed or the wallet state to become inconsistent. The fix skips the missing transaction, processes the rest of the batch, and tries again on the next refresh. It also ensures that if the wallet already holds a placeholder for an unfetchable transaction, it will be fetched again rather than treated as the real transaction.

AI review queuedescape the wallet name when using it to name the database update threadby Craig Raw · f4d53daa · Nov 17, 2026 · 1 fileMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

escape the wallet name when using it to name the database update thread

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 makes two small changes to how Sparrow Wallet handles its internal database. The first and more prominent change escapes percent signs in wallet names before using them as Java thread names, which prevents a harmless formatting quirk in logging/monitoring tools. The second change is a code-style refactor around how database metadata types are assigned, with no obvious security effect. There is no indication this fixes an exploitable vulnerability.

AI review queuedadd testnet5 network support and libbitcoin public electrum serversby Kevin Abramczyk · c21a4587 · Nov 17, 2026 · 7 filesMessage 50 · ThinInformational 20Details
Commit message · Kevin Abramczyk

add testnet5 network support and libbitcoin public electrum servers

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

This commit adds support for a new Bitcoin test network called testnet5 and lists two new public Electrum servers for that network. It also updates the bundled 'drongo' subproject. There are no changes that fix a vulnerability or alter security-sensitive behavior; it is a routine feature addition.

AI review queuedreport a wallet password change that fails on the update thread, and delete backups only once the file has been written with the new passwordby Craig Raw · 97ed5bbc · Nov 16, 2026 · 7 filesMessage 50 · ThinModerate 60Details
Commit message · Craig Raw

report a wallet password change that fails on the update thread, and delete backups only once the file has been written with the new password

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

This commit fixes a bug in Sparrow Wallet's password-change flow. Previously, if a password change failed while writing the wallet file on a background thread, the user was not told, and old password-protected backups could be deleted before the new password actually reached the file. The patch adds an error dialog for these failures and delays backup deletion until the wallet file is confirmed to have been written with the new password.

AI review queuedclear a selected paynym from the send tab pay to field before applying a scanned address or uriby Craig Raw · 51d01d9c · Nov 16, 2026 · 1 fileMessage 50 · ThinLow 38Details
Commit message · Craig Raw

clear a selected paynym from the send tab pay to field before applying a scanned address or uri

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 fixes a UI bug in Sparrow Wallet's send tab. Previously, if a user had selected a PayNym (a human-readable payment contact) in the 'pay to' field and then scanned a QR code containing a regular Bitcoin address or payment URI, the old PayNym text could remain in the field while the new address/URI was applied. The patch now clears the PayNym text before applying the scanned address or URI, preventing confusion about who or what address the payment is actually going to. This could reduce the risk of a user accidentally sending funds to the wrong recipient, but it is a UI consistency fix rather than a cryptographic vulnerability.

AI review queuedrename wallet backups along with the wallet when renamingby Craig Raw · ddb486dd · Nov 13, 2026 · 3 filesMessage 50 · ThinInformational 21Details
Commit message · Craig Raw

rename wallet backups along with the wallet when renaming

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 fixes a bug in Sparrow Wallet where renaming a wallet left its automatic backups behind under the old name. Previously, the old backups could be orphaned or deleted while a new set of backups was created under the new wallet name, potentially causing confusion or loss of backup continuity. The change makes the app rename existing backup files to match the new wallet name when the wallet is renamed.

AI review queueddelete backups made before a wallet was migrated from json when deleting a wallet or its backupsby Craig Raw · a50cb063 · Nov 13, 2026 · 2 filesMessage 50 · ThinLow 47Details
Commit message · Craig Raw

delete backups made before a wallet was migrated from json when deleting a wallet or its backups

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

This commit fixes a cleanup bug in Sparrow Wallet. When a user deletes a wallet or its backups, the app now also finds and removes old backups that were created before the wallet was migrated from the older JSON format to the newer database format. Previously, those pre-migration backups could be left behind on disk after deletion, meaning a wallet the user thought was gone might still have recoverable files sitting in the backup folder.

AI review queuedapply the wallet name dialog character filter to names suggested by imported wallet filesby Craig Raw · 2bf2830f · Nov 13, 2026 · 3 filesMessage 50 · ThinLow 42Details
Commit message · Craig Raw

apply the wallet name dialog character filter to names suggested by imported wallet files

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 UI ordering bug in Sparrow Wallet's wallet import flow. Previously, when a wallet file suggested a wallet name, the name was put into the text box before the character filter was attached, so dangerous characters like semicolons or backslashes could slip through. The fix simply applies the filter first, then sets the suggested name, so any bad characters are sanitized before the user sees them. A new test confirms that storage rejects names containing punctuation that could be misused.

AI review queuedsum the swept key once per input when sweeping to a silent payment address, and refuse silent payment sweeps from uncompressed keysby Craig Raw · e31af454 · Nov 13, 2026 · 1 fileMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

sum the swept key once per input when sweeping to a silent payment address, and refuse silent payment sweeps from uncompressed keys

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

This commit fixes two bugs in Sparrow Wallet's feature that lets users sweep old private keys into a 'silent payment' address. First, when multiple transaction outputs were being swept, the wallet was incorrectly using the same private key once instead of mathematically combining it once per input, which would produce the wrong silent payment address and likely make the funds unspendable or send them to an address no one controls. Second, the wallet now blocks sweeping from uncompressed private keys into silent payments, because silent payments require compressed keys to work correctly. The commit is a bug fix rather than an exploit against users, but the underlying flaw could have caused loss of funds if a user tried a multi-input silent-payment sweep.

AI review queuedderive node addresses rather than using stored addresses when importing a sparrow wallet fileby Craig Raw · 0b0e0e1e · Nov 13, 2026 · 3 filesMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

derive node addresses rather than using stored addresses when importing a sparrow wallet file

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 changes how Sparrow Wallet imports its own wallet files. Previously, when loading a wallet backup, Sparrow trusted the address data stored inside the file. Now it clears those stored addresses and re-derives them from the wallet's cryptographic keys. This prevents a tampered or crafted wallet file from sneaking in bogus Bitcoin addresses that could trick the user into sending funds to the wrong place. The change also adds tests to make sure addresses are always recalculated and that user labels on addresses are preserved.

AI review queuedname the device and its fingerprint when a connected device does not match the wallet keystoresby Craig Raw · 4aed8049 · Nov 12, 2026 · 1 fileMessage 50 · ThinInformational 14Details
Commit message · Craig Raw

name the device and its fingerprint when a connected device does not match the wallet 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 · Informational 14/100

This commit improves an on-screen message shown when a connected hardware wallet does not match the wallet being used. Instead of a generic 'No matching devices found' message, it now names the device and shows its fingerprint, helping the user check they plugged in the correct device and entered the right passphrase. There is no security vulnerability here; it is a usability and diagnostic improvement.

AI review queueduse the latest mempool data in the block summary service, and reset it on reconnectingby Craig Raw · 34413b20 · Nov 12, 2026 · 2 filesMessage 50 · ThinLow 25Details
Commit message · Craig Raw

use the latest mempool data in the block summary service, and reset it on reconnecting

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 commit changes how Sparrow Wallet caches and reuses recent Bitcoin mempool transactions when showing block summaries. It stores the most recently fetched mempool snapshot and only reuses it for up to 10 minutes and only if the blockchain tip has not advanced. It also clears that cached snapshot when the server reconnects. The change appears aimed at preventing stale or wrong mempool data from being shown to users after reconnections or tip changes.

Security candidateadd 1 234,56 unit format and use the unit format rather than the system locale for fee rates, sizes, percentages and chart labelsby Craig Raw · 26765f22 · Nov 12, 2026 · 27 filesMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

add 1 234,56 unit format and use the unit format rather than the system locale for fee rates, sizes, percentages and chart labels

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

This commit adds a new number format option ('1 234,56') to the Sparrow Wallet and makes the wallet consistently use the user's chosen number format for fee rates, transaction sizes, percentages, and chart labels instead of relying on the computer's system locale. It also fixes a few places where the wrong decimal separator was hardcoded when reading user-entered amounts. There is no direct evidence this commit fixes an active security vulnerability, but inconsistent number parsing can in principle lead to user mistakes or display confusion.

Security candidateadd jetty 12.1.15 verification checksums and remove stale entries and signing keys left by earlier upgradesby Craig Raw · 3ca7c4b7 · Nov 12, 2026 · 2 filesMessage 60 · AdequateInformational 18Details
Commit message · Craig Raw

add jetty 12.1.15 verification checksums and remove stale entries and signing keys left by earlier upgrades

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 boundarydefensive validation
AI analysis · Informational 18/100

This commit updates the project's list of trusted library fingerprints and signing keys used by its build system. It adds verification records for the Jetty web server version 12.1.15, removes old records for outdated libraries, and deletes two no-longer-needed public keys. There is no direct code change to the wallet application itself, and nothing in the commit message or diff indicates a security vulnerability was fixed.

AI review queuedrequest bitcoin core wallet spends in batches from v28 when starting cormorant and wait for the initial load before pollingby Craig Raw · 1356b2cc · Nov 11, 2026 · 4 filesMessage 50 · ThinLow 29Details
Commit message · Craig Raw

request bitcoin core wallet spends in batches from v28 when starting cormorant and wait for the initial load before polling

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 improves how the Sparrow Wallet desktop app talks to a self-hosted Bitcoin Core node when using the built-in 'Cormorant' connection. It batches transaction lookups on newer Bitcoin Core versions, waits for the initial wallet history load before starting background polling, and tweaks error messages so they don't wrongly blame firewall settings when the user is connecting through Tor. The changes are mostly reliability and performance fixes, not a patch for a remote attack.

AI review queuedupgrade tern to v1.1.2 and use it for bitcoin core rpc and paynym avatar requestsby Craig Raw · 96c3ef69 · Nov 11, 2026 · 14 filesMessage 50 · ThinLow 47Details
Commit message · Craig Raw

upgrade tern to v1.1.2 and use it for bitcoin core rpc and paynym avatar requests

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

This commit upgrades an internal networking library called 'tern' and switches Bitcoin Core RPC, PayNym avatar, and Payjoin requests to use it. The change is mostly a refactoring to consolidate HTTP handling, fix proxy-switching races, and add timeouts so unreachable nodes cannot freeze the wallet. It also adds many tests that verify traffic goes through Tor for onion addresses, does not follow HTTP redirects, and pins self-signed HTTPS certificates. There is no direct evidence in the commit that this fixes a known exploit, but it removes risky behaviors such as infinite connection hangs and redirect following that could be abused.

AI review queuedorder block transaction references consistently for any heightby Craig Raw · fb0e5856 · Nov 11, 2026 · 5 filesMessage 50 · ThinInformational 21Details
Commit message · Craig Raw

order block transaction references consistently for any height

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 sorts wallet transactions by block height. It replaces a manual subtraction-based height comparison with a dedicated comparison method. The change is likely intended to fix subtle sorting bugs—especially when heights are very large or negative—by avoiding integer overflow and inconsistent ordering. There is no direct evidence this is a security vulnerability, but inconsistent transaction ordering could theoretically confuse users or downstream logic.

AI review queuedupgrade pgpainless to v1.7.8by Craig Raw · 62b2f7ed · Nov 11, 2026 · 3 filesMessage 45 · ThinLow 48Details
Commit message · Craig Raw

upgrade pgpainless to v1.7.8

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

This commit updates the PGP verification library used by Sparrow Wallet and tweaks the logic that decides when a downloaded release file is considered valid. The code change makes the app less likely to wrongly disable manifest verification when the release file happens to match the detached signature file. On its own, the change looks like a defensive hardening fix, but the commit message does not explain whether it fixes a known security bug.

AI review queuedupgrade flyway to v13.12.1by Craig Raw · 2529bd74 · Nov 11, 2026 · 5 filesMessage 45 · ThinModerate 57Details
Commit message · Craig Raw

upgrade flyway to v13.12.1

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

This commit upgrades the Flyway database-migration library inside Sparrow Wallet from version 9.22.3 to 13.12.1 and rewrites the wallet-file validation code. The old validator inspected raw bytes of the H2 database file for suspicious keywords. The new validator parses the H2 file structure directly, checks that only expected internal map types and SQL DDL statements are present, and adds extra guards such as disabling Flyway placeholder replacement and rejecting account names containing a double quote. The change appears to be a hardening effort against malicious wallet files rather than a routine dependency bump.

Security candidatekeep the master private key for xprv output descriptors with an account path, and only warn of conversion to watch only when the xprv has a key origin pathby Craig Raw · d156f00a · Nov 10, 2026 · 2 filesMessage 55 · ThinLow 38Details
Commit message · Craig Raw

keep the master private key for xprv output descriptors with an account path, and only warn of conversion to watch only when the xprv has a key origin path

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

This commit changes how Sparrow Wallet handles private extended keys (xprv) when users edit wallet output descriptors. Previously, Sparrow warned it would convert any private key to a public key in more situations. Now it only warns when the private key has a key origin path. The goal appears to be preserving the master private key for descriptors that use an account path, while still warning when conversion to watch-only is actually happening. The change is small and the security implications depend on whether users expect their private keys to remain usable after editing descriptors.

AI review queuedprompt to accept an expired server certificate in settings test connection, and say an expired saved certificate has expired rather than changedby Craig Raw · a1b99e3f · Nov 9, 2026 · 3 filesMessage 60 · AdequateLow 29Details
Commit message · Craig Raw

prompt to accept an expired server certificate in settings test connection, and say an expired saved certificate has expired rather than changed

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: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit improves the user experience when a Bitcoin wallet connects to a server whose security certificate has expired. It changes the warning message to clearly say 'expired' instead of 'changed' and lets users accept an expired certificate during a settings test connection. The change itself is a usability improvement, but it slightly weakens the security prompt because it makes it easier to proceed with an expired certificate.

AI review queuedkeep the start of a server response that arrives across socket read timeouts instead of dropping it, and fail the connection on a response over 256m charactersby Craig Raw · a108ad10 · Nov 8, 2026 · 2 filesMessage 50 · ThinLow 47Details
Commit message · Craig Raw

keep the start of a server response that arrives across socket read timeouts instead of dropping it, and fail the connection on a response over 256m characters

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

This commit fixes how Sparrow Wallet reads replies from a Bitcoin/Electrum server over the network. Previously, if a reply arrived in pieces with pauses between them, the wallet could drop the first piece and misread the response. It also adds a 256 million character cap so a malicious or broken server cannot send an endless reply that exhausts the wallet's memory. The change is defensive hardening with a clear reliability and limited security benefit.

AI review queuedresend batch requests that have been skipped as making the batch response too large, so a large wallet history page syncs instead of failing every refreshby Craig Raw · f2ecfb2f · Nov 5, 2026 · 3 filesMessage 50 · ThinLow 27Details
Commit message · Craig Raw

resend batch requests that have been skipped as making the batch response too large, so a large wallet history page syncs instead of failing every refresh

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 wallet-sync reliability problem. When Sparrow asked an Electrum server for a large batch of transaction history data, some servers would skip part of the request because the answer would be too big. Previously those skipped requests were treated as failures, so a large wallet's history page could never finish refreshing. The change detects the 'response too large' signal from Frigate and ElectrumX servers and automatically re-sends the skipped items in smaller batches until they succeed or truly fail for another reason. It is a robustness improvement, not a typical security bug fix.