Developer xrpl_adam scanned the entire XRP Ledger and recovered 750,218 XRP worth over $1M from expired escrows holders who forgot to claim.
Escrow unlocks on the XRP Ledger just hit a spike nobody fully expected. Over $1,000,000 worth of XRP sitting idle in forgotten timelock contracts has been returned to holders. All of it recovered through a single community-led scan of the entire ledger.
The total came to 750,218 XRP. That figure surfaced after developer xrpl_adam went through the ledger manually, hunting for escrows where timelocks had expired but nobody had submitted an EscrowFinish transaction to actually claim the funds.
The Forgotten Funds Nobody Came to Collect
According to Vet_X0 on X, most of these escrows were created by individual holders and community members. The timelock on their contracts expired. But they either forgot about them entirely, or had no idea the process required a separate transaction to release funds back to themselves.
That last part catches a lot of people off guard. On the XRP Ledger, an escrow reaching its expiry date does not automatically return the tokens. Someone must actively submit a cancellation or finish transaction. Without that step, the XRP just sits there. Locked. Technically expired. Going nowhere.
Vet_X0 confirmed on X that xrpl_adam completed the full ledger scan and submitted the necessary transactions to finish those escrows, returning the funds to the original holders.
First Ledger Now Runs This Automatically
The fix did not stop there. As Vet_X0 posted on X, xrpl_adam also set up @First_Ledger to scan the ledger periodically going forward. The tool will now detect expired escrows continuously and process them before more funds go unclaimed for extended periods.
That matters for the XRPL community as a whole. Timelock escrows are common. Holders set them up, sometimes years in advance, and then simply lose track. The underlying mechanism on the XRP Ledger is straightforward enough: a time-based escrow enters a “ready” state after the FinishAfter time passes, then transitions to expired if a CancelAfter time is also set and nobody acts. Once expired, the XRP is locked out of use but still sitting in a ledger object waiting for someone to cancel it.
What Actually Happens When an Escrow Expires
The XRP Ledger’s escrow system covers three types of contracts: time-based, conditional, and combination. For time-based escrows, funds become accessible after a set period. If a CancelAfter field was included and the window closes without action, the escrow flips to expired.
In the expired state, no one can finish it. It can only be canceled. And cancellation sends the tokens back to whoever originally created the escrow, not to the intended recipient. Most of the 750,218 XRP recovered in this scan came from exactly that scenario: holders who created escrows for themselves, forgot, and left the contracts sitting in an expired state on-chain.
This kind of community tooling is exactly what projects like Vlightup have built on top of XRPL’s native escrow function, using programmable conditions and automated settlement layers to remove the manual step entirely. For individual holders operating without that infrastructure, the gap is real.
Over $1 million sitting unclaimed. Not from a hack. Not from a protocol bug. Just from people not knowing one transaction stood between them and their own XRP.
First_Ledger now handles that gap continuously.
