It does not matter what they say (nobody should accepts or deny anything until its verified by himself/herself). That’s why the nodes have more than ~100K node entries in their
all struct, which also can slow down the nodes, and lead to miss some block due to the computational resources. But, it depends on a lot of another factors too.
Especially, when jormungandr use an immutable global state structure, where you want to change something then you need to use some locking mechanism before you touch it (i.e. Futex or POSIX’ mutex the good old semaphores or condition variable or similar). If somebody studied CS/IT then it’s obvious that this is not and ideal solution to modify the state, but for complex system where lot of components want to use it, you must have some restriction for tis access. Of course you can clone that state if it does not harm, and change that cloned global state for some reason.
There is no such list, your node (and of course other nodes too) put any nodes in the quarantine if they triggered by these:
- cannot connect: You node cannot connect to a node that have public address specified.
- invalid public id, peer node identifier differs to the previously known/stored one, whihc is always the case if you restart your node.
- invalid data: not implemented.
We should need more info on this. VM/VPS/Phys spec of the node. Node version config etc.
Nr. of running node on the same VM/VPS/Phys. Network bandwidth/latency characteristic etc.