Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace akashnet.net rpc with proxy #263

Open
baktun14 opened this issue Jul 9, 2024 · 2 comments
Open

Replace akashnet.net rpc with proxy #263

baktun14 opened this issue Jul 9, 2024 · 2 comments
Labels
enhancement New feature or request P1 priority 1 feature/ enhancement

Comments

@baktun14
Copy link
Collaborator

baktun14 commented Jul 9, 2024

We're depedent on this node to run 100% of the time for the api and other places in the code. We need to replace it with the new RPC proxy that will be built,

@nick134-bit
Copy link

Hey @troian and @baktun14 ,

Public endpoints tend to enforce rate limits per IP address. As far as I know, using a proxy server would result in all users sharing the same rate limits if no caching is in place. Due to this, I recently created a REST API endpoint for another frontend that checks the health of public RPCs/RESTs and provides an updated list. Putting the RPC selection on the client side would ensure availability even if usage of the endpoints increases significantly.

You can check it out here: https://9c0pbpbijhepr6ijm4lk85uiuc.ingress.europlots.com/api/rpcs/akash

@baktun14
Copy link
Collaborator Author

Hey, we currently have client side rpc selection. This is mostly for our api that relies on the akashnet.net rpc and we need a proxy for reliability. Thanks for the list of rpcs.

@anilmurty anilmurty added enhancement New feature or request P1 priority 1 feature/ enhancement labels Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P1 priority 1 feature/ enhancement
Projects
Status: Up Next (prioritized)
Development

No branches or pull requests

3 participants