Other changes include adjusting the fee rate slider to match the minimum configured relay rate of the connected server, improvements for full screen usage, and better historical exchange rate support. See release notes for more: t.co/JbxxVV57Xg

This release also supports BIP353, also known as DNS payment instructions. You can now pay to an address that looks similar to ₿[email protected], which resolves to a DNSSEC-signed bitcoin: URI. For privacy reasons it's best to use only a silent payments address (and BOLT12 invoice) in the URI.

This release restricts sending to silent payments addresses from software (hot) wallets only. DLEQ validation of silent payments outputs will be added in a later release for hardware wallet support.

This means you can pay to the same silent payments address while ensuring bitcoin addresses are never reused. This both simplifies the payment experience and makes it more private, at the cost of increasing the burden on the recipient to scan incoming transactions for payments.

This release adds support for sending to silent payment addresses. Silent payment addresses are a new form of static payment address, where the actual bitcoin address that you send to is determined from both the silent payment address and the transaction inputs.

Sparrow's internal Tor has been upgraded, and pay to anchor (P2A) outputs are now better supported. On Linux, the sparrow package has been renamed to sparrowwallet (or sparrowserver), and in some cases the original sparrow package may need to be manually uninstalled. t.co/qowJki96Nb

Sparrow's internal Tor has been upgraded, and pay to anchor (P2A) outputs are now better supported. On Linux, the sparrow package has been renamed to sparrowwallet (or sparrowserver), and in some cases the original sparrow package may need to be manually uninstalled.

This release adds the Recent Blocks view on the Send tab, inspired by @mempool's block visualization. Including the last 2 blocks and estimated next block, it provides additional information helpful when choosing a fee rate.

2. Broadcasts can be future-dated, meaning the transactions will only be submitted to the mempool after a delay. This is particularly useful for privacy, for example in migrating UTXOs separately from one wallet to another without broadcasting all the transactions at once.

1. Wallets can retrieve previously broadcasted transactions regardless of mempool fee conditions, while still respecting RBF rules. Without this, rising fee rates can cause a broadcasted transaction to be evicted from the mempool, making it harder to find and fee bump.

Other changes include loading of PSBTv2 files, toggling of whether the scanned camera image is mirrored, an option in the Server Settings to configure a server from QR, and many other fixes and improvements. See the release notes for more: t.co/WEsVhCwh4G

Previously labelled addresses are now skipped when retrieving an unused address from the Receive tab, and the Send tab's Pay To wallet selection. Additionally, a new address is always retrieved when sending multiple payments to the same open wallet on the Send tab.

Any adjustments to table column widths and sort preferences are now stored in the wallet file and restored when the wallet is opened. This applies to the transactions, addresses, UTXOs, wallet search and wallet summary tables.

This release replaces HWI with Lark to handle USB hardware wallet communication. As a result, multisig wallets on Ledger devices no longer require re-registration, and BitBox02 pairing is handled natively in the app. Additionally, the Jade Plus is now supported over USB. x.com/craigraw/statu…

That false.

False

That false.

Bitcoin is Protection.