Summary
At the first stage we will test our solution on NEAR Testnet to see by how much RPC speed is improved. It is not possible to test without at least 50% of validator seats/stake sign up to our service on Testnet.
Details
Aurora+Pagoda validators will be sufficient for Testnet.
Additional Information
In regards to chnages required for testing. In a nutshell - we have 2 binaries(written in go) that act as a web service that allow validators to communicate with central cache storage(read/write). For the best performance it would be preferable if you could deploy them besides validator nodes. The means of deployment is whatever best suits you. We can provide docker-compose. Or they can be build directly.
The second requirement would be to add extra configuration to near config.json
Summary At the first stage we will test our solution on NEAR Testnet to see by how much RPC speed is improved. It is not possible to test without at least 50% of validator seats/stake sign up to our service on Testnet.
Details
Aurora+Pagoda validators will be sufficient for Testnet.
Additional Information
In regards to chnages required for testing. In a nutshell - we have 2 binaries(written in go) that act as a web service that allow validators to communicate with central cache storage(read/write). For the best performance it would be preferable if you could deploy them besides validator nodes. The means of deployment is whatever best suits you. We can provide docker-compose. Or they can be build directly. The second requirement would be to add extra configuration to near config.json
Specifically:
"chunk_distribution_network": { "enabled": true, "uris": { "get": "http://host:1324/get", "set": "http://host:1323/process?token=[token]” } }
token will be provided by us for each validator instance. I can provide all additional details directly. Repositories: https://github.com/aurora-is-near/caching-proxies-cache https://github.com/aurora-is-near/caching-proxies-terminal