lbrycrdd created invalid transaction, thinks address is empty even though its not #46
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#46
Loading…
Add table
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?
near the bottom, it looks like an invalid transaction was created
it was created using a script, but the script just calls
lbrycrd-cli sendtoaddress
anyway, the transaction was supposed to spent from the address
bWLB555cGfRcW4eCPBQgPScmocZoMPNGCd
, which is where the previous transaction (d5e2963d45dbf17a6eea65967de1a9dc44fe47f74420e3b73a3da62308e2aa76) sent its changehowever, the wallet now thinks that
bWLB555cGfRcW4eCPBQgPScmocZoMPNGCd
is emptyeven though the invalid transaction was never accepted by the network
i bet i could fix this by exporting the address, creating a brand new wallet, then reimporting the address
(though i havent tried that yet)
but the bug should probably be fixed first. plus it may be something we want to send upstream, since its probably not related to anything we changed in bitcoin
let me know if you need help reproducing this. i don't have the invalid transaction that was attempted, but i can send you the wallet file and more logs
i can maybe reconstruct the command that the script tried to run
@kaykurokawa did you ever look into this? if this hasn't come up since, maybe we can close this issue.
have not seen this issue again