Sparrow Wallet

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.

This commit updates a dependency or submodule named 'drongo' specifically for BIP32 (a Bitcoin wallet key-derivation standard) tests. The change is a single-line version bump in a test-related component. There is no diff available and no security-relevant description in the commit message.

This commit changes how Sparrow Wallet matches incoming PSBTs (Partially Signed Bitcoin Transactions) against already-open transaction tabs, and adds verification of signatures before combining them. Previously, the app matched transactions by exact byte-for-byte equality and then merged PSBTs without checking that signatures in the incoming PSBT were valid. Now it matches by transaction ID and witness data, warns when two transactions share the same ID but have different witnesses, verifies signatures before merging, and warns users about silent-payments transactions whose recipient addresses cannot be verified. The change reduces the risk that a malicious or malformed PSBT could silently overwrite or merge with an existing transaction.

This commit adds error handling for a new type of PSBT (Partially Signed Bitcoin Transaction) validation failure related to silent payments. Previously, if silent payment proof validation failed during transaction extraction, broadcasting, saving, sweeping private keys, or payjoin, the application would likely crash or propagate an unhandled exception. Now it shows an error dialog instead. The commit also makes some related payjoin logic more robust, such as computing the additional fee contribution before serialization and fixing a change-output value comparison bug.

This commit changes Sparrow Wallet to use PSBT version 2 as its default internal format instead of converting PSBTv2 files down to PSBTv0. It also adjusts how transactions are compared (by transaction ID instead of object equality) and changes how a PayJoin PSBT is prepared before being exported. These are internal refactoring changes; there is no direct evidence in the commit that they fix a security vulnerability.

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.

This commit updates a dependency or submodule named 'drongo' to support additional hardware wallet models from Keycard. The change is a single-line version bump in a dependency reference. There is no diff available and no disclosed security context, so it is impossible to tell from the provided materials whether this fixes a security issue, adds a feature, or is routine maintenance.

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.

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.

This commit is a routine build/packaging maintenance change. It renames the macOS packaging directory from 'osx' to 'macos', adds a configurable app name to the GitHub codesigning workflow, and moves the same Info.plist, entitlements, icon, and installer background files to the new location. There is no indication of a security vulnerability being fixed or introduced.

This commit updates the project's automated build workflow to use a custom Sparrow Wallet action for signing and notarizing macOS releases. It is a routine CI/CD configuration change and does not contain any apparent security vulnerability.

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.

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.

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.

This commit adds a new user-facing privacy feature called 'Hide Amounts' to the Sparrow Wallet desktop app. When enabled through a menu toggle, all Bitcoin and fiat amount labels, chart axes, transaction diagrams, and transaction hex output values are visually masked with dots (•••••) instead of showing real numbers. It is purely a UI/presentation change and does not alter how balances, transactions, or wallet data are stored or handled.

This is a user-interface bug fix in a Bitcoin wallet app. It changes how a table cell decides to skip its own refresh, so that it only skips during JavaFX's internal table-size recalculation and not in other situations. The previous shortcut could occasionally leave a reused cell showing stale or wrong information. There is no indication this is a security vulnerability or that it could be exploited to steal funds or data.

This commit simply adds another color format (YU12) that Linux webcams can use when scanning QR codes in Sparrow Wallet. It is a one-line addition to a list of supported pixel formats. There is no indication of a security bug or fix.

This commit adds a small UI label that shows which signing keystores have already signed a multisig transaction when viewing it in the transaction details form. It is a user-interface improvement, not a security fix or vulnerability.

This commit simply bumps the version of a small third-party Java library called jzbar from 0.0.1 to 0.2.1 in the project's build file. There is no information in the commit itself about why the update was made, what changed in the library, or whether any security issue is involved. It looks like a routine dependency maintenance change.

This commit changes how Sparrow Wallet asks Ledger hardware wallets to show extended public keys (xpubs). It now requests that the Ledger device display the derivation path on its screen whenever the path is non-standard. This helps users verify they are exporting the correct xpub and not one from an unexpected path, reducing the risk of misleading wallet backups or address generation. The change is a hardening improvement rather than a fix for an active exploit.

This commit simply bumps the version of a camera-capture library used by the wallet from 0.0.28-9 to 0.0.30-1. The change is a one-line dependency update with no description of why the update was needed or whether it fixes any security issue. On its own, this looks like a routine maintenance update rather than a confirmed security fix.

This commit is a straightforward internal code cleanup. It bundles many individual transaction settings into a single 'TransactionParameters' object and passes that object around instead of a long list of separate values. There is no change to what the software actually does, and nothing in the commit suggests a security fix.

This commit fixes a Windows build script bug. Previously, the build process granted file permissions to a group literally named 'Users', which fails on non-English Windows versions where that group has a translated name. The change uses the universal numeric identifier (SID) for the Users group instead, so the build works on all language versions of Windows. It is a reliability/localization fix, not a security vulnerability fix.

This commit refactors how Sparrow Wallet labels and handles payments that send bitcoin back to the user's own wallet (called 'consolidation' payments). It replaces an older imperative check with a new explicit 'WalletNodePayment' type. There is no direct evidence this fixes a security vulnerability; it appears to be a code-quality and UI-labeling improvement.

This commit is a minor user-interface tweak. It stops showing the number of blockchain confirmations inside a tooltip when the user is viewing the detailed inputs and outputs of a transaction. There is no security issue here.