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 44 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 candidateprevent a locked wallet from signing a message, opening the dialog in verify only modeby Craig Raw · 8db14617 · Oct 5, 2026 · 1 fileMessage 60 · AdequateModerate 52Details
Commit message · Craig Raw

prevent a locked wallet from signing a message, opening the dialog in verify only mode

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

This commit fixes a small UI bug in Sparrow Wallet. Previously, if you selected a locked (password-protected) wallet and tried to open the 'Sign/Verify Message' screen, the app would still open the signing screen as if it could sign. The fix checks whether the wallet is locked and, if so, opens the screen in verify-only mode instead. This prevents a user from being misled into thinking they can sign a message while the wallet is locked, and it avoids a confusing or potentially unsafe UI state.

Security candidatefix typos in keycard comments, the inverted p2pk hash and mnemonic type wording, and jade decoding error messagesby Craig Raw · 5adb27e4 · Oct 5, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

fix typos in keycard comments, the inverted p2pk hash and mnemonic type wording, and jade decoding error messages

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

This commit only fixes spelling mistakes in code comments and user-facing error messages. It changes no program logic, no security checks, and no cryptographic behavior. There is no security issue here.

Security candidatesupport inline signed manifests in the download verifier by reading hashes from the verified signature contentby Craig Raw · 6ef88d84 · Oct 5, 2026 · 2 filesMessage 55 · ThinLow 40Details
Commit message · Craig Raw

support inline signed manifests in the download verifier by reading hashes from the verified signature content

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

This commit changes how Sparrow Wallet's download verifier reads the list of trusted file hashes. Previously, the verifier read hashes from a separate manifest file on disk. Now, it reads the hashes from the cryptographically signed content itself. This is meant to support 'inline signed manifests' and reduce the chance that an attacker could swap the manifest file after the signature was verified. The change also adds a size limit on the manifest content to prevent memory exhaustion.

Security candidatedeclare the regtest coin to trezor and bitbox02 devices on regtest, and allow bitbox02 message signing off mainnetby Craig Raw · b2ed172f · Oct 2, 2026 · 1 fileMessage 50 · ThinInformational 16Details
Commit message · Craig Raw

declare the regtest coin to trezor and bitbox02 devices on regtest, and allow bitbox02 message signing off mainnet

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

This commit updates a submodule called 'lark' inside the Sparrow Wallet project. The change appears to be about telling Trezor and BitBox02 hardware wallets how to handle Bitcoin's regtest network (a test-only network) and allowing message signing on the BitBox02 on test networks. The actual code change is not visible in this commit—only the submodule pointer was moved to a newer version. No security issue is directly visible from this commit alone.

Security candidatediscard a wallet discovery result where the words or passphrase were edited while it ranby Craig Raw · f81f6790 · Oct 2, 2026 · 1 fileMessage 50 · ThinLow 43Details
Commit message · Craig Raw

discard a wallet discovery result where the words or passphrase were edited while it ran

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

This commit fixes a timing issue in Sparrow Wallet's wallet-import screen. If a user changed their seed words or passphrase while a background 'discover wallet' scan was still running, the app could previously show results from the old (or partially changed) words/passphrase. The patch now captures the words and passphrase at the start of the scan and discards the result if they changed before the scan finished, preventing the user from importing a wallet they did not intend to.

Security candidateshow an error when a scanned ur of type bytes is not a psbt, transaction or utf-8 textby Craig Raw · d326df88 · Sep 28, 2026 · 1 fileMessage 50 · ThinLow 30Details
Commit message · Craig Raw

show an error when a scanned ur of type bytes is not a psbt, transaction or utf-8 text

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

This commit fixes a small bug in Sparrow Wallet's QR code scanner. Previously, when a scanned QR code contained raw bytes that could not be recognized as a PSBT, transaction, or readable text, the scanner would create an error message but accidentally continue processing and eventually return nothing (null). Now it immediately returns the error message to the user. This is a minor user-experience and error-handling improvement, not a serious security flaw.

Security candidateremove the surplus signatures progress bar segments a finalized multisig transaction discardsby Craig Raw · 40f77206 · Sep 22, 2026 · 2 filesMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

remove the surplus signatures progress bar segments a finalized multisig transaction discards

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

