-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix decimals in corner cases and use round up #13287
Merged
Merged
Conversation
This file contains 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
RyanRHall
previously approved these changes
May 23, 2024
@@ -44,8 +44,8 @@ abstract contract AutomationRegistryBase2_3 is ConfirmedOwner { | |||
// Next block of constants are only used in maxPayment estimation during checkUpkeep simulation | |||
// These values are calibrated using hardhat tests which simulate various cases and verify that | |||
// the variables result in accurate estimation | |||
uint256 internal constant REGISTRY_CONDITIONAL_OVERHEAD = 97_700; // Fixed gas overhead for conditional upkeeps | |||
uint256 internal constant REGISTRY_LOG_OVERHEAD = 122_000; // Fixed gas overhead for log upkeeps | |||
uint256 internal constant REGISTRY_CONDITIONAL_OVERHEAD = 97_700 + 500; // Fixed gas overhead for conditional upkeeps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we just increase the values here?
RyanRHall
approved these changes
May 28, 2024
FelixFan1992
approved these changes
May 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 28, 2024
Quality Gate passedIssues Measures |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is to improve 2 things on payment:
Here is a good example of Rounding Errors, text search "Rounding Errors" in the article.
Went through the code paths again. decimal scaling is only in transmit path: more specifically they are in calculatePayment and handlePayment. handlePayment is to handle the 2 special cases which we missed before.