-
Notifications
You must be signed in to change notification settings - Fork 36.2k
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
[RPC][Wallet][Segwit] Bug: Transaction sent to imported P2WSH does not appear in listtransaction. #10924
Comments
A short update (thanks @NicolasDorier): there is no CTxDestination for native witness outputs, which means any There are 2 solutions here:
|
Actually, (1) is already warned about in the |
my attempt to fix the issue, #10947 it would need to have bech32 support though. |
Should #10947 be tagged for 0.15, or should this be untagged? |
Should not be tagged for 0.15. I think the best is to wait next version, non obvious code change. |
Cleared milestone 0.15. |
Closing as this was solved by #11167 |
It seems that there is a bug when a node sends coins to an imported P2WSH.
Such transaction does not appear in
listtransaction
unlike P2SH.Note that if node A sends to node B where B imported the P2WSH, things works as expected, and both A and B would see the transaction in
listtransaction
.The stangest thing is that
gettransaction
seems to know about the transaction. (but not the details)Repro:
https://github.com/NicolasDorier/bitcoin/commits/importaddresssegwit
If you switch
use_p2wsh
to false, it passes, else, it does not.Failing on
assert(self.nodes[0].listtransactions("*", 1, 0, True)[0]["txid"] == txid)
ping @sipa this is the bug I bumped on TumbleBit that I explained to you.
The text was updated successfully, but these errors were encountered: