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

Failing to setup the beacon-kit and reth #2360

Open
maheshtechpartner opened this issue Jan 17, 2025 · 2 comments
Open

Failing to setup the beacon-kit and reth #2360

maheshtechpartner opened this issue Jan 17, 2025 · 2 comments

Comments

@maheshtechpartner
Copy link

maheshtechpartner commented Jan 17, 2025

Hello,

I have setup the beacon-kit and reth.

Beacond version: v0.7.0

Reth version: 1.0.3

When I start the beacon service, I get the log 'execution client is not running.' When I start the execution client (Reth), I get an error on the beacon service, as shown below:

2025-01-17T10:32:48Z INFO Processed deposit to set Eth 1 deposit index service=state-processor previous=84 new=85
2025-01-17T10:32:48Z INFO failed deposit signature verification service=state-processor deposit_index=0x54 error=signer returned an invalid signature
invalid deposit message
2025-01-17T10:32:48Z INFO Processed deposit to set Eth 1 deposit index service=state-processor previous=85 new=86
2025-01-17T10:32:48Z INFO failed deposit signature verification service=state-processor deposit_index=0x55 error=signer returned an invalid signature
invalid deposit message
2025-01-17T10:32:48Z INFO Stopping services num=7
2025-01-17T10:32:48Z INFO Stopping service type=validator
2025-01-17T10:32:48Z INFO Stopping service type=node-api-server
2025-01-17T10:32:48Z INFO Stopping service type=reporting
2025-01-17T10:32:48Z INFO Stopping service type=engine-client
2025-01-17T10:32:48Z INFO Stopping service type=telemetry
2025-01-17T10:32:48Z INFO Stopping service type=blockchain
2025-01-17T10:32:48Z INFO Stopping service type=beacond
2025-01-17T10:32:48Z INFO Closing application.db
Error: error during handshake: error on replay: validator set is nil in genesis and still empty after InitChain

I’m also getting an error with the Reth client:

2025-01-17T10:31:12.731101Z  INFO Status connected_peers=0 freelist=2 latest_block=0
2025-01-17T10:31:37.730937Z  INFO Status connected_peers=0 freelist=2 latest_block=0
2025-01-17T10:32:02.731777Z  INFO Status connected_peers=0 freelist=2 latest_block=0
2025-01-17T10:32:24.731414Z  WARN Post-merge network, but never seen beacon client. Please launch one to follow the chain!
2025-01-17T10:32:27.731373Z  INFO Status connected_peers=0 freelist=2 latest_block=0
2025-01-17T10:32:45.448384Z ERROR Invalid JWT: Authorization header is missing or invalid
2025-01-17T10:32:52.731774Z  INFO Status connected_peers=0 freelist=2 latest_block=0
2025-01-17T10:33:17.731846Z  INFO Status connected_peers=0 freelist=2 latest_block=0
2025-01-17T10:33:42.730921Z  INFO Status connected_peers=0 freelist=2 latest_block=0

Can anyone help me resolve this issue with a solution or suggestion that I can apply to my node?

@graceFor
Copy link

@whatcher5

I have the same problem. How do I solve this?

@abi87
Copy link
Collaborator

abi87 commented Jan 26, 2025

Hello @maheshtechpartner,
lately we did add some checks around the genesis state to make sure that the Deposit contract is duly initiated with the deposits in genesis.
I can run make start and make start-reth without issue in the current main (commit 2afec05).

Is there any reason why you need to run 0.7.0?

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

4 participants
@abi87 @graceFor @maheshtechpartner and others