Suggestion: change service node option (not rep)

[nanostos]

A point of failure, as we've seen recently, is natrium's reliance on a single node. An option to select nodes from a curated list of high-performance nodes, and a field for entering a custom node address (if the user wishes to run their own node) will protect against downtime. At the moment the only recourse is to move your seed out of the wallet, which of course migrates users away from natrium. The suggested option would allow the user to change the node that the wallet uses to broadcast send/receive/change blocks without having to move out of the wallet. Cake wallet has an implementation of this, for reference.

[bbedward]

While this is a good idea, it's more complicated in practice.

In the network's current state every node is out of sync. If a user broadcasted a send on one node - became impatient it didn't reach another wallet, then switched to another node that didn't have the block and broadcasted another send they'd create a fork and one of those two chains would eventually get rolled back - but neither node would consider it a fork until it was eventually rolled back. In the recent attack we saw this even after several hours where blocks did not confirm.

There's other complications too, but nevertheless this is something we have considered and discussed before. Presently this is something we'll re- evaluate when Nano's upstream issues are resolved.

[Benhgift]

@bbedward If that's the main concern then it would probably be fine to only put in a custom IP field. That way power users could still use their own node.

Beyond that, there are other options like a cool down period if there are pending TXs, or a warning message.

Personally I just want to use my own node so I can crank the PoW way way up.