Build RPC proxy

[troian]

Is your feature request related to a problem? Please describe.

cosmos.directory proxy has caps and limitations for usage like Akash console.

Describe the solution you'd like

Build Go tool that:

1. reads list of available RPC servers from chain meta file.

• check each node if it's alive and if the node is not catching up
• check nodes are reporting correct chain-id
• calculate ping time overtime

2. /rpc endpoint receives requests and proxies them to live nodes
3. Live reload of RPC nodes without the need to restart the server
4. implement authentication via JWT.

• authenticated clients get best nodes
• implement caps on unauthenticated clients

Describe alternatives you've considered

n/a

Search

• I did search for other open and closed issues before opening this

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

No response

[thebigbone]

Hello, I am working on this. Just had a few questions:

• For checking if the node is alive and catching up, is there anything more required than a simple ping?
• Where do I get the chain-id for a RPC node?
• For ping overtime, what should be the duration over which I can show the average ping time? And should I add an endpoint for it?
• Can you explain the third point more clearly?

[brewsterdrinkwater]

I believe this issue has been resolved. I will follow up shortly.

It would be great to see what other contributions you can make to the Akash Network project.

[troian]

hi @thebigbone it was done in https://github.com/akash-network/rpc-proxy

[troian]

hi @thebigbone will you be able to implement GRPC part of the proxy?