[bug] <title>Ledger signing timelock script input does not work

[elRaulito]

Is there an existing issue for this?

• I have searched the existing issues

SATS-CONNECT Version

2.4.0

Current Behavior

Currently using timelock scripts in Bitcoin, I need to sign inputs coming from Bitcoin timelock script and from the bitcoin payment address using ledger wallet and xverse

I am signing all inputs using same pubkey however apparently the usual xverse way to sign inputs is not working

Should I split the process and sign first the time lock script inputs and then the payment inputs?

Please let me know

Expected Behavior

Since I am using the same pubkey I expect that I would be able to sign everything in once

Steps To Reproduce

Lock some BTC in a bitcoin timelock script and then try to unlock using ledger

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

No response

[victorkirov]

Hey @elRaulito

For Ledger, things are a bit more complicated. You cannot sign for alternate addresses generated from the pubKey; only for the ones specified in the wallet (Native segwit and taproot). When sending a sign request to Ledger, you need to specify how the address was derived in a wallet descriptor that is passed to the Ledger device so the user can confirm they are signing the correct thing.

We currently don't expose passing in a custom wallet descriptor for custom ledger addresses.

[elRaulito]

Thanks @victorkirov

Is there a way to create multisig using ledger then?
Anyway thanks a lot

Also importing the ledger seed in a hot wallet (making it useless) will get same addresses?

[victorkirov]

Multisig with Ledger is pretty limited, so we haven't really exposed the functionality as it has some hard requirements that are difficult to get around and would cause dev issues and require a lot of support.

Yeah, importing the ledger seed would result in the same addresses, but it would make the cold wallet kind of pointless, as you mentioned 😅