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
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
User f13r reports an incident in Gnosischain Discord after bumping version to 2.1.4
hello, I face several issues after updating my prysm gbc & validators to v 2.1.4:
level=error msg="config name=gnosis conflicts with existing config named=mainnet: configset cannot add config with conflicting fork version schedule" prefix=main
and
level=error msg="Failed to decode hex string." error="encoding/hex: invalid byte: U+000D"
any idea why. I didn't have these issues running v2.1.2
User
f13r
reports an incident in Gnosischain Discord after bumping version to 2.1.4hello, I face several issues after updating my prysm gbc & validators to v 2.1.4:
level=error msg="config name=gnosis conflicts with existing config named=mainnet: configset cannot add config with conflicting fork version schedule" prefix=main
and
level=error msg="Failed to decode hex string." error="encoding/hex: invalid byte: U+000D"
any idea why. I didn't have these issues running v2.1.2
https://discord.com/channels/502416149343109121/920642136272166972/1011265251263664228
The text was updated successfully, but these errors were encountered: