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
{{ message }}
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
@homotopycolimit @zelig this is expected behaviour. maxpeers is not intuitive and does NOT mean that you will have 0 peers. It is just used for limiting inbound connections.
If you want to have a node running in singleton mode, probably best to use netrestrict option.
I am closing this, please open if you disagree or if you think this is a bug we should address.
@homotopycolimit I haven't seen a good explanation of maxpeers, so I think the docs are wrong. It also depends on the DialRatio which can only be set in a toml config, and we have no config for in command line arguments.
Expected behaviour:
When we set
--maxpeers 0
we expect the Swarm node to be "in singleton mode". Specifically we expect there to be no handshakes with other peers.See also:
https://swarm-guide.readthedocs.io/en/latest/gettingstarted.html#swarm-in-singleton-mode-no-peers
Actual behaviour:
Even with
--maxpeers 0
the node still engages in handshakes.The text was updated successfully, but these errors were encountered: