Ripple Labs’ development arm, RippleX, has released a major update on the proposed XLS-40 amendment, which would integrate native support for W3C decentralized identifiers (DIDs) into the XRP Ledger.
Ripple Labs’ development arm, RippleX, has released a major update on the proposed XLS-40 amendment, which would integrate native support for W3C decentralized identifiers (DIDs) into the XRP Ledger.
Ripple stated in a recent tweet that a minor edge case has been discovered in the XLS-40 decentralized identity specification that may lead users to create empty DID objects. A solution to this issue has been proposed and is currently under review, which will be introduced as a new amendment.
The “AddthefixEmptyDID” amendment would fix an issue where DIDs could become empty, which should not be possible because an empty DID object is equivalent to having no DID object. This fix amendment is expected to be part of the next major release of the XRPL software, version 2.2.0.
Discussions on the XLS-40 feature began in March 2023, and by January 2024The XLS-40 decentralized identity feature amendment was introduced as part of version 2.0.
According to Ripple X, the Ripple validator has yet to vote for DID and has no intention of doing so until the fixed amendment is available. The reason is that you think it is better to fix it first, even if the error seems minor.
Decentralized identity (DID) is a technology that allows users to control their online identity autonomously. The XLS-40 DID implementation will employ the World Wide Web Consortium (W3C) standard to provide an autonomous, verifiable digital identity that is compatible with any network or distributed ledger. Its goal is to provide a standardized and interoperable solution for digital identities on the XRP Ledger.
Despite the minor setback faced, the blockchain community is excited about the proposed XLS-40 feature, which could herald a new era of digital identity on the XRP Ledger.
Expectations are generated for XRP Ledger AMM
In positive development news, the XRP Ledger AMM It is expected to come into force on March 22, having once again reached the majority.
To add new features to the XRPL Mainnet, XLS specifications that involve major changes to the core protocol must go through the amendment process, in which the validator community votes on the feature.
For an amendment to be approved, at least 80% of validators must vote yes or accept, and this level must be maintained for at least two weeks.