Ripple Releases XRP Ledger (XRPL) Upgrade to Boost Stability, DeFi: Details
-
Ripple introduces major XRP Ledger v3.0.0 upgrade.
-
The upgrade boosts network stability and expand decentralized finance (DeFi) capabilities.
-
XRP price moves near $2.08 following a 1.50% jump.
In today’s big XRP news, Ripple has officially released a major upgrade to XRP Ledger (XRPL). The major upgrade introduces significant changes, optimizations, and critical fixes to boost network stability and expand decentralized finance (DeFi) capabilities.
It comes as part of Ripple’s latest roadmap, placing stablecoins and tokenized real-world assets (RWAs) at the center of its institutional DeFi strategy.
Ripple introduces rippled v3.0.0, the core server software that powers the decentralized XRP Ledger (XRPL) network. It marks a major milestone for the XRPL network, with reliability improvements, fixes, and innovations such as a native lending protocol, as Ripple boosts XRP and RLUSD adoption.
Node operators are urged to upgrade to the new version immediately to ensure service continuity. It also mentioned installation packages and instructions for updating to the latest version.
The upgrade introduces major amendments, optimizations, and bug fixes, said Krippenreiter. He highlighted “fixIncludeKeyletFields” amendment, which adds missing keylet fields to ledger entries related to escrow and payments.
Similar to its successful Smart Escrow Devnet update, changes were made related to fees and reserves, function signatures, multi-purpose token (MPToken) issuance, as well as bug fixes and code cleanup.
The amendment fixes accounting errors in MPT escrows, adds missing keylet fields to several ledger entries, and improves transaction transparency. Moreover, it resolves rounding issues in automated market maker (AMM) transactions, ensuring precise LP token balances.
The ‘simulate API method’ now supports new metadata fields, which expands the capabilities of analytical and DeFi tools. The upgrade also adds STInt32, a new data type that supports negative 32-bit integers for more protocol flexibility in the future.
Source link
Written by : Editorial team of BIPNs
Main team of content of bipns.com. Any type of content should be approved by us.
Share this article:









