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
There was a discussion about eth_getTransactionReceipt in #12271
We have tx level granularity and now we are not storing receipts but generates them. However, there are issue with it: receipt needs CumulativeGasUsed field which obligates us to exec all block to calculate it.
So there are 2 ways of optimization
new route erigon_getTransactionReceipt without that field (would be really fast)
store this field somewhere in db (probably we are storing it now, should figure it out) and then we would also be able to exec only one tx instead of block
The text was updated successfully, but these errors were encountered:
JkLondon
changed the title
Find a better way to opti
Find a better way to optimize getTransactionRecipes
Oct 16, 2024
There was a discussion about eth_getTransactionReceipt in #12271
We have tx level granularity and now we are not storing receipts but generates them. However, there are issue with it: receipt needs CumulativeGasUsed field which obligates us to exec all block to calculate it.
So there are 2 ways of optimization
The text was updated successfully, but these errors were encountered: