* Package name : sparrow
Version : 1.7.1
Upstream Author : Craig Raw <ma...@sparrowwallet.com>
* URL : http://sparrowwallet.com/
* License : Apache 2
Programming Lang: Java
Description : Bitcoin wallet with a focus on security, privacy and usability
Sparrow Wallet is a Bitcoin only desktop wallet with a focus on security, privacy and usability. Suitable for beginner to advanced users, Sparrow reveals detailed information about a wallet’s configuration, transactions and UTXOs in order to minimise trust and be fully transparent.
Features:
* Full support for single sig and multisig wallets on all addressable script types
* A range of connection options: Public servers, Bitcoin Core and private Electrum servers
* Standards based including full support for PSBT and TXN files
* Support for all common hardware wallets in USB and airgapped / QR modes
* Wallet configuration via output descriptors
* Full coin and fee control with mempool visualisation
* Send to multiple outputs with change address selection
* Native support for fee bumping with RBF and CPFP
* Labelling of all transactions, addresses, inputs and outputs
* Lightweight and multi platform (Linux, OSX, Windows)
* Message signing and verification
* Collaborative coinjoin with Samourai Whirlpool and over Soroban
* Import and export to a number of different of wallet formats (incl. Electrum)
* Show wallets in different tabs, windows or minimised to system tray
* Payjoin (P2EP) support
* Anonymous broadcast via public blockchain explorers over Tor
* Built in Tor client
* Private blockchain explorer functionality
* Strong wallet file encryption
* Testnet, regtest and signet support
Inclusion into the Debian repository is a precursor to inclusion into Tails, which has been broadly requested in the Bitcoin community.
Sparrow is already released as a .deb package (see https://sparrowwallet.com/downloads/) as part of the standard release process.
I intend to maintain this package going forward.
In the past we've had a bit of trouble with bitcoin wallets in Debianwhen security issues emerged. If this package makes it into Debianstable, will you be able to provide security support for the version instable without upgrading to new upstream versions for the releaselifetime of stable?