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

failed to debug trace claim tx #3319

Closed

tclemos opened this issue Feb 20, 2024 · 0 comments

Assignees

Labels

bug rpc zkevm-bridge-sync-rpc

Milestone

Contributor

tclemos commented Feb 20, 2024 •

edited

Loading

curl -H "Content-Type: application/json" -X POST --data '{"jsonrpc":"2.0","method":"debug_traceBlockByNumber","params":["0x96ebfe", {"tracer": "callTracer"}],"id":1}' https://zkevm.rpc.url

is returning the following error:

{"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"failed to get trace for transaction 0xc38651ca34e85dea684e52f58ad4ed7f92b82331b10e07f3e6ebe9312bc876e1: failed to get trace: invalid l1_info_tree_smt_proof_value"}}%

tclemos added bug rpc zkevm-bridge-sync-rpc labels

tclemos added this to the v0.5.13 milestone

tclemos self-assigned this

tclemos mentioned this issue

add SkipVerifyL1InfoRoot as true when debug trace needs to provide the l1 info tree data #3321

Merged

tclemos closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment