Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALM does not work with BSC public nodes #529

Closed
akolotov opened this issue Mar 9, 2021 · 0 comments · Fixed by #542
Closed

ALM does not work with BSC public nodes #529

akolotov opened this issue Mar 9, 2021 · 0 comments · Fixed by #542
Labels
ALM bug Something isn't working

Comments

@akolotov
Copy link
Collaborator

akolotov commented Mar 9, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ALM bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant