Skip to content

CouldNotSatisfy in alternative thresh path. How to debug? #487

Answered by sanket1729
evd0kim asked this question in Q&A
Discussion options

You must be logged in to vote

Thanks for the detailed example. TLDR: finalize psbt API for pkh inside thresh where pkh is not being satisfied has a bug. As in your example, only 1 of pkh is satisfied other two are dissatisfied. I am working on a patch.

I think I figured out the issue. Unfortunately, this is a bug in the current miniscript psbt API. The psbt finalize API tries to infer minsicript from the raw bitcoin::Script, so it needs some information to maintain the mapping from pubkey_hash to public key. Right now, the finalized API looks all keys in partial_sigs field to find which bitcoin::PublicKey hashes to the given public key hash. While this works with satisfying pkh fragments, it does not work for dissatis…

Replies: 3 comments 5 replies

Comment options

You must be logged in to vote
1 reply
@evd0kim
Comment options

Comment options

You must be logged in to vote
3 replies
@sanket1729
Comment options

@evd0kim
Comment options

@evd0kim
Comment options

Comment options

You must be logged in to vote
1 reply
@evd0kim
Comment options

Answer selected by evd0kim
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants