Account for zero bloom
Description Erigon send receipt's bloom as zero bloom. Bloom can be regenerated locally and we do that, but if the bloom is null, not zero. This causes erigon to get disconnected during old receipts.
Steps to Reproduce Full sync, monitor the peer allocation graph, wait for old receipts.
Actual behavior Erigon got disconnected.
Expected behavior Erigon do not get disconnected.
Screenshots I'm out right now.
Desktop (please complete the following information): Please provide the following information regarding your setup:
- Operating System: Any
- Version: Who knows.
- Installation Method: Whatever ways you use.
- Consensus Client: I sure hope all.
Additional context
- Quite an old isse.
Logs
- No log appear.
Will be resolved in eth69 as Bloom gets dropped? https://eips.ethereum.org/EIPS/eip-7642
It does, yes.
I want to take this one, or should I go straight to it with a PR before assignment?