[BUG] No abuse handling for misbehaving nodes #3
Description
I have noticed that many of my nodes are utilizing more than a core doing nothing. After some debugging it seems like some nodes (ex: z2DWuWNZcdSyZLpXFK2uCU3haaWMXrDAgxzv17sDEMHstZb) are sending thousands of malformed messages a second and impacting performance.
I have addressed this in my branch (https://github.com/lukehmcc/lib5/tree/0.2.0-patched) by adding timeouts and a 3 strike rule for nodes that send more than 100 messages a second, but it's not the most elegant solution. Ideally there should be some way to persist the config in the long term without having to pass a JSON file like I did here.