Merge #404: Release notes for 0.3.1 and 0.4

df5c4ee85d2f138f180842df6aa09d73c663d51d doc: remove mentions of experimental Ledger apps (Antoine Poinsot)
c3d7039d910f5ea24115cf57bab827436421abe3 CHANGELOG: 0.4 release notes (Antoine Poinsot)
b6f13932d19286716d76b4aa52726484183f19dc CHANGELOG: 0.3.1 release notes (Antoine Poinsot)

Pull request description:

ACKs for top commit:
  darosior:
    self-ACK df5c4ee85d2f138f180842df6aa09d73c663d51d

Tree-SHA512: 4d0a91ba7af42ed48e2217f10ef11299bb4cb49977c44d80ff0c838596e0c1b8150ff14ef062dd00cabeecba06108c0bb264446ed70ad221b8cf2bf5c6058528
This commit is contained in:
Antoine Poinsot 2023-04-10 11:18:16 +02:00
commit e8a0d39cd6
No known key found for this signature in database
GPG Key ID: E13FC145CD3F4304
3 changed files with 53 additions and 34 deletions

View File

@ -1,5 +1,50 @@
# Liana daemon and GUI release notes
## 0.4
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.
### Features
- 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.
#### GUI-specific
- 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 `--datadir` is used).
- The GUI will now log to a `installer.log` file at the root of the datadir during installation, and
to a `<network>/liana-gui.log` when running. In case of crash, this will contain a backtrace.
- During installation we now check the connection to bitcoind.
### Fixes
- 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.
#### GUI-specific
- Blank addresses aren't treated as duplicates when creating a transaction.
## 0.3.1
A patch release for a serious bug fix in the GUI installer.
### Fixes
#### GUI-specific
- 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.
## 0.3
A small release which brings some fixes as well as the possibility to use Liana as a "hot wallet".

View File

@ -111,12 +111,9 @@ Liana can be used as a hot wallet. Note that mnemonics would be stored in clear
strongly recommend using a hardware signing device for any non-trivial amount.
For now, only the Ledger and Specter DIY signing devices are supported, as Miniscript compatibility
of the signer is a must. We expect more signing devices to implement Miniscript capability. For more
information, please read the [signing devices documentation](./doc/signing_devices.md).
If you are using a Ledger device, the minimum supported version of the Bitcoin application is
`2.1.0`. You may have to tweak with the Ledger Live options in order to install it for now, see the
instructions [here](./doc/signing_devices.md).
of the signer is a must. More signing devices are expected to implement Miniscript capability in the
near future. For more information (such as minimum supported versions, please read the [signing
devices documentation](./doc/signing_devices.md).
If you are using the GUI, it should be intuitive what menu to use depending on your intention. If it
is not, bug reports are very welcome so [feel free to report it](https://github.com/wizardsardine/liana/issues)! :)

View File

@ -1,9 +1,9 @@
# Signing devices
Documentation related to signing devices. For now only Specter and Ledger (at the latest version of
the application) are supported since we need them to support Miniscript descriptors.
Documentation related to signing devices. For now only Specter and Ledger are supported since we
need signers to support Miniscript descriptors.
The connection the signing devices is implemented in [another
The connection to the signing devices is implemented in [another
repository](https://github.com/wizardsardine/async-hwi).
@ -13,28 +13,5 @@ repository](https://github.com/wizardsardine/async-hwi).
## Ledger
Only the latest version of the Bitcoin application (with full Miniscript descriptors support) is
supported. This is version 2.1.0.
Unfortunately the 2.1.0 Bitcoin application comes with a breaking change of the interface. Its
[rollout was paused](https://twitter.com/salvatoshi/status/1610663029913313280) due to compatibility
issues with existing applications. Since then the application is not available through the regular
app store channel anymore.
Its rollout was later [resumed **on testnet only**](https://twitter.com/salvatoshi/status/1612432385013956617).
In order to be able to install the latest Bitcoin testnet application from Ledger Live, first go to
settings (top-right corner on the home screen), then "Experimental features" and tick "Developer
mode". You will then be available to install the "Bitcoin test" application from the "My ledger"
panel.
In order to be able to install the latest Bitcoin application on mainnet, one more step is required.
Go to "settings" (top-right corner), then "Experimental features", enable "My Ledger provider" and
insert "4" in the field. You may then go to "My Ledger" and install the 2.1.0 Bitcoin application
for mainnet. *Do not* download any other app from the provider 4. **Make sure to disable** the "My
Ledger provider" setting once you installed the Bitcoin app.
It's worth noting that although you need to tweak with the "Experimental features" settings, the
Bitcoin application is not experimental anymore. It was just downgraded in Ledger live from released
to experimental in order to prevent people from upgrading by mistake and not be able to keep using
applications not compatible with the new interface. It is however not safe to use it for installing
any other application.
Minimum supported version of the Bitcoin application is 2.1.0 (the first version to have full
Miniscript descriptors support).