-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add support for REST api proxy #9
Comments
should we get the seed nodes from here too? and to confirm, this is supposed to be a forward proxy as well, correct? |
We can start with these nodes under rest: Yes for forward proxy as well. Btw for RPC, is it possible to remove this node from the list (https://akash-rpc.publicnode.com/)? It returns an html page at the root instead of the available endpoints. I also got error 403, 404 and 502 from the rpc proxy. |
i added an error-rate health thing in #12, which should take care of it if it is really invalid, it should prob be removed from the list in https://raw.githubusercontent.com/cosmos/chain-registry/master/akash/chain.json - not sure if that's desirable or not, though |
see #13 |
Just like the rpc proxy, we would need to also have a proxy for REST apis. It would be great to have the swagger documentation of the API with the available endpoints.
A live example of this is the cosmos directory:
https://cosmos.directory/akash
https://rpc.cosmos.directory/akash
https://rest.cosmos.directory/akash
Example REST api swagger documentation (it doesn't have all the custom endpoints for Akash, but it would be amazing to have them):
https://akash-api.polkachu.com/swagger/#
The text was updated successfully, but these errors were encountered: