Due to the legal process with the SEC, Ripple has frequently been in the spotlight. However, this time a different discussion arose. Ripple’s Chief Technology Officer (CTO), David Schwarz, drew attention to the Automatic Market Maker (AMM) feature of the XRP Ledger (XRPL) validators. According to Schwarz, this feature now needs to be supported, but a consensus must be reached within the community.
AMM Should be Supported in Ripple
Ripple’s CTO sparked a debate about AMMs. In his initial post, Schwartz provided information about AMMs and drew attention to the decentralized finance (DeFi) sector, then turned to questions for more details. The XRP Ledger, a decentralized blockchain-based order book that supports the XRP cryptocurrency, is known for its transaction speed and scalability. These features make it suitable for various financial applications, including cross-border payments and remittances.
Schwartz also responded to a community member’s question regarding the timeline for publishing AMMs on XRPL after a governance vote. According to the CTO, if the majority supports the change, the modifications can be implemented in a short period, such as two weeks.
Adoption by Everyone
Highlighting the importance of the vote, Schwartz stated that so far, no one has supported this vote. The introduction of the AMM feature occurred with the release of the rippled 1.12.0 version, which also brought the potential Clawback feature. The addition of AMM to the ecosystem will not be limited to the introduction of a new trading program but will also enable integration with the XRPL DEX. Schwartz emphasized the importance of this feature and provided the following recommendations for validators:
“First, the community needs to reach a consensus, and then validators should vote YES with an overwhelming majority when they perceive that the community agrees and enough nodes have adjusted.”
David Schwarz is a prominent figure playing a role in the Ripple ecosystem. He is widely appreciated for his informative articles and his commitment to decentralization. Recently, he clarified misunderstandings regarding the Clawback feature, which was perceived as an attack on XRPL users, and explained that the purpose of the Clawback feature is to protect developers from potential legal obligations within the ecosystem.
