TODO: [PSBT] Support Electrum bip32Derivation style

[junderw]

When Electrum doesn't know the masterFingerprint it uses the fingerprint of the xpub, and the path is from the xpub (as m)

Perhaps we could make this a separate method?

[AndreasGassmann]

Is there an example available how this can be handled at the moment?

When working on PSBT integration I had a lot of trouble getting it to work. Turns out that this was the issue. I was not aware that electrum is not following the standard here. It's interesting that they still don't allow masterFingerprints to be imported by default. The only way I found is by using the integrated CLI, but that's not really feasible for regular users.

[junderw]

you have to check the bip32Derivation, derive the keys, and use sign

signHD doesn't support it yet.

[massimopavoni]

I know this is a rather old issue, but

The only way I found is by using the integrated CLI, but that's not really feasible for regular users.

@AndreasGassmann once imported the master fingerprint, is there a way of signing a transaction with Vault? It seems like it just doesn't recognize any of the Electrum generated QR codes.

[AndreasGassmann]

Is has been a long while, so I don't remember exactly anymore. But I'm pretty sure that when you import the masterFingerprint in Electrum, then it worked.

When you try it, what exactly didn't work? Maybe you can reach out on our social media channels so we can look into this.

[massimopavoni]

Essentially I tried to create a dummy transaction, that I wouldn't effectively broadcast afterwards, to see if I could sign it with the scanner in Vault, but the QR codes generated by Electrum, when scanned, trigger the incompatible code in the app. It does say I could "relay" it to the Wallet app, but I would rather keep my offline device with only one application.