Linkability error when not in sync sometimes really sucks #59

Open
opened 3 years ago by duke · 0 comments
duke commented 3 years ago
Owner

This error is technically valid, but can often happen when a new block is coming in and the node is updating local state for a few milliseconds. It's really not cool that we lose the input address, amount and memo field data completely. No bueno!

The correct thing to do is for the GUI wallet to detect this particular error, and try again a few times, as long as getinfo[blocks] is close to getinfo[longestchain]. If we are truly syncing, then we don't need to retry, but we must preserve what the user input to address, amount and memo field inputs.

This error is technically valid, but can often happen when a new block is coming in and the node is updating local state for a few milliseconds. It's really not cool that we lose the input address, amount and memo field data completely. No bueno! The correct thing to do is for the GUI wallet to detect this particular error, and try again a few times, as long as getinfo[blocks] is close to getinfo[longestchain]. If we are truly syncing, then we don't need to retry, but we must preserve what the user input to address, amount and memo field inputs.
duke added the
bug
label 1 year ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.