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

modexp test causes state root missmatch (fork13) #1484

Open
xavier-romero opened this issue Nov 18, 2024 · 3 comments
Open

modexp test causes state root missmatch (fork13) #1484

xavier-romero opened this issue Nov 18, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@xavier-romero
Copy link

This test vector from @laisolizq causes a state root missmatch:

Run from this test script.

You can easily reproduce it that way:

RPC_URL=http://x.x.x.x:8123
PRIVKEY=0000000000000000000000000000000000000000000000000000000000000000

docker pull xavierromero/devtooling

docker run --name devtooling --rm \
    -e L2_RPC_URL=$RPC_URL \
    -e L2_PRV_KEY=$PRIVKEY \
    xavierromero/devtooling \
    scripted -f /scripted/modexp-laia-issue-3.1.json

@Sharonbc01 Sharonbc01 changed the title modexp test causes state root missmatch modexp test causes state root missmatch (fork13) Nov 18, 2024
@Sharonbc01 Sharonbc01 added the bug Something isn't working label Nov 18, 2024
@Sharonbc01
Copy link

@hexoscott please highlight when this fix in release and in what release for testing.

@Sharonbc01
Copy link

once Gateway FM cut stable/2.61 this fix will go into images targeting fork 13

@hexoscott
Copy link
Collaborator

The latest code for this is now merged including updated unit tests, we haven't cut 2.61 yet but should we close this issue down as zkevm branch is effectively ready to test fork13 from now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants