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

feat: rate limit configuration #119

Open
anxolin opened this issue Nov 22, 2023 · 0 comments
Open

feat: rate limit configuration #119

anxolin opened this issue Nov 22, 2023 · 0 comments

Comments

@anxolin
Copy link
Contributor

anxolin commented Nov 22, 2023

Problem

Programmatic Orders is a decentralise system. Anyone can run watch towers and deploy their orders.

For convenience, we default to index all orders. However, some orders might be tests that yield broken orders, or we will see orders that make a check on every block when, once every 50 blocks is maybe enough.

Suggested solution

Configure the watch tower so it can slow down the checks for "some orders".

Ideally, we should be able to have a default rate limit for all new orders and be able to override it.

We should define a config that would give you the opportunity of reducing the consumption rate.

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

No branches or pull requests

1 participant