Liana - advanced multisig wallet coordinator.

[satscraper]

Although we already have several individual posts highlighting the unique features of this software ^{focused particularly on coordination in various multisig schemes, including advanced setups like inheritance planning and decaying multisig wallets} the forum still lacks the dedicated thread for Liana. Such thread could serve as a central hub for discussion, support, and updates.

The recent release of v11.0 ^{which dropped just two days ago} gave me the perfect opportunity to fix that.

Since its initial launch in 2023, Liana has seen over 35 releases ^{in my view an impressive pace that speaks volumes about the commitment of its developers}. Developers are clearly working hard to build the solid, open-source wallet solution focused squarely on Bitcoin and advanced key management schemes.^{A true McCoy in its domain}.

Among bunch of new features brought by the latest release I would highlight the following:

Hope we will use this thread to share insights/experiences/questions/relevant news around Liana’s development and use.

[satscraper]

The latest Liana release  version 12.0.0 has introduced a striking new feature to the wallet GUI.

Since version 10.0.0 it has been possible to work with multiple wallets in the same client's window. Now, with the new update, you can split the interface into separate panes for each wallet.

In the example below I launched three separate Liana instances, each aimed at creating the wallet with the different policy. I then arranged for each wallet to be displayed in its own pane. The key detail to achieve this is to right-click on the relevant launcher tab to access the "Close Split" menu.

Other added features and improvements:

[satscraper]

In its latest v.13.0 release Liana wallet has been enhanced with the standout feature, namely, support for encrypted descriptor backups and the corresponding import functionality. This is the great addition for securely storing backups without worrying that sensitive data, such as addresses, quorum, and other details relevant to multisig scheme, might be exposed to unauthorized eyes if the backup is ever intercepted. AFAIK, no other wallet currently implements the similar feature.

[satscraper]

Two days ago ^{after more than half a year of inactivity} Liana wallet was updated to v14.0. This release mainly focuses on making Liana easier to use by introducing the clearer UI and improving compatibility with hardware wallets. Version 14.0 also includes many fixes. Below is  summariziation of update which ^obviously it’s much easier to read than to enumerate every improvement and bug fix.

[NotATether]

I see Linux running Liana in your screenshot (GNOME?) but does it run on Mac and Windows?

This looks like an application that can be used by companies who need to securely store large amounts of BTC, or by somebody who just wants to make a bunch of independent signing keys and distribute them geographically.

[satscraper]

I see Linux running Liana in your screenshot (GNOME?) but does it run on Mac and Windows?

Yeah, those screenshots are from GNOME (Ubuntu), but my 13 years old laptop now runs Xubuntu (Xfce), which is much faster. In terms of speed, it’s comparable to my Acer Swift Go (2025) running Windows 11.

This looks like an application that can be used by companies who need to securely store large amounts of BTC, or by somebody who just wants to make a bunch of independent signing keys and distribute them geographically.

I doubt that companies like that keep their funds in Liana. AFAIK, they prefer using MPC wallets ^{such as Fireblocks}.

[satscraper]

Liana was elevated to v.15.0.

This is mostly a big visual revision of the wallet's gui and installer which means reworked home, receive, and spend screens, redesigned sidebar/tab menu, new signing-device popups, cleaner buttons/cards, and  friendlier receiving address format. Under the hood it bumps the iced UI framework to 0.14 and Rust to 1.88. On the fix side: signing-device detection issues the more consistent launcher list, a clearer spend warning when label's missing, and a reproducible Windows build fix.