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.

Sign up for GitHub

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

Jump to bottom

ETH genesis file may have the wrong chain ID? #2419

Open
letsbangout opened this issue Jan 26, 2025 · 2 comments
Open

ETH genesis file may have the wrong chain ID? #2419

letsbangout opened this issue Jan 26, 2025 · 2 comments

Comments

@letsbangout
Copy link

Following the guide at https://docs.berachain.com/nodes/quickstart

I got to the reth setup, and launched reth. Now reth does nothing (although it's connected to 7 peers), and in the beacon client I get the following:

2025-01-26T23:34:17Z INFO Starting service type=telemetry
2025-01-26T23:34:17Z INFO Starting service type=engine-client
2025-01-26T23:34:17Z INFO Initializing connection to the execution client... service=engine.client dial_url=http://localhost:8551
2025-01-26T23:34:20Z INFO Waiting for execution client to start... 🍺🕔 service=engine.client dial_url=http://localhost:8551
2025-01-26T23:34:20Z ERRR wanted chain ID 80094, got 80084: mismatched chain ID service=engine.client
2025-01-26T23:34:23Z INFO Waiting for execution client to start... 🍺🕔 service=engine.client dial_url=http://localhost:8551
2025-01-26T23:34:23Z ERRR wanted chain ID 80094, got 80084: mismatched chain ID service=engine.client

Is this indicating that the eth-genesis.json for reth should have its chain ID set to 80094?

$ grep chainId eth-genesis.json
                                                                                    "chainId": 80084,
@letsbangout
Copy link
Author

So I assumed the chain ID should have been 80094 in the eth-genesis.json, I made the change, wiped all the files under ~/beacon-kit/build/bin/config/reth, then put the corrected genesis file back in and re-ran the init procedure:

./reth init --datadir ./build/bin/config/reth --chain=./build/bin/config/reth/eth-genesis.json;

as it is given in the guide, then started reth with the flags given by the guide. Reth seems to start and run fine, but the beacon gives the following error before dying:

2025-01-27T01:33:53Z INFO Starting service type=telemetry
2025-01-27T01:33:53Z INFO Starting service type=engine-client
2025-01-27T01:33:53Z INFO Initializing connection to the execution client... service=engine.client dial_url=http://localhost:8551
2025-01-27T01:33:56Z INFO Waiting for execution client to start... 🍺🕔 service=engine.client dial_url=http://localhost:8551
2025-01-27T01:33:56Z INFO Connected to execution client 🔌 service=engine.client dial_url=http://localhost:8551 chain_id=80094 required_chain_id=80094
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getBlobsV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getPayloadV2
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getPayloadV3
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_newPayloadV4
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_forkchoiceUpdatedV2
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getPayloadV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_forkchoiceUpdatedV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getPayloadV4
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getPayloadBodiesByRangeV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_exchangeTransitionConfigurationV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getPayloadBodiesByHashV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_newPayloadV2
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_getClientVersionV1
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_forkchoiceUpdatedV3
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_newPayloadV3
2025-01-27T01:33:56Z INFO Exchanged capability service=engine.client capability=engine_newPayloadV1
2025-01-27T01:33:56Z INFO Starting service type=blockchain
2025-01-27T01:33:56Z INFO Starting service type=beacond
2025/01/27 01:33:56 [JOB 1] WAL file build/bin/config/beacond/data/blockstore.db/000002.log with log number 000002 stopped reading at offset: 70; replayed 2 keys in 2 batches
2025/01/27 01:33:57 [JOB 1] WAL file build/bin/config/beacond/data/state.db/000002.log with log number 000002 stopped reading at offset: 142; replayed 3 keys in 3 batches
2025-01-27T01:33:57Z INFO State store key layout version  version=vv1
2025-01-27T01:33:57Z INFO Blockstore version version=v1
2025-01-27T01:33:57Z INFO WARNING: deleting genesis file from database if present, the database stores a hash of the original genesis file now
2025-01-27T01:33:57Z INFO Starting multiAppConn service module=proxy impl=multiAppConn
2025-01-27T01:33:57Z INFO Starting localClient service module=abci-client connection=query impl=localClient
2025-01-27T01:33:57Z INFO Starting localClient service module=abci-client connection=snapshot impl=localClient
2025-01-27T01:33:57Z INFO Starting localClient service module=abci-client connection=mempool impl=localClient
2025-01-27T01:33:57Z INFO Starting localClient service module=abci-client connection=consensus impl=localClient
2025-01-27T01:33:57Z INFO Starting EventBus service module=events impl=EventBus
2025-01-27T01:33:57Z INFO Starting PubSub service module=pubsub impl=PubSub
2025-01-27T01:33:57Z INFO ABCI Handshake App Info module=consensus height=0 hash=E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 software-version=v1.0.1 protocol-version=0
2025-01-27T01:33:57Z INFO ABCI Replay Blocks module=consensus appHeight=0 storeHeight=0 stateHeight=0
2025-01-27T01:33:57Z INFO InitChain initialHeight=1 chainID=bartio-beacon-80084
2025-01-27T01:33:57Z INFO Stopping services num=8
2025-01-27T01:33:57Z INFO Stopping service type=beacond
2025-01-27T01:33:57Z INFO Closing application.db
2025-01-27T01:33:57Z INFO Stopping service type=blockchain
2025-01-27T01:33:57Z INFO Stopping blockchain service service=blockchain
2025-01-27T01:33:57Z INFO Stopping service type=engine-client
2025-01-27T01:33:57Z INFO Stopping service type=telemetry
2025-01-27T01:33:57Z INFO Stopping service type=reporting
2025-01-27T01:33:57Z INFO Stopping service type=node-api-server
2025-01-27T01:33:57Z INFO Stopping service type=validator
2025-01-27T01:33:57Z INFO Stopping service type=shutdown
2025-01-27T01:33:57Z INFO Stopping shutdown service service=shutdown
Error: error during handshake: error on replay: validator set cap 69, deposits count 86: validator set cap exceeded at genesis
2025/01/27 01:33:57 ERROR startup failure error="error during handshake: error on replay: validator set cap 69, deposits count 86: validator set cap exceeded at genesis"

@codingwithmanny
Copy link
Contributor

Expect that the node instructions will be changing soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@codingwithmanny @letsbangout