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

Validate and protect against register API index delays #585

Closed
Tracked by #574
sideninja opened this issue Sep 25, 2024 · 1 comment
Closed
Tracked by #574

Validate and protect against register API index delays #585

sideninja opened this issue Sep 25, 2024 · 1 comment

Comments

@sideninja
Copy link
Contributor

sideninja commented Sep 25, 2024

There could be a case where the transaction re-execution request is made or a call is made and using the remote register APIs we fail to execute because the AN did not yet index that register. We should make sure such cases can't happen. Right now the EVM GW node is configured to allow querying all the sealed blocks heights. We must make sure that once the block height is sealed the registers will be indexed.
If that is not the case we should guard and differentiate between register not existing and register not being indexed yet.

@j1010001
Copy link
Member

no londer needed, moving to dry-run solution (onflow/flow-go#6539)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants