1 min read

ethlambda Runs a 1,024-Validator Devnet

Lambda's 1,024-validator devnet exposed slow block production and recursive aggregation, while signatures and committee aggregates mostly arrived on time.

ethlambda Runs a 1,024-Validator Devnet

Lambda ran a devnet of its lean consensus client, ethlambda, with 1,024 validators and published the results.1

Setup

The network ran on 32 nodes with 32 validators each, split across 8 aggregation subnets. Each aggregator handled 128 signatures per interval. Slots lasted 4 seconds, with 0.8-second intervals. A signature is 1.3 KB; a block proof is 220 KB.1

Results

97% of signatures arrived within their interval. Only 5% of blocks arrived on time. Block building averaged 2.5 seconds and recursive aggregation 1.3 seconds. 11% of blocks were reorged, and finality lagged by 24 slots, close to two minutes.1

Findings

The proposer was the bottleneck. Late blocks were orphaned, and slow aggregation drove the finality lag. The team expects committee aggregation to hold at 2,048 validators.1

Sources

  1. https://blog.lambdaclass.com/ethlambda-what-we-learned-running-a-1024-validator-devnet/ ↩ ↩2 ↩3 ↩4