-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Liquid wrong derivation path/addresses #5967
Comments
There isn't any logic or standard for derivation paths. We picked one documented here https://github.com/satoshilabs/slips/blob/master/slip-0044.md
Yes, it doesn't change anything in the wallet's settings. This is only used for the PSBTs. If you want your own path, try to import an output descriptors by "importing an existing wallet"., Then "Enter Extended Pubkey". However, I really advise you against doing this for 2 reasons:
|
Also, I think @Kukks worked on something to make things more compatible with Green. But I don't really know about it. |
First of all, thank you for your response. If the derivation path is not the same as Green's and cannot be customized, there is no way to spend the funds received, since BTCPay does not allow sending from the Liquid hot wallet. |
@marcocattaneogotam you can through liquid's command line. When you create your hot wallet you need to import the keys in it. There might be a way to be compatible with Green, you need to ask to @Kukks though. |
Oh I see. |
What is your BTCPay version?
I'm running BTCPay Server v1.13.1+ca55e1f30****
How did you deploy BTCPay Server?
I'm running BTCPay Server on a VPN, enabling LBTC native support.
What happened?
I've imported a LIQUID hot wallet seedphrase in btcpay but addresses don't match with Green's ones. BTCPay shows a m/84'/1776'/0' derivation path for a native segwit account. Why? Also if I manually change the dev path, addresses don't change.
Alternatively, importing an XPUB via QR code, I get a list of liquid testnet VT*** addresses on the screen, again why?
How did you encounter this bug?
Relevant log output
No response
What browser do you use?
No response
Additional information
No response
Are you sure this is a bug report?
The text was updated successfully, but these errors were encountered: