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
Hi – this is more of a suggestion although I haven’t tried out the app in the test environment so I’m not sure what functionality it has right now.
For those who plan on running multiple time nodes, I think there should be some way that we can let the time nodes we run be aware of the nodes that we own or have control over in order to allow schedules transactions to be handed off to other nodes when there is downtime.
For example if you own node A and node B (or 6 or 10 nodes), somewhere on the settings page perhaps you should be able to let node A be aware that you own node B and vice versa. So that when node A goes offline it can send the scheduled transactions that it has in its queue over to node B so that the person running the node doesn’t lose ETH or DAY for missing out on processing the transaction. Obviously there should be room to provide multiple nodes and not just one.
If both nodes are down however, then yes the person would have to lose out on the transaction because both their nodes are down.
The reason I bring up the suggestion is that no system has 100% uptime but for those making the effort to keep the system running through the use of multiple nodes for example, shouldn’t have the same amount of risk of losing ETH or DAY because of system downtime versus someone who is only running one node.
I also realize that I don’t know what incentives are written into the code to cause someone to setup 1, 2, 10 or more nodes but the whole concept of a node is that they can communicate with each other so I would think that the nodes I setup should be able to notify each other if they are offline and help shift the transactions between themselves.
The text was updated successfully, but these errors were encountered:
cryogenn
changed the title
Communication between Nodes you Own - suggestion
[IDEA] Communication between Nodes you Own
Aug 11, 2018
Hi – this is more of a suggestion although I haven’t tried out the app in the test environment so I’m not sure what functionality it has right now.
For those who plan on running multiple time nodes, I think there should be some way that we can let the time nodes we run be aware of the nodes that we own or have control over in order to allow schedules transactions to be handed off to other nodes when there is downtime.
For example if you own node A and node B (or 6 or 10 nodes), somewhere on the settings page perhaps you should be able to let node A be aware that you own node B and vice versa. So that when node A goes offline it can send the scheduled transactions that it has in its queue over to node B so that the person running the node doesn’t lose ETH or DAY for missing out on processing the transaction. Obviously there should be room to provide multiple nodes and not just one.
If both nodes are down however, then yes the person would have to lose out on the transaction because both their nodes are down.
The reason I bring up the suggestion is that no system has 100% uptime but for those making the effort to keep the system running through the use of multiple nodes for example, shouldn’t have the same amount of risk of losing ETH or DAY because of system downtime versus someone who is only running one node.
I also realize that I don’t know what incentives are written into the code to cause someone to setup 1, 2, 10 or more nodes but the whole concept of a node is that they can communicate with each other so I would think that the nodes I setup should be able to notify each other if they are offline and help shift the transactions between themselves.
The text was updated successfully, but these errors were encountered: