TL;DR
- XRPL Commons approved two key upgrades: Permissioned Domains and a Permissioned DEX.
- A third amendment (Batch Transactions) was rejected after a critical bug was found.
- The next amendment voting session is scheduled for February 6, 2026.
XRPL Commons backed two network upgrades on Friday after completing its routine amendment voting session, following successful testing on the development network. The community organization released the statement on X on Monday.
One of the two voted proposals reached the validator voting threshold for integration into XRPL. An amendment backed earlier was rejected after a flaw emerged, while another amendment on token escrow remains under review pending additional testing.
XRPL Commons participates in the validator-driven process that determines which changes advance toward activation. Amendments require sustained support from a supermajority of validators before going live on the ledger.
Validators Approve Credential-Based Network Zones
88% of validators voted in favor of the XLS-80 proposal, also known as Permissioned Domains, after successful Devnet testing. The group indicated the change tracks an estimated activation date of February 4, 2026, at 09:57:51 UTC.
The proposal introduces restricted environments within the XRP Ledger that limit participation to accounts holding approved credentials. The framework does not expose sensitive personal records, as only proof that a credential is valid gets recorded on-chain, while any personal details remain off the ledger.
Permissioned Domains are gated zones that institutions can use, provided they verify counterparties before transacting. The measure differs from the fully open access model that blockchain systems used previously, including XRPL.
XRPL Commons also voted in favor of the XLS-81 “Permissioned DEX” amendment, proposed during the launch of software version v2.5.0 last year. According to the XRP amendment voting page, XLS-81 has not yet been enabled but remains in the voting phase.
The amendment requires 27 out of 34 validator votes to meet its threshold. At the time of reporting, consensus reached 55.88%, with only 19 validators in favor.
The proposal expands the XRP Ledger’s built-in exchange by allowing trading inside controlled settings. Participants must hold approved credentials before placing or filling orders, including financial firms operating under identity and reporting rules.
Permissioned DEX instances have “allow-lists” that determine who can access a given trading venue. Orders placed in these settings remain separate from the main open order books. One type limits activity strictly to traders within a specific domain, while another structure lets traders interact with both the restricted pool and the public exchange, giving priority to the controlled venue.
The framework is designed to work alongside XRP Ledger compliance mechanisms, such as authorized trustlines, asset freezing, and clawback functions, to enable regulated on-chain trading.
However, Commons switched its vote on XLS-56 (Batch Transactions) from yes to no after discovering a software issue during review. According to the group, the bug could validate inner transactions in a batch that appeared properly signed when they were not. Commons recommended that developers make fixes before its support on the ledger could resume.
Token Escrow Upgrade Awaits Further Testing
The XLS-85 amendment that extends escrow features to tokens issued on other chains saw no position change. XRPL Commons said more testing is scheduled ahead of the next voting session.
According to the proposal’s semantics, the ledger could hold IOUs and Multi-Purpose Tokens in escrow. It could also impact coin releases by conditions such as time, specific events, or programmable rules.
Token issuers would be barred from placing their own assets into escrow, and any assets under escrow could not be clawed back during the lock period. Transfer fees for certain tokens would be calculated when the escrow is created.
The amendment was also introduced with software version v2.5.0 and would require 80% validator backing to activate. Still, it does not provide direct cross-chain escrow functionality, as the limitation falls outside its current scope.
Beyond amendment decisions, XRPL Commons said the fee-based reserve remains at 1 XRP, while the owner reserve is capped at 0.1 XRP. All other open amendments had already been voted on in prior sessions, and no new proposals were added to the agenda in this round.
The next amendment voting session is scheduled for February 6, when validators will revisit pending proposals and review test results.
