Join process via consensus about go-lachesis HOT 2 CLOSED

A few questions:

• should we also consider removing a node from peer list and how it could be implemented? i.e. node self-removal should be obviously straightforward, should we consider node removal on consensus of other nodes?
• How can we use the same poset graph for peer list changes? Currently nodes do not look inside transactions. Would it better to maintain a separate poset graph for peer list so nodes will look into transactions in this poset for operations over peer list?

from go-lachesis.

To start with, we should confirm that all nodes joining have the same version. Otherwise they are rejected. Later, we can use a more detailed version scheme, like the SSH standard has: https://tools.ietf.org/html/rfc4253#section-4.2

I'm thinking in the REQ stage you could include the version in a header—see aforementioned RFC—you could send:

lachesis-0.3.3-5916fe75<CR><LF>

Then, in the ACK REQ stage you could confirm that the version strings equals its own version string, and if it does, accept it into the peers list & thus the network.

(obviously this has no security advantage, as anyone can fake versions, but it is handy for non security related stability and debugging)

from go-lachesis.