You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Roasbeef opened this issue
Jan 21, 2020
· 3 comments
· Fixed by #5047
Labels
advancedIssues suitable for very experienced developersP1MUST be fixed or reviewedrecoveryRelated to the backup/restoration of LND data (e.g. wallet seeds)safetyGeneral label for issues/PRs related to the safety of using the softwarev0.13walletThe wallet (lnwallet) which LND uses
This issue is related to this on going btcwallet PR which adds watch-only support to btcwallet as well as our issue tracking PSBT integration within lnd, and finally #3929 . Once those items are carried out lnd will be able to operate in a mode wherein it requires no private key material to be accessed within the main process. As a result, we'll need a slightly different initialization mode for lnd in order to support this new operating mode. As is, when creating a new lnd instance you need to either provide raw entropy which is used to derive a master private key, or an aezeed. What we need instead, is a new more which accepts a series of xpubs, which are them imported into the internal wallet.
Steps to Completion
Add a new set of RPC calls to the WalletKit sub-server that allows a user to export a given xpub based on a target key family.
This new watch-only variant will then need to interact with each of the yet-to-be-finalized APIs in the btcwallet PR referenced above to import each of the xpubs for each key family into the wallet.
Note that we'll need to complete #3929 before this issue can be fully implemented.
The text was updated successfully, but these errors were encountered:
Roasbeef
added
wallet
The wallet (lnwallet) which LND uses
advanced
Issues suitable for very experienced developers
safety
General label for issues/PRs related to the safety of using the software
recovery
Related to the backup/restoration of LND data (e.g. wallet seeds)
labels
Jan 21, 2020
Keeping this open for now as the second point to extend InitWallet to allow the relevant key families ti be passed in isn't yet resolved. This is the missing gap that would allow stuff like lnd just having the raw account xpubs for the multi-sig keys with signing being done in a remote/detached manner.
advancedIssues suitable for very experienced developersP1MUST be fixed or reviewedrecoveryRelated to the backup/restoration of LND data (e.g. wallet seeds)safetyGeneral label for issues/PRs related to the safety of using the softwarev0.13walletThe wallet (lnwallet) which LND uses
This issue is related to this on going
btcwallet
PR which adds watch-only support tobtcwallet
as well as our issue tracking PSBT integration withinlnd
, and finally #3929 . Once those items are carried outlnd
will be able to operate in a mode wherein it requires no private key material to be accessed within the main process. As a result, we'll need a slightly different initialization mode forlnd
in order to support this new operating mode. As is, when creating a newlnd
instance you need to either provide raw entropy which is used to derive a master private key, or anaezeed
. What we need instead, is a new more which accepts a series ofxpub
s, which are them imported into the internal wallet.Steps to Completion
Add a new set of RPC calls to the
WalletKit
sub-server that allows a user to export a given xpub based on a target key family.This new watch-only variant will then need to interact with each of the yet-to-be-finalized APIs in the
btcwallet
PR referenced above to import each of the xpubs for each key family into the wallet.Extend the existing
InitWalllet
RPC call to support importing a set of basexpubs
: one for each of our currently used active key families. Note that we need to import eachxpub
rather than a single one derived from the main seed as each key family or account uses hardened derivation for everything "above" it. #5486Note that we'll need to complete #3929 before this issue can be fully implemented.
The text was updated successfully, but these errors were encountered: