Skip to content
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

Cannot estimate fee of BTC transactions that have multi-origin inputs #141

Closed
ShookLyngs opened this issue Apr 28, 2024 · 0 comments · Fixed by #228
Closed

Cannot estimate fee of BTC transactions that have multi-origin inputs #141

ShookLyngs opened this issue Apr 28, 2024 · 0 comments · Fixed by #228
Assignees

Comments

@ShookLyngs
Copy link
Collaborator

ShookLyngs commented Apr 28, 2024

In TxBuilder, if there has inputs where their script public-key don't match to the script public-key of from, the fee estimation of the TxBuilder fails. For example, if Alice uses a P2WPKH script, and Bob uses a P2TR script, you cannot add inputs from both Alice and Bob into the TxBuilder. If you do, the fee estimation process will fail due to unrecognized script public keys in the inputs.

@Flouse Flouse added bug Something isn't working and removed bug Something isn't working labels May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants