-
Notifications
You must be signed in to change notification settings - Fork 45
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
panic: "hertzfixBlock enabled at 35682300, but berlinBlock enabled at 31103030" #269
Comments
fixed in latest devel branch |
this is happening to me only on the latest devel release (1.1.10) for versions 1.1.9 and lower erigon starts up normally, only latest version is having issues |
Fixed in this pr: #262. Maybe you can try with this commit. |
when i try to build erigon from the branch, i get the following error : here too, this only happen on latest devel commit |
Transfer to v1.20 |
System information
Erigon version:
./erigon --version
1.1.10OS & Version: Linux
Erigon Command (with flags/config): ./erigon --chain=chapel --db.size.limit=7T --db.pagesize=4kb --torrent.download.rate=20mb --private.api.addr=0.0.0.0:9090
Chain/Network: testnet & mainnet
Expected behaviour
start syncing
Actual behaviour
getting the following error :
[EROR] catch panic err="unsupported fork ordering: hertzfixBlock enabled at 35682300, but berlinBlock enabled at 31103030" stack="[main.go:31 panic.go:884 backend.go:234 node.go:112 main.go:59 command.go:274 app.go:332 app.go:309 main.go:36 proc.go:250 asm_amd64.s:1598]"
im able to sync on version 1.1.9 with the same start up method
The text was updated successfully, but these errors were encountered: