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

TX_MISSING_INPUTS is ambiguous #357

Open
BrannonKing opened this issue Jan 9, 2020 · 1 comment
Open

TX_MISSING_INPUTS is ambiguous #357

BrannonKing opened this issue Jan 9, 2020 · 1 comment

Comments

@BrannonKing
Copy link
Member

The TX_MISSING_INPUTS error makes it sound like the person creating the TX forgot to include inputs in that TX. However, the error is actually issued when the TX's inputs don't have corresponding TXOs in the history of the chain or if the TXOs have already been spent. We should clarify the message and consider breaking it into spent vs missing.

@BrannonKing
Copy link
Member Author

Should the error state what TXIs were already spent? Or should there be a way to query via RPC for what was spent? Maybe the unspent Sqlite table is sufficient for that.

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

No branches or pull requests

1 participant