In Summary
At dRPC, our mission is to make RPC infrastructure more accessible, transparent, and developer-friendly. That’s why we’re rolling out a major update to our pricing model that makes it easier than ever to predict and control your RPC costs.
- 20 CU per request – any method, any chain
- $6 per 1,000,000 requests
- One price for everything
- Volume discounts remain in place
What’s Changing?
Traditionally, like most RPC providers, dRPC priced different Ethereum JSON-RPC methods based on the computational resources they consumed — measured in Compute Units (CUs). While accurate from a backend perspective, this made budgeting unpredictable and complex for dApp teams and infrastructure engineers.
Starting June 2, 2025, that complexity is gone. We’re switching to a flat-rate pricing model where all supported methods cost just 20 CUs each — no more per-method variability.
What Does This Mean for You?
This change makes your $6 per 1M requests pricing even more powerful.
Here’s an example of how the new flat rate impacts typical usage:
| Method | Requests | Previous Cost per 1M | Total Cost Before | Cost After (Flat Rate) |
|---|---|---|---|---|
eth_call |
500,000 | $6 | $3.00 | |
eth_getLogs |
300,000 | $10 | $3.00 | |
debug_traceTransaction |
200,000 | $20 | $4.00 | |
| Total | 1M | $10.00 | $6.00 |
That’s a 40% savings on complex workloads like debug_traceTransaction and eth_getLogs. And for teams running a variety of method types, budgeting becomes as simple as multiplying your total requests by $6 per million.
Detailed Method Comparison: Before vs. After
To help you understand the impact across your stack, we’ve compiled a complete table of all supported methods with their previous CU consumption and the new flat 20 CU rate:
| Method name | Share of all requests | Old price, CU | New price, CU | Old price $/1M req | New price $/1M req |
|---|---|---|---|---|---|
| eth_call | 48.8172% | 21 | 20 | 6.3 | 6 |
| eth_getBlockByNumber | 15.4208% | 24 | 20 | 7.2 | 6 |
| eth_getTransactionByHash | 9.4442% | 30 | 20 | 9 | 6 |
| eth_blockNumber | 8.9935% | 10 | 20 | 3 | 6 |
| eth_getLogs | 4.9119% | 60 | 20 | 18 | 6 |
| eth_getBalance | 2.1180% | 11 | 20 | 3.3 | 6 |
| eth_getBlockByHash | 1.8855% | 21 | 20 | 6.3 | 6 |
| eth_getTransactionReceipt | 1.0312% | 11 | 20 | 3.3 | 6 |
| eth_getFilterChanges | 0.9429% | 20 | 20 | 6 | 6 |
| eth_estimateGas | 0.6325% | 60 | 20 | 18 | 6 |
| getTokenAccountsByOwner | 0.5682% | 15 | 20 | 4.5 | 6 |
| eth_gasPrice | 0.4271% | 15 | 20 | 4.5 | 6 |
| eth_getTransactionCount | 0.4260% | 11 | 20 | 3.3 | 6 |
| eth_getCode | 0.4150% | 24 | 20 | 7.2 | 6 |
| eth_getStorageAt | 0.3892% | 14 | 20 | 4.2 | 6 |
Why Flat-Rate Pricing Still Works for Power Users
Yes, some simple methods like eth_blockNumber or web3_clientVersion used to cost fewer CUs than 20. These may technically become slightly “more expensive” in CU terms. But because of our low $6 per million request rate, the actual dollar impact is minimal — and still highly competitive with other leading RPC providers like QuickNode, Ankr, Alchemy, and Chainstack.
Plus, our research into user behavior and request breakdowns shows this update benefits the vast majority of our users, especially those building wallets, explorers, dashboards, and DeFi protocols that rely on a mix of standard and complex methods.
Why We Made This Change
-
Predictability: Devs shouldn’t need a spreadsheet to calculate RPC costs.
-
Transparency: No more surprises based on backend-specific pricing logic.
-
Competitiveness: dRPC continues to deliver top-tier performance at better-than-market rates.
This update is part of our ongoing effort to make RPC infrastructure simple, scalable, and builder-first.
Rollout Timeline
This update will go live on June 2, 2025. If you’re already using dRPC, there’s no action needed on your part — you’ll simply start benefiting from better predictability and potential savings automatically.
📚 Learn More
🧾 Visit our docs for a breakdown of CU consumption and pricing.
💬 Have questions? Reach out to our team on Discord.
Happy building,
The dRPC Team
