Ripple’s Latest Update Sets the Stage for Effortless Digital Identity on XRP Ledger
RippleX, the development arm of Ripple Labs, has provided an update on the XLS-40 amendment, which aims to integrate W3C Decentralized Identifiers (DIDs) into the XRP Ledger.
A minor issue has been identified within the decentralized identity framework, potentially leading to the creation of empty DID objects. RippleX is currently reviewing a proposed fix for this issue, which will be introduced as a new amendment.
1/ RX engineering has identified a minor edge case in the XLS-40 decentralized identity spec, where users may be able to create empty DID objects. We have proposed and are reviewing a fix, that will be introduced as a new amendment:https://t.co/7G7dz9dOAh
— RippleX (@RippleXDev) March 13, 2024
The “AddthefixEmptyDID” amendment seeks to address this loophole and is expected to be included in the next core release of XRPL software, rippled version 2.2.0. Despite this setback, discussions surrounding the XLS-40 feature, which began in March 2023 and were finalized in January 2024, are still ongoing.
Ripple X has decided to hold off on voting for the DID amendment until the fix amendment is finalized, emphasizing the importance of resolving even minor issues before proceeding.
Decentralized Identity (DID) technology empowers individuals to manage their online identities autonomously. The upcoming implementation of XLS-40 DID aims to provide users with a standardized, interoperable solution for managing digital identities within the XRP Ledger ecosystem.
READ MORE: Trump Voices Acceptance of Bitcoin as ‘Additional Currency’ in CNBC Interview
Despite the setback, optimism remains within the blockchain community regarding the potential of the proposed XLS-40 feature.
In other news, the XRP Ledger Automated Market Maker (AMM) is set to launch on March 22, following widespread support. The process of introducing new features to the XRPL Mainnet involves amendments outlined in XLS specifications, which undergo a rigorous evaluation process by the validator community. Successful amendments require approval from at least 80% of validators, maintained for a minimum of two weeks.