Sparrow Wallet

This commit adds a safety check when extracting a BIP-322 signature from a signed PSBT file. Before, Sparrow would blindly copy the signature into the dialog even if the message inside the PSBT did not match the message the user originally asked to sign. Now it warns the user and asks whether to continue, and if the user declines (or the extraction returns null), it no longer overwrites the signature field. This reduces the risk of a malicious or mismatched PSBT tricking a user into accepting a signature for a different message than intended.

This is a small bug-fix patch that prevents a crash (NullPointerException) when displaying a tooltip on a wallet transaction entry. The tooltip shows estimated confirmation time based on current network fee conditions. If a transaction had no fee rate data, the old code would crash while trying to use that missing value. The fix checks for the missing value and safely returns nothing instead. There is no indication this can be exploited by an attacker to steal funds or compromise the wallet.

This commit is a routine version bump from 2.5.0 to 2.5.1. It only changes version strings in four files and contains no security-related code changes.

This commit changes the width of a dropdown menu in the wallet settings screen from 170 pixels to 180 pixels. It is purely a cosmetic user-interface tweak with no security relevance.

This commit makes two tiny user-interface changes: it shortens an error message so it doesn't show a full silent payment address, and it widens a dropdown box by 10 pixels. There is no security issue here.

This commit is a routine version bump from 2.4.3 to 2.5.0. It only changes three version number strings in build files and application metadata. There are no code logic changes, no bug fixes, and no security-related modifications visible in the diff.

This commit only changes user-facing help text in the wallet settings screen. It updates the descriptions for wallet policy types (single signature, multisignature, silent payments) and script types (Segwit, Taproot, Legacy). There are no code logic changes, no security fixes, and no behavior changes.

This commit fixes a problem where Sparrow Wallet did not properly 'finalize' transaction inputs that belong to another wallet when creating or handling cross-wallet PSBTs (Partially Signed Bitcoin Transactions). Without finalization, those inputs could end up with empty witness data, which may cause a signed transaction to be rejected by the Bitcoin network or to behave unexpectedly. In practical terms, this could affect multi-party or multi-wallet transactions where one wallet provides inputs it does not fully control.

This commit simply increases how long Sparrow Wallet waits after broadcasting a transaction before giving up on seeing it in the Bitcoin memory pool (mempool). The change is from 3 polling iterations to 12, with the stated goal of supporting Bitcoin Core's 'privatebroadcast' feature, which can delay when a transaction becomes visible. There is no indication this fixes a security vulnerability; it is a compatibility/timeout adjustment.

This commit simply updates a third-party barcode scanning library called jzbar from version 0.3.1 to 0.4.0. There is no information in the commit itself indicating what changed in the new library version or whether it fixes any security issue.

This commit adds a new default public Electrum server (frigate.2140.dev) to the Sparrow Bitcoin wallet and changes how the app picks a public server when a connection fails. The new server is advertised as supporting 'Silent Payments' (a newer Bitcoin address type), and the app now tries to choose only servers that can handle the types of wallets currently open. There is no direct evidence in the commit of a security vulnerability, but adding a new third-party server and changing server-selection logic can affect user privacy and reliability.

This commit adds the ability for Sparrow Wallet users with 'silent payments' wallets to sign messages using the BIP322 standard. It is a feature addition that extends existing message-signing support to a new wallet type. There is no indication in the commit that it fixes a security bug or vulnerability.

This commit adds a safety feature for a new Bitcoin privacy technology called 'silent payments.' It records the relationship between a regular-looking payment address and its silent-payment counterpart in the wallet's database. The main goal is to prevent users from accidentally breaking silent-payment outputs when they later modify (RBF) a transaction, such as by removing inputs. The commit also blocks one risky UI action with a warning dialog when such a change would be unsafe.

This commit fixes a concurrency bug in Sparrow Wallet's Electrum server connection code. Previously, a single read lock was held continuously while waiting for data from the server, which could starve or block other client requests. The change releases that lock during socket reads and restructures the read loop so responses are delivered only when the lock is held. This is a reliability/performance fix that reduces the chance of the wallet becoming unresponsive or misbehaving when talking to an Electrum server, but it is not a direct theft-of-funds vulnerability.

This commit tightens which Bitcoin signature hash (sighash) types users can pick when sending to a silent payment address. Previously the UI offered all normal signing options; now it forces the recommended/required sighash (ALL for non-taproot, DEFAULT for taproot) and labels it as required. The change is defensive: using the wrong sighash type with silent payments could break privacy or make the transaction invalid, so the wallet now prevents that choice.

This commit removes the 'Receive To' button and menu option for a specific type of wallet called a 'single sig single purpose' (SINGLE_SP) wallet. Previously, these receive actions were shown for all wallets except BIP47 (PayNym) wallets. The change appears to be a UI hardening measure to prevent users from accidentally or inappropriately reusing addresses in wallets that are intended to be used only once.

This commit is a user-interface polish change for the Sparrow Wallet desktop app. It hides the 'Rescan Wallet' hyperlink when the wallet has already been scanned as far back as possible, and shows a helpful label instead. There is no indication it fixes a security vulnerability.

This commit changes Sparrow Wallet so that newly created or renamed single-signature (SINGLE_SP) wallets get a default 'birth date' set to the current time. The birth date tells the wallet how far back in the blockchain it needs to scan for transactions. Without it, the wallet would perform a full rescan of the entire blockchain, which is slow and resource-intensive. The change is a performance/usability improvement, not a security fix.

This commit changes how Sparrow Wallet decides whether a message from an Electrum server is a subscription notification. Previously it used a simple text search (looking for the word 'method' and absence of the word 'error'), which could be fooled by JSON strings containing those words. Now it uses a proper JSON parser to check whether the message actually has a 'method' field at the top level. This is a hardening fix: the old approach could misclassify server responses, possibly causing user notifications to be missed or processed incorrectly. There is no direct evidence in the commit that this was exploited or treated as a security bug by the vendor.

This commit fixes a small logic bug in how Sparrow Wallet caches scans for silent payments (a privacy-preserving way to receive Bitcoin). During a specific multi-step process called 'widening rollback,' if the user or a server disconnect had already cancelled the scan, the code could accidentally un-cancel it and restore old cached data. The fix simply checks 'if already cancelled, stay cancelled' before restoring the snapshot. It is a correctness/reliability fix rather than a direct theft-of-funds vulnerability, but it could cause the wallet to miss or misreport silent-payment transactions after a cancellation.

This commit fixes a display timing issue in the Sparrow bitcoin wallet. When a user makes a payment to themselves (a 'self-spend'), the wallet could briefly show an incomplete transaction notification—showing the money leaving but not the matching change coming back. The patch pre-fills internal wallet records so the first notification is complete and accurate. It is a correctness/UX fix, not a vulnerability that lets an attacker steal funds.

This commit adjusts network waiting periods when Sparrow Wallet connects to a Bitcoin server through the Tor privacy network. It gives Tor connections slightly more time before retrying, likely to reduce false failures caused by Tor's slower routing. There is no indication this fixes an exploitable security flaw.

This commit removes one of several ways Sparrow Wallet can broadcast Bitcoin transactions to the network. The deleted code supported broadcasting through Bisq's market service (both a clearnet website and a Tor onion address). It is a simple feature removal with no obvious security bug being fixed in the code itself.

This commit changes how Sparrow Wallet's connection to Electrum servers handles replies. Previously, the app tried to match an entire sent request object to a received response object to decide if the reply belonged to the current request. The new code instead compares only the numeric 'id' fields found in the JSON, and keeps reading and discarding any responses whose ids don't match. It also adds optional wire-level logging. The change is a defensive fix against 'stale' or out-of-order server responses being mistaken for the answer to the current request.

This commit simply swaps the web and Tor addresses used by Sparrow Wallet to broadcast Bitcoin transactions through the Bisq mempool service. It changes one line in a list of broadcast sources, replacing 'mempool.bisq.services' with 'markets.bisq.network' and updating the corresponding onion address. There is no code logic change and no indication of a security vulnerability being fixed.