I also tested modifying the endpoint and it gives no response at all, status 400 but nothing in payload its empty
Just want to know if there is anything I could do other then cope with 30 requests or sneak through with more and more servers and requests
Geeks Chat If the userid is indeed hardcoded in the payload, rotating your attestation IDs won't help because the server is likely tracking that specific ID Have you tried implementing a delay or exponential backoff in your script to stay under that 30-request-per-minute threshold?
Impossible to claim that post whatever im trying to claim during race condition its scattered all around 1000 ms window, i am staggering every 7ms with c code that is more precise then anything in the world, i can sometimes sneak through many requests at peak race condition time when everyone else is racing too, for now thats the only bypass i’ve found but its still very unreliable, and hitting that post with 30 request limit is 50/50 i need it to be stable
If the userid is indeed hardcoded in the payload, rotating your attestation IDs won't help because the server is likely tracking that specific ID Have you tried implementing a delay or exponential backoff in your script to stay under that 30-request-per-minute threshold?
1
Im running into a specific problem that I cannot seem to avoid, i’ve tried almost everything except modifying JWT payload , when sending requests im rate limited over 30 requests in less then a min I cannot send more, what should I do I need to somehow overcome the rate limit, any suggestions I tried rotating attestation and sending from different jwts and attestation ids but didn’t work, it looks like i. JWT PAYLOAD it has userid embedded and I think its catching that and rate limiting based on that any suggestions ?
Hello, does anyone know any Telegram groups where I could find sites or forums about data leaks?
2