This release introduces support for Liana Connect as an optional backend for the Liana GUI and Electrum server as an optional node interface for the Liana daemon.
Running Liana v7 on an existing installation will migrate its database. Once migrated the database won't be compatible with previous versions of Liana. This means you won't be able to open with Liana v6 (or below) any wallet opened or created with Liana v7.
- Transactions are now created with fee sniping protection.
- You can now remotely connect to your node using Electrum, as an alternative to running Bitcoin Core locally.
- The user does not have to select a network at start up anymore, the launcher looks for an installed
network in the following order:
mainnet,testnet,signet,regtest. - The launcher reads the
settings.jsonfile and provides information about the installed wallet or provides the user with a choice to create or add a wallet. - When creating or adding a wallet for the selected network, user has the choice to use his local node or an Electrum server or the Liana Connect service as a backend for the Liana GUI.
- User can share his hardware wallets xpubs by clicking on "Share xpubs" from the launcher.
- Wallet policy description was added to the installer and in the wallet settings.
- If using the Wizardsardine servers as remote backend, a user can provide access to a wallet to an other user by sending him an invitation with the invitee email in the wallet settings.
- Coldcard and Specter DIY can now be used with taproot descriptors.
- We now display the software version in the title bar.
- A
--helpflag was added to display a help menu about the available flags. - The Bitcoin Core node version to install for managed local nodes was upgraded to 27.1.
- We now check the change multipath is not hardened when importing a descriptor (or creating a
LianaDescriptorstruct). - We add the minimum feerate requested in the error message of the create spend command.
- The rendering of amounts superior to thousands now includes space.
- We detect if the descriptor changed before displaying registration status in the installer.
- We fixed some display issues with overlapping text, notably in the transaction panel.
- On reload, new labels are correctly loaded in existing transaction list in the home panel.
- In order to handle flaky connection, the whole hardware wallet list is reset at each step of the install process.
This release introduces support for the Jade signing device, a number of usability improvements as well as some bug fixes.
- The
hardware_walletsfield in the configuration file is now disregarded. It was deprecated since version 0.2.
- We now more accurately estimate the size of a signed spend transaction, preventing overpaying fees in some configurations.
lianadnow accepts two new arguments:--versionand--help.
- We now support the Jade signing device.
- We now use a more recent graphic renderer (
wgpu), which offers better compatibility with newer systems. - The network is now set first in the installer.
- It's now possible to get back from the descriptor creation step to the installer landing page.
- Advanced text shaping was enabled. Basically: you can now use emojis in labels and aliases.
- Date and time are now displayed according to the system's timezone configuration.
- We now also show the BIP388 wallet policy when registering a descriptor on a signing device.
- The descriptor backup step was removed in installer when a descriptor was just imported in the previous step.
- We now set a minimum window size.
- When creating a new wallet, we now better communicate if a wallet already exists in the selected network.
- When configuring the connection to bitcoind manually, we now display a warning if specifying a non-loopback IP address.
- Clicking on "Wallet" breadcrumb in Settings used to open "About" page.
- When entering the feerate for an RBF, it was made easier to edit a single-digit value.
- When updating an existing transaction draft, entering an invalid PSBT could crash the application.
This release introduces support for the Coldcard signing device, experimental Taproot support and a number of user experience improvements.
- Experimental support for Taproot was added.
- It's now possible to configure the connection to
bitcoindusing a user and a password in place of the cookie file. See the discussion at #356. - The
getinforesult now contains the "descriptor's timestamp": that is the oldest date at which we scanned the blockchain for coins. - The
createspendcommand now doesn't error anymore on insufficient funds, it instead returns the missing amount in its result. - The
listspendtxscommand now accepts a new optional parameter to filter the result by txids.
- Support for Coldcard was added. At the time of writing Miniscript support on the Coldcard is only available on the Edge firmware.
- You can now choose to create a Taproot descriptor in the installer. See doc/signing_devices.md for details about the compatibility with hardware wallets.
- When creating a Spend transaction using automated coin selection (the default), setting the amount for any recipient to "Max" to sweep all the funds from the wallet to this recipient, minus the amount set for any other recipients.
- When creating a Spend transaction using manual coin selection, setting the amount of any of the recipient to "Max" will sweep all the selected coins (not all funds in the wallet) to this recipient, minus the amount set for other recipients.
- The automated coin selection when creating a spend transaction now also considers unconfirmed coins.
- When creating a Spend transaction, you can now change screen and come back to your draft. The state does not get cleared as soon as you leave the "Spend" menu anymore.
- We now display warnings to the user when creating a Spend transaction. For instance when the change output's value was too small that we added it to fees.
- RBF transaction now get automatically labeled.
- Signing a transaction on a hardware device does not hide the transaction details anymore.
- When broadcasting a transaction, the payments are now immediately available on the home page.
- The QR code for deposit address is now shown in a pop-up, which makes it available for all new addresses a user may generate on the Deposit screen.
- The address QR codes now also contain the derivation index in the URI.
- We now display a warning if a user tries to RBF a transaction whose change output is being spent by a later transaction. A warning is also displayed when broadcasting a spend if any of the inputs are currently being spent by another transaction.
- We now directly open the installer when starting Liana on a new datadir.
- The "Backup Descriptor" step was dropped from the installer flow when recovering from a descriptor.
- A new command line argument was added:
--version. - It's now possible to use
<Tab>to move between text inputs across the GUI.
- We now disallow rescanning from timestamps before the genesis block on test networks too.
- A potential crash was fixed when an immature coinbase transaction contains an output which pays to our change address.
- An off-by-one in address usage detection was fixed.
- We now use a user/password to connect to
bitcoindin the installer, removing the potential for flakiness due to having to detect the.cookiefile. - A crash was fixed in the installer when the user would change the network in step 1 after having started the managed bitcoind in step 4.
- Errors when triggering a rescan are now correctly displayed.
- In the installer, the details to connect to bitcoind in step 4 are now correctly updated when changing the network in step 1.
- In the list of PSBTs, the labels are now correctly aligned.
This release introduces support for bumping the fees of a transaction, verifying a deposit address on your signing device, and more.
- The
outpointsparameter of thecreatespendcommand is now optional. If not provided, we'll select coins automatically. - A new
listaddressescommand was introduced. - A new
rbfpsbtcommand was introduced. - The
createspendcommand has a new, optional,change_addressparameter. This makes it possible to create a transaction which sweeps all funds from the wallet.
- When creating a Spend transaction, coins to be spent are now pre-selected. The selection is updated as you update the recipients and/or the feerate. The selection will stop being modified if you change it manually.
- It is now possible to verify deposit addresses on your signing device.
- You can now bump the fees of an unconfirmed transaction. A "bump fee" button was introduced in the transaction details (available from the list of transactions).
- You can now "cancel" an unconfirmed transaction. A "cancel" button was introduced in the transaction details (available from the list of transactions). NOTE: the cancel feature is not guaranteed to work. It's simply leveraging RBF to double spend the outgoing transaction with a transaction paying back to ourselves.
- You can now delete a wallet for a specific network from the launcher.
- When selecting a signing device, those which are not related to the wallet or which don't support a specific method (such as displaying an address) are now greyed-out.
- The managed Bitcoin Core version was bumped to 26.0.
- In case a transaction spending one of our coins was RBF'd, we could incorrectly assign an incorrect spending transaction to this coin.
- Setting a feerate larger than
2^64when creating a Spend would previously crash the software. - When displaying a PSBT the software could crash if some of the inputs of the transaction disappeared (were double-spent).
This release introduces support for the BitBox02 signing device, as well as the possibility to label payments, batches of payments, coins and addresses.
- Descriptors with duplicate signers within a single spending path are not supported anymore. Note re-using a signer across spending paths (for instance for a decaying multisig) is still supported, this only concerns pathological descriptor where the same signer would be repeated in the same path.
- Two new optional parameters were introduced to the
listcoinscommand to be able to filter coins by status (confirmed, spent, etc..) and outpoints (to query specific coins). - We updated the "quick try" guide
to make use of the managed
bitcoind. Trying out Liana on Signet is now easier than ever!
- You can now use the BitBox02 signing device. The minimum supported version of the firmware is v9.15.0, so make sure to upgrade!
- It's now possible to label coins and payments (that is, a transactions output). It's also possible to label batches of payments (that is, a transaction itself) and addresses.
- The number of steps in the installer was reduced by dropping the final confirmation screen. The wallet will now start automatically after configuration, reducing the information load and number of clicks for the user.
- All text inputs are now sanitized to remove whitespaces. No need to manually remove a trailing whitespace when importing a PSBT for instance!
- Various loading screens at startup were updated to include more information.
- The transaction fee rate is now displayed in addition to the absolute fee in the details.
- The managed bitcoind version was bumped to 25.1 for new installations.
- We fixed the minimum glibc version in the dependencies of the Debian package.
- We could previously crash if we were started up against a bitcoind itself recovering from a previous crash and in the process of re-connecting the entire chain.
- A few incorrect commands were corrected in the wallet recovery documentation.
- Selecting a coinbase transaction won't make the GUI crash anymore.
- At startup there could previously be a small lag before the home page gets updated with the list of payments and correct balance.
- During installation, when using a managed bitcoind, the GUI could previously freeze after starting up bitcoind.
This release significantly simplifies the installation of Liana. It also fixes a number of small bugs and glitches.
- Descriptors created with Liana v2 may not be backward compatible with Liana v1.
- We made it possible to re-use an xpub within a descriptor, so long as it uses a different derivation path.
- We added new RPC commands allowing for updating and querying labels of txids, addresses and outpoints.
- We've made our RPC connection to
bitcoindmore robust. - We now distribute packages for Debian-based and Arch-based Linux distributions.
- A guide on how to recover a Liana wallet backup with Bitcoin Core was added.
- An example config file for running
lianadwas added. - We've worked around the use of prefixed-paths on Windows thereby allowing us to bring back the watchonly wallet at the same location as for other operating systems, under our own datadir.
- The UX for creating a descriptor where a signer is present in different spending paths was significantly improved.
- The installation process, as well as the usage of the wallet, was made more user friendly by
optionally encapsulating the management (download, start and stop) of the
bitcoind.
- We more gracefully stop the Bitcoin backend poller when the block chain is still in the process of being synchronized. This would previously appear to hang and could freeze the GUI.
- The handling of conflicting unconfirmed spend transactions (RBFs) was fixed.
- If paid directly through a coinbase transaction output, the wallet could have previously missed it. This was fixed.
- We now correctly treat immature coinbase deposits as unspendable. They are otherwise treated similarly to unconfirmed coins.
- We now tell
bitcoindto load our watchonly wallet upon startup. Not loading the watchonly wallet on startup could makebitcoindunable to load it without reindexing the block chain, if using an aggressive pruning configuration. lianadwill now print a more helpful message on startup failure (and link to the newly added config file example).
- We now check the network of xpubs when importing a descriptor.
- The GUI would sometimes fail to connect to the Specter DIY signing device.
- We now convey the descriptor registration step on a signing device isn't necessary if none were used.
- We could previously appear to hang during shutdown.
This is the first non-beta release of Liana.
Improvements were concentrated on the GUI. The UI was entirely overhauled.
- The
createspendcommand now allows you to not provide any destination. In this case it will create a send-to-self transaction containing a single change output.
- Overall there is a new layout and color scheme. The "draft transactions" menu was renamed to the more common "PSBTs".
- The homepage now features a list of payments, instead of transactions.
- The spend transaction creation process is now contained in a single screen. It allows you to easily create a send-to-self transaction by not specifying any recipient.
- The homepage will now feature an approximation of the remaining time before the first recovery path becomes available.
- The homepage now features a button to refresh all coins whose recovery path is available (or close to be), if there is any.
- Entries in the coins list now features a button to refresh a coin (create a send-to-self transaction in order to restart the timelock).
- You can now generate multiple receive addresses in a row.
- We now display the alias of signing devices (if any) in the final installer step.
- Send-to-self transactions are now displayed as such instead of being affected a "0.00000BTC" value.
- The installer will not present a step to register the descriptor on the signing device if there isn't any.
- Some wording improvements all around.
- The slider to configure timelocks in the installer now has a step of 144 (instead of 1).
This fourth release brings support for descriptors with multiple recovery path as well as several usability improvements in the GUI around signing devices management, and more.
- We now support having multiple recovery path in a descriptor.
- We now support more general descriptors: multisigs in the primary or any of the recovery paths
henceforth aren't required to use
multi()anymore and the maximum number of keys per spending path is thereby lifted.
- You can now re-register the descriptor on a hardware signing device in the settings.
- You can now change the alias of each of the signers from the settings panel.
- At signing time we now warn you if the descriptor is not registered on the signing device.
- The signer alias is now displayed along with its type when signing.
- You can now connect to a running daemon without having to provide a path to its configuration,
provided it is using the default location for its data directory (or
--datadiris used). - The GUI will now log to a
installer.logfile at the root of the datadir during installation, and to a<network>/liana-gui.logwhen running. In case of crash, this will contain a backtrace. - During installation we now check the connection to bitcoind.
- We won't error when parsing of descriptor with a 1-of-N multisig as primary path.
- We won't error at startup if our watchonly wallet is loading on bitcoind. Instead, we'll wait for completion of the previous loading attempt.
- Blank addresses aren't treated as duplicates when creating a transaction.
A patch release for a serious bug fix in the GUI installer.
- Under very specific conditions the GUI installer would not store the mnemonic words corresponding to a hot key that was used in the descriptor, nor present it to the user for backup.
A small release which brings some fixes as well as the possibility to use Liana as a "hot wallet".
- Hot keys: users can now generate and sign with keys that are stored on the device. It is recommended to be only used for testing for now.
- It is now possible to use multiple signing device of the same type without having to first connect one then the other.
- When used as a daemon the
lianadprocess had its PID and logs file mixed up. This is now fixed. - We fixed the transaction creation sanity check that was overestimating the transaction fee.
- In the installer flow, extended keys are now shared without the
/<0;1>/*suffix.
The second release of Liana brings various fixes as well as the possibility to use a multisig in either, or both, of the spending paths.
- Multisig: we now support descriptors with multiple keys both in the primary (non-timelocked) spending path and the recovery (timelocked) path.
- You can now import and update Spend transaction drafts as PSBTs to collaboratively create and sign transactions.
- When creating a new descriptor you can now set an alias for each key. Those will be displayed when inspecting a transaction's signatories.
- Amounts are now displayed with the sats in bold for better redability.
- We now remove the fixed interpreter and rpath set by GUIX reproducible builds in the
liana-cliELF binary. - We now check the
bitcoindversion before trying to import a Miniscript descriptor. - We now discard unconfirmed incoming payments that were dropped from our mempool.
- Breaking change: the first version of Liana mistakenly accepted extended keys without origin
in descriptors. This meant that unless this extended key was the master extended key of a chain,
it would not be possible to sign with it (since signing devices need to know the origin). Starting
from version 2 Liana forces extended keys to contain an origin (of the form
[a1b2c3d4]) to avoid this footgun. This means that existing descriptors might have to be migrated, but it's very likely only for test configurations where an xpub wasn't gathered from a signing device (which prepends an origin) but generated (probably imported from Coleman's website) and pasted without origin.
- Various wording fixes on the UI.
- Amounts are now updated when moving between steps in the Spend creation flow.
- Coins are now sorted by age when displayed as a list.
- Some flakiness in the connection to a signing device were fixed.
- The descriptor registration on a signing device step in the installer was made clearer.