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 53 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 queuedrefresh a node when its script hash status returns to an earlier value, retiring the mitigation for electrs < 0.9.0by Craig Raw · 70e56a5b · Sep 9, 2026 · 3 filesMessage 50 · ThinModerate 63Details
Commit message · Craig Raw

refresh a node when its script hash status returns to an earlier value, retiring the mitigation for electrs < 0.9.0

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

This commit changes how Sparrow Wallet tracks Electrum server notifications about Bitcoin address activity. Previously, the app remembered every status value it had ever seen for each address and ignored repeats of any earlier value. Now it only remembers the latest status and treats any change—even a return to an earlier value—as a real update. The old behavior could leave the wallet showing transactions that the server no longer has (for example, after a mempool replacement or a chain reorganization), which could mislead users about their balance or transaction history.

AI review queuedrequire the policy line and check the declared cosigner count when importing coldcard format multisig walletsby Craig Raw · 5aa262ee · Sep 9, 2026 · 4 filesMessage 50 · ThinModerate 56Details
Commit message · Craig Raw

require the policy line and check the declared cosigner count when importing coldcard format multisig wallets

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

This commit tightens how Sparrow Wallet imports multisig wallet files from Coldcard. Previously, if the file omitted the 'Policy' line or listed fewer cosigner keys than the policy required, Sparrow would silently assume a default 2-of-2 setup. That could let a malformed or attacker-crafted import file create a wallet whose security rules don't match what the user expects. The patch now requires the policy line and verifies the number of cosigner keys matches the declared policy, throwing an error if they don't.

AI review queuedclear a replacement transaction when a utxo it spends is frozen rather than silently removing the inputby Craig Raw · b7902f54 · Sep 8, 2026 · 1 fileMessage 50 · ThinLow 32Details
Commit message · Craig Raw

clear a replacement transaction when a utxo it spends is frozen rather than silently removing the input

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 change fixes a bug in Sparrow Wallet where freezing a coin (UTXO) that was being used in a replacement transaction could silently remove the input and accidentally break the transaction's privacy-related outputs. Now, if removing the frozen coin would be unsafe, the wallet clears the replacement transaction instead of silently altering it. This is a correctness and safety improvement rather than a typical remote-exploitable vulnerability.

AI review queuedreport a transaction tab height the server will not prove instead of marking it unverified until it doesby Craig Raw · 080be605 · Sep 7, 2026 · 9 filesMessage 50 · ThinLow 36Details
Commit message · Craig Raw

report a transaction tab height the server will not prove instead of marking it unverified until it 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 36/100

This commit changes how Sparrow Wallet shows a transaction's block height when the connected server cannot prove the transaction is actually in that block. Previously, the transaction tab would label such a height as 'Unverified' while waiting for proof. Now it shows the height plainly, and only after the server has had a fair chance to prove it and fails does it add an 'Unverified' warning. The change also makes the transaction-tab verification use the same retry logic and user-facing reporting that wallet history verification already uses, so a momentary server hiccup is not treated as a server lie.

AI review queuedcompare silent payment scan addresses when considering wallet address changesby Craig Raw · 62ec51ce · Sep 4, 2026 · 1 fileMessage 50 · ThinLow 46Details
Commit message · Craig Raw

compare silent payment scan addresses when considering wallet address changes

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

This commit fixes a logic gap in Sparrow Wallet's settings form. When a user changes wallet settings, the app checks whether the wallet's receiving addresses would change, so it can warn or take appropriate action. The check already compared regular extended public keys, but it forgot to compare 'silent payment scan addresses'—a newer Bitcoin privacy feature. Without this comparison, changing the silent-payment scan key might not be detected as an address change, potentially causing the wallet to show stale or incorrect addresses without warning.

AI review queuedrevert the sighash selection when the sighash none warning is dismissed rather than answered noby Craig Raw · 6983c955 · Sep 4, 2026 · 1 fileMessage 50 · ThinLow 44Details
Commit message · Craig Raw

revert the sighash selection when the sighash none warning is dismissed rather than answered no

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

This commit fixes a small UI bug in Sparrow Wallet's transaction signing dialog. When a user chooses the risky 'SIGHASH_NONE' option, Sparrow shows a warning asking if they are sure. Previously, clicking 'No' reverted the choice, but closing/dismissing the warning box without answering left the risky option selected. The fix now reverts the choice whenever the user does not explicitly click 'Yes'.

AI review queuedcorrect an amount or fee entry that parses as zero when only part of it validatesby Craig Raw · b0a4934a · Sep 4, 2026 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Craig Raw

correct an amount or fee entry that parses as zero when only part of it validates

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

This commit fixes a bug in Sparrow Wallet's text input handling for Bitcoin amounts and transaction fees. Previously, if a user typed something like '0abc', the wallet would partially match only the '0' and treat the amount as zero, silently dropping the invalid trailing characters. This could let a user accidentally (or be tricked into) entering an amount that the wallet interprets as zero when they intended something else. The fix now only keeps a zero value if the entire typed text is a valid amount, not just a partial match.

AI review queuedshow a height the transaction tab takes from the server as unverified until it is provenby Craig Raw · 97954f44 · Sep 4, 2026 · 6 filesMessage 50 · ThinModerate 63Details
Commit message · Craig Raw

show a height the transaction tab takes from the server as unverified until it is proven

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

This commit changes Sparrow Wallet so that when you open a transaction in the transaction tab, the block height claimed by the server is not automatically trusted. Instead, the wallet now asks the server for a cryptographic proof (a Merkle proof) that the transaction really is in that block. Until the proof arrives and checks out, the height is shown as 'Unverified'. Previously, the transaction tab would display the server's claimed height and block hash as if they were confirmed facts, even though they came only from the server. This change closes a trust gap: a malicious or mistaken server could no longer make an unconfirmed or differently-located transaction appear confirmed in the UI simply by reporting a fake height or block hash.

AI review queuedrefuse an announced tip below the last pinned headerby Craig Raw · 8ab75efd · Sep 4, 2026 · 3 filesMessage 50 · ThinHigh 70Details
Commit message · Craig Raw

refuse an announced tip below the last pinned header

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

This commit hardens Sparrow Wallet against a malicious or misbehaving Electrum server that tries to 'rewind' the blockchain tip to a height below the last built-in checkpoint after it has already announced a higher tip. Previously, such a fake low announcement could have been accepted for public servers that are required to verify transactions, potentially letting the server hide or rewrite recent history. The fix refuses those regressive announcements and adds tests to confirm the behavior.

AI review queuedretain an entered https scheme for its host when configuring a bitcoin core serverby Craig Raw · e6242780 · Aug 28, 2026 · 5 filesMessage 50 · ThinLow 36Details
Commit message · Craig Raw

retain an entered https scheme for its host when configuring a bitcoin core server

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

This commit fixes a UI behavior in Sparrow Wallet where a user-entered HTTPS scheme for a Bitcoin Core server was not being remembered. Previously, if a user typed or selected an HTTPS Bitcoin Core URL, the wallet could silently fall back to HTTP when the host or port was edited, potentially sending wallet traffic over an unencrypted connection. The patch now records that a specific host was intended to use HTTPS and keeps using HTTPS for that host unless the host is changed. This is a security-relevant correctness fix for connection configuration, not an active exploit in the code itself.

AI review queuedreport bitcoin core rpc errors that carry no result instead of failing on a null responseby Craig Raw · b415e380 · Aug 28, 2026 · 1 fileMessage 50 · ThinLow 45Details
Commit message · Craig Raw

report bitcoin core rpc errors that carry no result instead of failing on a null 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 45/100

This commit fixes how Sparrow Wallet handles error responses from Bitcoin Core's RPC interface. Previously, the app could silently return a null value or crash with a confusing NullPointerException instead of telling the user what actually went wrong. The change makes error messages clearer and adds handling for HTTP 403 'forbidden' responses and non-JSON replies, which can happen when a proxy or TLS issue sits between Sparrow and Bitcoin Core.

AI review queuedbump to v2.5.5by Craig Raw · 067b4d37 · Aug 27, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · Craig Raw

