{"id":2945,"date":"2025-05-29T10:58:04","date_gmt":"2025-05-29T10:58:04","guid":{"rendered":"https:\/\/drpc.org\/blog\/?p=2945"},"modified":"2025-05-30T08:42:54","modified_gmt":"2025-05-30T08:42:54","slug":"announcing-flat-pricing-simple-transparent-fair","status":"publish","type":"post","link":"https:\/\/drpc.org\/blog\/announcing-flat-pricing-simple-transparent-fair\/","title":{"rendered":"RPC Pricing, Simplified: dRPC Moves to Flat-Rate Method Pricing"},"content":{"rendered":"In Summary<\/h2>\n
At dRPC<\/strong>, our mission is to make RPC infrastructure more accessible, transparent, and developer-friendly. That\u2019s why we\u2019re rolling out a major update to our pricing model that makes it easier than ever to predict and control your RPC costs.<\/p>\n\n- 20 CU per request \u2013 any method, any chain<\/li>\n
- $6 per 1,000,000 requests<\/li>\n
- One price for everything<\/li>\n
- Volume discounts remain in place<\/li>\n<\/ul>\n
What’s Changing?<\/h2>\n
Traditionally, like most RPC providers, dRPC priced different Ethereum JSON-RPC methods based on the computational resources they consumed \u2014 measured in Compute Units (CUs)<\/strong>. While accurate from a backend perspective, this made budgeting unpredictable and complex for dApp teams and infrastructure engineers.<\/p>\nStarting June 2, 2025<\/strong>, that complexity is gone. We\u2019re switching to a flat-rate pricing model<\/strong> where all supported methods cost just 20 CUs each<\/strong> \u2014 no more per-method variability.<\/p>\nWhat Does This Mean for You?<\/h2>\n
This change makes your $6 per 1M requests pricing even more powerful<\/strong>.<\/p>\nHere\u2019s an example of how the new flat rate impacts typical usage:<\/p>\n
\n
\n
\n\n\n| Method<\/th>\n | Requests<\/th>\n | Previous Cost per 1M<\/th>\n | Total Cost Before<\/th>\n | Cost After (Flat Rate)<\/th>\n<\/tr>\n<\/thead>\n |
\n\neth_call<\/code><\/td>\n| 500,000<\/td>\n | $6<\/td>\n | $3.00<\/td>\n | <\/td>\n<\/tr>\n | \neth_getLogs<\/code><\/td>\n| 300,000<\/td>\n | $10<\/td>\n | $3.00<\/td>\n | <\/td>\n<\/tr>\n | \ndebug_traceTransaction<\/code><\/td>\n| 200,000<\/td>\n | $20<\/td>\n | $4.00<\/td>\n | <\/td>\n<\/tr>\n | \nTotal<\/strong><\/td>\n1M<\/strong><\/td>\n| <\/td>\n | $10.00<\/strong><\/td>\n| $6.00<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n That\u2019s a 40% savings<\/strong> on complex workloads like debug_traceTransaction<\/code> and eth_getLogs<\/code>. And for teams running a variety of method types, budgeting becomes as simple as multiplying your total requests by $6 per million.<\/p>\nDetailed Method Comparison: Before vs. After<\/h2>\nTo help you understand the impact across your stack, we\u2019ve compiled a complete table of all supported methods with their previous CU consumption<\/strong> and the new flat 20 CU<\/strong> rate:<\/p>\n\n \n\n\n| Method name<\/th>\n | Share of all requests<\/th>\n | Old price, CU<\/th>\n | New price, CU<\/th>\n | Old price $\/1M req<\/th>\n | New price $\/1M req<\/th>\n<\/tr>\n<\/thead>\n | \n\n| eth_call<\/td>\n | 48.8172%<\/td>\n | 21<\/td>\n | 20<\/td>\n | 6.3<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getBlockByNumber<\/td>\n | 15.4208%<\/td>\n | 24<\/td>\n | 20<\/td>\n | 7.2<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getTransactionByHash<\/td>\n | 9.4442%<\/td>\n | 30<\/td>\n | 20<\/td>\n | 9<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_blockNumber<\/td>\n | 8.9935%<\/td>\n | 10<\/td>\n | 20<\/td>\n | 3<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getLogs<\/td>\n | 4.9119%<\/td>\n | 60<\/td>\n | 20<\/td>\n | 18<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getBalance<\/td>\n | 2.1180%<\/td>\n | 11<\/td>\n | 20<\/td>\n | 3.3<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getBlockByHash<\/td>\n | 1.8855%<\/td>\n | 21<\/td>\n | 20<\/td>\n | 6.3<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getTransactionReceipt<\/td>\n | 1.0312%<\/td>\n | 11<\/td>\n | 20<\/td>\n | 3.3<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getFilterChanges<\/td>\n | 0.9429%<\/td>\n | 20<\/td>\n | 20<\/td>\n | 6<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_estimateGas<\/td>\n | 0.6325%<\/td>\n | 60<\/td>\n | 20<\/td>\n | 18<\/td>\n | 6<\/td>\n<\/tr>\n | \n| getTokenAccountsByOwner<\/td>\n | 0.5682%<\/td>\n | 15<\/td>\n | 20<\/td>\n | 4.5<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_gasPrice<\/td>\n | 0.4271%<\/td>\n | 15<\/td>\n | 20<\/td>\n | 4.5<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getTransactionCount<\/td>\n | 0.4260%<\/td>\n | 11<\/td>\n | 20<\/td>\n | 3.3<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getCode<\/td>\n | 0.4150%<\/td>\n | 24<\/td>\n | 20<\/td>\n | 7.2<\/td>\n | 6<\/td>\n<\/tr>\n | \n| eth_getStorageAt<\/td>\n | 0.3892%<\/td>\n | 14<\/td>\n | 20<\/td>\n | 4.2<\/td>\n | 6<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\nWhy Flat-Rate Pricing Still Works for Power Users<\/h2>\nYes, some simple methods like eth_blockNumber<\/code> or web3_clientVersion<\/code> 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<\/strong>, the actual dollar impact is minimal \u2014 and still highly competitive with other leading RPC providers like QuickNode, Ankr, Alchemy, and Chainstack.<\/p>\nPlus, our research into user behavior and request breakdowns shows this update benefits the vast majority of our users<\/strong>, especially those building wallets, explorers, dashboards, and DeFi protocols that rely on a mix of standard and complex methods.<\/p>\n | | | | | | | |