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 Sep 5, 2020. It is now read-only.
As geth will create the keystore folder on demand the account backup menu-item will be non reactive on the first screens of the on-boarding:
There are two reasons for the availability of the menu-item:
to backup accounts
to import web3-secret-storage files
As for 2. the current importer only supports presale-wallets, though #997 will extend its functionality to cover web3-secret-storage files.
Following ways are feasible:
unload the menu-item during the on-boarding
disable it (and add some hint to it) during the on-boarding
leave it as is and let it create the folder if not available
leave it as is and let it open the closest available parent folder
Possibility 3 and 4 might not be node agnostic and thus prevent the abstraction of the backend nodes as #1064 tries to initiate. 😈
(..for sure this can be case depending if the node name is known to Mist considering the low number of nodes.)
The text was updated successfully, but these errors were encountered:
As geth will create the keystore folder on demand the account backup menu-item will be non reactive on the first screens of the on-boarding:
There are two reasons for the availability of the menu-item:
As for 2. the current importer only supports presale-wallets, though #997 will extend its functionality to cover web3-secret-storage files.
Following ways are feasible:
Possibility 3 and 4 might not be node agnostic and thus prevent the abstraction of the backend nodes as #1064 tries to initiate. 😈
(..for sure this can be case depending if the node name is known to Mist considering the low number of nodes.)
The text was updated successfully, but these errors were encountered: