Incorrect genesis hash #1

New Issue

f4ts0 · 2024-12-09T17:11:57+01:00

f4ts0 commented

2024-12-09 17:11:57 +01:00

I've spent couple of days to run both applications and found out that the error comes from the wrong genesis hash. You accept only networks with specific hash, which is stored here and here.

That means that if you run latest version of ghost-node with given config any data will be rejected. Changing them manually helped and data is collected as expected. Make sure that genesis hash is fixed ASAP because of telemetry deployment.

As a side note, during the execution telemetry-core for some reason throws the error periodically:

No idea what is the reason and how this error can affect the application overall. The error deserves careful consideration IMHO

I've spent couple of days to run both applications and found out that the error comes from the wrong genesis hash. You accept only networks with specific hash, which is stored [here](https://git.ghostchain.io/ghostchain/ghost-telemetry-backend/src/commit/51e78f29e735f8a5bc46f40a41327c3733ca349b/telemetry-core/src/state/chain.rs#L71) and [here](https://git.ghostchain.io/ghostchain/ghost-telemetry-backend/src/commit/51e78f29e735f8a5bc46f40a41327c3733ca349b/telemetry-core/src/state/state.rs#L280). That means that if you run latest version of ghost-node with given config any data will be rejected. Changing them manually helped and data is collected as expected. Make sure that genesis hash is fixed ASAP because of telemetry deployment. As a side note, during the execution telemetry-core for some reason throws the error periodically: ![image](/attachments/ab141825-7069-4b8d-8ece-f4533dcd622a) No idea what is the reason and how this error can affect the application overall. The error deserves careful consideration IMHO

image.png

169 KiB

st1nky was assigned by f4ts0

2024-12-09 17:11:57 +01:00

str3tch was assigned by f4ts0

2024-12-09 17:11:57 +01:00

str3tch commented

2024-12-23 13:27:32 +01:00

Genesis hashes fixed. I'll ping you whenever the genesis hash will be updated, on the other hand I think that you'll know for sure when new network will be deployed.

Talking about errors logs were extended by @st1nky, we believe that errors occures when connection is dropped by the client which is normal behavior.

Issue could be closed for now.

Genesis hashes fixed. I'll ping you whenever the genesis hash will be updated, on the other hand I think that you'll know for sure when new network will be deployed. Talking about errors logs were extended by @st1nky, we believe that errors occures when connection is dropped by the client which is normal behavior. Issue could be closed for now.

str3tch closed this issue

2024-12-23 13:27:36 +01:00

Sign in to join this conversation.