Hacker News Reader

> Being able to set up access rules for the service and having user set limits would also be very helpful.

The documentation is pretty clear on that: https://developers.cloudflare.com/web3/how-to/restrict-gatew...

Thank you this is actually something that appears to solve one of my main issues. I did not see this before, and it's not linked to from their dashboard UI or the ethereum gateway docs [1]. It appears that I could make the DNS record go through another cloudflare product Cloudflare Zero Trust[2] which can do the access management.

While this is good to know, I still would much like visibility into public usage and user set billing limit caps. A large portion of use cases for an ethereum gateway is going to be frontend client side calls, and yes I know I could make another proxy layer on my own servers and set limits there, which if I could do things over I would have.

1. https://developers.cloudflare.com/web3/ethereum-gateway/ 2. https://developers.cloudflare.com/cloudflare-one/

It’s pretty terrible that they even allow public access to these gateways, let alone default to it. At a very bare minimum some sort of origin header checks should be done. Who in their right mind would want to pay an exorbitant rate to put a frontend-specific JSON-RPC API out on the public internet to be abused for free by other sites?

Reply on news.ycombinator.com