kordlib
Continue adding node even if checks fail
Perhaps you have a more elaborate strategy in mind. This is enough to do the trick for me at least.
I am not sure whether this is the right call, since the version check should stop connecting to the node, maybe we can move it to after the ws connect, however that wouldn't be ideal either. Maybe add a config flag for it?
It didn't occur to me it throws an exception on purpose. What you could do is apply the same retry strategy to the version check
I think you should also put some thought into what happens if a node is rejected. Currently if a node is rejected, it just seems to linger in an inactive state in the AbstractLavakord instance.