You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I send transaction, the UI history list doesn't register it for more than half a minute, which is bad, as user might be confused what happened. I understand this can be due to some api calls not getting it right away.
I propose...
to optimistically update the history with the newest transaction and keep it as "placeholder" until the wallet actually fetches it from blockchain. This would help UX and avoid user's confusion.
Or wallet can ask for this specific ID at first and add it temporarily to history.,
The text was updated successfully, but these errors were encountered:
When I send transaction, the UI history list doesn't register it for more than half a minute, which is bad, as user might be confused what happened. I understand this can be due to some api calls not getting it right away.
I propose...
to optimistically update the history with the newest transaction and keep it as "placeholder" until the wallet actually fetches it from blockchain. This would help UX and avoid user's confusion.
Or wallet can ask for this specific ID at first and add it temporarily to history.,
The text was updated successfully, but these errors were encountered: