ce8e1f3c3eed5a6e991307f8740e54cb0680e5bc installer: let user choose account (derivation path) before fetching an xpub from signing device (pythcoiner)
8efc55bcf5a314997ac4b2a1de9a0a587fb7c9fe ui: add a widget to let user select custom derivation path of an xpub (pythcoiner)
Pull request description:
This PR closes#1700.
ACKs for top commit:
jp1ac4:
tACK ce8e1f3c3eed5a6e991307f8740e54cb0680e5bc.
edouardparis:
ACK ce8e1f3c3eed5a6e991307f8740e54cb0680e5bc
Tree-SHA512: a24ebe58da30b81767d67e4da587299a6942f1a62ec0ccd02fd52b06cbe33dca3e27c9e6ab713f141cad84208a200ebbb21f988180862c4909d6080262ef5fea
654be987f2da61ed47310c3d30720126b64aa292 fix settings: missing update_aliases for backup restore (edouardparis)
Pull request description:
While restoring a backup at the import/export panel, the message to update the wallet keys aliases was not handled and although the aliases are stored in the settings file, the wallet was not "reloaded" through the Message::WalletUpdated result. The consequence was while opening the wallet section, users found the aliases not updated by the backup (even if the file was updated).
The change in the update_aliases is to update the wallet alias only if the function require the change by passing
`Some(alias)` in arg.
ACKs for top commit:
jp1ac4:
utACK 654be987f2da61ed47310c3d30720126b64aa292.
Tree-SHA512: eabaeb48f6167365373a1839ca317879c1314d79c687d0648cae1d001ee125c364ad10a411c3392be4f001fbfb2cf85be63371e0cc36f8351066c832adfe9789
01ceb237f8446a31653bc294142a3a1397128373 fix: use scrollbar for node settings (Michael Mallan)
Pull request description:
This fixes an issue when viewing a long node setting value, such as the cookie path, on a reduced window size.

ACKs for top commit:
edouardparis:
utACK 01ceb237f8446a31653bc294142a3a1397128373
Tree-SHA512: f81b70df5c20d7339bdcd2e480dfbfb8e9381859ecc64338e32873dea11f8159b2d59c97d947bf2003aff38cebcabca50763f7d7a988a153b14c17d237f8e9a2
904fc728de20cdd283a4273093e6b59c5609630c fix import backup for existing wallet (edouardparis)
Pull request description:
We pass the wallet to the import_backup method
so the wallet id is used to find the correct wallet settings to update in the settings file.
ACKs for top commit:
jp1ac4:
utACK 904fc728de20cdd283a4273093e6b59c5609630c.
Tree-SHA512: 0a2a6c77d333460cc06ad141a7685d88911bc40bc3cd221111dd6611ca45e8c5552f46f7a694e44f0b47b4a5c1cd6946e25c755de83cbfe6259de93d6b9b65e0
7281e6352967009419a493ccd3825887001afa14 gui: store SignModal state and allow to open export modal after signing in PSBT panel (pythcoiner)
Pull request description:
This PR fixes#1681:
- `PsbtState::modal` was not properly reset after signing modal closed
- When `PsbtState::modal` is of type `SignModal` we store it's state, else we lost track of which key already signed.
- `SignModal::display_modal` is not useful anymore, as we store the modal state, and only "hidding" the modal not let display another modal (export modal for instance)
ACKs for top commit:
jp1ac4:
tACK 7281e6352967009419a493ccd3825887001afa14.
Tree-SHA512: 6627c1f788048349fee2fd9f6fc1a9044da03c9b6ac61339b19c5ae503cb0d522501ce4438f70359906231c06928c8756b52715901898c56fa58dd7da5194cdc
a9917d17810b3d47c0bd5623ffa7636e2f299c72 Add wallet alias step to installer (edouardparis)
51d913b9efff2ec360190fc75e0013d691dd8d7e Set wallet alias in settings if liana-connect wallet alias changed (edouardparis)
36fb3d877552099ef7fbdce21753352a1c4219df Add wallet alias in window title (edouardparis)
381421038b0e12ed257679b31a16102021d6d76a Add wallet alias to settings (edouardparis)
Pull request description:
We had a new `wallet_alias` to settings file.
This field is displayed in the launcher when wallets are listed and in the window title when the app is running the wallet.
The field is also store in liana-connect wallet.metadata field to facilitate import of wallet from Liana-Connect.
If the field was modified on Liana-Connect, then next time the user open the wallet in the gui, the settings field is updated.
User can modify the wallet alias in the Settings > Wallet section.
ACKs for top commit:
edouardparis:
Self-ACK a9917d17810b3d47c0bd5623ffa7636e2f299c72
Tree-SHA512: 819fb84660894a8c546132a21966c8084b4820b4cb7f57c9de80648355ebf053581964dea8e8fe455523e0c7692244fc0803e8dec03d50946139ed88832622f7
74087c37cf0b0796e794f98bebb11167ca243969 refactor: map fingerprint only once (Thomas Ballivet)
86c4896534c1ac169a3352651b0e27170e8cb06f Disable signing devices that are not related to the actual spending path (Thomas Ballivet)
Pull request description:
Inspired by #1607 this shoud closes#1041.
Notice that I added the wanted logic also for the recovery spending. That means you can only select a signing device related to the primary path for usual spend. But for recovery spending you can only select a signing device related to the recovery_path.
You can see here both examples :


ACKs for top commit:
jp1ac4:
tACK 74087c37cf0b0796e794f98bebb11167ca243969.
Tree-SHA512: 93e452ca9f56e214f308cbaf3cdc9ffb52301e64fded860d1a961e97df21270e18f994cef83358459981ddc3029c89183d23bc33bab863253cfa2a2c5a9d9554
78a2defb6c08ef19cc249da7415fac873d32e20f docs: add a link to SIGNING_DEVICES.md in USAGE.md instead having a duplicate of supported devices (pythcoiner)
Pull request description:
replacing list of supported devices by a link to SIGNING_DEVICES.md to avoid maintenance burden
fixes#1690
ACKs for top commit:
nondiremanuel:
ACK [78a2def](78a2defb6c)
Tree-SHA512: 83cae2da1865a55415c064a12c1fcac956827fbc910f19ad544fac90540bf4965ee414975bfd0bae781bd82eec606aa37bf2b290717751a419bece8689a69bd1
63ef4838a705a6f9187cf607a4e320b71f374557 fix: use cookie file auth for new wallets with managed bitcoind (Michael Mallan)
Pull request description:
This fixes#1708.
There would be no way to get the RPC password of an existing managed bitcoind installation without looking in other daemon.toml files.
An existing rpcauth field in the bitcoin.conf file will remain unchanged so that an existing wallet using username/password authentication will continue to work.
ACKs for top commit:
edouardparis:
ACK 63ef4838a705a6f9187cf607a4e320b71f374557
Tree-SHA512: 69d6c0f5eed78227be0854306bdfe53abf2ea989083e4adfae5b17d952ee6570b8f98ede8bf43bcfbe2e3b529a19088a7500aa59ecca276323f0bf8cd0281f6e
Mnemonics are now stored with the following format:
mnemonic-fingerprint-checksum-timstamp.txt
checksum and timestamp are the new way to identify wallets.
When deleting wallet user expects any mnemonic related
to the wallet to be removed.
For legacy wallets, any mnemonic-fingerprint.txt file will be deleted.
And make launcher open default network directory
as the first directory with a settings file.
Fallback to the Create wallet view when no settings
file exist anymore or if the settings file has no wallet.
There would be no way to get the RPC password of an existing
managed bitcoind installation without looking in other
daemon.toml files.
An existing rpcauth field in the bitcoin.conf file will remain
unchanged so that an existing wallet using username/password
authentication will continue to work.
d2c6f9bb96fa01b8f590fb67f5fdb34eedeca45a fix: "Generate address" become secondary after generation (Thomas Ballivet)
15f4dc1ed145e49f52576c0aaabd0608847c698f fix: set "Go to replacement" as primary (Thomas Ballivet)
881621f03b901198f47f31e44b1599f3dc75df06 Improve visibility of primary button text (Thomas Ballivet)
Pull request description:
The first commit fixes#1697.
The second set "Go to replacement" as primary.
The third make "Generate address" become secondary after generation.
Tell me if I should squash.


