By far the most relevant issue affecting Bitcoin today👇.

RT @coinjoined: 1/🧡 The board of the @_einundzwanzig_ Bitcoin Association proudly supports @SparrowWallet with a 2.1 million sat donation!….

RT @BitcoinReviewHQ: Consolidating UTXOs into a single tx during wallet migration? 🚫. Staggered broadcasts and privacy-preserving wallet mi….

Lark is available as a command line application, and as a Java library for JVM-based applications. Hardware wallet manufacturers are invited to test their devices before it's integrated into @SparrowWallet. See for docs and binaries.

All common commands are already supported, and there is some additional functionality, such as retrieving a wallet registration from Ledger devices to avoid re-registration on every signing.

Even though HWW manufacturers have used a dizzying array of different communication protocols and standards, Lark seeks to be identical to the HWI API, providing direct interchangeability and a more robust ecosystem.

However, with all the wealth stored on hardware wallets (especially those that can only communicate over USB) it's important to have multiple implementations. Lark represents the first complete reimplementation of all common USB HWW clients in a language other than Python.

HWI is a good example of the situation described in this famous @xkcd comic. Until now, there has been no project like it. My personal thanks to @achow101 for building and maintaining it, in addition to all your other responsibilities. Thank you Ava.

Introducing Lark. Lark is a Java port of HWI, a library used by many wallets to communicate over USB with with hardware wallets like @Coldcardwallet, @Ledger, @Trezor, @BitBoxSwiss and @BlockstreamJade.

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.

Broadcast pool is a proposed feature for Bitcoin Core which would allow a node to keep a separate record of transactions sent directly to it from a wallet for broadcasting. This provides two key benefits 🧵.

RT @nvk: We need this Bitcoin Core feature My motivation is helping people migrate wallets without consolidating U….

RT @fjahr: The CISA panel from Bitcoin 2024 in Nashville is now online: Featuring @lopp @craigraw @niftynei and mys….

RT @thebtcmag: Privacy and Pain: @craigraw, Creator of @SparrowWallet, on Self-Custody 👁️🩸 . The greatest Bitcoin teacher is not a person o….

RT @ck_SNARKs: Craig Raw | How You Can (Still) Transact Privately with Bitcoin.🔒@craigraw of @SparrowWallet explains Bitcoin’s UTXO model a….

RT @gladstein: HRF is excited to announce the CISA Research Fellowship 🎉. Cross-Input Signature Aggregation (CISA) is a proposed upgrade to….

Whatever the proposal, I will continue to evaluate it on the key principles of self sovereignty. Without them, I believe we will simply end up in another fractional reserve, fiat world.

As an application developer I am time constrained to reviewing and building on top of these proposals, not actively developing them. I tend to favour things that I know people will have an immediate use for - for example, OP_VAULT, which uses CTV.

The main pushback to half-aggregrate CISA seems to be that it doesn't do enough, but I think that ignores the incentives.