bump to v2.5.5

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine version bump from 2.5.4 to 2.5.5. It only changes version strings in four files: the build script, macOS app metadata, in-app version constant, and documentation example. There are no code logic changes, no bug fixes, and no security-related content.

AI review queuedfix the windows test failures from crlf converted resources and a directory that cannot deny removalby Craig Raw · 8871f4f1 · Aug 27, 2026 · 3 filesMessage 60 · AdequateInformational 15Details
Commit message · Craig Raw

fix the windows test failures from crlf converted resources and a directory that cannot deny removal

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

This commit fixes automated test failures that only happen on Windows. It tells Git not to alter line endings in test resource files, updates a linked library (drongo), and skips one test on Windows because Windows cannot make a directory undeletable in the way the test expects. There is no user-facing security issue or vulnerability here.

AI review queuedname the conflicting keystore when an entered extended key is not uniqueby Craig Raw · ffc1221e · Aug 27, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · Craig Raw

name the conflicting keystore when an entered extended key is not unique

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

This commit improves an error message in Sparrow Wallet. When a user enters an extended public key that is already used by another keystore in the same wallet, the app now names the conflicting keystore instead of giving a generic 'not unique' message. There is no security vulnerability here; it is a user-experience improvement.

AI review queueddisable payjoin on transactions with silent payment outputsby Craig Raw · bb60cf0a · Aug 27, 2026 · 6 filesMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

disable payjoin on transactions with silent payment outputs

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 disables the Payjoin privacy feature when a Bitcoin transaction includes 'silent payment' outputs. Silent payments let someone receive Bitcoin without publicly revealing their address. The change prevents a risky combination where a Payjoin receiver adds their own inputs to the transaction, which would silently break the math that lets the real recipient detect and claim the silent payment. In short, the wallet now refuses to mix these two features so users don't accidentally send money to an address the recipient can no longer find.

AI review queuedfall back to the next usable camera instead of failing the qr scan on one reporting no resolutionsby Craig Raw · 344700f0 · Aug 26, 2026 · 2 filesMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

fall back to the next usable camera instead of failing the qr scan on one reporting no resolutions

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

This commit fixes a bug in Sparrow Wallet's QR code scanner. Previously, if one connected camera reported no supported video resolutions, the entire QR scan would fail. Now the app ignores such cameras and tries the next usable one instead. It also prevents a crash when the selected camera device becomes null. This is a robustness improvement, not a security vulnerability fix.

AI review queuedscope payjoin endpoints to the payment tab and transaction instead of the destination addressby Craig Raw · 7da2ebc7 · Aug 26, 2026 · 7 filesMessage 50 · ThinLow 44Details
Commit message · Craig Raw

scope payjoin endpoints to the payment tab and transaction instead of the destination 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 44/100

This commit changes how Sparrow Wallet remembers Payjoin payment instructions. Previously, the app stored Payjoin details keyed only by the destination Bitcoin address. That meant if you later made an unrelated payment to the same address, the app might still treat it as a Payjoin and contact the original Payjoin server. Now, Payjoin details are tied to the specific transaction (using its ID) and the payment tab, so they don't leak across separate payments to the same address. The included tests explicitly check that a later payment to the same address no longer retrieves the old Payjoin URI.

AI review queuedverify inclusion proofs for newly confirmed transactions, leaving them unconfirmed where they cannot be provedby Craig Raw · 12d45a8c · Aug 26, 2026 · 16 filesMessage 60 · AdequateModerate 68Details
Commit message · Craig Raw

verify inclusion proofs for newly confirmed transactions, leaving them unconfirmed where they cannot be proved

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

This commit adds a security feature to Sparrow Wallet that verifies Bitcoin transaction inclusion proofs supplied by Electrum servers. Before this change, the wallet trusted the server when it reported a transaction as 'confirmed' in a particular block. Now, for newly confirmed transactions, the wallet asks the server for a cryptographic Merkle proof and checks it against a verified block header. If the proof is missing, wrong, or for a different block, the transaction is demoted to 'unconfirmed' and the user is warned that the server may be faulty or dishonest. The change protects users against a malicious or compromised server falsely claiming a transaction was confirmed.

