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

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.

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.

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.

Security candidatereach an onion host written with a trailing dot over tor, and remove the dot from saved server urlsby Craig Raw · 70f2f51f · Nov 19, 2026 · 4 filesMessage 50 · ThinLow 44Details
Commit message · Craig Raw

reach an onion host written with a trailing dot over tor, and remove the dot from saved server urls

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathparser or protocol path
AI analysis · Low 44/100

This commit fixes a handling quirk for Tor 'onion' web addresses when they are written with a trailing dot (for example, 'example.onion.'). Previously, Sparrow did not recognize these dotted onion addresses as Tor destinations, so it might try to connect over the regular internet instead of through Tor, and could fail to enforce the requirement that a Tor proxy must be configured. The change makes Sparrow strip the trailing dot, recognize the address as an onion address, route it through Tor, and save server URLs without the trailing dot.

Security candidaterefuse to sign a paynym authentication token in another formatby Craig Raw · ebd3bdad · Nov 19, 2026 · 2 filesMessage 55 · ThinModerate 61Details
Commit message · Craig Raw

refuse to sign a paynym authentication token in another format

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

This commit adds a safety check so that Sparrow Wallet will refuse to sign a PayNym authentication token if it looks like a web link (for example, starting with 'auth47://' or 'https://'). Before this change, the wallet might have signed such a token, which could potentially let an attacker trick the user into signing a message that authorizes something on a website instead of a simple PayNym token. The change is defensive and includes tests to confirm the new behavior.

Security candidateremove auth47 soroban callback supportby Craig Raw · 37ea7b97 · Nov 19, 2026 · 2 filesMessage 45 · ThinLow 41Details
Commit message · Craig Raw

remove auth47 soroban callback support

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 41/100

This commit removes support for a special callback protocol called 'srbn://' from Sparrow Wallet's Auth47 authentication feature. Previously, Auth47 could accept callbacks using this protocol, which would be converted to HTTPS and sent through a different response path involving a 'Soroban' directory service. Now, only HTTPS and HTTP-onion callbacks are accepted. The change is defensive: it narrows what callback types are allowed and removes a less common code path, but the commit message does not say it fixes a specific security vulnerability.

Security candidatedisable the locktime controls for a psbt input requiring a locktime, and show the locktime that will be signedby Craig Raw · 1f5993b7 · Nov 19, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · Craig Raw

disable the locktime controls for a psbt input requiring a locktime, and show the locktime that will be signed

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

This commit changes how Sparrow Wallet handles 'locktime' settings when editing a transaction that came from a PSBT (Partially Signed Bitcoin Transaction). Previously, the user could edit the locktime even when a PSBT input required a specific locktime, which could lead to the wallet displaying or signing a different locktime than the one required by the transaction's inputs. Now, the locktime controls are disabled when any PSBT input requires a locktime, and the displayed locktime is forced to the value that will actually be signed. This is a defensive UI fix to prevent user confusion and potential signing of an unexpected transaction locktime.

Security candidateverify silent payment outputs against the open wallet providing all inputs when a psbt is exported or combined before finalizingby Craig Raw · a7ccc7d5 · Nov 19, 2026 · 3 filesMessage 60 · AdequateModerate 57Details
Commit message · Craig Raw

verify silent payment outputs against the open wallet providing all inputs when a psbt is exported or combined before finalizing

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 boundarysigning or wallet path
AI analysis · Moderate 57/100

This commit fixes a gap in how Sparrow Wallet checks Silent Payment addresses when a partially-built transaction (PSBT) is exported or combined before it is finalized. Previously, the wallet only verified the Silent Payment output against the wallet that would eventually sign. If the PSBT had no signing wallet yet, the output could go unverified. The change makes the app also look at all currently open wallets and verify against the one that can prove all inputs, reducing the chance of paying to a wrong or attacker-controlled Silent Payment address.

Security candidateapply the required all sighash to the inputs of a psbt with silent payment outputs in the transaction tab, and check each input a card will sign before it signs anyby Craig Raw · 418e726a · Nov 19, 2026 · 5 filesMessage 50 · ThinModerate 58Details
Commit message · Craig Raw

apply the required all sighash to the inputs of a psbt with silent payment outputs in the transaction tab, and check each input a card will sign before it signs any

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

This commit fixes how Sparrow Wallet handles Bitcoin transactions that use silent payments. Silent payments require every input to be signed with SIGHASH_ALL, meaning the signature covers the whole transaction. Previously, the wallet might have let a hardware card sign an input with a weaker signature type, or let the user pick a different one in the transaction tab. The patch forces SIGHASH_ALL on all inputs when silent payment outputs are present, and makes each card check that requirement before signing anything. A wrong sighash could let an attacker alter parts of the transaction after some inputs are signed, potentially redirecting funds or breaking the silent-payment protocol.

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.

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.

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.

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.

Security candidateread whole rows in the search wallet results, name the add account pop-up and hide the glyph icons in dialog headers from screen readersby Craig Raw · 66b3f71b · Oct 29, 2026 · 11 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

read whole rows in the search wallet results, name the add account pop-up and hide the glyph icons in dialog headers from screen readers

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

This commit improves accessibility for users who rely on screen readers. It makes the 'search wallet' results read out entire rows instead of only the first cell, gives the 'add account' pop-up a hidden label so screen readers can name it, and hides decorative icon graphics from screen readers across several dialog windows. There is no security vulnerability or exploit here.

