SW
← All projectsSparrow

Sparrow Wallet

Desktop Bitcoin wallet focused on security, privacy, multisignature, and hardware signers.

BitcoinHardware integrationSoftware walletsNormal
Repository coverage

630 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

102security candidates447second-pass queue606AI analyses
181commits · 30 days
220commits · 60 days
411commits · 180 days
584commits · 365 days
Backfill bands
Aug 5 → Feb 6100 seen9 candidatesComplete
Feb 6 → Jun 6128 seen15 candidatesComplete
Jun 6 → Jul 67 seen1 candidatesComplete
Jul 6 → Aug 546 seen8 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

49/100 average clarity
0Strong · 80–100
55Adequate · 60–79
520Thin · 40–59
55Opaque · 0–39
3security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Craig Raw61398589949
doblon8313048
Michele Balistreri212048
nzb-tuxxx212060
nroktib111050
Liz Lightning202045
Aaron Leeb101060
PeterXMR101045
craigraw101060
Ian McKenzie101050
Jan Dvořák101050
Kevin Abramczyk101050
Analysis record

Published AI watches

Last scanned 48 minutes ago

Informational 18 AI analysisMessage 60 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

document building v2.5.3 to v2.5.6 with lenient dependency verification, as two pom files were later republished to maven central with additional metadata

This commit only updates documentation. It explains that when building older Sparrow Wallet releases (versions 2.5.3 through 2.5.6), two dependency files on Maven Central were later republished with extra descriptive metadata, causing a ha…

Dependency checksum mismatch in recorded verification metadataPOM-only republication of two Sparrow-published artifacts (hid4java, usb4java)Documentation instructs lenient verification for reproducible builds of older releases
6a83c9a5by Craig Raw+15−01 file
No security note in commit
Low 34 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

warn that a bip353 name resolved to a silent payment address for a different network on the send tab and in send to many, rather than reporting it has no address

