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

[RPC] zkevm_consolidatedBlockNumber crashes when only batch 0 #712

Closed
tclemos opened this issue Jul 4, 2024 · 0 comments · Fixed by #718
Closed

[RPC] zkevm_consolidatedBlockNumber crashes when only batch 0 #712

tclemos opened this issue Jul 4, 2024 · 0 comments · Fixed by #718
Labels
bug Something isn't working

Comments

@tclemos
Copy link

tclemos commented Jul 4, 2024

System information

Erigon version: any

Premise: All CDK networks are supposed to have Batch 0 and Block 0 generated via genesis, which are assumed to be virtualized and verified.
Even though this scenario will only happen once per network, this is important for integrated tests that depend on empty networks to run tests.

Steps to reproduce:

  • With a brand new CDK network without any new batch or block, just batch and block 0, send the following request:
{
	"jsonrpc":"2.0",
	"method":"zkevm_consolidatedBlockNumber",
	"params":[],
	"id":83
}

expected response:

{
    "jsonrpc": "2.0",
    "id": 83,
    "result": "0x0"
}

actual response

{
    "jsonrpc": "2.0",
    "id": 83,
    "error": {
        "code": -32000,
        "message": "method handler crashed"
    }
}
@tclemos tclemos added the bug Something isn't working label Jul 4, 2024
@V-Staykov V-Staykov linked a pull request Jul 5, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant