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
goerli after cancun upgrade: prysm 4.2.1 and geth 1.13.11 don't work together anymore #13562
Comments
Same issue on Holesky |
I see that you have your |
Hey this should be resolved with this: https://github.com/prysmaticlabs/prysm/releases/tag/v4.2.2-rc.0 If this goes well, it will be our next release. |
I was setting 512 for |
Indeed, removing the |
Will it be an issue for mainnet as well? My mainnet beacons are set |
I will prioritize getting this in: along with a follow-up PR to cap the batch limit. After Deneb the network batch limit is fixed at 128, which is why it has been triggered for your setups. |
Describe the bug
We missed the Upgrade on January 17th and didn't upgrade our clients in time.
So we wanted to start from scratch, upgraded prysm to
4.2.1
and geth to1.13.11
and removed each others databases.Both prysm and geth only do log errors and not sync anything at all.
Has this worked before in a previous version?
worked until january 17th 2024 with prysm
4.1.1
and geth1.13.5
🔬 Minimal Reproduction
prysm systemd service file
geth systemd service file
Error
prysm errors
geth errors
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
Prysm/v4.2.1/59b310a2216c57fcf67ea0fdec739dad07aeec8b.
Anything else relevant (validator index / public key)?
No validator.
The text was updated successfully, but these errors were encountered: