Move.

Post

Share your knowledge.

Tawhid.
Jan 29, 2025
Expert Q&A

How to bypass rate limit on local full node setup?

I've set up a full node locally and I'm sending requests to it, but I run into a 429 rate limit error. I'm trying to fetch object information using the sui_multiGetObjects method, but the server returns an error when I exceed 50 objects. This happens even when running requests on the same machine. Is there a way to get rid of this rate limit, or is it hardcoded in the node setup? Are nodes from the official config supposed to have no rate limits?

  • Move CLI
  • Move
4
3
Share
Comments
.

Answers

3
skywinder.
Jan 29 2025, 17:03

You're working locally (127.0.0.1), and typically, full nodes from official configurations should not have rate limits. It might be worth checking with the maintainers or community for specific configuration tweaks or issues. You might want to check or adjust any rate limiting factors in your local node's setup, if accessible. Otherwise, it would be useful to bring this up on a platform with the developers for a more detailed understanding and assistance.

4
Best Answer
Comments
.
deriss.
Jan 30 2025, 06:41

Make sure your requests per second are within the limits. Use batching or increase delay between requests if necessary. If you are fetching a large number of objects, consider spreading them out over multiple requests.

3
Comments
.
DuAn.
Jan 30 2025, 13:41

The rate limit error occurs because too many objects are being requested at once, exceeding the allowed number, possibly 50. You might try reducing the number of objects you fetch in each request to avoid the 429 error.

1
Comments
.

Do you know the answer?

Please log in and share it.

We use cookies to ensure you get the best experience on our website.
More info