[#408] Add per-user rate limiting to raffle creation endpoint - #454
Merged
Otaiki1 merged 2 commits intoApr 29, 2026
Conversation
Apply a raffle-create throttle policy that keys limits by authenticated wallet address on raffle POST routes, with env-configurable limits and guard coverage to ensure 429 behavior remains informative.
…le-creation-endpoint
|
@Otaiki1 is attempting to deploy a commit to the otaiki1's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #408
What changed
TikkaThrottlerGuardforPOST /raffles*routes so limits are per-user instead of per-IP.RAFFLE_CREATE_RATE_LIMITandRAFFLE_CREATE_RATE_WINDOW_SECONDS.Validation
npm run buildnpm test -- --runInBand