Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: Optimism support

See original GitHub issue

@cgewecke

Hey, pretty new in web3 space, I am wondering - can the eth-gas-reporter support Optimism?

I am not familiar with eth-gas-reporter internals and thought that maybe you can give me initial guidance on what kind of changes are necessary to make it work and the place where to start looking?

Depending on the work required I may try to implement it.

From an initial naive glance it seems we need:

Separate gasPrice on gasPriceL1, and gasPriceL2.
Separate gasUsed on gasUsedL1, and gasUsedL2.
Calculate the calldata size, and derive cost based on gasPriceL1 and gasUsedL1.
Leave the rest of the cost to be based on gasPriceL2 and gasUsedL2.

About Optimism fees: https://community.optimism.io/docs/developers/l2/new-fees.html#frontmatter-title

Issue Analytics

State:
Created 2 years ago
Reactions:7
Comments:7 (2 by maintainers)

Top GitHub Comments

7reactions

andrewshvvcommented, Jan 24, 2022

First calculation: Screen Shot 2022-01-24 at 6 29 43 AM

4reactions

smartcontractscommented, Jan 21, 2022

FYI, we just updated the Optimism docs to give more information about how to accurately estimate the current L1 data cost for a given transaction: https://community.optimism.io/docs/developers/build/transaction-fees/#estimating-the-l1-data-fee