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
Examples are useful and they all work well, but there is no example about how to run more than one node (a second_node.py or additional_node.py example).
As an alternative, first_node.py could become a generic node which tries to bootstrap if a host and a port are specified.
The text was updated successfully, but these errors were encountered:
Hey @frafra - both "get.py" and "set.py" run additional nodes, since running a node is necessary to interact with the network. I do take the point though that it might be a good idea to have a generalized script that could either be a long running bootstrap node or connect to an existing network. What if first_node.py was changed to just node.py, and then accepted an optional host/port argument. If the argument is omitted, then it would run as a bootstrap node. If the argument is given, then it will try to connect to that node and join its network. What do you think?
Examples are useful and they all work well, but there is no example about how to run more than one node (a
second_node.py
oradditional_node.py
example).As an alternative,
first_node.py
could become a generic node which tries to bootstrap if a host and a port are specified.The text was updated successfully, but these errors were encountered: