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

no forkID received #47

Open
gr8h opened this issue Jan 5, 2024 · 8 comments · May be fixed by #59
Open

no forkID received #47

gr8h opened this issue Jan 5, 2024 · 8 comments · May be fixed by #59

Comments

@gr8h
Copy link

gr8h commented Jan 5, 2024

After running make build-docker containers zkevm-sync, zkevm-sequencer, .... are logging error getting forkIDs. Error: error: no forkID received. It should receive at least one, please check the configuration.... Is there a miss configs? I used the default file test.node.config.toml.

@HudsonGraeme
Copy link

I also run into this error both on WSL and real Ubuntu 22.04

@Jasun0925
Copy link

I also encountered this issue on AWS Linux
image

@Jasun0925
Copy link

@gr8h @HudsonGraeme Have you solved this problem? I also encountered it

@HudsonGraeme
Copy link

@gr8h @HudsonGraeme Have you solved this problem? I also encountered it

Yes, I was able to resolve it by downgrading to cdk-validium-node:v0.0.2

@gr8h
Copy link
Author

gr8h commented Jan 11, 2024

Same here

@UrsaMajor-t
Copy link

UrsaMajor-t commented Jan 13, 2024

Hello, under cdk-validium-node:v0.0.2, what version of zkevm-prover do you use? Can proof be generated normally? @HudsonGraeme @gr8h

@gr8h @HudsonGraeme Have you solved this problem? I also encountered it

Yes, I was able to resolve it by downgrading to cdk-validium-node:v0.0.2

@Jasun0925
Copy link

Jasun0925 commented Jan 15, 2024

@UrsaMajor-t I have given up my resistance and am using rollup now. This github warehouse is updating slowly and there are still many unresolved issues

@bap2pecs
Copy link

make sure you set genesisBlockNumber correct in genesis.config.json

@toanalien toanalien linked a pull request Jan 25, 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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants