Willian Mitsuda

Regarding comparing converted holesky vs. generated holesky (only snapshots dir), it seems now everything matches, except: - `v1-receipt.*` -> probably due to concerns I mentioned in the previous comment -...

Given the overall results on holesky now seems satisfactory, now triggering a regeneration run on mainnet, should be done in < 1 week

Status: mainnet sync from scratch still running after 1 week, at block 17.9M. note: mainnet sync performance noticeably drops after block 16M, going from +700Mgas/s -> 400-500Mgas/s.

Status: mainnet sync from scratch done after 11 days, now proceeding to check data integrity. FYI: a few hours after reaching the tip I got: https://github.com/erigontech/erigon/issues/13676 , but I think...

data seems good, diffs are similar to what I found on holesky. I have another node that is not converted, but new data is being generated in the new format,...

given our previous conversation about leaving this one post-E3 final, I'll keep merging main and running multiple rounds of sync from scratch on mainnet from now on in order to...

Status: - last mainnet sync test resulted in .ef data being semantically correct compared to plain E3. - however the data generated by this PR also differs in some other...

Results: (2) vs (3) ``` diff -r -x '*.torrent' -x 'preverified.toml' -x '*.seg' -x '*.idx' erigon3-mainnet-regen/snapshots/ erigon3-mainnet-experimental/snapshots/ > experimental-vs-regen.txt ``` the attached diff shows the result is what we expected,...

Results: (1) vs (3) ``` diff -r -x '*.torrent' -x 'preverified.toml' -x '*.seg' -x '*.idx' erigon3-mainnet-regen/snapshots/ erigon3-mainnet/snapshots/ > original-vs-regen.txt ``` noticed how many data files seems different, like regenerated .ef...

I'm taking this PR out of draft state in order to trigger the CI pipeline and because after the latest round of tests on mainnet I'm now confident about it's...