Key Highlights
- XRP Ledger’s Token Escrow amendment passed with 28 yes votes and starts a two-week activation period.
- The amendment lets users lock Trustline tokens, MPTs, stablecoins, and meme coins in escrow safely.
- Issuers must enable specific flags, like Allow Trust Line Locking or Can Escrow, for tokens to be held in escrow.
The XRP Ledger Token Escrow amendment has officially entered its activation period. The update was confirmed by XRP Ledger validator Vet after the proposal reached the required support from network validators.
The proposal has now started its two-week activation timer following an 82.35% consensus, backed by 28 “yes” votes. Data from xrpscan shows the expected activation date is scheduled for February 12, 2026, at 9:21:01 p.m. UTC. A live countdown is already running, showing just under two weeks left before the feature becomes active on the XRP Ledger main network.
In an X post on Friday, Vet explained that this amendment will allow users to place many different tokens into escrow, not just XRP. This includes stablecoins like RLUSD, project tokens, meme coins, and even real-world asset tokens issued on the XRP Ledger.
He described the Token Escrow as an important tool because it gives the ecosystem more ways to lock tokens safely and use them in new financial setups.
“Token Escrow allows you to escrow any issued on the XRP Ledger, think of RLUSD, Meme Coins, Real World assets. Important tool for the ecosystem!” he wrote.
How Token Escrow works
The amendment extends escrow beyond XRP to fungible tokens, making it possible for Trustline Tokens and Multi-Purpose Tokens (MPTs) to be held in escrow directly on the ledger. The amendment brings changes to ledger objects, transaction types, and transaction processing rules. These updates are designed to support token escrows while still keeping the ledger secure and respecting the controls set by token issuers.
The Token Escrow amendment, also known as XLS-85, allows users to lock tokens in time-based escrows or condition-based escrows without needing a third-party service. This makes it easier for projects to create clear vesting schedules and complete trustless deals directly on the blockchain. A companion fix amendment is also planned to solve a bug linked to transfer fees on multi-purpose tokens. Both changes still require validator approval, with at least 80% consensus needed for final activation.
Important issuer rules also apply. For Trustline Tokens to be escrowed, the issuing account must enable the Allow Trust Line Locking flag. For MPTs, issuers must turn on the Can Escrow and Can Transfer flags when creating the token.
They cannot create escrows with their own issued tokens, but they can still receive escrowed tokens as recipients. If a token requires authorization, the sender must be pre-approved by the issuer before creating an escrow, and both sender and recipient must remain authorized throughout the process.
Recent XRPL upgrades
The amendment comes during a busy period for XRP Ledger development. XRPL recently released version 3.1.0, which includes Single Asset Vaults, a Lending Protocol, and bug fixes.
At the same time, several fixed amendments from XRPL version 3.0.0 have already gone live on the XRP Ledger mainnet. These include:
- fixTokenEscrowV1
- fixIncludeKeyletFields
- fixMPTDeliveredAmount
- fixAMMClawbackRounding
- fixPriceOracleOrder
The fixTokenEscrowV1 amendment fixes a minor accounting error in the handling of MPT escrows.
Another proposal, the permissioned domains amendment (XLS-80), has also reached a majority vote and is now in its own countdown period, with about 4 days and 18 hours remaining, according to xrpscan data.
All these changes show that the XRP Ledger is moving quickly, with multiple upgrades being introduced and voted on by validators in the coming days.
Also Read: US Court Tosses XRP Investor Lawsuit Against Ripple
