Ripple CTO Proposes ‘Deletable Accounts’ On The XRP Ledger (XRPL) Via An Amendment Process

A new feature was proposed by Ripple’s CTO David Schwartz in the amendment process of deletable accounts. This feature will allow XRPL accounts to be removed from the ledger and recovers most of the reserve locked in the account to prevent spam.

In the past deleting accounts was impossible as an account always existed, said software engineer Nik Bougalis who is leading the C++ team at Ripple and drafted the spec for deletable accounts. But now, someone that is able to sign a transaction on the account can now delete that.

Amendment Process to Introducing New Features

Schwartz in his latest article, “Amendments: Ensuring Sensible Evolution of the XRP Ledger,” talks about one of the key governance mechanisms that XRPL uses, the amendment process.

Purposely designed and built for broad participation, the amendment system provides a means of “introducing new features to the decentralized XRP Ledger network without causing disruptions.” The system utilizes the core consensus process of the network to approve any changes. Schwartz said,

“The activation of any changes to the XRP Ledger protocol are coordinated by the community through this process.”

The Power to Coordinate Activation of Amendments

Amendments are now assigned to a feature discussed by the community to be introduced to the XRP Ledger (XRPL) which needs 80% support to enable it. The community is then given two weeks to voice their opinion on the amendment and if enabled, those who did not agree to will become ‘amendment blocked‘ —

“a security feature designed to protect applications that depend on XRP Ledger data.”

XRPL, Shwartz explained, is to provide a robust feature for the foundation of the digital asset XRP, in addition, to exchange digital token ad settling payments. Schwartz explained,

“The purpose of this amendment process is to empower the community to coordinate activation of amendments that do have broad support with minimal disruption and to avoid an accidental fork if servers do not agree on network rules.”

Validators can’t activate amendments that don’t have broad support. Previously, support for multi-signing, ledger’s on-chain escrow and payments channel features were enabled by amendments.

Read Original/a>
Author: AnTy

Related Articles

Author: ICO Warz