It would enhance UX if users did not have to wait for the next release to be able to use newly listed coins.
The unified coin config that was recently created has made implementing the below proposal a little easier.
Like we do for app version to alert for updates, we should host an API endpoint which defines the current commit hash to be used from the coins repo
App needs to have awareness of (1) the coins commit used at build time, and (2) coins commit currently in use for logged in user.
If the API returns a different commit, update coins? modal appears offering to do a config reset which will download the latest coins data and replace the existing coins data in the OS userdata area, then reset the user wallet to use this coins file (not the coins file within the original app build).
The API could also return a changelog for display in the modal to show which coins were added / removed
In certain cases, we can force an update by making it mandatory to update coins file to use app. (e.g. token migrations)
When user does a regular "config reset", it downloads the latest first, unless it is already up to date locally.
One thing that is not yet covered from the unified coins config is inclusion of coin icon images. We should be able to detect where missing, and source from coins repo commit (if available) as required.
It would enhance UX if users did not have to wait for the next release to be able to use newly listed coins. The unified coin config that was recently created has made implementing the below proposal a little easier.
update coins?
modal appears offering to do a config reset which will download the latest coins data and replace the existing coins data in the OS userdata area, then reset the user wallet to use this coins file (not the coins file within the original app build).One thing that is not yet covered from the unified coins config is inclusion of coin icon images. We should be able to detect where missing, and source from coins repo commit (if available) as required.