docs: update remote signing update hint to v0.15.3-beta [skip ci]

This commit bumps the recommended version to upgrade to for remote
signing setups.
This commit is contained in:
Oliver Gugger
2022-10-11 09:42:43 +02:00
parent 079537514c
commit 299152e631
3 changed files with 3 additions and 3 deletions

View File

@@ -38,7 +38,7 @@ detecting Taproot compatibility of a seed.
necessary when upgrading from `lnd v0.14.x-beta` to `lnd v0.15.x-beta`, see [the necessary when upgrading from `lnd v0.14.x-beta` to `lnd v0.15.x-beta`, see [the
remote signing documentation for more remote signing documentation for more
details](../remote-signing.md#migrating-a-remote-signing-setup-from-014x-to-015x). details](../remote-signing.md#migrating-a-remote-signing-setup-from-014x-to-015x).
Please upgrade to `lnd v0.15.2-beta` or later directly! Please upgrade to `lnd v0.15.3-beta` or later directly!
## MuSig2 ## MuSig2

View File

@@ -48,7 +48,7 @@ default](https://github.com/lightningnetwork/lnd/pull/6810) in most cases.
necessary when upgrading from `lnd v0.14.x-beta` to `lnd v0.15.x-beta`, see [the necessary when upgrading from `lnd v0.14.x-beta` to `lnd v0.15.x-beta`, see [the
remote signing documentation for more remote signing documentation for more
details](../remote-signing.md#migrating-a-remote-signing-setup-from-014x-to-015x). details](../remote-signing.md#migrating-a-remote-signing-setup-from-014x-to-015x).
Please upgrade to `lnd v0.15.2-beta` or later directly! Please upgrade to `lnd v0.15.3-beta` or later directly!
## `lncli` ## `lncli`

View File

@@ -161,7 +161,7 @@ Taproot account to the watch-only node, otherwise you will encounter errors such
as `account 0 not found` when doing on-chain operations that require creating as `account 0 not found` when doing on-chain operations that require creating
(change) P2TR addresses. (change) P2TR addresses.
**NOTE**: For this to work, you need to upgrade to at least `lnd v0.15.2-beta` **NOTE**: For this to work, you need to upgrade to at least `lnd v0.15.3-beta`
or later! or later!
The upgrade process should look like this: The upgrade process should look like this: