Last week we ran a devnet with 1024 validators, split across 8 aggregation sub-networks. That layout keeps the network scalable, since each aggregator combines 128 signatures per interval, well inside budget. Each of the 32 ethlambda nodes is in its own server, with 32 validators each, twice as many

In our previous blog post, we mentioned devnet 5 introduced full-block aggregation, making each block include a single proof for all its attestations. This makes the required bandwidth constant, not dependent on the number of attestations. However, this moves a lot of aggregation to the proposer, which quickly becomes

We already introduced ethlambda, our Lean Consensus client. We also wrote a blog post about devnet 4, which introduced recursive aggregation. Now that devnet 5 is implemented and in interop testing, it's a good time to recap the devnets so far and look at the candidates for the