Timeliness detectors and 51% attack recovery in blockchains

[dankrad]

@vbuterin

then (at least because they themselves can rebroadcast it) that block will get into the hands of an attester before the attester deadline T+δT + \delta

Should this be T + 2 \delta?

@vbuterin

Hence, in all cases, we can prevent 51% attacks from breaking finality, at least past a certain point in time ( T+2kδT + 2k\delta , the time bound after which if a client has not accepted a block as timely then we know that it will never accept it as timely).

What you’re saying is also, if both chains are published at the same time, there’s really nothing we can do in terms of choosing the right one. I guess in that case we just display the message “consensus failure” to the user and wait for social recovery?