According to David Schwartz, the amendment could be implemented in as little as two weeks if a majority backs it.
Ripple CTO David Schwartz has called for XRP Ledger (XRPL) validators to support an automated market maker (AMM) capability, but only if there is community consensus. Schwartz mentioned the XRPL’s AMM feature on X (previously Twitter). Schwartz described AMMs as an intriguing aspect of decentralized finance in his initial essay.
The XRP Ledger is a decentralized blockchain that runs on XRP. Its speed and scalability make it suited for a wide range of financial applications, including cross-border payments and remittances. In answer to a question from a community member concerning the timing for AMMs to become live on the XRPL following governance voting, Schwartz noted that if the majority adopts the amendment, the modifications could be implemented in as short as two weeks. However, validators should not vote YES individually. The community should make a decision, and then validators should almost unanimously vote YES when they believe the community is on board and there are enough nodes to support the change. Expanding on the relevance of a majority vote, Schwartz stated that, to the best of his knowledge, no validators now support the vote. The AMM feature was introduced with the release of rippled version 1.12.0, which also included the potential clawback feature.
Despite the importance of this functionality, Schwartz urged validators against voting independently to support these changes. On the contrary, he stated that “the community should reach a consensus first, and then validators should overwhelmingly vote YES when they perceive that the community is in agreement and sufficient nodes endorse the adjustment.”
Aside from his major position in Ripple, Schwartz is well-known for his educational publications and dedication to decentralization. Recently, he cleared up misconceptions about the clawback mechanism, which is frequently viewed as an intrusion on XRPL users. He added that the functionality is intended to protect developers from potential legal risks in the ecosystem.