Ripple Technology and XRPL Upgrades
Understand recent XRP Ledger and Ripple Custody updates, including XRPL 3.3.0, and why a software release does not confirm mainnet activation.
Ripple product updates and XRP Ledger upgrades affect different systems. Ripple Custody updates change a commercial digital asset management product. XRP Ledger releases update network server software and may introduce amendments that require separate activation. A product launch or software release alone does not establish that a network feature is enabled. Sources: Ripple Custody release notes, XRPL amendment documentation.
Two examples are the August 6, 2026 release of XRP Ledger server software version 3.3.0 and Ripple Custody version 1.40, whose phased SaaS deployment began August 17. These are separate release tracks. Sources: XRPL 3.3.0 release notes, Ripple Custody 1.40 release notes.
| Update | System affected | Date stated in the source | What the date means |
|---|---|---|---|
| XRPL 3.3.0 | XRP Ledger server software | August 6, 2026 | Software release; included amendments have separate activation requirements |
| Ripple Custody 1.40 | Ripple's custody product | August 17, 2026 | Start of phased deployment across hosted environments |
Sources: XRPL 3.3.0 and Ripple Custody 1.40. These are selected releases, not a complete list of 2026 updates.
What did XRPL 3.3.0 introduce?
The release included amendments for atomic batch transactions, confidential Multi-Purpose Token transfers, configurable token properties, account permission delegation, and reserve and transaction sponsoring. It also contained bug fixes and build improvements.
These features address different needs. Batch transactions concern coordinating multiple operations. Permission delegation concerns authorizing another account to perform specified actions. Sponsoring concerns covering reserves and transaction costs. Confidential transfers concern Multi-Purpose Tokens, so that feature should not be described as blanket privacy for every XRP transfer. Source: XRPL 3.3.0 release notes.
Does inclusion in a release mean a feature is live?
No. Software support and network activation are separate milestones.
The XRP Ledger uses an amendment process for changes affecting transaction processing. Amendments require sustained validator support over a two-week period before activation. A release announcement therefore does not establish that every included amendment is enabled on mainnet. Source: XRPL amendment documentation.
Readers should check the status of the specific amendment in the official Known Amendments reference. This article describes release contents and does not assert current activation for the listed features.
Where do Ripple's product updates fit?
Ripple Custody has its own versions and deployment schedule. Its version 1.40 documentation describes a phased rollout across hosted environments, illustrating why a product release date and availability in a particular customer environment can differ. Source: Ripple Custody 1.40 release notes.
When assessing any technology headline, identify the system, the capability, and its deployment status. Then ask whether there is evidence of customer use. That sequence makes it easier to distinguish engineering progress from adoption and to connect an update to something a user or institution can actually do.
For the organizations involved in the wider ecosystem, see our Ripple partnerships guide.
For the release-specific announcement and its status at publication, read our August 2026 report on XRPL 3.3.0. That dated report should not be used as a current amendment-status check.
Frequently asked questions
Where can I check whether an XRP Ledger amendment is enabled?
Check the amendment's entry in the official Known Amendments reference. A release note describing support for an amendment is different from confirmation that it is enabled on mainnet.
Does a Ripple Custody release upgrade the XRP Ledger?
Ripple Custody and XRP Ledger server software have separate release tracks. A custody product version does not, by itself, activate an XRP Ledger protocol amendment.
Continue learning
Primary sources
Use these first-party references to verify protocol details and time-sensitive platform information.
Sourcing: factual reporting uses the linked Ripple announcements and XRP Ledger documentation. Interpretations of what those sources establish are editorial analysis. Dates identify the cited events and releases, not a claim that every announced integration is live.