You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in History Bridge, we are switching to a fallback provider if the request to the EL node fails.
However, there are cases where the requests don't fail but the EL node is out of sync and doesn't update the latest block number.
This prevents us from pushing the latest headers into the network.
To prevent such issues, we want to switch to a fallback provider if we are unable to follow the chain and if we keep getting the same latest block from the EL node.
The text was updated successfully, but these errors were encountered:
Currently, in History Bridge, we are switching to a fallback provider if the request to the EL node fails.
However, there are cases where the requests don't fail but the EL node is out of sync and doesn't update the latest block number.
This prevents us from pushing the latest headers into the network.
To prevent such issues, we want to switch to a fallback provider if we are unable to follow the chain and if we keep getting the same latest block from the EL node.
The text was updated successfully, but these errors were encountered: