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.

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.

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.

Since you’re running locally on 127.0.0.1, you shouldn’t be hitting rate limits—official Sui full node configs typically don’t enforce them on local traffic. If you are experiencing limits, it could be due to: • Custom config overrides in your local node setup • Tooling (like proxies, firewalls, or API wrappers) imposing artificial limits • Heavy local request load triggering safeguards unintentionally

To troubleshoot: • Inspect your node’s config files (fullnode.yaml, etc.) for any rate_limit settings • Restart the node cleanly and monitor logs for any warnings • If possible, test with a fresh config or minimal setup

If the issue persists, raise it with the Sui community or core devs (via Discord, GitHub Issues, or forums). They may point out undocumented defaults or confirm if it’s an unexpected behavior