-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
A livelock bug in the presence of byzantine validator #1047
Comments
Thanks for opening this and for your support for the project! What language are you implementing Tendermint in ? Is the code open source? Indeed there was a live lock bug in my thesis that is not in the code itself. See the consensus/reactor.go file for the gossiping mechanism we use. We are working on more comprehensive and superior documentation and specification for the algorithm and the implementation. You can see a start in https://github.com/tendermint/tendermint/tree/develop/docs/specification/new-spec We will be publishing a full formal specification and safety and liveness proofs for the Tendermint consensus algorithm very soon - stay tuned! |
Thanks for the reply. So basically because of gossiping, eventually it is unlikely that only some correct processes receive a specific message. Do I understand right? |
Yes, you are right. If a correct process receives a message, it will gossip it to other processes, so eventually (with high probability) all correct processes will get it. |
Sorry for the late reply. Please contact me via mingcl.tw@gmail. I'm looking forward for your comments, thanks! |
…tendermint#1047) Closes tendermint#666 This PR adds double quotes to `path` param of `/abci_query` endpoint. --- #### PR checklist - [ ] Tests written/updated - [ ] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments (cherry picked from commit f6f13b1) Co-authored-by: Steven Ferrer <steven.r.ferrer@gmail.com>
Hello, our team are re-implementing the elegant tendermint byzantine consensus algorithm described in the wiki.
However, we found a liveness bug can happen when malicious byzantine validators are participating (if they have a carefully planned strategy). Also we found this bug may have already been pointed out in Christian Cachin (@cca88) and Marko Vukolić's paper, Blockchain Consensus Protocols in the Wild page 11:
The reference number 14 is "E. Buchman and J. Kwon. Private discussion, 2017.".
Since tendermint is the pioneer of BFT consensus algorithm in the age of blockchain, and also powers critical services like Cosmos, I think it would be great if people can learn more about the detail of consensus mechanism. @ebuchman @jaekwon would you mind to share the additional mechanisms mentioned by @cca88's paper?
Thank you for all that you've done to this awesome project!
The text was updated successfully, but these errors were encountered: