Cutting tens of thousands per month in excess RPC spend
An infrastructure and code audit for a crypto company that uncovered a bug driving tens of thousands of dollars per month in unnecessary blockchain RPC costs.
SolidityWAGMIReactEVM RPC
The problem
A crypto company's infrastructure bill kept climbing, with blockchain RPC (node) usage as a large and growing line item. The spend was far higher than the product's actual on-chain activity justified, but the root cause wasn't obvious from the dashboards.
Our approach
- Ran an advisory engagement: audited the application's on-chain data-access patterns across the contract and frontend layers.
- Profiled where and how RPC calls were being made, and traced redundant and excessive call patterns back to their source in the code.
- Identified a bug responsible for a large share of the wasted calls, and laid out concrete fixes to call batching, caching, and access patterns.
Outcome
- Pinpointed a bug causing tens of thousands of dollars per month in excess RPC spend.
- A remediation path that cut recurring infrastructure cost without changing product behavior.
- Clear visibility into on-chain access patterns for the client's team going forward.
Have a similar problem?
Tell us what you're building. We'll reply with how we'd approach it.
Start a ProjectAnonymized at the client's request — sector and outcomes are real, identifying details removed.