update block number calculation for query filter - #3443
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
flopez7
approved these changes
Jul 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue tracking
NA
Context behind the change
Change the block number from which the governance logs are fetch to avoid timeouts.
Since the blocktime in polygon is 2s, voting delay is 1 day (86400s) and the duration of proposals is1 day (86400s), we won't need
more than 86400/2+86400/2= 86400 blocks and we rounded it 100k.
How has this been tested?
Run locally
Release plan
NA
Potential risks; What to monitor; Rollback plan
NA