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

"Corrupted deposits history detected" loop (with besu) #4669

Open
ibhagwan opened this issue Feb 25, 2023 · 1 comment
Open

"Corrupted deposits history detected" loop (with besu) #4669

ibhagwan opened this issue Feb 25, 2023 · 1 comment

Comments

@ibhagwan
Copy link

ibhagwan commented Feb 25, 2023

Describe the bug
Using besu besu/v22.10.3/linux-x86_64/openjdk-java-17 nimbus keeps downloading the Eth1 deposit history and when it's done raise an error Corrupted deposits history detected.

To Reproduce
Steps to reproduce the behavior:

  1. Platform details (OS, architecture): Linux
  2. Branch/commit used:
❯ nimbus_beacon_node --version
Nimbus beacon node v23.2.0-6b9381-stateofus
Copyright (c) 2019-2023 Status Research & Development GmbH

eth2 specification v1.3.0-rc.2-hotfix

Nim Compiler Version 1.6.11 [Linux: amd64]

Synced from a trusted node using --trusted-node-url=https://beaconstate.ethstaker.cc.

Screenshots
image

Additional context
As per the suggestion in #4227, deleted besu's caches folder and restarted both besu and nimbus (multiple times) but the issue persists.

After the corrupted history is detected nimbus restarts the Eth1 sync process but as soon as it reaches the latest block it would fail again with Corrupted deposits history detected.

@kiss81
Copy link

kiss81 commented Jun 29, 2023

Seems I got the exact same issue now. Will try deleting the cache folder of besu as well.

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

No branches or pull requests

2 participants