feat: introdue reth era export

[lean-apple]

Closes #15495.

Only start introducing the functional logic (not the interface with the cli) :

For a certain number of block set up in the config, it fetches the data (header, block body, receipts) to reconstruct the block history and write them directly into era files.

Still to do :

• Add writing logic,
• Add tests with import/export rountrip --> started but not finished

[mattsse]

awesome, this looks pretty good!

I think we should considering merging both import and export into one crate and rename era-import @RomanHodulak

and I believe we're missing tx.commit calls in import @RomanHodulak

we could also handle those externally but maybe a better idea to commit file after file?

[RomanHodulak]

@mattsse @lean-apple

I think merging and renaming the crates fits.

Commit per ERA file seems best for this use-case, i.e. the file remains imported even if the process is interupted

[mattsse]

cool, only thing missing really is a rebase and moving a few things around

[codspeed-hq]

CodSpeed Performance Report

Merging #15909 will degrade performances by 10.84%

_{Comparing lean-apple:reth-era-export (8c9ef87) with main (da95e57)}

Summary

❌ 1 regressions
✅ 76 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
❌	hash builder[init size 10000 | update size 100 | num updates 1]	9.1 ms	10.2 ms	-10.84%

[yorickdowne]

@mattsse I see some era1 in the code, I didn’t see era. I might just be missing it, or this is intended to be era1. To be cautious and mention it here:

• Era1 files are pre-merge
• Era files are post-merge
• They have a different format
• With full 4444 coming, era export (post merge) will be a thing. This will use two file repositories for chains with pre-merge history, era1 and era. And one repository for chains that were merged at genesis, just era.

[lean-apple]

@mattsse I see some era1 in the code, I didn’t see era. I might just be missing it, or this is intended to be era1. To be cautious and mention it here:

• Era1 files are pre-merge
• Era files are post-merge
• They have a different format
• With full 4444 coming, era export (post merge) will be a thing. This will use two file repositories for chains with pre-merge history, era1 and era. And one repository for chains that were merged at genesis, just era.

Hello @yorickdowne :)

Will let @mattsse complete but from what I understood :

This pr is addressing this feature #15495 that is part of this more global tracking issue #13186 only covering pre-merge history.

Until now only .era1 (and more globally .e2s file) is covered, as you can see https://github.com/paradigmxyz/reth/blob/main/crates/era/src/era1_file.rs, but I guess in a second time, another tracking-issue will cover post merge (@mattsse ?).

I guess also we use era as an shorthand when referring to era1 file features, which might be causing some confusion in the naming.

[lean-apple]

Sorry wont have time to continue.