Abstract
Ripple acts as a real-time settlement and payment system to connect banks and payment providers. As the consensus support of the Ripple network to ensure network consistency, Ripple consensus protocol has been widely concerned in recent years. Compared with those Byzantine fault tolerant protocols, Ripple has a significant difference that the system can reach an agreement under decentralized trust model. However, Ripple has many problems both in theory and practice, which are mentioned in the previous researches. This paper presents Ripple+, an improved scheme of Ripple consensus protocol, which improves Ripple from three aspects: (1) Ripple+ employs a specific trust model and a corresponding guideline for Unique Node List selection, which makes it easy to deploy in practice to meet the safety and liveness condition; (2) the primary and view change mechanism are joined to solve the problem discussed by the previous research that Ripple may lose liveness in some extreme scenarios; (3) we remove the strong synchrony clock and timeout during consensus periods to make it suitable for weak synchrony assumption. We implemented a prototype of Ripple+ and conducted experiments to show that Ripple+ can achieve the throughput of tens of thousands of transactions per second with no more than half a minute latency, and the view change mechanism hardly incurs additional cost.
Highlights
As one of the most famous blockchain projects, Ripple plays the role of the bridge among different currencies
Unlike proof-of-series consensus adopted in other digital cryptocurrency, the Ripple consensus protocol is a Byzantine fault tolerant (BFT) protocol with decentralized trust property, which means that
Compared with other BFT protocols with centralized trust (e.g., PBFT [2]), the Ripple consensus protocol is more flexible to apply in a diversifying trusted network
Summary
As one of the most famous blockchain projects, Ripple plays the role of the bridge among different currencies. We refer to the view change mechanism in [2,7] to ensure that the system will not get stuck when similar scenarios appear Another disadvantage of the Ripple consensus protocol is that it relies on the synchrony timing assumption. Has similar ideas with us to ensure the UNL overlap for safety, we consider that Ripple+ is more flexible and scalable than Ripple for leaf nodes have the right to choose which core nodes to trust to a certain extent instead of the whole core set. Liveness: Amores-Sesar et al [6] has proved that the core set itself may lose liveness when only one Byzantine node gossips contradictory input transactions in the open phase To deal with this issue, Ripple+ selects one core node as the primary at any time. The above experimental results indicate that Ripple+ is suitable to be the consensus support of permissionless blockchain in terms of both latency and throughput
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