This commit fixes a UI display bug in Sparrow Wallet's signature progress bar. When a multi-signature Bitcoin transaction becomes finalized, extra signatures beyond the required threshold are discarded. Previously, the progress bar did not remove the visual segments representing those discarded signatures, which could leave the bar showing more segments than actually exist. The fix cleans up those surplus segments and resets progress to zero for any segment whose signature was removed. There is no direct evidence this affects funds or transaction security.

Security candidateinclude the non-witness utxo in psbts for krux keystores, and in the qr display when the psbt has more than one inputby Craig Raw · 0e2c402f · Sep 15, 2026 · 2 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

include the non-witness utxo in psbts for krux 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 boundarysigning or wallet path
AI analysis · Low 34/100

This commit changes how Sparrow Wallet builds QR codes for partially-signed Bitcoin transactions (PSBTs). For certain hardware wallets (Krux), it now includes extra data (the full previous transaction, called 'non-witness utxo') in the QR code when the transaction has more than one input. This extra data is needed by some devices to verify inputs securely, but it also makes the QR code larger and slower to scan. The change appears to be a correctness/usability fix for hardware signing rather than a traditional software vulnerability.

Security candidatekeep the trezor pairing credential and v1 message payloads out of the logsby Craig Raw · 2a60100e · Sep 14, 2026 · 1 fileMessage 50 · ThinModerate 56Details
Commit message · Craig Raw

keep the trezor pairing credential and v1 message payloads out of the logs

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Moderate 56/100

This commit updates a linked subproject called 'lark' with the stated goal of preventing Trezor hardware wallet pairing credentials and older v1 message payloads from being written to application logs. If successful, it reduces the risk that sensitive wallet communication secrets could leak through log files, which might otherwise be read by malware, backups, or support staff. However, the actual code changes are inside the subproject and not visible in this commit, so we can only judge from the commit message.

Security candidateverify psbt silent payment metadata against the input hash of every input, not only the eligible onesby Craig Raw · 8e9661a6 · Sep 11, 2026 · 1 fileMessage 60 · AdequateModerate 55Details
Commit message · Craig Raw

verify psbt silent payment metadata against the input hash of every input, not only the eligible ones

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 boundary
AI analysis · Moderate 55/100

This commit updates a submodule called 'drongo' with a one-line change whose message says it now checks silent payment metadata against every transaction input, not just the eligible ones. Silent payments are a privacy feature for Bitcoin. The change sounds like a security fix because verifying only some inputs could let a malicious or malformed PSBT (a partially-signed Bitcoin transaction) slip past checks. However, the actual code change is just a submodule pointer bump, so we cannot see the real code fix from this commit alone.

Security candidateexplicitly reject a psbt signed over silent payment outputs that have not been computedby Craig Raw · 6fcdc88b · Sep 11, 2026 · 1 fileMessage 50 · ThinModerate 55Details
Commit message · Craig Raw

explicitly reject a psbt signed over silent payment outputs that have not been computed

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

This commit updates a submodule called 'drongo' inside the Sparrow Wallet project. The title says it now explicitly rejects a partially-signed Bitcoin transaction (PSBT) if it has been signed over silent payment outputs that were not actually computed. In plain terms, it tries to prevent a wallet from accepting a transaction signature that covers hidden recipient addresses it never verified. We cannot see the actual code change because only the submodule commit hash changed.

Security candidateverify the signatures of a finalized psbt before copying its fields into an open transactionby Craig Raw · 3590fb3a · Sep 9, 2026 · 2 filesMessage 60 · AdequateModerate 69Details
Commit message · Craig Raw

verify the signatures of a finalized psbt before copying its fields into an open transaction

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

This commit fixes a security gap in Sparrow Wallet when merging two partially-signed Bitcoin transactions (PSBTs). Previously, if a newly loaded PSBT was already finalized, Sparrow would copy its signatures and final transaction data into an open transaction without first checking that those signatures were valid. The change adds a verification step so invalid or malicious finalized PSBT data is rejected before it can overwrite the existing transaction.

Security candidatedo not offer copy and qr export actions for an extended private key pasted into the keystore xpub fieldby Craig Raw · 34f27fd8 · Sep 9, 2026 · 1 fileMessage 55 · ThinModerate 59Details
Commit message · Craig Raw

do not offer copy and qr export actions for an extended private key pasted into the keystore xpub field

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

