Sparrow Wallet

This commit fixes how Sparrow Wallet writes output descriptors when a wallet uses a non-standard key derivation path. Previously, the code stripped the leading 'm/' from the derivation path in a simplistic way, which could produce incorrect descriptors for unusual paths. The fix now uses a dedicated parser/formatter (KeyDerivation.parsePath/writePath) to handle the path correctly. This is primarily a correctness/reliability fix, but incorrect descriptors could in theory lead to users backing up or sharing wrong wallet configuration data.

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.

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.

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.

This commit adds a brand-new feature to Sparrow Wallet: support for Keycard hardware wallets via a smart card interface. It introduces many new Java files that handle low-level smart card communication, secure channel encryption, PIN handling, key derivation, and signing. The change is a large feature addition (+3,250 lines) rather than a small bug fix. There is no direct evidence in the commit message or diff that this fixes a known security vulnerability, and no external references were provided. Some implementation details—such as hardcoded pairing passwords, a TODO comment about device certificate verification, and a fallback to a default derivation path—could become security concerns if misused, but they are not proven vulnerabilities on their own.

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.

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.

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.

This commit changes Sparrow Wallet so that, when a user chooses a wallet to sign a Bitcoin transaction (PSBT), the app automatically fills in any missing key-path details needed for signing. The change is small and appears to be a usability/fix improvement rather than a clear security patch. There is no vendor statement or external reference saying this fixes a vulnerability, so we cannot confidently label it as a security fix.

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.

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.

This commit improves the user interface for pairing a Trezor hardware wallet with Sparrow Wallet. It adds a numeric-only input filter for the pairing code, makes the text larger, and shows the device name in pairing messages. There is no clear security vulnerability in the changes.

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.

This commit simply changes one of the macOS build machines used by the project's automated packaging workflow from an older GitHub-provided runner (macOS 13) to a newer Intel-based runner (macOS 15). It is a routine infrastructure update with no visible security relevance.

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.

This commit updates a dependency called 'drongo' to a newer version that exports a 'bip93' package. BIP-93 is a Bitcoin standard for encoding seed phrases in a language-independent way. The change itself is a one-line version bump in a dependency list, with no code changes visible and no security-related description in the commit message.

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.

This commit makes two small user-interface tweaks to the screen where a user imports a master private key: it changes a title to say 'Enter master private key', makes the Import button the default button that activates when the user presses Enter, and adds a period to a description sentence. There is no security-relevant code change.

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.

This commit claims to improve how Sparrow Wallet calculates Taproot tweaked keys, which are a cryptographic detail used in Bitcoin's newer Taproot address type. A flaw in this calculation could in theory cause incorrect addresses, make funds unspendable, or weaken privacy, but the actual code change is not visible in the supplied materials. Only the one-line summary and file name ('drongo') are provided.

This commit updates a sub-component named 'drongo' to include a 'bech32 refactor'. Bech32 is a Bitcoin address format. The actual code changes are not visible because the diff was not supplied, and no verified references were provided. There is no direct evidence this update fixes or introduces a security problem.

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.

This commit only changes the color fill of a small logo image used in the Sparrow Wallet user interface. It makes the block.xyz icon appear correctly on dark backgrounds. There is no security relevance.

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.

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.