2

I spent a while reading ripple protocol, specially the consensus process, the protocol works based only on a sub-network ( from a huge network) reaching a consensus for the current state, it's supposed to prevent double-spending and other attacks. There is no analysis about fork events!

First, any one can explain step by step the underlying consensus mechanism? Second, what's in the mechanism that prevents double-spending, attacks and fork events?

Murch
  • 71,155
  • 33
  • 180
  • 600
efaysal
  • 41
  • 5
  • possible duplicate of [How does Ripple solve the double-spend problem?](http://bitcoin.stackexchange.com/q/7550/5406), [Is it possible to execute a double-spending attack in Ripple during a network split?](http://bitcoin.stackexchange.com/q/10249/5406), [What is the exact consensus protocol Ripple uses?](http://bitcoin.stackexchange.com/q/13330/5406), [Ripple Distributed Consensus Algorithm](http://bitcoin.stackexchange.com/q/25275/5406), [What are the pros and cons of Ripple's consensus as compared with Bitcoin's proof-of-work?](http://bitcoin.stackexchange.com/q/10180/5406) – Murch Jan 13 '15 at 09:44
  • Hi efaysal, I think that the question you are interested in probably has been answered in combination by the posts I linked too. Please check whether a question has been asked already before you create a new one. You can find more information on how Stack Exchange works in our **[tour]**. – Murch Jan 13 '15 at 09:49
  • Hi Murch, many thanks for the hint, indeed this combination is covering some points. The fork event point is still missing, any idea? Also I wish if one can structure the consensus protocol into one unified writing and clearly explain what's in the mechanism that prevents double-spending, attacks and fork events? Having one defined understanding of the ripple consensus will foster many interesting follow up. Bitcoin paper was really magical, in sense, handled most of important points in an acceptable concise manner. – efaysal Jan 13 '15 at 19:17
  • AFAIK, there is no such thing as a fork event in Ripple. The ledger can only advance when a majority of the validators is in agreement. You can find the Consensus Whitepaper of Ripple here: [Consensus Whitepaper](https://ripple.com/consensus-whitepaper/) – Murch Jan 13 '15 at 19:37
  • Many thanks Murch. Great to have online this Consensus Whitepaper of Ripple. A good reading my help to answer my questions. – efaysal Jan 14 '15 at 01:15
  • Actually that whitepaper seems to not describe the necessary requirements of the network topology in enough detail, see: https://forum.ripple.com/viewtopic.php?f=2&t=7801#p56432 https://bitcointalk.org/index.php?topic=144471.msg1548672#msg1548672 If everybody uses the UNL in https://ripple.com/ripple.txt then it is secure, but also centralized. – jtimon Jan 14 '15 at 14:45
  • @jtimon, many thanks, your links are very informative. The consensus assessment has to take into consideration the network topology and its size. Its current form has very ad-hoc settlements and it seems that to be really efficient, Ripple is more set to be a centralized system. – efaysal Jan 14 '15 at 19:45

0 Answers0