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
Some operation in AMB Live Monitoring tool assumes that the RPC node it requests the bridge info from is able to provide transactions logs from the block 1. But obviously it is not needed for ALM operations in the worst case it makes sense to request information starting for the block where the corresponding contract were deployed at. But even with this improvement some nodes will still fail: for example, the BSC public nodes return the error "exceed maximum block range: 5000".
Consider to optimize the work with historical data in ALM to make it more robust.
The text was updated successfully, but these errors were encountered:
Some operation in AMB Live Monitoring tool assumes that the RPC node it requests the bridge info from is able to provide transactions logs from the block
1
. But obviously it is not needed for ALM operations in the worst case it makes sense to request information starting for the block where the corresponding contract were deployed at. But even with this improvement some nodes will still fail: for example, the BSC public nodes return the error "exceed maximum block range: 5000".Consider to optimize the work with historical data in ALM to make it more robust.
The text was updated successfully, but these errors were encountered: