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

Bug in logging, "No incoming messages from the consensus client.. " but we have them #7575

Open
MarekM25 opened this issue Oct 8, 2024 · 0 comments

Comments

@MarekM25
Copy link
Contributor

MarekM25 commented Oct 8, 2024

Logs from user in discord: https://discordapp.com/channels/629004402170134531/1293170041256280138/1293172049774383156

It looks like a bug in https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.HealthChecks/NodeHealthService.cs
or in teku

I think the situation might be like this: We haven’t explicitly announced support for the new hardfork in our capabilities, but we do have the support in place. As a result, Teku is using those methods to send newPayloads and fcU to the Nethermind client

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants