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
{{ message }}
This repository has been archived by the owner on Jan 3, 2019. It is now read-only.
Consolidating all issues related to timeouts, XMLHttpRequest Error ( #233 ) etc in this issue and closing the rest.
Reduce network payload
Open the wallet as soon as all the used addresses are discovered. At this point we have the balance. User can see the balance, but not the transaction history, and they will not be able to spend any money.
Fetch all the unspents for the discovered addresses. After this is done, user will be able to send money.
Load transactions. Given the limitation of blockr, we cannot query transactions by block height for a given set of addresses, so there's no sure way to load the latest transactions first. Our best bet is to load the transactions in order of the newest discovered to the first discovered addresses. In UX words, 1) it's not possible to load the latest n transactions first, then wait for user to scroll to load more, while guarantee correctness. 2) if we decide to show transactions as they come in, transactions will come in no particular order -- you will see transactions inserted in between already loaded transactions, if we want to preserve the current reverse chronological order in the history tab. Whether we want to show transactions as they come in or show nothing until all transactions are loaded, that's a UX decision I'll leave to @mattatgit
Serialize the previous instance of the wallet to browser db. We should always assume that balance and unspents are out of date. Only show transactions from the old wallet, until we have updated transaction data.
The text was updated successfully, but these errors were encountered:
Hive was working until now, was trying to check if loading times were faster (from Heroku) - but kept on getting this when trying to sync, I also created a new wallet just to check, got the same error.
Consolidating all issues related to timeouts, XMLHttpRequest Error ( #233 ) etc in this issue and closing the rest.
The text was updated successfully, but these errors were encountered: