Closed emizzle closed 3 months ago
We have a list of Endpoints for Testnet and one of them is Geth RPC endpoint, which is publicly available for now
curl -X POST \
-s curl https://rpc.testnet.codex.storage \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}'
And in the Codex Testnet Starter we have and example how to use it with Codex
export CODEX_ETH_PROVIDER=https://rpc.testnet.codex.storage
And some notes about it
If you think we should handle more load, we can spin up several nodes and create s single endpoint with a load balancer and sticky sessions
Geth-01
/
RPC Endpoint --> Load Balancer - Geth-02
\
Geth-03
I think at this point we really have no idea how many people will be attending the workshop. Let's wait to find out more details about this before we make an assumptions on upper limits.
Slava can run one or two additional nodes for one or two days and then drop them.
Slava will run additional nodes behind a load balancer and close this issue.
Based on the experiments we performed during https://github.com/codex-storage/infra-codex/issues/193, it was decided to just increase resources for an existing Geth RPC node, because of the issue with sticky sessions.
We also may consider to test that during #823.
As it was checked during #823, we can use existing PRC node for the workshop.
Will we have a publicly accessible endpoint for geth?
Are there any limitations on this geth instance in terms of connections?
Any NAT issues?