This commit fixes a UI behavior in Sparrow Wallet where a user could accidentally paste a secret extended private key (xprv) into the public-key-only 'xpub' field of a watch-only wallet. Previously, the app treated it as valid, offered copy/QR-code export actions, and could leak the private key through those export paths. Now the app rejects xprv input in that field, removes the export context menu, and shows a validation error.

Security candidateverify silent payment output scripts before device signing, combining and exportby Craig Raw · ed78418a · Sep 7, 2026 · 3 filesMessage 60 · AdequateModerate 68Details
Commit message · Craig Raw

verify silent payment output scripts before device signing, combining and export

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

This commit adds safety checks in the Sparrow Bitcoin wallet to verify Silent Payment output scripts before exporting, copying, combining, or sending a transaction to a hardware device for signing. Silent Payments are a privacy feature that lets someone generate a unique receiving address from a public 'silent' address. The change makes sure the wallet can prove the claimed payment address is correct before the user signs or shares the transaction, reducing the risk of sending funds to a wrong or attacker-controlled address.

Security candidateshow the signatures for a signed transaction opened offline or when the server cannot return every inputby Craig Raw · aeeeeb54 · Aug 31, 2026 · 4 filesMessage 50 · ThinInformational 17Details
Commit message · Craig Raw

show the signatures for a signed transaction opened offline or when the server cannot return every input

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

This commit fixes a UI bug in the Sparrow Bitcoin wallet. When a user opened a fully signed transaction while offline, or when the connected server could not provide every previous transaction input, the wallet failed to display the transaction's signature details and the broadcast controls. The patch makes the wallet derive and show the signature progress bar directly from the signed transaction data in those cases, instead of waiting for server data that may never arrive.

Security candidategate the display address, sign message and keystore discovery panes on a fingerprint resolved after pin entryby Craig Raw · 5f7770b8 · Aug 26, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · Craig Raw

gate the display address, sign message and keystore discovery panes on a fingerprint resolved after pin entry

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

This commit changes how Sparrow Wallet checks that a connected hardware wallet is the correct one before letting the user display a receiving address, sign a message, or discover keystores. Previously, the app disabled the relevant buttons if the device's reported fingerprint did not match the wallet. The problem is that a PIN-protected device reports no fingerprint until after the PIN is entered, so the old check happened too early and could be bypassed. The new code waits until after PIN entry, re-enumerates the device to get its real fingerprint, and only then enables or disables the button. This prevents a user from accidentally using the wrong hardware wallet and, for example, displaying or signing with keys that do not belong to their wallet.

Security candidatereport an oversized download manifest instead of verifying the signature aloneby Craig Raw · 0e8d8192 · Aug 26, 2026 · 2 filesMessage 55 · ThinLow 46Details
Commit message · Craig Raw

report an oversized download manifest instead of verifying the signature alone

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

This commit changes how Sparrow Wallet's download verifier handles large manifest files. Previously, if a downloaded manifest exceeded 100 KB, the software would reject it outright and stop verification. Now, if the oversized file does not look like a manifest (no PGP signed-message header and no typical hash lines), it is treated as a release file that the signature signs directly. The change also adds a more descriptive error message. The commit title frames this as reporting an oversized manifest rather than only verifying the signature, suggesting a fix for a verification-logic edge case.

Security candidateconfirm the passphrase in the wallet-level and terminal seed importsby Craig Raw · d8ea4264 · Aug 26, 2026 · 3 filesMessage 50 · ThinLow 34Details
Commit message · Craig Raw

confirm the passphrase in the wallet-level and terminal seed imports

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

This commit adds a 'confirm your passphrase' step when importing a Bitcoin wallet seed in two places: the desktop wallet import screen and the terminal/command-line wallet creation. Previously, if a user typed a BIP39 passphrase (the extra password that unlocks a hidden wallet) with a typo, Sparrow would silently create a different wallet. The user might then send funds to addresses they do not actually control or cannot later reproduce. The fix forces the user to type the passphrase twice so typos are caught immediately.

Security candidateclarify that the slip39 import passphrase applies to all shares and not individual onesby Craig Raw · 0a484201 · Aug 23, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

clarify that the slip39 import passphrase applies to all shares and not individual ones

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 only changes on-screen text labels and help messages in the wallet import flow. It clarifies that when using SLIP39 'shamir secret sharing' recovery, any passphrase applies to the whole reconstructed wallet secret, not to each individual recovery share. There is no code behavior change, no bug fix, and no security vulnerability being patched.

Security candidateupdate drongo and lark to require anti-klepto on bitbox02 and fix taproot signing issueby Craig Raw · e7ae9cca · Aug 21, 2026 · 2 filesMessage 50 · ThinModerate 55Details
Commit message · Craig Raw

update drongo and lark to require anti-klepto on bitbox02 and fix taproot signing issue

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

This commit updates two internal library submodules (drongo and lark) used by the Sparrow Wallet. The stated purpose is to require an anti-klepto protection feature for BitBox02 hardware wallets and to fix a Taproot signing issue. The actual code changes are not visible in this commit—only the submodule pointers were moved to new commits—so we cannot directly inspect what was fixed. Anti-klepto protections reduce the risk of a compromised hardware wallet leaking private key material through biased signatures. A Taproot signing issue could, in principle, affect the ability to spend or the validity of signatures, but the diff gives no details.

Security candidatecomment on why the securerandom.getinstancestrong() fallback is neither weaker nor reachableby Craig Raw · 9b05c26c · Aug 21, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · Craig Raw

comment on why the securerandom.getinstancestrong() fallback is neither weaker nor reachable

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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit only adds explanatory comments to existing code. It does not change any behavior. The comments clarify that a fallback to a standard SecureRandom is not a security weakness and is practically unreachable in the bundled Java runtime. There is no functional change to how random numbers are generated for wallet seed phrases.

Security candidatecompare the ecies mac in constant time and test the invalid password causeby Craig Raw · 4e2903fe · Aug 21, 2026 · 2 filesMessage 60 · AdequateLow 47Details
Commit message · Craig Raw

compare the ecies mac in constant time and test the invalid password cause

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
constant-time or timing behaviorsigning or wallet path
AI analysis · Low 47/100

This commit updates a subproject dependency called 'drongo' and adds a test. The title says the update makes an ECIES (a type of encryption) MAC comparison run in constant time, which is a defensive fix against timing attacks that could let someone guess a wallet password faster. The new test checks that entering the wrong password produces a clear 'invalid password' error rather than a vague import error. No direct code change is shown in the diff for the crypto routine itself; it lives inside the updated submodule.

Security candidatereprompt for the bip38 passphrase rather than clearing the encrypted keyby Craig Raw · 325ab3b7 · Aug 21, 2026 · 2 filesMessage 50 · ThinInformational 22Details
Commit message · Craig Raw

reprompt for the bip38 passphrase rather than clearing the encrypted key

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

This commit changes how Sparrow Wallet handles a wrong BIP38 passphrase when sweeping an encrypted private key. Previously, entering the wrong passphrase cleared the entire encrypted key text, forcing the user to retype it. Now, the app simply shows an 'Incorrect passphrase' error and asks again, leaving the encrypted key in place. It is a usability improvement, not a security fix, and does not appear to prevent or introduce any exploit.

Security candidatepin the gradle distribution checksum in the wrapper propertiesby Craig Raw · b3b55a5f · Aug 20, 2026 · 3 filesMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

pin the gradle distribution checksum in the wrapper properties

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

This commit adds a cryptographic fingerprint (SHA-256 checksum) to the project's Gradle wrapper configuration. The wrapper is the tool that downloads the Gradle build system when developers compile the wallet. Pinning the checksum helps ensure that a compromised or tampered Gradle download is detected before it can run during the build process. Two Git submodules named drongo and lark were also updated, but no details about their changes are provided in the diff.

Security candidateredact the core credentials from the bwt debug logby Craig Raw · fb811e10 · Aug 20, 2026 · 2 filesMessage 50 · ThinLow 49Details
Commit message · Craig Raw

redact the core credentials from the bwt debug log

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

This commit fixes a privacy/security issue where Sparrow Wallet's debug log could accidentally record the username and password used to connect to a Bitcoin Core node. When debug logging was enabled, the app printed the full internal configuration of a component called bwt, including the 'bitcoind_auth' field that contained the user's Core RPC credentials. The patch now replaces that credential with '*****' before writing it to the log. This reduces the risk that sensitive credentials leak into log files, which could then be exposed when users share logs for troubleshooting.