<p>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!  </p>

<p>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?</p>

CC BY-SA 3.0
2015-01-13T09:44:41.490Z
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
CC BY-SA 3.0
2015-01-13T09:49:46.937Z
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
CC BY-SA 3.0
2015-01-13T19:17:21.240Z
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
CC BY-SA 3.0
2015-01-13T19:37:48.003Z
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
CC BY-SA 3.0
2015-01-14T01:15:23.233Z
Many thanks Murch. Great to have online this Consensus Whitepaper of Ripple. A good reading my help to answer my questions.
efaysal
CC BY-SA 3.0
2015-01-14T14:45:23.473Z
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
CC BY-SA 3.0
2015-01-14T19:45:35.170Z
@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
<ripple><consensus><ripple-ledger>
Ripple: only a sub-network reaching a consensus is largely enough to be decentralized&secure system?
efaysal
# Ripple: only a sub-network reaching a consensus is largely enough to be decentralized&secure system?

(Asked by: username_0 on 2015-01-13)

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?

**Tags:** ripple, consensus, ripple-ledger

> **Comments:**
> **username_1**: 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)  
> **username_1**: Hi username_0, 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]**.  
> **username_0**: Hi username_1, 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.  
> **username_1**: 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/)  
> **username_0**: Many thanks username_1. Great to have online this Consensus Whitepaper of Ripple. A good reading my help to answer my questions.  
> **username_2**: 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.  
> **username_0**: @username_2, 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.  

---

## 0 answers

