The reason for this is that we don’t store data on our server. as you know. Thus GHcloud will check yoru LocalData and install the dependencies. Usually the Blockstrap modules and plugins will only load the first time or occasionally. Asset information and the GHfarm data is updated / fetched more often which requires a refresh of the LocalData on your end.
in future versions we’ll be looking at changing the loading processor or not display the loading screen “as is” right now. However since GHcloud is basically just your HUB to connect to the GH services with all data being stored on your end the refreshing of data is necessary. It’s the only way without storing user data on our servers or even operate the hot wallets which we don’t wan to do to maintain the decentralized part of GHcloud as well as security.
[quote=“Daffy, post:7, topic:2303, full:true”]
A new update should not invalidate the salt and wallet anymore. The ssl update was the only switch that required the reimport of the salt/wallet.[/quote]
After doing some testing on GH’s cloud account I’ve come to the conclusion that the wallet backup + backing up the private keys for each GHwallet account is the best approach. Noting down the details used to create the actual account is recommended as well in case you happen to forget a password, security question / answer or one of the other details. However, I found that adding a password and pin as security option to a new address is sufficient enough. Using all available security options including the security question, pin, password etc can make sending an transactions a rather time consuming task.
The actual GHcloud “account” SALT already contains the security options including the security image which makes the SALT impossible to crack. Adding all security options to an address again is a bit of an overkill and depending on the number of accounts a user might have in GHwallet it will also make the SALT massive.