Liana 16 Gives Bitcoin Wallets Taproot, Safer Backups and a Security Fix

Original cinematic-anime artwork of a male Bitcoin wallet developer studying secure recovery paths and linked wallets on dual monitors, with the saved neon-green BitcoinVersus.tech logo at the bottom left.

Bitcoin wallet developer Wizardsardine has released Liana 16.0, combining Taproot-by-default wallet creation, standardized encrypted recovery-policy backups and a security fix for users connected to malicious Electrum servers. The release was dated November 3, 2026, and Bitcoin Optech’s November 20 newsletter highlighted the changes. Liana is built for self-custody with multiple spending paths, including recovery keys that become usable after a selected period of inactivity. The update changes wallet software, not Bitcoin’s consensus rules.

A normal Bitcoin seed phrase reproduces private keys. Liana additionally relies on a wallet descriptor, which specifies how keys, scripts and timelocks combine into a spending policy. Losing the descriptor can therefore make recovery difficult or impossible even when a seed survives. For households planning long-term custody, preserving the spending instructions matters as much as preserving the keys.

Official Wizardsardine video: a tutorial showing how to set up and use Liana. Recorded in 2024, it explains the wallet model rather than demonstrating version 16 features. Watch directly on YouTube.

Why Taproot changes the default

New Liana wallets now select Taproot unless the user chooses SegWit instead. Taproot lets the wallet encode alternative spending conditions efficiently and generally reveal only the executed spending path on-chain. That can conceal unused recovery paths and reduce transaction weight. It does not make blockchain activity invisible, eliminate address reuse or guarantee anonymity. Signing-device compatibility still matters, and the installer warns when the hardware cannot handle the selected address type.

The design has a connection to our earlier coverage of silent-payment building blocks and OpenSwap privacy tools. Each relies on a different mechanism; changing address type alone does not provide a private coin swap or a reusable silent-payment address.

Encrypted backups gain a standard format

Liana now writes encrypted descriptors as .bip138 files rather than its earlier .bed format. The BIP138 format makes the backup structure more interoperable and adds an option to omit key-derivation paths from the encrypted file’s public metadata. Omitting those paths can reveal less information, though restoring the wallet may take longer because a signer must test candidate paths.

The wallet can continue reading older backups, but Liana 15 and earlier cannot open the new BIP138 files. The change also complements the separate COLDCARD Codex32 backup rollout, which uses a different mechanism for preserving signing secrets. Encrypted descriptors do not replace private-key or seed backups.

The malicious-server transaction trap

Wizardsardine also fixed a medium-severity weakness in the replace-by-fee workflow. A hostile Electrum server could falsely acknowledge a payment broadcast and then present a conflicting transaction that paid an attacker’s address. A user trying to bump or cancel the fee might see a prepared replacement transaction containing that destination. Theft still depended on the user signing the misleading transaction without checking its output address.

Version 16 validates that the transaction actually spends the wallet’s coins with proper signatures before constructing any replacement. When validation fails, the fee-bump and cancellation actions are disabled. The problem resembles the trust-boundary questions examined in our Electrum fee-bump security report, although the wallet and implementation details differ. The developer recommends connecting to a node under the user’s control and reviewing destinations on the signing device.

Independent tutorial: Liana’s Miniscript recovery paths and hardware-device workflow, published in 2023. The walkthrough is contextual education, not a tested demonstration of the November 2026 release. Watch directly on YouTube.

Upgrade carefully: database migration is irreversible

The release also adds French, Italian and Portuguese interfaces, improves inherited transaction labels and redesigns several wallet screens. More importantly, opening a wallet with Liana 16 migrates its local database: the migrated database cannot be opened with Liana 15 or earlier. Anyone running the same wallet on multiple computers should prepare backups, validate recovery documentation and coordinate the upgrades.

Liana remains a self-custody coordinator rather than a substitute for a safe signing device or sound recovery procedures. Anyone considering time-locked inheritance should test a configuration using small amounts before relying on it for family funds. Wizardsardine’s release explanation and the official version 16 release provide the full technical notes and installer files.

Leave a Reply