All news is rigorously fact-checked and reviewed by leading blockchain experts and seasoned industry insiders.
- The XRP Ledger has just released v2.4.0, bringing a host of new features, performance upgrades, and important bug fixes to enhance the network’s efficiency and functionality.
- One of the significant updates is the introduction of Dynamic NFTs that allow NFT issuers to update the Uniform Resource Identifier after minting NFTs.
The XRP Ledger (XRPL), the decentralized, layer-1 blockchain that powers XRP, one of crypto’s largest and longest-standing assets, has launched version 2.4.0, introducing a range of new features and bug fixes aimed at enhancing security, compliance, and overall network performance.
One of the key highlights of this release is the introduction of several amendments, which are now open for voting. Under XRPL’s governance model, an amendment must receive at least 80% approval from validators for two consecutive weeks before it can be activated. This process ensures that changes are widely supported by the network before being implemented, maintaining the decentralization and integrity of the XRPL ecosystem.
Key Amendments in XRPL v2.4.0
Among the most notable amendments is the introduction of Dynamic NFTs (dNFTs), which will allow NFT issuers to update the URI (Uniform Resource Identifier) of an NFToken after minting. Traditionally, once an NFT was created on XRPL, its metadata was permanently fixed. However, with DynamicNFT, the associated URI can be changed, making NFTs more flexible and adaptable.
Additionally, the DeepFreeze amendment grants token issuers the ability to permanently freeze trust lines, preventing asset transfers for holders affected by this freeze. Unlike temporary freezing mechanisms, DeepFreeze allows issuers to take long-term action against suspicious or non-compliant accounts. This feature is particularly useful for regulatory compliance, fraud prevention, and risk management.
The fixInvalidTxFlags amendment enhances XRPL’s transaction validation by introducing stricter checks for flags used in CredentialCreate, CredentialAccept, and CredentialDelete transactions. These transactions play a crucial role in XRPL’s identity and authentication system, ensuring secure and reliable credential management. By enforcing proper flag usage, this prevents invalid transactions, reduces errors, and strengthens network security, ultimately improving the integrity of XRPL’s transaction processing framework.
Security and governance improvements remain a key focus in the XRPL v2.4.0 update. Validators now have the ability to require a minimum number of UNL publishers to agree on a validator before trusting it. This strengthens decentralization and security, ensuring no single UNL publisher can dictate trusted validators alone.
On top of this, the XRPL Foundation UNL keys have been updated as part of its ongoing governance transition. To support migration without modifying the key for the current UNL list, a new XRPL Foundation subdomain has been introduced, ensuring a smooth and secure transition process.
Other enhancements include support for Multi-Purpose Tokens (MPTs) in transaction asset definitions, providing more flexibility for token-based applications. The ledger’s API has been updated to include state aliasing for ripple-state and improved ledger entry filtering.
Bug Fixes and Performance Improvements
A fix has been implemented to resolve overlapping data types in the expected class, preventing potential conflicts that could cause errors during execution. Additionally, an issue that prevented Rippled from building on Windows using Visual Studio 2022 (VS2022) has been corrected, restoring Windows compatibility and making it easier for developers to compile and run Rippled on Windows-based systems.
Alongside this, a fix was applied to server definition prefixes, ensuring proper functionality across the XRPL ecosystem. Another issue was identified and resolved where submitting the connect admin RPC would trigger a failing assertion under certain conditions. Also, the assert name used in PermissionedDomainDelete was corrected, improving the accuracy and consistency of permissioned domain operations.
The update ensures smoother development, testing, and operation of the XRPL network by addressing data type conflicts, platform-specific issues, assertion failures, and build process inefficiencies.
