onbjerg

@diglos Please report that as a separate issue as it is unrelated to the parsing error. Closing this in favor of #3328

I am going to test this on a node and compare the results to Erigon to get a sense of if the implementation is flawed or not

**TL;DR: It matches except in the case of block count of 0, but this case is not defined in the spec..** Comparison between Erigon's impl and Reth's impl. Each example...

@mattsse Now uses the cache and sealed headers

> reth: > > > "reward":null > > looks like erigon/geth don't return this field if null? > > but return empty > > ``` > "gasUsedRatio":[ > > ],...

@mattsse I removed the 1024 limit, it seems I was mistaken and this is not actually part of the spec.

This is the full node config, i.e. it is capped because it will not have data for more than 1024 blocks at head afaik. Unsure what the best approach is...

@mattsse used GPO config to cap the length

Closing this in favor of #2629

Do you have available disk space?