The XLS-56 feature eliminates the risk of funds becoming stuck in a commercial settlement if one party fails to meet its obligations. XLS-75, in turn, addresses strict banking security requirements by allowing organizations to distribute operational roles flexibly.
The upcoming upgrade centers on two automation tools:
- Atomic batches (BatchV1_1 and fixBatchV1_2 amendments): Validator support currently stands at 85–94%, with activation expected on October 9, 2026. The feature allows multiple operations to be combined into a single, indivisible batch that executes on an “all or nothing” basis.
- Permission delegation (PermissionDelegationV1_1): The amendment has secured 82% support and entered its waiting period. Activation is scheduled for October 5, 2026. It allows organizations to delegate account permissions to third-party services or departments without revealing the primary private key.
Both features are expected to support institutional-grade account management. Meanwhile, validators are also gathering votes for the related fixCleanup3_4_0 amendment, which is needed to stabilize AMM pools in the recent xrpld v3.4.0 software release.
A parallel development: Why one of XRPL’s principal creators has returned
The ecosystem’s push into the corporate market is also accompanied by a return of technical expertise. Nik Bougalis, a key cryptographer and Ripple pioneer who left the project in 2022, has officially returned to work on the XRPL core.
In his high-level plan, he has already proposed a substantial overhaul of the ledger’s low-level architecture. Moving the network to 64-bit components and eliminating raw pointers are intended to significantly improve the ledger’s security ahead of potential institutional demand.
Activating these features in the code creates a foundation; it does not bring an immediate influx of liquidity. The speed at which major fintech companies incorporate the tools into real products will determine whether this technological upgrade becomes a driver of long-term demand for the native coin, $XRP.
