The use case here, is that we can take down any node independently of each other. Right now , if we take the registry node down, we have to restart all the other nodes to register.
Registry serializes into JSON the manifest
Load up on startup.
It should be based on public key, and update the ip if the user has changed.
Use case 1:
stop registry node
restart registry node
expect: consensus to work as normal
Use case 2:
stop a single node (non registry)
start the node again
expect: consensus work as normal
Use case 3:
stop a single node (non registry)
start a node again with different port or ip, but same public key
expect manifest to update & broadcast & consensus work as normal
The use case here, is that we can take down any node independently of each other. Right now , if we take the registry node down, we have to restart all the other nodes to register.
It should be based on public key, and update the ip if the user has changed.
Use case 1:
Use case 2:
Use case 3:
expect manifest to update & broadcast & consensus work as normal