Why Did Loopring DEX Close? The 2026 Shutdown and $7.4 Million Return

Loopring's decentralised exchange stopped trading on 28 June 2026. Less than three weeks later, the team said it had returned $7,396,559.49 in cryptocurrency to 31,644 Ethereum addresses. The return involved 142 on-chain distribution batches and 73 assets.

That result makes Loopring's closure unusual. Rather than instructing every user to race through a withdrawal interface, the team collected balances and sent eligible funds directly to Ethereum mainnet addresses. The published figures describe the team's completed ERC-20 and ETH programme, not a guarantee that every NFT, smart-wallet or excluded balance was resolved.

Why Loopring stopped operating

The 28 June shutdown announcement explained that the exchange had never achieved the adoption needed to sustain its business. Loopring was an early Ethereum zero-knowledge rollup, but its original architecture did not offer the general-purpose virtual machine and composability later competitors provided.

The team also pointed to limited business development and delistings of its LRC token. It said newer zkEVM platforms had overtaken the specialist design. These were Loopring's explanations for ending operations, not allegations of missing reserves or a regulator's closure order.

The decision followed earlier retrenchment. Loopring had already retired its DeFi products during 2025 and previously wound down wallet services. By June 2026, trading, the automated market maker (AMM) and the relayer were being retired as well.

The Loopring homepage subsequently displayed a shutdown message. It should no longer be described as a functioning exchange simply because older tutorial pages remain indexed.

The $7.4 million asset return

Loopring initially promised to publish a snapshot of customer holdings. It planned a review period before moving assets back from its Layer 2 to Ethereum mainnet. Customers were told the team would pay the transaction fees.

The proposed approach required a contract change that allowed approved team-controlled addresses to execute the batch return. That meant users would not need to generate their own Merkle proofs or individually submit expensive Ethereum withdrawal transactions. It also made the published balance calculation and contract permissions unusually important.

The team later acknowledged an error in its first snapshot. Automated market-maker and liquidity-pool positions had been undercounted. The corrected dataset raised the planned allocation from approximately $7.17 million to $7.40 million, restoring about $223,000 of LP-related value.

The correction reportedly added 276 payouts, including holders whose earlier amounts fell below the minimum threshold. Loopring said no previously eligible address lost funds because of the revision. That is an important part of the record: even a planned orderly return needed an amended balance calculation.

By 17 July 2026, Loopring reported the ERC-20 and ETH programme complete. Its final transaction summary gave:

Loopring identified mainnet blocks 25550510 through 25551445 for the batches and published its distributor contract address. These are operator-reported final figures with transaction references, not an independently audited statement of all liabilities the project ever had.

The team said the returns matched the corrected published dataset one-to-one. That statement applies to the specified distribution programme. It must not be stretched into a claim that every address or asset category was included.

Did holders need to pay fees or submit a claim?

For eligible normal Layer 2 ETH and ERC-20 balances, Loopring said no. It covered Ethereum gas charges and executed the payouts itself. Holders were directed to check their original Layer 1 addresses.

The initial shutdown terms excluded balances valued below $10 from standard batch payouts. The revised snapshot brought some additional holders above that threshold. It did not establish that all very small balances were eventually reimbursed.

The published programme also contained special handling for smart-wallet addresses. These wallets could not necessarily accept funds through the same method as ordinary externally owned Ethereum accounts. A holder in that category needed to follow the operator's separate verification process.

Users should never submit a seed phrase to someone claiming to assist with Loopring refunds. A publicly visible Ethereum transaction is stronger evidence of a completed payment than a message or screenshot offering a new recovery portal.

NFTs followed a different path

Loopring's NFT return work continued after the ERC-20 distributions. Reporting on 20 July 2026 said the team had sent 2,046 NFTs to 1,241 Ethereum Layer 1 addresses across 283 collections.

That comprised 544 ERC-721 NFTs and 1,502 ERC-1155 NFTs, according to the reported completion update. Nine mainnet batches were executed.

Some items did not transfer successfully. The reported exceptions included 14 reverted transactions, 21 expired ENS domains and NFTs without a compatible mainnet collection. Certain Loopring Smart Wallet holdings required manual handling, with a stated verification deadline of 15 August.

It would therefore be inaccurate to write that the NFT programme resolved every exceptional asset. The July update documents substantial completed transfers but also records specific unresolved or excluded categories.

Why a trading shutdown did not erase historical data

After the service ended, Loopring's usual explorer and API endpoints stopped operating. But the project said historical Layer 2 data remained indexed and could be retrieved through The Graph.

A 10 July 2026 update said the surviving records covered accounts, balances, blocks, token transfers, trades, AMM pools and NFTs. The team also published developer guidance for querying that information.

This matters for former traders. A discontinued website does not necessarily mean the full transaction history is gone. At the same time, the ability to query old data is not the same as operating a live market or recovering an omitted asset.

The earlier CryptoBridge closure exposed the risks of relying on operator-maintained gateways. Loopring approached its exit through batch transfers and preserved blockchain records. The underlying technical dependencies were different.

Why the original Loopring design fell behind

Loopring's early strength was its specialist exchange architecture on Ethereum. Zero-knowledge proofs allowed transactions to be batched and verified on the base chain, reducing costs for trading.

But the Layer 2 was not a general-purpose smart-contract platform. Modern zkEVM competitors could support a much broader range of applications. Loopring's team said its lack of composability restricted adoption beyond the exchange use case.

The shutdown did not mean the Ethereum network or every zero-knowledge system stopped working. Nor did it erase the historical research associated with Loopring. It ended the operation of a specific protocol and its related services.

For comparison, Tapp Exchange's Aptos frontend shutdown left users potentially dependent on direct contract calls. Loopring instead organised its own return to Ethereum addresses. Both exchanges stopped trading in 2026, but the withdrawal procedures followed different technical paths.

What happened to LRC?

Loopring's shutdown did not automatically destroy the LRC token on Ethereum. However, the team cited exchange delistings and limited adoption as pressures on the business. A token remaining transferable is not proof that its original project continues to operate.

Customers should distinguish any LRC already held in their own Ethereum wallet from balances held inside the discontinued Loopring Layer 2. The latter were the focus of the organised return programme.

The closure announcement did not promise a future LRC price, a redemption at its former trading value or a new exchange that would support it. Historical token prices also cannot establish how much customer money was returned.

What former users can verify now

A former Loopring Layer 2 user should first identify the Ethereum address used with the service. Eligible direct returns were meant to land on Layer 1, so the appropriate place to check is the public Ethereum transaction history of that address.

They should compare the token contract, transfer amount and transaction origin against the published distribution details. The team described the TokenDistributor contract and 142 executed batches. Ethereum block explorers can independently show those on-chain records.

Smart-wallet holders or users with unusual NFTs should consult the original project communications and any verifiable updated instructions. The historical August 15 deadline must not be presented as a currently open support window.

There is no verified basis here to promise recovery of every excluded dust balance, blocked NFT or smart-wallet asset. Neither a token price nor the project's reported total return supplies a personal entitlement.

A closure measured by delivered assets

Most exchange-closure articles start with the announcement. For Loopring, the more revealing part came in July, when the team published a corrected snapshot and executed Ethereum transfers.

The result also shows why exchange exits require different evidence. A custodial company's bankruptcy, such as Knaken's Dutch proceedings, involves a trustee and creditor claims. Loopring returned eligible tokens through blockchain transactions.

Readers examining the history of closed cryptocurrency exchanges should therefore see both the 28 June service closure and the later July return milestones. Counting only the first date would miss most of what affected users.

Sources and reporting method

The Loopring shutdown notice covered by The Block establishes the business reasons and original return plan. Loopring's published distribution updates and corrected dataset announcement supply the team-reported transaction totals.

Longbridge's July 20 account records the NFT programme and exceptions. The July 10 historical-data update explains continued data access. L2BEAT independently records the June 28 shutdown milestone.

Information reviewed 25 October 2026. Figures are attributed to the reporting source and are not represented as an independent audit of every user account.