This repo hosts a one-click-deploy Cloudflare worker that proxies RPC requests to Helius. The proxy will allow you to keep your API key hidden from public requests made by clients. You will need both a Helius account and a Cloudflare account to deploy this. Helius offers 100k credits for free each month, and Cloudflare workers can execute 100k invocations each day for free. Most projects can easily get started within these free tiers.
Both standard JSON RPC and Websockets are supported!
Press the button below to deploy this to your own Cloudflare account:
Navigate to your newly deployed worker, and click "Settings" and then "Variables":
Add a new variable with the key name HELIUS_API_KEY and your Helius API key as the value:
NOTE: We recommend selecting "Encrypt". This will hide your key from the UI and API responses, and redact them from logs.
Refresh the page and confirm that your key is now saved and encrypted:
You can now use your worker URL as an the RPC endpoint in all SDK and client side configurations without your API key leaking!
This implementation is intentionally left in a less-than-ideal security state to facilitate easy deployment by anyone. If you would like to lock down your RPC proxy further, consider the following steps after you have successfully deployed the worker:
- Update the
Access-Control-Allow-Originheader by adding a new variable with the key nameCORS_ALLOW_ORIGINto contain the host that your requests are coming from (usually your client application). For example, if you wanted to allow requests fromhttps://example.com, you would change the header tohttps://example.com. - Cloudflare Web Application Firewall (WAF) - You can configure the WAF to inspect requests and allow/deny based on your own business logic.
- Modify the IP address allow list in Helius for your API key to only accept connections from the Cloudflare ranges (https://cloudflare.com/ips-v4).