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
After running a network, I can successfully trace a first block using "debug_traceBlockByNumber" endpoint.
Actual behaviour
"debug_traceBlockByNumber" endpoint of the first block returns the following error:
failed to get trace for transaction 0xfcd9fff0177d0e86727354a93ac01e15b7c682ddfbbcc33a54dcece43f7db268: failed to get trace: batch v2 must start with changeL2Block before Tx (suspect a V1 Batch or a ForcedBatch?))
=== RUN Test_DebugFirstBatch
debug_1batch_test.go:31: {
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32000,
"message": "failed to get trace for transaction 0xfcd9fff0177d0e86727354a93ac01e15b7c682ddfbbcc33a54dcece43f7db268: failed to get trace: batch v2 must start with changeL2Block before Tx (suspect a V1 Batch or a ForcedBatch?))"
}
}
--- PASS: Test_DebugFirstBatch (0.02s)
PASS
The text was updated successfully, but these errors were encountered:
This happens because networks starting with a forkID from Etrog will have their first block containing a particular transaction called Injected TX.
This Injected TX requires a different way to be executed.
I've adapted the code to process this particular transaction when tracing it In this commit 9769672
System information
zkEVM Node version:
v0.0.X-RCXX
OS & Version:
OSX
Commit hash : 567d1df
Network:
Mainnet/Testnet
Expected behaviour
After running a network, I can successfully trace a first block using "debug_traceBlockByNumber" endpoint.
Actual behaviour
"debug_traceBlockByNumber" endpoint of the first block returns the following error:
Steps to reproduce the behaviour
Backtrace
The text was updated successfully, but these errors were encountered: