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
There has been some ongoing discussion regarding the ability for users to update their coins file "on demand" when a newer version is available or when a critical infra update etc would otherwise require a new release of the app(s).
The way the API currently works, app users would need to restart mm2 for any updated coins file to take effect. It would be better UX if an additional rpc like refresh_coin_data was available which could internally update the coins configuration without a restart.
This would also be useful for more quickly testing coins file variations, or being able to load from folder of snippets etc.
Something like
{
"mmrpc":"2.0",
"userpass":"testpsw",
"method":"refresh_coins_data",
"params": {
"path":"/path/to/coins" # optional, defaults to 'coins' file in mm2 binary folder
},
"id":42
}
One potential cases to consider how to best handle - what happens to coins which are activated but not present in the new file?
Is this rpc doable without disturbing the foundations?
The text was updated successfully, but these errors were encountered:
for bonus points, "path" could also be a url. ideally we could have a few coins_configs hosted, and people can use url to get them or path to use a local custom one. Instead of defining electrums etc in activation method params, it uses whats in the active coins file.
There has been some ongoing discussion regarding the ability for users to update their coins file "on demand" when a newer version is available or when a critical infra update etc would otherwise require a new release of the app(s).
Related: https://github.com/KomodoPlatform/komodo-wallet-desktop/issues/2035
The way the API currently works, app users would need to restart mm2 for any updated coins file to take effect. It would be better UX if an additional rpc like
refresh_coin_data
was available which could internally update the coins configuration without a restart.This would also be useful for more quickly testing coins file variations, or being able to load from folder of snippets etc.
Something like
One potential cases to consider how to best handle - what happens to coins which are activated but not present in the new file?
Is this rpc doable without disturbing the foundations?
The text was updated successfully, but these errors were encountered: