DeFi

March 12, 2024

Polygon zkEVM: New Custom Endpoints for dApps

Recent changes to the network caused users to see estimated gas prices that were much higher than the transaction fee paid. This custom endpoint is the solution.

DeFi

Earlier this year, Polygon zkEVM changed how it calculated transaction fees. While the actual transaction fee paid by users went down for most types of DeFi activity, there was one unintended consequence: The estimated gas price users had to sign was much higher than what they would end up paying. 

If you have a dApp deployed on Polygon zkEVM, this solution is for you. Using this custom endpoint is not obligatory, but strongly recommended.

Relevant Calls 

Standard endpoint

  • eth_estimateGas returns the gas needed to execute the transaction, given the state of the network

New custom endpoints 

  • zkevm_estimateGasPrice returns an almost exact gas price based on the transaction type and calldata being used, given the state of the network.
  • zkevm_estimateFee returns the estimated transaction fee following the estimated gas price, given the state of the network.

How-to for dApps devs

The relevant JSON content and documentation can be found here: 

  1. Copy the JSON content for node v0.5.13: zkevm-node / json / 0.5.13
  2. You can visualize the spec by pasting the code into the playground area of the OpenRPC Playground
  3. The process is the same as requesting eth_estimateGas. You’ll call the new endpoints with the exact same parameters. For additional reference, see the call examples below.
eth_estimateGas
zkevm_estimateGasPrice
zkevm_estimateFee

Given the state of the network and the responses to the above calls, the new custom endpoint returned an estimated fee that was ~20% lower than the standard endpoint. Note: On dApps that continue using the standard endpoint, users are always going to sign the higher price but the actual fee paid will be the same as with the custom endpoint. 

For RPC infra providers: node compatibility

This custom endpoint is available for Node version 0.5.13, which was included in the Etrog upgrade: 

If you’re an infrastructure provider running RPC nodes on Polygon zkEVM, you need to update to the latest release of the node on mainnet for dApps to call zkevm_estimateGasPrice.

Nearly all of the node providers on Polygon zkEVM are already running the latest version. 

Additional Material

A complete list of all JSON RPC endpoints supported on Polygon zkEVM can be found here: 

Tune into the blog and our social channels to keep up with updates about the Polygon ecosystem.

The future of blockchains is aggregated.

Website | Twitter | Forum | Telegram | Discord | Instagram | LinkedIn | Polygon Knowledge Layer

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

April 23, 2026

DeFi
Polygon CDK

Agglayer Processed $200M Post-Hack With Zero Incidents. ZK Proofs Are Why.

April 21, 2026

Payments
Open Money Stack

Non-USD Stablecoins: What Enterprise Payment Teams Should Know About Local Currency Settlement

April 15, 2026

Open Money Stack
Polygon CDK
Institutional

Custom-Built Blockchains for Institutions: Where Financial-Grade Privacy Meets Global Crypto Liquidity

April 15, 2026

Institutional

The GENIUS Act, Explained: What Enterprise Payment Teams Need to Know

April 14, 2026

Polygon Chain
DeFi

We’re Launching sPOL to Bring Better Rewards to Polygon Stakers

April 10, 2026

Open Money Stack
Payments

What 2026 Signals for the Future of Cross-Border Finance

April 8, 2026

Polygon CDK
Institutional
Open Money Stack

Why Apex Group Committed to $100B in Tokenized Assets on a Blockchain Built with Polygon CDK

April 8, 2026

Polygon Chain
Open Money Stack

Giugliano Upgrade: Faster Confirmations, Predictable Fees, and a More Resilient Network for Polygon Chain

April 6, 2026

Institutional
Payments

What Is a Stablecoin Sandwich?

April 3, 2026

Open Money Stack
Case Studies
Payments

Case Study: How Rise is paying global teams faster and cheaper with Polygon

Next
PREV
More Blogs