<djrtwo> eth2 call in 35 minutes
warning, I'm going to ask for biggest bottleneck, what you're doing to solve it, and open up others for comment/advice
<Sebastian> Hi! is there going to be an ETHLondon group? I looked at this document: https://notes.ethereum.org/@protolambda/eth2_start
and I'm wondering if there is anything left to hack on after EthDenver?
<sly> I can't find it in the spec, but I presume the intention is that clients keep a record of SignedBeaconBlock that they receive, so that they can respond to requests such as BeaconBlocksByRange.
The spec says clients must support the request, and respond if they have the requested signed blocks, but there is nothing in the spec that requires them to keep a record of signed blocks. (Fork Choice only requires a record of BeaconBlock, not the signed envelope.)
MUSTin the p2p spec as constraining clients to keep the signed block data
<djrtwo> Networking call in about 13.5 hours
Top priority -- iron out how to use fork_version in planned forks, across chains, and other usecases. I have a proposal to start us off and we can go from there
Then we can get the last couple of PRs cleaned and merged