bitshares-ui
bitshares-ui copied to clipboard
JSON node input
Is your feature request related to a problem? Please describe.
User has to enter nodes manually via GUI; this can be tedious.
Sometimes nodes are added in batches of 20 ore more by node operators.
It takes time for UI team to update the reference wallet.
The shipped list is static, the list of live nodes is dynamic.
Describe the solution you'd like
JSON input field in the reference UI with a brief description of required format.
[
{"node": wss://xyz.com, "description": "XYZ"},
{"node": wss://abcd.com, "description": "ABCD"},
{...},
]
Describe alternatives you've considered
The UI could allow for a config file input of nodes.
Additional context I am currently aware of 200+ nodes of current or historic significance. I check them regularly, I know of 72 live today. The reference UI has had a dated list of 35 nodes since the last live worker, many of which are no longer live.
When companies like deex and walldex come online with large node offerings its should just be a cut, paste, and text format operation for the user to upgrade to new nodes.
Screenshot
New input for JSON formatted list would go here:

It's easier and usually safer for developers and/or maintainers of this repository to verify a static list rather than a dynamic one. It's not saying that we don't trust you, but rather it's better to have someone reviewing when changes are being made. Just my own opinion.
Importing batches of new nodes, by a user that knows what it means, could probably be a good idea for a feature though.
It's not saying that we don't trust you
I don't understand the trust issue.
There is already UI to input nodes one at a time.
I want UI to input multiple nodes in JSON format.
How is that exploitable?
I thought to update the list from a server automatically, that's where trust is needed. I think I misunderstood it. If someone likes to implement it, it's fine. Although any feature would be useful, average users don't update the list at all, nor know where to get a updated list; advanced users usually know where to get one working node or a few, add manually and stick with it/them forever.