Adrian Sutton

For the record, if this pans out it would be an excellent addition to the honest validator spec so that it becomes expected behaviour for validators to penalise late blocks.

The logs look completely normal around slot 688 where they were slashed. It's not near a restart point and looks like the chain is progressing forward as you'd expect.

Experience with ETH1 is that coordinating a hard fork on a testnet takes a lot of time and effort from the client development teams and others like the cat herders...

> Been considering this. The easiest equivalent I can think of would be a modified deposit contract that contains a per-sender allowance of deposits (with empty value being 0 to...

We do have an option already that outputs these to logs though it would be more convenient to get them as files

It would also be good to improve the reporting when one, but not all eth1 nodes are unavailable. Currently we print: ``` teku[2523]: 03:52:25.650 WARN - Endpoint localhost:8545 [1] is...

We did a round of improvements for this and the eth1-endpoint is going away post-merge which changes the reporting requirements anyway.

We did add some metrics. Not seeing other things that would be useful currently.

We could just refuse to sync from a state outside the weak subjectivity period by default and then have a flag to allow it. That will act as a prompt...

With epoch transition now being precomputed we're seeing Teku produce the first block of epochs well inside the 4s cutoff to get votes. It's still slower than other blocks but...