Adds sanity-check on checkL1InfoTreeUpdate to check that blockhash of the L1 block where l1InfoRootIndex was synced matches ethereum blockhash. If it doesn't match it means that probably a L1 reorg happened and the Synchornizer has not detected it. Therefore the data stored in the exit_root table for this l1InfoRootIndex is not valid and this index cannot be used in the new L2 blocks.
What does this PR do?
Adds sanity-check on checkL1InfoTreeUpdate to check that blockhash of the L1 block where l1InfoRootIndex was synced matches ethereum blockhash. If it doesn't match it means that probably a L1 reorg happened and the Synchornizer has not detected it. Therefore the data stored in the exit_root table for this l1InfoRootIndex is not valid and this index cannot be used in the new L2 blocks.
Reviewers
Main reviewers:
@ToniRamirezM @joanestebanr