fix: DexPaprika entry claims no rate limits and ~1s updates; both are wrong - #334
Open
donbagger wants to merge 1 commit into
Open
fix: DexPaprika entry claims no rate limits and ~1s updates; both are wrong#334donbagger wants to merge 1 commit into
donbagger wants to merge 1 commit into
Conversation
…counts) The free tier is metered at 200K requests/month per IP and 30/min, so 'no rate limits' is wrong. Price updates are swap-driven rather than ~1 second: a 60s sample of WETH on Ethereum produced 8 frames with gaps up to 14s. Coverage figures updated from 34 chains / 30M+ pools / 27M+ tokens to the published 36 / 36M+ / 33M+.
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
1 participant
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.
One line. I work on DexPaprika and this entry is from my own PR #232, so I am correcting my own claims rather than reporting someone else's.
Three things in it are wrong now.
"no rate limits" is not true and should never have been written. The free tier is metered. Our published limits:
Source: https://docs.dexpaprika.com/knowledge-base/rate-limits. Exceeding the per-minute rate returns HTTP 429. To be straight with you: a 40 request burst from one IP still returns 200 for me today because enforcement is being phased in, so I am not going to claim I reproduced a 429. The point is that the documented product has limits and this line promises none, which is exactly the sort of thing someone builds against and then gets burned by.
"~1 second price updates" is misleading. Updates are swap-driven, not on a fixed interval: a token emits a frame when someone trades it. I sampled WETH on Ethereum, about as busy as an ERC-20 gets, for 60 seconds:
Median gap is around 10 seconds on a top-liquidity pair, and a quiet token on a quiet chain can go minutes with nothing. "Swap-driven" is the honest description on a list that exists for streaming data.
The coverage numbers are a release behind. 34 chains, 30M+ pools and 27M+ tokens are old:
I have used 36 chains, 36M+ pools and 33M+ tokens rather than the exact live values, deliberately: rounded-down figures do not need re-editing every time the index grows.
Entry stays in its current section and position. Nothing else in the file changes.
Written with Claude Code (anthropic/claude-opus-5). Every command above was run and its output pasted unedited.