Phil Ngo

We should continue discussing this for https://github.com/ChainSafe/ssz

Vitest has its own codecoverage and is sending it to the backend.

Closing, nobody should be installing via NPM. Ever. We should provide alternative distribution methods.

> somehow there is a gap between new deposit index and old deposit index, this is strange because we always based on highest deposit event block number before fetching deposit...

Adding some discussion points from Devconnect here after speaking to @nflaig and conversations with other node operations teams. It seems like this would be a preferred approach to helping adoption...

#6008 should resolve this issue

Reevaluate snappy locations based on current block sizes.

Superseded by #5961

What is the scope and estimation of this fix? It's not really a blocker for v1.15 but can degrade the UX if we released with this.

New contributor guide/getting started section for developers: Examples: - Add new API? What files do I need to update? - How do I add a new network?