Event Store vs. corruption scenarios


How would Event Store do under some of the scenarios researched in https://blog.acolyer.org/2017/03/08/redundancy-does-not-imply-fault-tolerance-analysis-of-distributed-storage-reactions-to-single-errors-and-corruptions/ ?

Eventstore will detect the problem on start up (there is checksumming)
on bad data while in headers there is again checksumming. Bad data
written on master node by default cannot be shared to other nodes
unless there is a memory fault or a replica has fallen significantly