On February 12, RippleX, the development division of Ripple, launched announced that Token Escrow is now live on the XRP Ledger’s (XRPL) mainnet.
The change, called Token Escrow (XLS-85), extends conditional locking and release to trustline-based tokens (IOUs) and Multi-Purpose Tokens (MPTs).
This extends the network’s escrow function beyond XRP to cover issued assets used for stablecoins and tokenized instruments.
The upgrade comes as stablecoins continue to expand as crypto’s most established product line. Crypto Slates Data shows that the total circulating supply of these assets hovers around $308 billion and continues to rise week after week.
At the same time, tokenized real-world assets also scale in parallel. Data from RWA.xyz shows that tokenized US Treasuries on public chains are valued at roughly $10 billion, with tens of billions more in categories such as private credit and commodities.
For XRPL, that market context is the point. The new feature is less about adding another optional tool for developers and more about introducing an on-chain settlement primitive that institutions can use to move assets only after conditions are met.
Escrow goes beyond XRP, but the issuers retain control
XRPL has supported escrow for years, but this feature historically only applied to XRP.
Token Escrow extends that scope to issued tokens, where most institutional use cases occur.
On XRPL, stablecoins, tokenized Treasuries and other tokenized instruments are generally not recognized as native coins. Instead, they are viewed as issued assets.
XRPL documentation makes the issuer control model explicit. Token escrow is allowed at the issuer and token level and is not automatically available for every item issued on the network.
For trustline tokens, issuers must enable the ‘Allow Trust Line Locking’ flag before escrow can be used on that issuance. For MPTs, issuers must enable ‘Can Escrow’ (and related flags) before an issue supports escrow.
That design matters to regulated issuers, who often want policy hooks and control points embedded in the asset lifecycle.
It also means that the adoption process is not automatic. A live amendment doesn’t guarantee immediate volume if issuers don’t sign up and if wallets and venues don’t build user flows around it.
The feature is designed for workflows that require conditional settlement. In the traditional financial world, these terms are handled through intermediaries, contracts and operational processes.
On-chain settlement can compress these steps as the base ledger locks the value and only releases it when predefined rules are met.
In practical terms, token-enabled escrow can support delivery versus payment settlement, timed distributions and structured payouts, over-the-counter trade settlement that reduces counterparty risk, and collateral and margin mechanisms that require conditional release rather than immediate transfer.
Each of these workflows becomes easier to model when the escrow primitive can hold the same types of assets that institutions use in settlement, rather than forcing the process to run only through XRP.
XRPL’s reserve model converts asset growth into structural XRP demand
XRPLs reserve model creates a second-order mechanism that can translate increased ledger usage into base XRP balances held for operational reasons, rather than for transaction fees.
On Mainnet, accounts must have a base reserve of 1 XRP plus 0.2 XRP per ledger object owned (owner reserve). These requirements were sharply reduced on December 2, 2024, a change that made resource-intensive applications more feasible.
That’s important because Token Escrow is an object-driven function. Each escrow created on the ledger is an owned object. As escrow-based settlement workflows scale, they can increase owner reserve requirements for the entities that own these properties.
A simple scenario scope illustrates the mechanical relationship.
If Token Escrow adoption yields an additional 100,000 escrow objects, this means an incremental 20,000 XRP in owner reserves (100,000 × 0.2). With 1,000,000 new escrow objects, the total XRP is 200,000. At 10,000,000 this is 2,000,000 XRP.
These numbers are not a prediction of adoption, nor are they price calls. However, they show how XRPL’s design ties usage to reserve requirements.
For institutions, that reserve functions more as operational collateral than a fee, and remains so because the system requires resource-intensive workflows to be executed.
This is one of the reasons why XRPL developers focus on ‘plumbing’ features.
In a reserves-based model, the unit economics of growth are tied to whether there are more meaningful objects in the ledger, not to whether transaction costs increase.
The bigger push is an authorized stack, not a single amendment
Meanwhile, Token Escrow is being introduced alongside a broader set of changes that XRPL developers have framed as a “authorized” toolkit, designed for regulated participation in a public ledger.
Allowed domains (XLS-80) were activated on Mainnet earlier this month.
These domains are controlled environments that “do nothing on their own” but enable other functions, including authorized decentralized exchanges and lending protocols, that can restrict access and support on-chain compliance.
RippleXDev noted on X that the Permissioned DEX had reached validator consensus to activate shortly afterwards.
When viewed as a combined architecture, these features answer three different questions for institutional participants.
Permissioned Domains address that is allowed to participate in a transaction. Token Escrow addresses how assets are settled conditionally and securely. Finally, the Permissioned DEX addresses where compliant liquidity and price discovery occur.
These trio of characteristics suggest a shift in the XRPL’s fundamental value proposition.
It is not only seen as a payment chain with a central limit order book, but is also increasingly coming into play as an institutional settlement layer defined by closed participation, controlled locations and native conditional settlement.
The premise is simple. Stablecoins and tokenized assets are growing in size and regulated entities often prefer not to interact with open pools where participant identities and access controls are undefined.
If the ledger can support gated participation and conditional settlement without being completely dependent on external systems, it becomes easier to map real-world compliance and operations onto on-chain rails.
What comes next and what could delay it?
The activation of Token Escrow represents a forward-looking bet that the future of blockchain lies in compliance-compliant stacks rather than purely permissionless systems.
The first pillar is regulated liquidity formation, where approved venues reduce the compliance friction that currently prevents many institutions from accessing open liquidity pools.
The second is the standardization of the RWA settlement. With tokenized treasuries and other assets already scaling, conditional settlement primitives can make production workflows easier to dispatch.
The third pillar is expanding the usefulness of stablecoin beyond simple transfers. Escrow capabilities enable structured settlement and treasury automation, use cases that are more like back-office operations than active trading.
Significant implementation risks remain as issuers must opt for token escrow capabilities by enabling the required flags. At the same time, wallets and exchanges must integrate the new flows to make them accessible to users.
Furthermore, the rise of permissioned domains poses the risk of fragmenting liquidity if the ecosystem becomes too split between open and closed markets.