-
Notifications
You must be signed in to change notification settings - Fork 72
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
Remove MAXIMUM_SPONSOR_WALLET_REQUESTS to avoid throttling request fulfillments #1763
Conversation
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.
See my comment for clarification around the goal of the PR. Looking at the issue title I can see how this may have been unclear. Two other quick points:
- When your PR is ready to review, please mark it as such by clicking "Ready for review"
- See "2" within my comment here for the correct language to link a PR to an issue that the PR is closing.
I kept the |
Closes #1644 |
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.
Nice! Approving with one nit- please feel free to squash & merge afterwards
This PR closes #1644 by removing the
MAXIMUM_SPONSOR_WALLET_REQUESTS
constant. The initial intention of this constant was to prevent a single user from monopolizing the Airnode response bandwidth. However, as discussed in this thread, this measure is not effective, and it may obstruct legitimate usage.