-
Notifications
You must be signed in to change notification settings - Fork 54
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
rm offchain check for token pool rate limits #690
Conversation
I see you updated files related to core. Please run |
ec2dd40
to
d8f51d8
Compare
) (executableMessages []ccip.ObservedMessage) { | ||
inflightAggregateValue, inflightTokenAmounts, err := inflightAggregates(inflight, destTokenPricesUSD, sourceToDestToken) | ||
inflightAggregateValue, _, err := inflightAggregates(inflight, destTokenPricesUSD, sourceToDestToken) |
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.
Probably you can remove computing inflightTokenAmounts entirely from inflightAggregates
fun
@@ -385,11 +305,6 @@ func (r *ExecutionReportingPlugin) buildBatch( | |||
continue | |||
} | |||
|
|||
if !r.isRateLimitEnoughForTokenPool(destTokenPoolRateLimits, msg.TokenAmounts, inflightTokenAmounts, sourceToDestToken) { |
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.
Please remove that function (isRateLimitEnoughForTokenPool
) from the codebase
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.
Looks good, make sure that CI is green ;)
## Motivation Self serve will allow for token pools that do not have all the functions we currently call offchain After this PR we assume it will go through due to the same rate limits being enforced onchain on send
Motivation
Self serve will allow for token pools that do not have all the functions we currently call offchain
After this PR we assume it will go through due to the same rate limits being enforced onchain on send