Compatibility Layer Expansion #6
Description
One of the goals at the moment is to make the CL easy to use for devs, to drive adoption of verifiable RPC. The most practical way is to let them deploy it themselves and configure their own RPC endpoints as they wish. You can see it as an verifiable RPC proxy.
It should be:
- Easy to deploy: Docker, ideally a Railway template for 1-click deployments.
- Easy to configure: straight forward way to have them tweak the proxy settings + add their RPC endpoints
- Batteries included: observability stack i.e. resource usage, requests per second, accuracy, etc.
This will allow our software to be adopted more easily because people won't have to give us their paid RPC endpoints (trust factor) and they can scale it as they wish.