new patch release: Erigon v3.0.2 , "Otterly Odissey" 🚨 @gnosischain users 🚨: this is a required update for the upcoming Pectra hardfork scheduled for 30 April 2025 RPC fixes: - Previous versions of Erigon 3 have two bugs regarding handling of state sync events on Polygon chains: Incorrect logIndex on all state sync transaction logs Missing log events when using eth_getLogs with filters A proper fix has been implemented and will be progressively rolled out in Erigon 3.1 and 3.2 (track issue here). A temporary workaround has been introduced if these issues are critical for your use-case. This requires regenerating receipts for all transactions on the chain. The procedure is as follows: 1. Shutdown Erigon and all rpcdaemon processes 2. Update binaries Erigon release 3. erigon seg rm-state-snapshots --domain=receipt --datadir <your-datadir> 4. integration stage_custom_trace --datadir <your-datadir> --chain <amoy|bor-mainnet> --bor.heimdall <heimdall-url> [For machines with many cores, you can add --exec.workers=<num> to improve performance (default is 7)] 5. Once complete, rm -rf <your-datadir>/chaindata 6. Start Erigon