Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a better way to optimize getTransactionRecipes #12343

Open
JkLondon opened this issue Oct 16, 2024 · 0 comments · May be fixed by #12424
Open

Find a better way to optimize getTransactionRecipes #12343

JkLondon opened this issue Oct 16, 2024 · 0 comments · May be fixed by #12424
Assignees
Labels
erigon3 imp2 Medium importance

Comments

@JkLondon
Copy link
Member

JkLondon commented 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

  1. new route erigon_getTransactionReceipt without that field (would be really fast)
  2. 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
@JkLondon JkLondon changed the title Find a better way to opti Find a better way to optimize getTransactionRecipes Oct 16, 2024
@AskAlexSharov AskAlexSharov added the imp2 Medium importance label Oct 21, 2024
@JkLondon JkLondon linked a pull request Oct 23, 2024 that will close this issue
@JkLondon JkLondon self-assigned this Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
erigon3 imp2 Medium importance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants