XRP Ledger The developers have announced the release of rippled 2.0, an update that introduces two new feature modifications: XLS-38 Cross-Chain Bridge and XLS-40 Decentralized Identity.
XRP Ledger The developers have announced the release of rippled 2.0, an update that introduces two new feature modifications: XLS-38 Cross-Chain Bridge and XLS-40 Decentralized Identity.
Apart from this, there are fixes and many other improvements.
New amendments
There are two new feature modifications, as noted above: The XLS-38 cross-chain bridge will allow XRP and fungible tokens issued on XRPL to flow between the XRPL Mainnet and XRPL Sidechains, as well as between the XRPL Mainnet and the planned EVM sidechain.
The Cross-Chain Bridge is protected by independent witness servers, which certify any transaction that crosses chains.
XLS-40 Decentralized Identity (DID) is a system that allows users to have full control over their online identity autonomously.
The XLS-40 DID implementation will be interoperable with any network or distributed ledger and will leverage the World Wide Web Consortium (W3C) standard to enable autonomous, verified digital identification.
XLS-40 is a lightweight amendment that adds a new general ledger object. This object can be created, updated and deleted through associated transactions.
The new version of the software also incorporates API updates. API v2 has been released, which cleans up the API by removing obsolete fields and methods, renaming frequently misread fields, and increasing response consistency.
Some issues arose, such as those with authorized trust lines, as well as a mix of indicators when a bid exchange rate differs from the order book rate. These were classified as updates to the main ledger.
To add new features to the XRPL Mainnet, XLS specifications that involve major changes to the core protocol must go through an amendment procedure 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” the amendment. This level must be maintained for a minimum of two weeks.
If both conditions are met, the amendment will take effect and the functionality described in the XLS standard will be available on the core network. This procedure is followed for each modification separately.
