The XLS-38 Cross-Chain Bridge and the XLS-40 Decentralised Identity are the two new feature modifications included in the rippled 2.0 upgrade, which was released by the creators of the XRP Ledger.
In addition, there are several more enhancements and fix modifications.
New amendments
The XLS-38 Cross-Chain Bridge will enable XRP and fungible tokens generated on the XRPL to flow between the XRPL Mainnet and the XRPL Sidechains, as well as between the XRPL Mainnet and the proposed EVM sidechain. These are the two new feature modifications, as previously mentioned.
Independent witness servers safeguard the Cross-Chain Bridge by validating any transactions spanning chains.
https://x.com/RippleXDev/status/1745181954427826254?s=20
A self-sovereign system called XLS-40 Decentralised Identity (DID) gives people total control over their online persona.
In order to provide verifiable, self-sovereign digital identity, the XLS-40 DID implementation will be compatible with any distributed ledger or network and make use of the World Wide Web Consortium (W3C) standard.
A simple adjustment that adds a new ledger object is called XLS-40. Associated transactions have the ability to create, alter, and remove this item.
Updates to the API are also included in the latest software release. With the introduction of API v2, the API has been made cleaner by eliminating outdated fields and methods, renaming fields that were commonly misinterpreted, and improving response consistency.
A few problems surfaced, including those involving approved trustlines and a mix of warning signs when an offer’s exchange rate deviates from the order book rate. These were classified as revisions to the main ledger.
Any XLS specifications that violate the core protocol must go through an amendment process where the validator community votes on the feature before it can be added to the XRPL Mainnet.
A minimum of 80% of validators must vote “yes” or “accept” for an amendment to be approved. This level has to be kept up for at least two weeks.
The modification will go into effect and the functionality specified in the XLS standard will go live on the mainnet if both requirements are satisfied. Every modification is processed through this process independently.
