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

Add RuntimeAPI for Rate Limit Checks #892

Open
camfairchild opened this issue Oct 30, 2024 · 0 comments · May be fixed by #985
Open

Add RuntimeAPI for Rate Limit Checks #892

camfairchild opened this issue Oct 30, 2024 · 0 comments · May be fixed by #985
Assignees

Comments

@camfairchild
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently, submitting weights, registering networks, and staking/unstaking (among others) are rate-limited. It would be useful to be able to check this rate limit via an API without having to send off a transaction and receive an error.

Describe the solution you'd like

Add a Runtime API that returns whether a specific key (if applicable) is within the rate limit for a next extrinsic.

Describe alternatives you've considered

  • The alternative is to pull the rate limit value and the current usage from storage and duplicate the check for the rate limit on the client-side. But this would be difficult if any changes are made on the chain-side later-on and would involve a level of coupling.

Additional context

No response

@ales-otf ales-otf linked a pull request Nov 15, 2024 that will close this issue
13 tasks
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.

2 participants