- XRPL 3.3.0 is scheduled for launch next week and will have five amendments, among which two will be redesigned due to security fixes.
Batch and Permission Delegation are back, having been fixed, although still requiring validation by the validators.
A software update does not implement amendments, since the validators first need to validate them.
XRPL 3.3.0 release is expected next week, bringing five protocol amendments back into focus after earlier development work addressed security issues that previously halted part of the rollout.
The upcoming software version, xrpld 3.3.0, has been tracked through the XRP Ledger Foundation’s GitHub milestone, where contributors prepare changes for each release before they become available to node operators.
While the release package is nearing completion, the amendments included in the update are not automatically activated across the network. Instead, each proposed protocol change must still complete the XRP Ledger’s validator approval process before taking effect.
XRPL 3.3.0 Release Returns Two Revised Amendments
RippleX Head of Product Jazzi Cooper said the upcoming release will include Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT.
Among the five amendments, Batch and Permission Delegation return after earlier versions were removed from consideration because of security concerns identified during development.
Previous Security Issues Prompted Redesign
Batch previously entered the validator voting process before researchers identified a signature validation issue that could have allowed unauthorized transactions from accounts without possession of their private keys.
Following the discovery, validators were advised not to support the amendment, while an emergency server update marked it as unsupported before activation. The amendment never became active on the main network, and no user funds were reported lost.
Source: Whale Insider
Permission Delegation was also withdrawn after developers disclosed a separate vulnerability. The issue could have allowed one account to charge transaction fees to another account, creating the possibility of draining XRP balances. Documentation later marked the original version as obsolete pending a revised implementation.
The new package brings both amendments back after modifications to their implementation to solve the existing vulnerabilities.
Features of the XRPL 3.3.0 Release
In addition to amendments that have been improved, the XRPL 3.3.0 release also has three more protocol proposals.
Three Additional Amendments Join the Update
Confidential MPT combines zero-knowledge proofs with elliptic-curve encryption to keep Multi-Purpose Token balances and transfer amounts private while allowing authorized verification when required.
Sponsored Fees and Reserves enable one account, such as a financial institution or platform operator, to pay XRP transaction fees and reserve requirements on behalf of another account. The feature removes the requirement for every participant to acquire XRP before submitting transactions.
Dynamic MPT allows token issuers to determine during token creation which properties may be modified later. The approach enables updates to selected token settings without requiring a complete migration to a newly issued token.
Cooper said the XRP Ledger has already demonstrated support for tokenized assets at scale. According to his remarks, the proposed amendments are intended to support activities including global transfers, trading, collateral use, and settlement through additional protocol capabilities.
Software Release Remains Separate From Network Activation
Although xrpld 3.3.0 is expected to become available next week, publication of the software does not activate the amendments across the XRP Ledger.
Validator Approval Still Required
Protocol amendments require approval from at least 80% of trusted validators for two consecutive weeks before they become active on the network. This governance process means validators, rather than software publication alone, determine whether proposed protocol changes are adopted.
The distinction remains important because previous amendments have failed to meet the required approval threshold. Batch previously entered the voting process before being withdrawn following the security findings, while other proposed amendments have also remained below the activation requirement.
In relation to the period covered by the information, the five amendments are supposed to be included in the software release, although the timetable for their network activation has not been determined yet.
Operators Waiting for Final Release Information
The XRPL 3.3.0 release has a direct impact on the node operators and validators who are using the reference server software to participate in the consensus in the XRP Ledger.
The software update is complemented by ongoing developments on the XRP Ledger’s infrastructure that include the XRPL toolkit by Ripple that adds support for XRP and RLUSD in x402 payments, a partnership between Amazon and Ripple aimed at decoding XRPL logs, and institutional development including a single-asset vault effort by Soil.
Despite the expected release next week, no exact deployment date has been confirmed. The published milestone and accompanying release documentation remain the primary sources for finalized implementation details until xrpld 3.3.0 is officially released.
FAQs
What is included in the XRPL 3.3.0 release?
The release is expected to include five amendments: Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT.
Will the amendments go live right after their release?
No. Every amendment should be accepted by no less than 80% of trusted validators for two weeks in a row.
Which amendments were withdrawn earlier?
Batch and Permission Delegation were removed after security vulnerabilities were identified. Both return in revised form in the upcoming software release.
