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.

Sign up for GitHub

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

Jump to bottom

investigation: research about eth_simulateV1 and how to incorporate it in our RPC #1060

Open
Eikix opened this issue May 6, 2024 · 1 comment
Open

investigation: research about eth_simulateV1 and how to incorporate it in our RPC #1060

Eikix opened this issue May 6, 2024 · 1 comment
Labels
enhancement Enhancement of the code, not introducing new features. timebox-1day Exploratory issue: Do not spend more than a day on it to assess doability.

Comments

@Eikix
Copy link
Member

Eikix commented May 6, 2024

Describe the enhancement request

Ethereum foundation, championed by Nethermind / Geth is looking to add a simulate tx route in the RPC spec of Ethereum

ethereum/execution-apis#484

Describe Preferred Solution

Task: Try to understand if in its current form, we can incorporate the proposal in Kakarot

If yes: Should we do it using Reth (like tracing/debug API)? Or using Kakarot zkEVM?
@Eikix Eikix added enhancement Enhancement of the code, not introducing new features. timebox-1day Exploratory issue: Do not spend more than a day on it to assess doability. labels May 6, 2024
@github-project-automation github-project-automation bot moved this to 🆕 Backlog in Kakarot on Starknet May 6, 2024
anukkrit149 pushed a commit to karnotxyz/kakarot-rpc that referenced this issue Aug 9, 2024
@Eikix
fix dockerfile python version (kkrt-labs#1060)
56c201c 
<!--- Please provide a general summary of your changes in the title
above -->

<!-- Give an estimate of the time you spent on this PR in terms of work
days.
Did you spend 0.5 days on this PR or rather 2 days?  -->

Time spent on this PR:

## Pull request type

<!-- Please try to limit your pull request to one type,
submit multiple pull requests if needed. -->

Please check the type of change your PR introduces:

- [x] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [ ] Other (please describe):

## What is the current behavior?

<!-- Please describe the current behavior that you are modifying,
or link to a relevant issue. -->

Resolves #<Issue number>

## What is the new behavior?

<!-- Please describe the behavior or changes that are being added by
this PR. -->

-
-
-

<!-- Reviewable:start -->
- - -
This change is [<img src="https://reviewable.io/review_button.svg"
height="34" align="absmiddle"
alt="Reviewable"/>](https://reviewable.io/reviews/kkrt-labs/kakarot/1060)
<!-- Reviewable:end -->
@Eikix
Copy link
Member Author

Eikix commented Oct 2, 2024

This is not prio, but more and more clients are starting to incorporate this route.
It is essentially hard to do using Kakarot state since it has state overrides, we could reuse Reths' stack for it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Enhancement of the code, not introducing new features. timebox-1day Exploratory issue: Do not spend more than a day on it to assess doability.
Projects
No open projects
Kakarot on Starknet
Status: 🆕 Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Eikix