-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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]: Consensus error, but node continues to run normally and produce blocks. #22625
Comments
thank you for the issue. Did you add in any custom modules? |
https://github.com/fiamma-chain/fiamma/blob/main/app/babylon.go My project does indeed depend on an external Babylon module, but I did not modify the consensus module code, just normally wrote my business logic |
does the babylon code introduce any vote extensions? this issue is with consensus less so cosmos sdk but we can help |
The Babylon module code we introduced has not included any voting extensions; here is the link to its repository. https://github.com/babylonlabs-io/babylon-sdk |
sorry for the delay in responding, are you still running into this issue? |
closing this issue as it seems the issue is not cosmos sdk but possibly from the comet side. im not sure why it would be presnt |
Is there an existing issue for this?
What happened?
Cosmos SDK Version
v0.50.9
How to reproduce?
I used the Ignite to build a chain, and the Cosmos SDK version is v0.50.9.
I deployed four nodes on Amazon Web Services, and these nodes used private IP addresses as their seed nodes. After the network started, there were no error messages at first, but after running for some time, such log information appeared, but the network continued to run normally and produce blocks as usual.
The text was updated successfully, but these errors were encountered: