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

Consider moving main logic of rate limiter into ZetaClient #2092

Closed
Tracked by #2056
lumtis opened this issue Apr 29, 2024 · 0 comments · Fixed by #2110
Closed
Tracked by #2056

Consider moving main logic of rate limiter into ZetaClient #2092

lumtis opened this issue Apr 29, 2024 · 0 comments · Fixed by #2110
Labels
m:crosschain zetaclient Issues related to ZetaClient

Comments

@lumtis
Copy link
Member

lumtis commented Apr 29, 2024

Describe the Issue
Would depend on #2082
-> Once we have broken down the query into pure methods, moving the rate limiter logic will be trivial

This task is about moving the main logic of the rate limiter (algorithm for CCTX filtering) into the ZetaClient so eventual upgrade/bug of the functionality would be easier to ship/patch

Two tasks:

  • Implement the right query for the crosschain module for the ZetaClient to query CCTXs with performance
  • Move the filtering logic to ZetaClient
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
m:crosschain zetaclient Issues related to ZetaClient
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant