You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Fix] rate limiting not applied to GET /vaults and GET /positions Vercel handlers #176
checkRateLimit is only applied in the four /tx/ Vercel handlers (deposit, withdraw, add-trustline, submit). The GET /api/v1/vaults and GET /api/v1/positions/:publicKey handlers have no rate limiting, even though they trigger DeFiLlama HTTP fetches and Stellar RPC calls respectively. A scraper or accidental polling loop could exhaust upstream rate limits.
The Fastify layer has a global @fastify/rate-limit that covers all routes; the Vercel layer does not.
Fix
Add if (!checkRateLimit(req, res)) return; at the top of the vaults and positions Vercel handlers, consistent with the tx handlers.
changed the title [-]fix: rate limiting not applied to GET /vaults and GET /positions Vercel handlers[/-][+][Fix] rate limiting not applied to GET /vaults and GET /positions Vercel handlers[/+]on Jun 21, 2026
Activity
[-]fix: rate limiting not applied to GET /vaults and GET /positions Vercel handlers[/-][+][Fix] rate limiting not applied to GET /vaults and GET /positions Vercel handlers[/+]