The XRP Ledger is preparing for two major technical upgrades aimed at facilitating large-scale financial operations. Both the Batch and Permission Delegation updates have entered their final voting phase, with activation expected in October 2026.
The XLS-56 "Batch" amendment and its 82% support level
The XLS-56 amendment, commonly referred to as "Batch," is designed to combine several operations into a single, indivisible sequence. According to the XRPL Foundation, this "all or nothing" execution model is intended to prevent funds from becoming trapped during commercial settlements if a single party fails to meet their obligations. By enabling atomic settlement, the update aims to significantly reduce counterparty risk for corporate users who require high-certainty payment flows.
As the report indicates, the Batch amendment has already secured 82 percent support among validators and has entered its mandatory waiting period. the network is currently on track to activate this feature on October 5, 2026, providing a foundation for automated, structured transactions that mirror the requirements of modern financial institutions.
Managing bank security through XLS-75 permissioning
To satisfy the rigorous security standards of traditional finance, the Permission Delegation amendment (XLS-75) is moving through the final stages of the voting process. This update allows organizations to assign specific operational roles to third-party services or internal departments without ever exposing the primary private key. This mechanism is expected to align the XRP Ledger more closely with established banking security models, where access is compartmentalized rather than centralized.
Validator support for XLS-75 is currently robust, ranging between 85 and 94 percent. If the current trajectory holds, the Permission Delegation feature is scheduled for activation on October 9, 2026, offering banks a way to manage institutional-grade accounts with greater flexibility and reduced risk of total key compromise.
Nik Bougalis's proposal for 64-bit architecture
Beyond these immediate amendments, the XRP Ledger is undergoing a deeper structural review to prepare for increased enterprise demand. Cryptographer Nik Bougalis has proposed a significant overhaul of the ledger's low-level architecture to enhance its fundamental security. This high-level plan involves transitioning the network to 64-bit components and eliminating the use of raw pointers,a move intended to harden the system against vulnerabilities.
This architectural shift is being considered alongside the Cleanup3_4_0 amendment,which validators are currently reviewing to stabilize Automated Market Maker (AMM) pools following the recent xrpld v3.4.0 software release.. These technical refinements suggest a concerted effort to move the ledger from a purely experimental state to a hardened, enterprise-ready environment.
Will fintech firms bridge the gap to liquidity?
While the technical foundation is being laid, several critical questions remain regarding the actual market impact of these upgrades. the source notes that activating these features in the code does not guarantee an immediate influx of liquidity. It remains unknown which specific major fintech companies will be the first to integrate these tools into commercial products, and there is no certainty on how quickly the transition from technical readiness to real-world adoption will occur. Furthermore, it is yet to be seen if the Cleanup3_4_0 amendment will provide the long-term stability required for AMM pools to attract significant institutional capital.
Comments 0