This commit improves user-facing error messages in the Sparrow Wallet when a BIP353 human-readable name (like a DNS-based Bitcoin payment alias) resolves to a silent payment address meant for a different Bitcoin network (for example, testn…

BIP353 DNS payment resolutionsilent payment address network mismatchuser-facing warning improvement
08f32515by Craig Raw+6−13 files
No security note in commit
Low 26 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

skip the keepalive ping while another request is awaiting its response

This change stops Sparrow Wallet from sending unnecessary 'are you still there?' keepalive pings when another request is already waiting for an answer. On some Electrum server backends (notably electrs), a ping would queue up behind the pe…

Avoidance of redundant keepalive pings that could delay synchronizationNew transport-level predicate exposing in-flight request stateUnit test added to assert correct pending-request lifecycle
4df18311by Craig Raw+50−13 files
No security note in commit
Low 38 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

wait for a slow electrum server response instead of resending the request, halving batch page sizes only after a request goes unanswered, and retry the keepalive ping once

This commit changes how the Trezor hardware wallet app talks to Bitcoin servers when responses are slow. Previously, the app would quickly resend a request if it didn't get an answer in time, and each timeout would double the wait and halv…

Change to timeout/retry logic that could affect denial-of-service resilienceReduction in retry count for keep-alive pings from 5 to 2Avoidance of duplicate request sending to slow servers, reducing amplification
96d217cfby Craig Raw+84−194 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

reduce the minimum window width to 750, fitting the send tab, transaction diagram and transaction tab views to narrow windows and narrowing the wallet menu and transaction tree below 900

This commit is a user-interface layout tweak for the Sparrow Wallet desktop app. It makes the main window usable at narrower widths by shrinking minimum sizes, wrapping labels, and making diagrams and menus responsive. There is no security…

86e52311by Craig Raw+117−4717 files
No security note in commit
Moderate 61 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

check a proof that does not reconstruct against the server chain before reporting it, as a server can report a transaction on a branch before announcing its tip

This commit fixes a bug in how Sparrow Wallet checks Bitcoin transaction proofs from an Electrum server. Previously, if a server had switched to a different blockchain branch (for example due to a reorganization) but had not yet announced …

Merkle proof verification bypass/relaxation under reorganization windowServer-side blockchain state synchronization before proof validationRisk of false-negative proof rejection leading to incorrect transaction confirmation status
f7357906by Craig Raw+91−22 files
No security note in commit
Low 33 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This commit fixes a bug in Sparrow Wallet's 'Border Wallets' feature. Previously, the app guessed whether a grid of seed-word abbreviations was hexadecimal (base-16) by looking only at the cells the user selected. If a user happened to pic…

Incorrect input classification leading to wrong BIP39 word derivationWallet seed/recovery correctness issueUI dialog parsing bug in mnemonic grid import
0d4f1482by Craig Raw+9−61 file
No security note in commit
Low 43 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This commit fixes a bug in how Sparrow Wallet reads QR codes using the ZBar scanner. ZBar converts binary QR code data into text and silently stops at the first null byte, which can corrupt non-text data. The fix makes Sparrow only trust Z…

Data integrity issue in QR code parsingReliance on lossy text conversion for binary dataSilent truncation at NUL byte
0c28eafeby Craig Raw+25−12 files
No security note in commit
Low 27 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

save the freeze status and labels of nested wallet outputs to the wallet that stores them

This commit fixes a bookkeeping bug in Sparrow Wallet for users who have a main wallet with nested sub-wallets (for example, PayNym-style wallets). Previously, when you froze an unspent coin or changed its label, the change was recorded ag…

State-persistence bug: freeze/label changes for nested-wallet UTXOs were saved to the wrong walletUI/event routing now keyed by owning wallet rather than display walletNew unit tests added to assert correct ownership semantics
5c47c3a4by Craig Raw+116−2611 files
No security note in commit
Moderate 58 AI analysisMessage 62 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This commit fixes how Sparrow Wallet stores the backup/recovery seed when a user imports a wallet using SLIP39 shares (a type of multi-share mnemonic backup). Previously, the wallet decrypted the shares with the passphrase entered at impor…

SLIP39 passphrase handling changed from one-time decryption to persistent encrypted master secretStored seed now derives correct keys regardless of which passphrase is later usedNew unit test explicitly checks passphrase-variant key derivation parity
9b998a78by Craig Raw+47−43 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This is a minor user-interface bug fix. It ensures that Bitcoin addresses in the wallet's UTXO list keep their fixed-width (monospaced) font after the table is refreshed. There is no security issue here.

868fa081by Craig Raw+2−11 file
No security note in commit
Low 46 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

refuse descriptors that do not derive on the standard receive and change chains when importing a wallet or keystore, and warn of them in the descriptor editor

This commit tightens how Sparrow Wallet handles Bitcoin output descriptors imported from files, hardware wallets, QR codes, and the descriptor editor. It now rejects (or warns about) descriptors whose key paths don't follow the standard 'r…

New validation of BIP32 derivation paths on all descriptor import pathsRejection of descriptors with non-standard receive/change chains during wallet/keystore importWarning (but not rejection) retained for descriptor editor where user can amend the descriptor
3d2fbac4by Craig Raw+23−910 files
No security note in commit
Moderate 58 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This commit changes how Sparrow Wallet handles QR code and file imports of Bitcoin wallet descriptors. Previously, when scanning a descriptor from a QR code, the wallet might ignore or mishandle 'child derivation' paths that tell it how to…

Input validation added for scanned output descriptor child derivationsRejection of non-standard child derivation chainsConsistent application of child derivations between QR/file import and text descriptor parsing
6a000160by Craig Raw+290−403 files
No security note in commit
Moderate 60 AI analysisMessage 55 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

refuse an extended private key in place of an xpub in imported wallet files, and use the public key of a private hdkey in a scanned output descriptor

This commit fixes a security issue in Sparrow Wallet where wallet import files or QR scans that were supposed to contain only public extended keys (xpubs) could accidentally or maliciously contain private extended keys (xprvs). The wallet …

Rejection of extended private keys where extended public keys are expectedPublic-key derivation from private HD keys in scanned output descriptorsAddition of defensive validation helper across multiple wallet import formats
97742cabby Craig Raw+52−298 files
Vendor flagged security relevance
Informational 19 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This change improves the Sparrow Wallet terminal (command-line) interface. Previously, if the wallet discovery process found transactions matching more than one Bitcoin script type, it would silently pick the first one. Now it shows a menu…

Behavioral fix: prevents silent selection of first discovered wallet script typeUser-choice dialog added in terminal wallet creation flowNo cryptographic, network, or input-validation changes observed
a18db115by Craig Raw+18−41 file
No security note in commit
Low 33 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

use the bip352 derivation for silent payment wallets imported from a mnemonic or device, created in the terminal, scanned from a seedqr or added at another account

This commit changes how Sparrow Wallet picks the derivation path when creating or importing wallets. It makes the wallet choose BIP-352 (silent payments) paths when the wallet policy is a single-key silent-payment wallet, instead of always…

Derivation-path selection now depends on policy type, which can change wallet fingerprint/address generation for silent-payment walletsBroad surface area (12 files) increases risk of an import path being missed or behaving differentlySubmodule bump (drongo) likely contains the actual ScriptType.getDefaultDerivation(PolicyType) implementation, but its diff is not supplied
002b1b58by Craig Raw+41−3012 files
No security note in commit
Low 37 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This commit makes two small UI fixes in Sparrow Wallet. First, it strips hidden control characters from cosigner labels when importing a shared multisig wallet setup, preventing odd or misleading label display. Second, it fixes alert dialo…

Sanitization of user-supplied labels (control/format characters replaced)UI dialog sizing fix to prevent content clippingNo explicit security framing in commit message or diff
c1d4feeaby Craig Raw+3−12 files
No security note in commit
Low 34 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This commit fixes a bug where Sparrow Wallet's database update path failed to shorten (truncate) long labels for wallet addresses, purpose nodes, and keystores before saving them. The full save path already did this truncation, but the inc…

Data-integrity bug: inconsistent truncation between full save and incremental updatePotential denial-of-service against local wallet state via overly long labelsRegression test added to prevent future recurrence
0721ca98by Craig Raw+50−52 files
No security note in commit
Low 32 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

refuse the bwt fallback for bitcoin core over https and ignore the legacy wallet setting for it

This commit changes Sparrow Wallet so that when it connects to a Bitcoin Core node over HTTPS, it no longer falls back to an older 'BWT' connection method and no longer tries to use legacy Bitcoin Core wallets. The change appears to be a h…

Disables legacy wallet handling for HTTPS Bitcoin Core connectionsRemoves BWT fallback for HTTPS Bitcoin Core connectionsForces Bitcoin Core v24+ requirement for HTTPS connections
b935568aby Craig Raw+8−22 files
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

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

This one-line change fixes how Sparrow Wallet checks a Bitcoin server’s TLS certificate. Previously, when the server used an RSA certificate, the app told Java’s certificate validator to expect an old-style RSA key exchange ("RSA"). That w…

TLS certificate validation logic changedX509TrustManager.checkServerTrusted authType correctedPotential for certificate acceptance/rejection mismatch before fix
1071ed7cby Craig Raw+1−11 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedadd connected device wallet discovery with configurable number of accounts to scanby Craig Raw · 0c2ee669 · Jan 22, 2026 · 9 filesMessage 50 · ThinInformational 18Details
Commit message · Craig Raw

add connected device wallet discovery with configurable number of accounts to scan

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 adds a new feature to Sparrow Wallet that lets users scan a connected hardware wallet for existing accounts and transactions across multiple script types. It is a feature addition, not a security fix. The code changes how wallet import events and discovery results are handled, moving from single-wallet to multi-wallet results. There is no direct evidence in the commit of a vulnerability being patched.

AI review queuedadd user agent to coingecko historical rates callby Liz Lightning · 85c81adc · Jan 21, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · Liz Lightning

add user agent to coingecko historical rates call

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

This commit is a small cleanup that makes the CoinGecko historical exchange-rate request send the same browser-like User-Agent header that other exchange-rate calls already use. Previously, that one CoinGecko call sent no special headers. The change is unlikely to be a security fix on its own; it looks more like a reliability tweak to avoid being blocked by the CoinGecko API, which sometimes rejects requests without a User-Agent.

AI review queuedimprove qr encoding ui, save previous selection and add raw encoding for tx hexby Craig Raw · 04de8370 · Jan 20, 2026 · 13 filesMessage 50 · ThinInformational 18Details
Commit message · Craig Raw

improve qr encoding ui, save previous selection and add raw encoding for tx hex

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 is a user-interface improvement for Sparrow Wallet's QR code sharing feature. It replaces a simple on/off toggle between two QR formats with a dropdown menu that also adds a new 'Raw' option for transaction hex, and it remembers the user's last chosen format. There is no indication this fixes a security vulnerability.

AI review queueduse precise fee rates estimate from mempool.spaceby Craig Raw · 53857389 · Jan 15, 2026 · 1 fileMessage 45 · ThinInformational 21Details
Commit message · Craig Raw

use precise fee rates estimate from mempool.space

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

This commit changes the Bitcoin fee-rate data source used by Sparrow Wallet from mempool.space's standard recommended-fee endpoint to its more precise fee-estimate endpoint. It is a minor data-source change, not a code-level security fix. There is no indication in the commit that this resolves a security vulnerability.

AI review queuedconvert from tilepane to gridpane to resolve mnemonic words layout issueby Craig Raw · 98576d40 · Jan 14, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

convert from tilepane to gridpane to resolve mnemonic words layout issue

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

This commit is a purely cosmetic UI change in the Sparrow Wallet desktop app. It swaps the JavaFX layout component used to display BIP39 mnemonic word fields from a TilePane to a GridPane so the 12 or 24 seed words line up in a tidy grid. There is no change to how seed words are generated, stored, validated, or protected, and no security-relevant behavior is introduced or fixed.

AI review queuedadd additional fee rate limit check for high fee transactionsby Craig Raw · 96f7d4bd · Jan 13, 2026 · 1 fileMessage 50 · ThinLow 45Details
Commit message · Craig Raw

add additional fee rate limit check for high fee transactions

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 adds an extra safety check in Sparrow Wallet that warns users before broadcasting Bitcoin transactions with extremely high fee rates. Previously, the wallet only warned if the fee rate exceeded the top of a long-term fee rate range. Now it also warns if the fee rate is more than 100 times the default fee rate. This helps prevent users from accidentally overpaying transaction fees, which could be caused by user error, wallet misconfiguration, or potentially a malicious or compromised transaction.

AI review queuedadd user agent to coingecko exchange source requestby Craig Raw · 0515d805 · Jan 13, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Craig Raw

add user agent to coingecko exchange source request

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

This commit changes how Sparrow Wallet asks CoinGecko for currency exchange rates. It now sends a fake web-browser 'User-Agent' header instead of none. This is likely a workaround because CoinGecko started blocking or rate-limiting requests that had no user agent. It is not a fix for a vulnerability in Sparrow itself, but it does make Sparrow's exchange-rate requests slightly more identifiable and could affect privacy if the same user agent is reused elsewhere.

AI review queuedavoid extraneous error logging on card enumerationby Craig Raw · cf15760d · Jan 13, 2026 · 2 filesMessage 50 · ThinInformational 11Details
Commit message · Craig Raw

avoid extraneous error logging on card enumeration

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

This commit makes two small logging and error-handling changes in code that talks to smart cards (hardware wallets). It downgrades one routine card-enumeration error from 'error' to 'info' level, and turns a swallowed CBOR parsing error into a thrown exception. There is no indication these changes fix a security vulnerability; they appear to be code-quality or diagnostic-noise improvements.

AI review queuedremove unnecessary lark .gitmodulesby Craig Raw · f28f15df · Jan 13, 2026 · 1 fileMessage 35 · OpaqueInformational 12Details
Commit message · Craig Raw

remove unnecessary lark .gitmodules

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

This commit removes an unnecessary Git submodule configuration entry named 'lark' from the .gitmodules file. It is a minor repository cleanup change with no apparent security relevance.

AI review queuedadd warning when entering outdated slip132 values into a watch-only wallet of a different script typeby Craig Raw · 430f2ee3 · Dec 23, 2025 · 1 fileMessage 50 · ThinLow 30Details
Commit message · Craig Raw

add warning when entering outdated slip132 values into a watch-only wallet of a different script type

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

This commit adds a warning message in Sparrow Wallet when a user pastes an older-style extended public key (SLIP132 format) into a watch-only wallet that uses a different Bitcoin address type. It does not change wallet logic or fix a vulnerability; it only alerts the user to a possible mismatch so they can correct it. The change is defensive UX, not a security patch.

AI review queuedminor trezor v2 fixesby Craig Raw · 74160ba3 · Dec 20, 2025 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Craig Raw

minor trezor v2 fixes

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 changes the left and right margins of a text input dialog box from 60 pixels to 65 pixels. It is purely a cosmetic/layout adjustment for the Trezor hardware wallet v2 integration and has no security relevance.

AI review queuedadd trezor safe 7 noise config implementationby Craig Raw · 04064219 · Dec 17, 2025 · 2 filesMessage 45 · ThinInformational 20Details
Commit message · Craig Raw

add trezor safe 7 noise config implementation

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

This commit adds support for pairing the Trezor Safe 7 hardware wallet with Sparrow Wallet. It introduces a JavaFX dialog flow that asks the user to confirm pairing and enter a pairing code shown on the device. The change is a feature addition for a new hardware device and does not, on its own, appear to be a security vulnerability. The pairing secrets are stored in a local JSON file, similar to how the existing BitBox02 pairing is handled.

AI review queuedadd ledger nano gen5 supportby Craig Raw · a49edb7c · Dec 11, 2025 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Craig Raw

add ledger nano gen5 support

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 adds support for a new Ledger hardware wallet model (Ledger Nano generation 5) and also includes a small UI update to recognize the Trezor Safe 7 model in a list of devices that support passphrase toggling. There is nothing in the code changes that suggests a security vulnerability or malicious behavior.

AI review queuedadd codex32 importer to software keystore import workflowby Ian McKenzie · 4dcd463d · Dec 9, 2025 · 4 filesMessage 50 · ThinInformational 16Details
Commit message · Ian McKenzie

add codex32 importer to software keystore import workflow

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

This commit adds a new feature to Sparrow Wallet that lets users import a Bitcoin keystore from a Codex32 (BIP93) secret share. Codex32 is a standard for encoding a seed or secret as a human-readable string with a checksum. The change is purely additive: it introduces a new import pane, a new BIP93 importer class, and wires them into the existing software keystore import workflow. There is no indication in the commit that this fixes a security bug; it appears to be a normal feature addition.

AI review queuedensure plugdev is added as a system groupby Craig Raw · b0ab6c9d · Dec 3, 2025 · 4 filesMessage 45 · ThinInformational 21Details
Commit message · Craig Raw

ensure plugdev is added as a system group

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

This commit changes how the Linux installer creates the 'plugdev' group. Previously it created a normal user group; now it creates it as a system group using the -r flag. System groups are intended for services and hardware access, and using one here is more conventional for a group that grants device access. The change is a packaging/installation hardening improvement, not a fix for an active exploit.

AI review queuedfollowup to display address for watch-only walletsby Craig Raw · a6081970 · Nov 26, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Craig Raw

followup to display address for watch-only 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 · Informational 15/100

This is a small UI follow-up fix that changes when the 'Display Address' button is shown for watch-only wallets. Previously, the button only appeared if all keystores were watch-only software wallets. Now it appears if any keystore is watch-only or a hardware USB device. There is no security issue visible in the change.

AI review queuedadd block.xyz augur fee estimatorby Liz Lightning · 6452bf81 · Nov 25, 2025 · 3 filesMessage 45 · ThinInformational 19Details
Commit message · Liz Lightning

add block.xyz augur fee estimator

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

This commit adds a new optional Bitcoin transaction fee estimator source called block.xyz (using Block's 'Augur' fee estimation service) to the Sparrow Wallet desktop app. It lets users choose this service when estimating how much fee to pay for Bitcoin transactions. There is no obvious security bug in the code, but adding any new external data source creates a small expansion of the app's 'attack surface' and trust assumptions.

AI review queuedalways show display address for watch-only walletsby Craig Raw · 71cb5852 · Nov 25, 2025 · 1 fileMessage 50 · ThinLow 26Details
Commit message · Craig Raw

always show display address for watch-only 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 · Low 26/100

This small change makes the 'Display Address' button always appear for watch-only wallets in Sparrow Wallet. Watch-only wallets cannot spend funds, so this is mainly a usability improvement to help users verify receiving addresses. It does not appear to fix a vulnerability that lets someone steal bitcoins, but it may reduce the chance a user sends funds to a wrong or attacker-controlled address.

AI review queuedpass default derivation to usb device and card import panesby Craig Raw · 8efee4ea · Nov 25, 2025 · 6 filesMessage 50 · ThinLow 27Details
Commit message · Craig Raw

pass default derivation to usb device and card import panes

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

This commit changes how Sparrow Wallet picks the default Bitcoin key derivation path when importing from a hardware wallet or card. Previously, the wallet always used the default path for the wallet's script type. Now it can accept and use a 'default derivation' suggested by the caller, falling back to the script type default only if none is provided. The change also fixes a potential null-pointer issue when no wallet or script type is available. There is no direct evidence in the commit of a security vulnerability being fixed; it reads more like a correctness or feature improvement for derivation-path handling.

AI review queuedupdate to support bip375by Craig Raw · 6f772cb1 · Nov 18, 2025 · 7 filesMessage 28 · OpaqueInformational 15Details
Commit message · Craig Raw

update to support bip375

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 code cleanup to support a new Bitcoin standard (BIP375). It simply moves the definition of a default placeholder fingerprint for watch-only wallets from one class (KeystoreController) to another (KeyDerivation), and updates all references. There is no security bug being fixed here.

AI review queuedadd keycard shell importers for singlesig and multisigby Michele Balistreri · a794dafd · Nov 12, 2025 · 8 filesMessage 50 · ThinInformational 15Details
Commit message · Michele Balistreri

add keycard shell importers for singlesig and multisig

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

This commit adds support for importing Bitcoin wallet data from a new hardware device called Keycard Shell. It is a straightforward feature addition: two new import handlers (one for single-signature wallets, one for multi-signature wallets), wiring them into the existing import menus, and adding device icons. There is no indication of a security bug, vulnerability, or malicious change in the diff.

AI review queuedadd bech32m testsby Craig Raw · 9fb19ebe · Nov 12, 2025 · 1 fileMessage 38 · OpaqueInformational 2Details
Commit message · Craig Raw

add bech32m tests

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 2/100

This commit appears to add tests for bech32m, a Bitcoin address format used with newer wallets. The title and message say only 'add bech32m tests', and the diff was not supplied. There is no indication of a security fix, vulnerability, or behavior change in the application itself.

AI review queuedadd frigate to detected electrum server capabilities listby Craig Raw · 39cb946e · Nov 10, 2025 · 1 fileMessage 50 · ThinInformational 16Details
Commit message · Craig Raw

add frigate to detected electrum server capabilities list

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

This commit adds 'frigate' to the list of Electrum server software names that Sparrow Wallet recognizes. It is a straightforward compatibility update: when Sparrow connects to a server identifying itself as 'frigate', it will now treat it like other supported servers and enable the same features. There is no security fix or vulnerability here.

AI review queueddelete home folder on exit if emptyby Craig Raw · 0894407b · Nov 7, 2025 · 1 fileMessage 45 · ThinInformational 18Details
Commit message · Craig Raw

delete home folder on exit if empty

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

This commit adds a cleanup instruction so that Sparrow's home folder is automatically deleted when the application exits, but only if the folder is empty. It is a minor housekeeping change and does not appear to be a security fix.

AI review queuedbump to v2.3.2by Craig Raw · c76acb8d · Nov 6, 2025 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · Craig Raw

bump to v2.3.2

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.3.1 to 2.3.2. It only changes version strings in four files and contains no functional code changes, bug fixes, or security-related modifications.