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

Formal description of Byzantine Consensus algorithm #213

Closed
vinniefalco opened this issue Nov 20, 2013 · 2 comments
Closed

Formal description of Byzantine Consensus algorithm #213

vinniefalco opened this issue Nov 20, 2013 · 2 comments

Comments

@vinniefalco
Copy link
Contributor

The consensus algorithm used in Ripple, is the core of the software. However, there is no formal explanation of how it works, or any sort of unit-testable pseudo-code. We need a formal description along with supporting research, pseudo-code, and sample programs.

There's a more in-depth discussion here:

https://ripple.com/forum/viewtopic.php?f=2&t=4118&p=23393#p23393

@kravets
Copy link

kravets commented Nov 21, 2013

IMHO, Ripple's long term vision of becoming "Open Transaction Protocol" will not happen without:

  • Rigorous Paper showing soundness of Consensus
  • IETF-style RFC specification of network messages and their semantics
  • Existence of alternative implementations based on the spec above.

These things don't need to happen right away or even soon, but without them RTXP will never become a real internet standard.

Cheers ...

rec pushed a commit to rec/rippled that referenced this issue Sep 9, 2015
@vinniefalco
Copy link
Contributor Author

There's been a lot of progress on this, including consensus refactoring and simulation tests. This issue is obsolete.

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

No branches or pull requests

2 participants