I've tried to make the icon thicker but doesn't work the same way. Maybe using a different font or an image would help to fixes this.
ACKs for top commit:
pythcoiner:
tACK d2c6f9bb
Tree-SHA512: 5ca6201ac77106dbb866badaeda9a097823dda37630ee437fd816bb749802fcae8a225bad999bbde232f63976dc8a823a09a5a7e593fb889f226b05f4f28a41d
efd0c32e5df323a555850e364ef7c18ce6474cbb fix: hide prev addresses option if there are none (Michael Mallan)
c629142c58408909877d60b4ab38f76cb3ad5518 fix: ignore address with index 0 (Michael Mallan)
Pull request description:
This PR consists of two fixes following #1704:
1) don't show the address with index 0 in the list of unused addresses. This is because a new Liana wallet starts generating new addresses from index 1.
2) hide the option to view unused addresses if there aren't any (such as for a new wallet).
ACKs for top commit:
pythcoiner:
tACK efd0c32e
Tree-SHA512: d80ff4358387b8a06867845eea89aac6f9a6896292975b92901b17e324564b01ca6b2af00faadf932a37bf38d6459d18f2533659adb5c8e8582f71ea6e1d7869
f8e702b65ea894131b212fdfed89b16068699fe9 feat: list unused addresses already revealed (Michael Mallan)
d84c75c1ce548c2c7dfecf98960e9a19409cb9e7 refactor: extract address card logic to function (Michael Mallan)
daa3daa938567e6d76e7dce02bddd725b97a72d9 refactor: add message for next receive address (Michael Mallan)
8b8b48142f60ede2b8ce702c89a61f3fd32a1842 feat: add list addresses method to gui daemon interface (Michael Mallan)
Pull request description:
This implements #809 by listing unused addresses on the Receive panel.
ACKs for top commit:
edouardparis:
ACK f8e702b65ea894131b212fdfed89b16068699fe9
Tree-SHA512: 05538d099433bad33c947694e91bc082147159bebd4607ac2d37f9127013656c928a2a332f1212fc5f9d6a2d68e3047e7c3da5523233b92d47b2802811a706d8
3d6a22ea05df70d6f0c11f2f00c85dc16975ad28 feat: add rpc command to list revealed addresses (Michael Mallan)
4945dba7c066d1434fa38a09a955339b7182e693 feat: add command to list revealed addresses (Michael Mallan)
75f37708b3b1f6a89e0f5488c95618a07356f166 test: implement methods for getting/setting labels (Michael Mallan)
16b96b5456b46cd3703d4829b24746c8a489b3ed style: apply black formatting (Michael Mallan)
Pull request description:
This implements #1678.
The command parameters differ slightly from those described in the issue:
- instead of a `keychain` enum parameter, I used `is_change` to control whether receive or change addresses are returned.
- I used an optional `continue_from` parameter to control pagination. The value to pass in the next request is provided by the previous response. If no value is provided in the response, there are no more addresses to list. If no value is set in the request, the addresses will be returned starting from the last revealed address.
Setting the positional argument for `continue_after` as `null` will be treated the same as omitting it (for other RPC commands, a `null` value results in a parsing error).
ACKs for top commit:
pythcoiner:
utACK 3d6a22e
Tree-SHA512: 0efa93bc40d0751cbe64570f9789b3a701e0bc5aab982da9ed9f21117a2eea073a81388370d56a9021c0ff87b6cbaec7338339427e6c879e8e97eababb107f57