Security candidatekeep chart points out of the tab order, let the message dialog close after signing, and name the qr code, encoding and message dialogby Craig Raw · 4c275f66 · Oct 28, 2026 · 7 filesMessage 50 · ThinInformational 20Details
Commit message · Craig Raw

keep chart points out of the tab order, let the message dialog close after signing, and name the qr code, encoding and message dialog

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

This commit is an accessibility and user-experience patch for the Sparrow Wallet desktop app. It makes screen-reader navigation smoother by removing chart data points from the keyboard Tab order, naming QR code and encoding controls, and improving focus behavior after signing a message. It also fixes a small interaction bug where the Sign/Verify buttons in the message dialog would close the dialog instead of staying open to show results. There is no indication this change fixes a security vulnerability.

Security candidategive dialogs titles and keep focus on the new tab or button after creating a transaction or keystoreby Craig Raw · cd56ab75 · Oct 28, 2026 · 26 filesMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

give dialogs titles and keep focus on the new tab or button after creating a transaction or keystore

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

This commit is a user-experience polish change for the Sparrow Wallet desktop app. It adds visible titles to many popup windows and shifts keyboard focus to the newly opened tab or button after creating a transaction or importing a keystore. There is no direct security fix here, but better focus handling can reduce accidental user mistakes (for example, pressing Enter/Space on the wrong control) and titled dialogs help screen readers and users identify windows correctly.

Security candidatename the passphrase checkbox and field, and the derivation fields in the import panes, for screen readersby Craig Raw · 5b186688 · Oct 28, 2026 · 7 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

name the passphrase checkbox and field, and the derivation fields in the import panes, for screen readers

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

This commit improves accessibility for users who rely on screen readers. It adds hidden labels and accessible text to checkboxes and text fields in wallet import screens so screen-reading software can correctly describe what each field is for. There is no security vulnerability or exploit here.

Security candidateread signatures as a summary for screen readers, and move focus to the signatures after signing and to the transaction status after broadcastingby Craig Raw · cdadd767 · Oct 28, 2026 · 3 filesMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

read signatures as a summary for screen readers, and move focus to the signatures after signing and to the transaction status after broadcasting

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 improves accessibility for users who rely on screen readers. It makes the wallet announce how many signatures a transaction has, moves keyboard focus to the right place after signing or broadcasting, and labels the broadcast progress bar. There is no security vulnerability here.

Security candidateupgrade to java 25.0.5by Craig Raw · d8e679d9 · Oct 27, 2026 · 5 filesMessage 38 · OpaqueInformational 15Details
Commit message · Craig Raw

upgrade to java 25.0.5

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit simply updates the project's build and documentation to use a newer patch version of Java (25.0.5 instead of 25.0.2). It changes version numbers in configuration files and download links. There is no indication of a security vulnerability or malicious change in the diff itself.

Security candidateverify wallet input signatures of unconfirmed transactions before adding them to the wallet historyby Craig Raw · e7454d97 · Oct 26, 2026 · 5 filesMessage 60 · AdequateHigh 73Details
Commit message · Craig Raw

verify wallet input signatures of unconfirmed transactions before adding them to the wallet history

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 boundarysigning or wallet path
AI analysis · High 73/100

This commit adds a security check in the Sparrow bitcoin wallet. When the wallet connects to an external Electrum-style server, the server can tell the wallet about unconfirmed transactions that appear to spend from the wallet. Before this change, the wallet would add those transactions to its history without checking whether they were actually signed by the wallet's own keys. A dishonest or compromised server could therefore make the wallet believe money was spent or received when it really wasn't. The new code verifies the signatures on any unconfirmed transaction that spends from the wallet, and if the signatures are invalid, the transaction is kept out of the wallet history and the user is warned.

Security candidateverify payjoin receiver input signatures against their declared utxos before checking the proposal feeby Craig Raw · 3a63d346 · Oct 25, 2026 · 3 filesMessage 60 · AdequateHigh 76Details
Commit message · Craig Raw

verify payjoin receiver input signatures against their declared utxos before checking the proposal fee

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 boundarysigning or wallet path
AI analysis · High 76/100

This commit fixes a security gap in Sparrow Wallet's Payjoin handling. Payjoin lets a receiver add their own bitcoin inputs to a transaction you are sending. Before this change, Sparrow could be tricked into accepting a Payjoin proposal where the receiver's claimed coins were not properly signed, or where the receiver hid the real previous transaction for old-style (non-Segwit) inputs. The change makes Sparrow verify the receiver's signatures against the exact coins they declared, and it rejects proposals that omit required data for non-Segwit inputs. This closes a path where a malicious or buggy payjoin server could make the sender pay more fees or include invalid inputs.

Security candidateuse the application http client for lnurl-auth and auth47 callback requestsby Craig Raw · 8f98f045 · Oct 12, 2026 · 2 filesMessage 55 · ThinLow 38Details
Commit message · Craig Raw

use the application http client for lnurl-auth and auth47 callback requests

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
signing or wallet pathauthentication path
AI analysis · Low 38/100

This commit changes how Sparrow Wallet sends authentication callbacks for two login features (Auth47 and LNURL-auth). Instead of using Java's built-in web request code directly, it now routes those requests through the wallet's shared HTTP client service. This is likely a hardening or consistency improvement, but the diff alone does not prove a specific security vulnerability was fixed.