You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I noticed that for tx 0xd05bf9676006101c15249494d5a1c83a16d3e8751ae589291d64cdd370b36314 the gasUsed field is 261183, but the gas used shown on the Etherscan page is 257657. 261183 is actually the gas limit of the tx and not the gas used by the tx.
Expected behavior (required)
A clear and concise description of what you expected to happen.
The gasUsed field should represent the gas used by a tx and not the gas limit of the tx.
The text was updated successfully, but these errors were encountered:
Yeah so the update changed that field name to be gasLimit instead of gasUsed. And then there's the option to have a receipt field to get the gasUsed. We'd need to add a bit more code to get the gasUsed field to be actual gas used and not gas limit
Describe the bug (required)
A clear and concise description of what the bug is.
I entered the following query at https://thegraph.com/explorer/subgraph/livepeer/livepeer:
and I noticed that for tx 0xd05bf9676006101c15249494d5a1c83a16d3e8751ae589291d64cdd370b36314 the gasUsed field is 261183, but the gas used shown on the Etherscan page is 257657. 261183 is actually the gas limit of the tx and not the gas used by the tx.
Expected behavior (required)
A clear and concise description of what you expected to happen.
The gasUsed field should represent the gas used by a tx and not the gas limit of the tx.
The text was updated successfully, but these errors were encountered: