An major update on the planned XLS-40 modification, which would incorporate native support for W3C Decentralised Identifiers (DIDs) on the XRP Ledger, has been released by RippleX, the development arm of Ripple Labs.
A small edge case in the XLS-40 decentralised identity specification has been found, according to a recent tweet from Ripple, which might cause users to generate empty DID objects. A potential solution to this problem is presently being reviewed and will be presented as a new amendment.
https://x.com/RippleXDev/status/1767984732908957970?s=20
An empty DID object is the same as having no DID object at all, therefore the “AddthefixEmptyDID” amendment would address a problem where DIDs might become empty. It is expected that rippled version 2.2.0, the upcoming core XRPL software release, would include this repair amendment.
In January 2024, the XLS-40 Decentralised Identity feature amendment was added as part of the rippled 2.0 release, after discussions over the XLS-40 feature that started in March 2023.
The validator for Ripple X claims that they have not yet voted for DID and do not plan to do so until the rectified amendment is released. The rationale is that, even if the problem seems small, it thinks it is better to release the remedy first.
With the use of decentralised identification (DID) technology, people may exercise self-sovereign control over their online personas. The World Wide Web Consortium (W3C) standard will be used in the XLS-40 DID implementation to offer a digital identity that is self-sovereign, verifiable, and interoperable with any network or distributed ledger. With this, the XRP Ledger will have a standardised and compatible method for handling digital IDs.
The blockchain community is excited about the planned XLS-40 feature, which might usher in a new era of digital identification on XRP Ledger, despite the small hiccup that has occurred.
Expectations brewing for XRP Ledger AMM
Positive development news: after achieving a majority once more, the XRP Ledger AMM is expected to go live on March 22.
Any XLS specifications that break modifications to the core protocol must go through the amendment process before new features may be added to the XRPL Mainnet. During this procedure, the validator community votes on the proposed feature.
At least 80% of validators must vote in favour of the change or accept it in order for it to pass, and this threshold must be kept for at least two weeks.
