Jim McDonald

> There is definitely value in being able to filter by status even though it can be calculated from the result. Because if I want to query for all active_exiting...

Going back to the questions in the original comment with this PR: - should we add an epoch metadata field in the returned data to allow recreation of validator states...

@rkapka dropping status is to allow us to move to SSZ encoding, which gives us significant memory usage and speed improvements. So the benefit is a lot more than "pretty".

Latest update tweaks the wording to consider both `[]` and an empty body as "return all validators".

The gas used in a block has little relationship to the size of the block (see: blob transactions). So I don't think that this would address the issue raised.

I haven't considered this deeply, but it seems that there are multiple dimensions in play here, at least: - number of blobs - value to proposer - gas used -...

"Fixes to rewards during inactivity leak" should be addressed before phase 0 goes live. The idea that a validator can act perfectly and still lose funds due to the actions...

What's the gap between 3) and 4), in general? Can they be far enough apart that they warrant separate events? I'd prefer to keep the `block` event as at item...

> Not a strong requirement in timing in general, but they convey different information: 2. is precise in timing but may emit invalid blocks. 3. is imprecise in timing but...

I'm not sure how multiple timestamps would work. You would either be holding the event back from the event stream until all timestamps were available, or you would be sending...