Reduce RPC requests and DB changes by Staking DApp #3583
Merged
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.
Motivation
Staking DApp requests information about pools and delegators (and rewrites the corresponding DB tables) on every block even when there are no changes in StakingAuRa and ValidatorSetAuRa contracts. This PR makes DApp only do that when some changes occurred. For that purpose, it uses the
lastChangeBlock
field from the contracts introduced in poanetwork/posdao-contracts@ef9ccffAlso, this PR comments out the warning added in #3576 (but doesn't remove it completely).
Checklist for your Pull Request (PR)
CHANGELOG.md
with this PRmaster
in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.