David Schwartz talks about the smart development of the Ripple XRP Ledger

David Schwartz spoke about the rational development of Ripple XRP Ledger, presenting the material on the official Ripple website. Ripple often issues various articles related to various aspects of their projects, as well as the blockchain as a whole. Such materials explain in detail various important points. New article related to Ripple XRP Ledger. Ripple CTO David Schwartz talked about ensuring the smart development of the XRP Ledger.

David Schwartz  - David Schwartz talks about the smart development of the Ripple XRP Ledger

David Schwartz talks about the smart development of the Ripple XRP Ledger: Details

David Schwartz spoke about the rational development of the Ripple XRP Ledger, indicating how this is ensured. Ripple’s CTO first noted that XRP Ledger was designed to provide a robust feature set for creating XRP digital assets in addition to payments and exchanges of all kinds of digital assets. The Ripple XRP Ledger innovations open source community continues to make major technological improvements to ensure performance, stability, security, quality, decentralization, developer experience and management.

It’s no secret to anyone, as the representative of Ripple emphasized, that management is one of the most difficult problems that today has to be solved in blockchain technology. Blockchain is a fast-growing set of technologies, so its adaptability and continuous improvement are very important.

However, as the number of developers in the community grows and the number of servers in the network increases, the management process becomes more complex. As the Ripple XRP Ledger network grows, so does the need for improved management. One of the key management mechanisms that the Ripple XRP Ledger uses is an amendment process specifically designed and built for widespread use.

The activation of any changes to the Ripple XRP Ledger protocol is coordinated by the community through this process. Making changes to a process always starts with an idea of ​​improvement or a new feature. Since changes require general agreement, discussions of new features often take place in public forums.

Last year, the community discussed a number of possible features and design changes that could be made to the Ripple XRP Ledger. The next steps are to transform the ideas into the proposed implementation and create a set of code changes. At this stage, corrections can be assigned to a function. Those who support this feature can run the Ripple XRP Ledger software version.

The amendment process itself can then be used by the community to coordinate the inclusion of this feature. Validators who want the amendment to be activated on the network can indicate this. If there is 80% support, validators will launch a two-week clock to activate the correction. The amendment should maintain 80% for two weeks, otherwise the cycle should begin anew. During these two weeks, the community has the opportunity to express their opinion on the amendment. Validators can change their position, and in extreme cases, the community can even change which validators they are willing to listen to. The list of unique Ripple nodes (UNLs) continues to become more and more diverse and reliable: Ripple now works with approximately 18% of UNL validators.

If an amendment is activated at the end of a two-week process, participants who do not agree with this amendment will not be able to negotiate with validators who support it, and will become blocked. This will trigger a security feature designed to protect applications that depend on the Ripple XRP Ledger. The goal of collective change is to provide the community with the opportunity to coordinate the activation of amendments that really have broad support, with minimal disruption and to avoid accidental forking if the servers do not agree on network rules.

Validators cannot activate corrections that do not have broad support, because this can lead to network branching and, of course, participants can change which validators they want to agree with at any time. In the past, as the Ripple CTO noted, the amendments included a number of new features and fixed many minor bugs. Support for Managed Multiple Signatures has been incorporated by amending, as well as escrow and payment channel functions.

Managed multiple signatures, according to a Ripple spokesperson, allow an account to have multiple signatories with the quorum required to complete transactions. Quorum members can manage their credentials. Payment channels significantly improve scalability, allowing you to conduct transactions outside the register, but at the same time save for it.
Currently, one new feature proposed during the amendment process is Changeable Accounts, and it expects to acquire and retain an 80% majority before activation. This feature allows you to delete Ripple XRP Ledger accounts from the register and restore most of the reserve blocked in accounts to prevent spam.
These changes, as David Schwartz emphasized, as well as changes in the future will further increase confidence in the register and provide high performance Ripple XRP Ledger, without downtime. The Ripple XRP Ledger amendment process will continue to ensure that new features are responsibly activated by the community in a measurable way and protect against accidental power plugs.

Leave a comment

Your email address will not be published. Required fields are marked *