Following successful development network testing, XRPL Commons announced Friday that it has endorsed two network upgrades following a regular amendment voting session.
According to a community statement on X released on Monday, one of the two proposals voted on reached the voting threshold for validators to be integrated into XRPL. One previously supported amendment was rejected after flaws surfaced, and another amendment regarding token escrow is under consideration pending further testing.
Latest information on XRPL Commons voting
On Friday, January 23, we completed our regular amendment voting session.
Vote on the amendment:
🔷XLS-80 (Allowed Domains): Voted YES after successful Devnet test🔷XLS-81 (Allowed DEX): Voted YES after successful Devnet test…
— XRPL Commons (@xrpl_commons) January 26, 2026
XRPL Commons will participate in a validator-driven process to determine which changes will advance towards activation. Proposed amendments require continued support from a majority of validators before they are reflected on the ledger.
$XRP Validator Grant permission to credential-based network zones
After a successful Devnet test, 88% of validators voted in favor of the XLS-80 proposal, also known as Allowed Domains. The group said the change tracks an estimated effective date of February 4, 2026, 09:57:51 UTC.
This proposal introduces a restricted environment. $XRP A ledger that limits participation to accounts that hold authorized credentials. With this framework, only evidence that credentials are valid is recorded on-chain and no personal details remain on the ledger, so sensitive personal records are not exposed.
Allowed domains are gated zones that institutions can use, provided they verify the counterparty before doing business. This differs from the completely open access model that blockchain systems have previously used, such as XRPL.
XRPL Commons also voted in favor. XLS-81 Fixed “Allowed DEX”. It was proposed last year when software version v2.5.0 was released. According to $XRP On the amendment voting page, XLS-81 is not yet enabled, but is still in the voting stage.
This amendment requires 27 of the 34 verifier votes to meet the criteria. At the time of reporting, the consensus was 55.88%, with only 19 validators in favor.
This proposal is $XRP Ledger’s built-in exchange allows you to trade within a controlled setting. Participants, including financial companies operating under identity and reporting rules, must maintain authorized credentials before placing or fulfilling orders.
Permitted DEX instances have “allowed lists” that determine who can access a particular trading venue. Orders placed with these settings are kept separate from the main open order book. One type strictly limits activity to traders within a specific domain. At the same time, a separate structure allows traders to interact with both limited and limited. pool Prefer managed venues.
Frameworks are intended to work in parallel $XRP Ledger compliance mechanisms such as authorized trustlines, asset freezes, and clawback features enable regulated on-chain transactions.
However, the Commons switched its vote on XLS-56 (batch transactions) from “yes” to “no” after software issues were discovered during consideration. According to the organization, bug Internal transactions within a batch that appear to be signed correctly may verify that they are not. Commons recommended that developers make fixes before support for the ledger is reinstated.
XRPL token escrow upgrade awaits further testing
The XLS-85 amendment, which extends escrow functionality to tokens issued on other chains, did not change the position. XRPL Commons said further testing is planned ahead of the next voting session.
According to the proposed semantics, the ledger can store IOUs and multi-purpose tokens in escrow. Coin releases can also be influenced by conditions such as time, specific events, and programmable rules.
Token issuers will be prohibited from placing their assets in escrow, and will not be able to retrieve assets under escrow during the lock period. Transfer fees for a particular token are calculated at the time of escrow creation.
This fix is also introduced in software version v2.5.0 and requires 80% verifier support to enable. However, it does not provide direct cross-chain escrow functionality as that limit is currently out of scope.
Beyond the revised decision, XRPL Commons stated that the fee-based reserve will remain at 1 $XRPthe upper limit of owner reserve is 0.1. $XRP. All other outstanding amendments had already been voted on in previous sessions, and no new proposals were added to the agenda this round.
The next amendment voting session is scheduled for February 6th, when validators will revisit pending proposals and review test results.