AI review queuedmaintain a verified block header store anchored at the pinned checkpoints, refreshing affected wallets on a reorgby Craig Raw · 74060d14 · Aug 25, 2026 · 10 filesMessage 50 · ThinModerate 61Details
Commit message · Craig Raw

maintain a verified block header store anchored at the pinned checkpoints, refreshing affected wallets on a reorg

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 adds a verified block-header store to the Sparrow Bitcoin wallet. It keeps a local copy of block headers above the built-in checkpoints, checks that each new header really links to the previous one, and automatically rewinds and refreshes wallet history if the Bitcoin chain reorganizes (a 'reorg'). The goal is to stop a malicious or buggy Electrum server from fooling the wallet with fake transaction confirmations.

AI review queueddocument the electrum server rpc method contractsby Craig Raw · 70f9c844 · Aug 24, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Craig Raw

document the electrum server rpc method contracts

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

This commit only adds plain-English documentation comments (Javadoc) above each method in an interface that describes how a Sparrow Wallet component talks to Electrum servers. No code behavior was changed, no bugs were fixed, and no security-sensitive logic was introduced.

AI review queuedsupport additional electrum server rpc methods and configurable batch pagingby Craig Raw · ccfb9fdb · Aug 24, 2026 · 15 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

support additional electrum server rpc methods and configurable batch paging

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 adds stronger verification when Sparrow Wallet talks to public Electrum servers on mainnet. It fetches and checks Merkle proofs for transactions and block headers from the server, and refuses to continue if the server cannot provide that proof. It also adds a new test task that checks built-in header checkpoints against live public servers. The change is defensive: it reduces the chance a malicious or buggy server can lie about transaction confirmations or chain history, but it is not a fix for a known active attack.

AI review queuedserialise usb device access so the periodic enumeration cannot interrupt an operation in progressby Craig Raw · 87c78be3 · Aug 23, 2026 · 3 filesMessage 50 · ThinLow 42Details
Commit message · Craig Raw

serialise usb device access so the periodic enumeration cannot interrupt an operation in progress

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 race condition in how Sparrow Wallet talks to USB hardware wallets. Previously, a background check for connected devices could run at the same time as a user action such as entering a PIN, signing a transaction, or displaying an address. That overlap could interrupt the device mid-operation, clear the PIN screen, or return confusing results. The change wraps all USB device operations with a single lock so they cannot overlap, and the periodic background check now skips its run if any device operation is already in progress.

AI review queueddisable transaction version and locktime editing once signedby Craig Raw · 5cdb3e04 · Aug 23, 2026 · 2 filesMessage 50 · ThinLow 44Details
Commit message · Craig Raw

disable transaction version and locktime editing once signed

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

This commit tightens Sparrow Wallet's user interface so that once a Bitcoin transaction has been signed, the user can no longer edit its version number or locktime fields. Before the change, the form relied on a simpler 'isEditable' check that could leave these fields enabled after signatures were added. Editing those fields after signing would change the transaction's hash (TXID), making the existing signatures invalid and potentially confusing the user into broadcasting a transaction that wallets or the network will reject. The fix centralizes the disable logic and makes editability explicitly depend on whether the transaction already contains script signatures or witness data.

AI review queuedclose storage opened when testing rejected wallet schemasby Craig Raw · 5b87f351 · Aug 23, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Craig Raw

close storage opened when testing rejected wallet schemas

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

This commit fixes a minor cleanup issue in a single test file. When running a test that checks whether invalid wallet files are rejected, the test now properly closes a temporary storage object afterward. It does not change any production code or fix a security vulnerability in the wallet itself.

AI review queuedimmediately close storage opened by persistence testingby nzb-tuxxx · bbfca5fd · Aug 23, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · nzb-tuxxx

immediately close storage opened by persistence testing

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

This is a small test-only cleanup. It adds a helper method that closes a temporary storage object after checking whether a wallet file is valid, and replaces four inline storage openings in tests with calls to that helper. There is no change to production code or user-facing behavior.