In https://github.com/bnb-chain/opbnb/pull/115, I added the ability to handle L1 reorganization to pre-fetching. During testing, I found that if the cache already exists, blockInfo should also be added to blockInfoChan, which avoids oldestBlockParentHash and parentHash being incorrectly set to common.hash.
Rationale
Even if the cache already exists, blockInfo should be stuffed into blockInfoChan to avoid incorrect recording of the parent hash.
In addition, due to the higher reliability requirements for pre-fetching, PreFetchReceipts will continue to loop until successful after returning err.
Example
none
Changes
Notable changes:
Some minor logic changes for GoOrUpdatePreFetchReceipts
Description
In https://github.com/bnb-chain/opbnb/pull/115, I added the ability to handle L1 reorganization to pre-fetching. During testing, I found that if the cache already exists, blockInfo should also be added to blockInfoChan, which avoids oldestBlockParentHash and parentHash being incorrectly set to common.hash.
Rationale
Even if the cache already exists, blockInfo should be stuffed into blockInfoChan to avoid incorrect recording of the parent hash. In addition, due to the higher reliability requirements for pre-fetching, PreFetchReceipts will continue to loop until successful after returning err.
Example
none
Changes
Notable changes: