You mentioned only the rewrite of history, but there is at least one other attack on a network - a coordinated refusal of blocks with transaction(s) attacker de

You mentioned only the rewrite of history, but there is at least one other attack on a network - a coordinated refusal of blocks with transaction(s) attacker deem ungood. This way, some person(s) will be denied the right to transact. A direct way to do that is to vote NO for such blocks. Does PoS protocol of yours require the NO vote to have reasons for that decision? It can be analyzed and having wrong NO reasons may be a reason to punish validator. An indirect way to do that attack is to timeout on unwanted blocks. E.g., if a malicious validator sees a block it does not want, it will stop sending any messages at all until it sees next block or has an opportunity to be a proposer. How PoS protocol of yours handle such attack?