Lion - dapplion

> It would be good to maintain the script either in this repo or another repo under ethereum. I feel uneasy about one person maintaining it privately (not from a...

> Can we have the conversion script in this repo or in consensus-specs and just run it during build or something? or produce something in consensus-specs as part of that...

I had the impression that @arnetheduck main goal was to have a separate type (e.g. `UnaggregatedAttestation`) only used in the `beacon_attestation` topic. And leave `Attestation` as is for the rest...

+1 to burn the meta

No one likes the meta element, but there's no appetite either for the effort to remove it - See discussion in https://github.com/ethereum/beacon-APIs/pull/384#issuecomment-1850805471 According to @mcdee review of clients seems that...

> What's the gap between 3) and 4), in general? Can they be far enough apart that they warrant separate events? Not all blocks end up being head, so for...

I would vote to define the event strictly to be emitted after full validation (gossip, consensus, execution, and DA) plus append a precise timestamp of received time before full validation....

> Wouldn't it be simpler to use the delay since start of slot instead of a timestamp? Not sure if simpler, sounds mostly equivalent. For the purpose of measuring latency...

> but if there's a good reason then we can add support. I just think we want a good idea of the problem we're solving before we look for a...

> This isn't the main purpose of the events stream, though. If we're trying to track this information then I think that this is better off coming from telemetry rather...