SeaMonkey82
SeaMonkey82
I can't say for certain, but as checkpoint sync has been failing to do much besides refresh DNS records and receive new payloads from an already-synced CL, I *think* this...
[mainnet-besu-v22.7.0-stopped_importing_blocks.log](https://github.com/hyperledger/besu/files/9275781/mainnet-besu-v22.7.0-stopped_importing_blocks.log)
> I believe you must provide a genesis state for a network that isn't mainnet. If that's true, then it must only apply on the initial run, as I removed...
> @SeaMonkey82 @mandrigin the erigon (rosten, unpruned, commit [329d586](https://github.com/ledgerwatch/erigon/commit/329d586464334fce05a4613055c30077b4630c78)) response to the provided `eth_getLogs` request is semantically identical to infura's one (and infura uses `geth` client according to [FAQ](https://infura.io/faq/general)) [erigon_329d586.txt](https://github.com/ledgerwatch/erigon/files/9109485/erigon_329d586.txt)...
> @SeaMonkey82 if you get infura.txt, and your json and use something like http://jsondiff.com, it shows no differences whatsoever. So maybe its another request that fails or something? In my...
For what it's worth, I'm not seeing this error on goerli-prysm-besu pre-merge.
Came back to this issue because I'm seeing the same thing in goerli-prysm-erigon now. ``` [2022-09-26 21:28:21] ERROR powchain: Could not process deposit log: received incorrect merkle index: wanted 181465...
The fix for missing deposit logs seems to be running the CL client in checkpoint sync mode. This worked for me both with prysm-erigon and teku-erigon on Goerli.
Some initial thoughts based on testing done so far: > # Merge test cases > ## Initial Syncing (beacon_blocks_by_range) > > * [ ] BN(fresh) EE(fresh) can sync to head...