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

outbound rate limiter enhancement #2074

Closed
ws4charlie opened this issue Apr 24, 2024 · 0 comments · Fixed by #2110
Closed

outbound rate limiter enhancement #2074

ws4charlie opened this issue Apr 24, 2024 · 0 comments · Fixed by #2110

Comments

@ws4charlie
Copy link
Contributor

Describe the Issue
The current implementation of rate limiter comes with a sliding Window and a total Rate parameters. The gRPC query iterates on chains by a fixed order: BTC, Ethereum and others

Once the total cctxs' value has reached the total Rate of sliding Window, the BTC chain has the priority to take the funds because BTC chain is the 1st chain in list.

Expected Outcome
We should figure out a way to evenly release the funds across the chains when Rate is reached. Evenly releasing funds doesn't mean dividing total Rate by number of chains, it probably mean releasing funds according to cctx's creation height?

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

Successfully merging a pull request may close this issue.

1 participant