Skip to content

Commit

Permalink
tapfreighter: allow internal key to be unknown
Browse files Browse the repository at this point in the history
If we want to have the ability to encumber the BTC level outputs by a
MuSig2 internal key and/or have a Tapscript sibling, we need to allow
for the internal key to be unknown to the wallet.
Otherwise we can't choose the NUMS pub key as the internal key if we
wanted, for example, to only allow a script spend on the BTC level.
  • Loading branch information
guggero committed Feb 19, 2024
1 parent edc9c9e commit acde627
Showing 1 changed file with 0 additions and 7 deletions.
7 changes: 0 additions & 7 deletions tapfreighter/wallet.go
Original file line number Diff line number Diff line change
Expand Up @@ -879,13 +879,6 @@ func (f *AssetWallet) setVPacketInputs(ctx context.Context,
// now we just put this check in place.
assetInput := eligibleCommitments[idx]
internalKey := assetInput.InternalKey
if !f.cfg.KeyRing.IsLocalKey(ctx, internalKey) {
return nil, fmt.Errorf("invalid internal key family "+
"for selected input, not known to lnd: "+
"key=%x, fam=%v, idx=%v",
internalKey.PubKey.SerializeCompressed(),
internalKey.Family, internalKey.Index)
}

inBip32Derivation, inTrBip32Derivation :=
tappsbt.Bip32DerivationFromKeyDesc(
Expand Down

0 comments on commit acde627

Please sign in to comment.