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
Retrieving the latest transactions list takes up to 120 seconds to show on the app. This is issue leads to one question, isn’t the data already synced and available locally on the device? we have it locally so why we are retrieving the data from the explorer API. If the data is available locally it will be faster to query and we will remove the dependency on a single explorer server.
Improvement in this area would enhance the user experience with this beautiful wallet.
update:i also noticted that the application spends about 77 seconds in opened connection with digibyte.org which i'm not sure if the connection over https with digibyte.org is required because my undertanding it only needs to connect to (seed.digibyteservers.io on port 12024) + (explorer-1.us.digibyteservers.io over https)
the delay seems to be caused by the fact that we try to sync before listing the transactions list. woud it be faster to first list the transactions from whatever cached on the device? then try to sync. this aproach would give the end user faster experiance and intraction
The text was updated successfully, but these errors were encountered:
Retrieving the latest transactions list takes up to 120 seconds to show on the app. This is issue leads to one question, isn’t the data already synced and available locally on the device? we have it locally so why we are retrieving the data from the explorer API. If the data is available locally it will be faster to query and we will remove the dependency on a single explorer server.
Improvement in this area would enhance the user experience with this beautiful wallet.
update:i also noticted that the application spends about 77 seconds in opened connection with digibyte.org which i'm not sure if the connection over https with digibyte.org is required because my undertanding it only needs to connect to (seed.digibyteservers.io on port 12024) + (explorer-1.us.digibyteservers.io over https)
the delay seems to be caused by the fact that we try to sync before listing the transactions list. woud it be faster to first list the transactions from whatever cached on the device? then try to sync. this aproach would give the end user faster experiance and intraction
The text was updated successfully, but these errors were encountered: