-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
PSBT funding flow failed with bitcoin core #6372
Comments
this one has a multisig input, but i also tried witness v0 keyhash inputs and they failed with the same error |
what is the peer id? oh sorry I thought this was a peer returned err nm |
Thank you for the report. I was able to reproduce it and narrow it down to the
Those derivation paths seem to be empty. Even though that is allowed by the spec (and should probably be fixed in the Golang implementation of the PSBT library), this seems weird. Can you tell us anything about those inputs or derivation paths? Are you using a hardware wallet with HWI? |
I imported those keys in bitcoin core |
But what does lnd do with the derivation paths? |
Ah, interesting, thanks. I'll create a fix in the mentioned library. |
This was auto closed by the btcd PR (TIL that's even possible), but we still need to update |
Updates a version of `btcutil/psbt` that has looser parsing requirements to properly match the BIP. Fixes: lightningnetwork#6372
Background
Describe your issue here.
i have opened channel in the past with PSBTs without any issues, but now suddenly they all fail to decode bitcoin core's PSBTs
Your environment
lnd
lnd version 0.14.2-beta commit=v0.14.2-beta
uname -a
on *Nix)Linux myhostname 5.16.16-arch1-1 #1 SMP PREEMPT Mon, 21 Mar 2022 22:59:40 +0000 x86_64 GNU/Linux
btcd
,bitcoind
, or other backendbitcoin core v22
Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
--psbt
and try again until the funding address is tb1qpqgwtdeucepnk6uyvf8m4lucjhuwxuz5jp3nj3w3sdntfqqxh5kq0qaare (can take a long time)Expected behaviour
Tell us what should happen
normal channel open flow as usual
Actual behaviour
Tell us what happens instead
additional notes
i think it is related to #4400, but it is a PSBT generated by Bitcoin Core, which sets the standard
decoded:
The text was updated successfully, but these errors were encountered: