

The Monero Research Lab (MRL) has decided to recommend that all Monero node operators enable a ban list
I was under the impression that there was a network attack going on which was disrupting node operations, as has had happened in the past and that is why this post was created.
My point is the nodes should be able to dynamically determine if misadjusted or allegedly misbehaving nodes are present and block/ignore those automatically without needing to apply a ban-list from a centralized authority. This is a long standing issue and measures in the protocol should be able to govern this, since it has not happened it appears that this is a fundamental flaw that cannot be addressed and instead a ban-list is the only solution.
My question is what is preventing this from being properly addressed so applying a centralized ban list is not necessary? Is it a whack-a-mole situation where attackers will just tweak some other parameters and get around any detection?
OK, thanks for the extra info, would have a been a good idea to include this in the post from the start.