Developers building with Chain Fusion on the Internet Computer are getting a smoother experience with the latest update to the EVM RPC Canister (v2.7.0) and the evm rpc client library (v0.2.0). The release focuses on simplifying how developers estimate the Cycles required for Ethereum RPC calls, an area that has often been a source of friction.
Previously, estimating Cycles meant manually assembling raw JSON RPC payloads and sending them through a general requestCost endpoint. That approach was known for being complex and prone to errors, especially for developers who were still learning the structure of specific Ethereum RPC calls. The requestCost method is now deprecated.
The update introduces new query endpoints with the naming format *_CyclesCost. Each one mirrors an existing RPC method with the same function signature. For example a developer using eth_getLogs can now call eth_getLogsCyclesCost without building manual JSON and without switching between different request formats. The change aims to make development feel more intuitive and reduce the need to constantly reference technical documentation.
The client library has been refreshed to match these improvements. Version 0.2.0 adds a high level request_cost function that wraps the new cost estimation process and removes the need for low level handling. The update also supports estimating Cycles when multiple RPC providers are involved, which was not possible with the previous method.
For builders working across multiple chains, this generally means cleaner code, fewer mistakes, and clearer control over resource spending. It does not change the fact that Cycles usage varies based on factors like response sizes, provider configuration and network conditions. Developers still need to monitor their consumption and consider the ongoing operational cost of running applications on the Internet Computer.
Reaction from the broader developer community is likely to focus on practical benefits. Simpler interfaces tend to speed up productivity and reduce onboarding friction, especially for teams exploring Chain Fusion features or experimenting with new decentralised applications.
While the update does not alter how much requests cost, it makes it far easier to understand and plan for those costs. For most teams that alone will feel like a meaningful improvement.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
