TX_MISSING_INPUTS is ambiguous #357
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#357
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.