0x61e531f561e5…61e531f8
0xTria: $183,000 in Duplicate Lighter Deposits Remains Unreturned
About $183,000 remained unreturned after 395 duplicate transfers sent roughly $527,000 to 10 accounts during a Relay solver failure, according to 0xTria’s Nov. 17 post.

Outputs
On Nov. 16, a Relay solver replay produced 395 transfers in 25 minutes to 10 accounts, about $527,000 combined, according to 0xTria.
By 0xTria’s Nov. 17 post, about $345,000 had been returned and roughly $183,000 remained outstanding.
0xTria attributed the issue to Relay, a cross-chain bridge, rather than Lighter.
One account deposited $3,200, received 70 duplicate payments and later returned $225,000.
A third account withdrew $33,000, redeposited it the next day and returned the full sum.
About $183,000 in duplicate Lighter deposits remained unreturned as of 0xTria’s Nov. 17 post, following 395 repeated transfers worth roughly $527,000 to 10 accounts. The arb.sh founder attributed the incident to Relay, a cross-chain bridge, rather than Lighter, and said the transaction records can be checked in Lighter’s block explorer.
What caused the duplicate deposits?
The incident occurred on Nov. 16. According to 0xTria, Relay’s solver remained idle during the Lighter withdrawal freeze, then replayed paused payment requests after resuming. The replay generated 395 transfers in 25 minutes, which 0xTria characterized as “duplicate payments.”
That sequence attributes the replay to Relay’s solver, according to the source. The source provided no independent incident report or corroborating statement from either company.
The 395-transfer burst averaged nearly 16 transfers per minute. The source provides no transaction-by-transaction timeline, so that average does not establish that all requests arrived together.
Operationally, the solver appears to have treated queued requests as executable after service resumed. That is a request-processing failure, not evidence that Lighter itself authorized each payment twice, and the source reaches no finding on whether recipients knew the payments were duplicated. In plain terms, the evidence supports a replay failure, but not a conclusion about intent.
How much came back?
By the Nov. 17 update, recipients had returned about $345,000, leaving roughly $183,000 outstanding. On the source’s rounded figures, the returns covered about 65% of the $527,000 sent, so approximately 35% remained outstanding. The identified activity breaks into three disclosed cases:
- One account deposited $3,200, received 70 duplicate payments and later returned $225,000.
- Another deposited $6,000, received 26 duplicate payments and moved $156,000 through Relay 15 minutes later.
- A third account withdrew $33,000, redeposited the funds the next day and returned the full sum.
The source does not reconcile the $345,000 aggregate with the three examples, so the $156,000 movement should not be treated as a confirmed repayment. The first account returned $221,800 more than its $3,200 deposit, while the second moved 26 times its $6,000 deposit. In the disclosed data, recoveries were partial and staggered, not a single coordinated reversal.
Can the transfers be checked?
0xTria said the transaction records can be checked in Lighter’s block explorer. That provides a route to test the 395-transfer sequence, the 10 recipient accounts, and the disclosed deposits and returns against on-chain history.
The available record does not include addresses, transaction hashes or a complete ledger, so the figures remain 0xTria’s analysis rather than a transaction-level reconstruction. Public records may test the account, but this source does not independently prove every figure.
What remains unresolved?
The source does not explain whether the remaining $183,000 is recoverable or whether account owners recognized the duplicate credits. It provides no response from Relay or Lighter, no reimbursement commitment and no remediation deadline.
That omission matters because the reported sequence spans two systems: a freeze on Lighter withdrawals and a Relay solver that resumed and replayed requests. Neither the cause classification nor the $345,000 recovery total establishes that no further losses will emerge. Until those gaps are closed, the $183,000 balance remains an open exposure.
Bridge-level payment handling needs a control that distinguishes a retried instruction from a new transfer; otherwise, a resumed service can repeat a queued payment. The source did not report whether Relay installed such a control, whether Lighter compensated users, or whether legal recovery proceedings are under consideration.
No remediation deadline was announced, so the next hard checkpoint is whether recipients return the remaining $183,000. A durable fix at the bridge level would require Relay to prevent queued requests from executing again after a freeze; the source reported no completed control, and recurrence risk remains unverified.
via tokenpost.com (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles