LoopExchange

A next-gen, community-first, Layer 2 NFT marketplace: (R.I.P.)

[LoopExchange @LoopExchange]

@H4llucinogenUsn Basically we went from a bunch of scripts with an okayish interface to a serious aggregator/community app we all deserve. It just grew so much in the process that it needed a proper rewrite/redesign which we handled as if it was a paid project (whilst we handled real clients too)

[LoopExchange @LoopExchange]

📢 Soon we'll launch a Loopring NFT Museum/Preservation project that lets everyone look at their wallets again, browse all L2 collections, redeploy to L1 for all holders or remint legitimate copies tied to official data & more. Work in progress (core ready & working). Stay tuned!

[Loopring @loopringorg]

Loopring L2 NFT return: it is also done.

━━━━━━━━━━━━━━━━━
🔹 What executed
━━━━━━━━━━━━━━━━━

9 sendNfts() batches confirmed on Ethereum mainnet, blocks 25571319 to 25571397:
- Delivered: 2,046 NFTs (544 ERC‑721 + 1,502 ERC‑1155)
- Recipients: 1,241 L1 addresses
- Collections: 283
- Held and sent every NFT (the "from" on each transfer): 0x0BABA1Ad5bE3a5C0a66E7ac838a129Bf948f1eA4

━━━━━━━━━━━━━━━━━
🔹 What was not sent on‑chain (and why)
━━━━━━━━━━━━━━━━━

Full honesty, same as the token return. Apart from the smart‑wallet holds below, only a small set could not be moved on‑chain — none is lost, and each is explained.

14 transfers reverted at the token level and were left untouched rather than risk a failed or lost transfer. All 14, in full:

Blocked by the collection itself (5) — the contract refuses the transfer no matter who sends it, so they stay in the recovery contract until the collection's own rules allow a move:
1 SAW Games Pass (0x347e…5ceb) token #205 → 0x2ead…ac49 "Sales & transfers are locked during games"
2 SAW Games Pass (0x347e…5ceb) token #223 → 0x7ef4…4cd7 "Sales & transfers are locked during games"
3 SAW Games Pass (0x347e…5ceb) token #388 → 0x2803…c2e7 "Sales & transfers are locked during games"
4 SAW Games Pass (0x347e…5ceb) token #2240 → 0xff39…f9b8 "Sales & transfers are locked during games"
5 Wu Tiger Clan (0xf4ac…9d6e) token #7286 → 0xdf7b…c597 "!TRANSFER_ROLE" (access‑gated)

Recipient can't receive the NFT (9) — the L1 owner address is a contract with no ERC‑1155 receiver, so delivery reverts by design. Each NFT is intact and can be redirected to an address able to hold it:
6 OpenSea Shared Storefront (0x495f…7b5e) 1 edition → 0x190a…71ab empty revert
7 OpenSea Shared Storefront (0x495f…7b5e) 2 editions → 0x19cc…ffcd empty revert (2 transfers)
8 Unnamed ERC‑1155 (0x916f…bdbf) 1 edition → 0x7307…047f transfer to non‑ERC1155Receiver
9 Unnamed ERC‑1155 (0x916f…bdbf) 1 edition → 0x7292…2902 transfer to non‑ERC1155Receiver
10 Unnamed ERC‑1155 (0x9300…9980) 1 edition → 0xa0a6…8369 transfer to non‑ERC1155Receiver
11 Rarible (0xb66a…18b8) 1 edition → 0x19cc…ffcd undecodable revert
12 Rarible (0xb66a…18b8) 1 edition → 0x3207…c9e6 empty revert
13 Rarible (0xb66a…18b8) 1 edition → 0x00b4…c948 undecodable revert

(13 recipient‑units, 14 transfers — line 7 carries two token ids. Full rows, ids and raw revert data: nft/phase-4/reverting-nfts.json.)

Separately, 21 .eth ENS names could not be returned: each had expired on ENS and, past the 90‑day grace period, was released, so the name no longer exists on L1 to transfer — recoverable only by re‑registering it on ENS. All 21, by name, expiry, and the L2 owner it was headed to:

# name expired (UTC) L2 owner
1 gabriel🦊.eth 2022-08-19 0xa980…cee9
2 52252252.eth 2022-12-11 0xc95e…f6a9
3 h4ze.eth 2023-05-03 0x777d…e4be
4 bestpcrepair.eth 2023-06-15 0x6aa4…c6ba
5 dxsta.eth 2023-06-17 0xce05…69a4
6 purplecircle.eth 2023-07-14 0xfb61…5503
7 kartoffelsalat.eth 2023-08-10 0xa660…18be
8 spookyboogie.eth 2023-09-07 0x6f93…c0dd
9 ronjuicebox.eth 2023-09-14 0xdf7b…c597
10 ibuythatforadollar.eth 2024-05-28 0xf06b…e5c1
11 bellzor.eth 2024-06-28 0x5fb1…ce0c
12 bibsy.eth 2024-08-07 0x0b99…4c59
13 v-batistella.eth 2024-08-07 0x3778…ce3d
14 banana4u.eth 2024-08-31 0x20ee…ada4
15 ryanlackey.eth 2025-01-04 0xdcb9…5e9c
16 tercar.eth 2025-05-25 0x384c…8ab4
17 marisp.eth 2025-06-01 0xa647…ad06
18 diamondheartdao.eth 2025-06-05 0x4812…2e68
19 wutangwitit.eth 2025-06-09 0x0ed3…1dce
20 ajumma.eth 2025-07-12 0x7c3b…9f1c
21 purplecorvette.eth 2025-07-19 0x5c2d…aad0

(Each name was recovered from its on‑chain ENS registration and verified: keccak256(label) equals the ERC‑721 token id in the snapshot. Full token ids and per‑name expiry timestamps: nft/phase-2/EXCLUSIONS.md and nft/phase-2/missing-detail.json.)

Separately again: NFTs minted natively on Loopring L2 have no L1 counterpart — their collection was never deployed to Ethereum — so there is nothing on mainnet to return them to, and they are outside the scope of this on‑chain return. Their canonical minters can redeploy the collections to Ethereum and re‑mint to holders using the published L2‑only files (nft/phase-1/nfts-l2-only-*.csv).

━━━━━━━━━━━━━━━━━
🔹 Verify it yourself
━━━━━━━━━━━━━━━━━

# NFTs block transaction
1 264 25571319 0xafa6cc0c194e763079c029f6871216b7f8a9362f6e6d13d8d39807f8d7eec195
2 231 25571388 0xf1556fe9fd73f66286e4231d29fb9e2e24c3df18578b5948eac916f00f846ad6
3 262 25571391 0xaa3029d8486ff48a4ae5c678dd0b7c50dc5219f2f37cdb14895e263c7376bfb1
4 229 25571394 0xa47142f9a9c0bc54b47430129164e065510059748a9f63c0dc9eb31b36e91988
5 267 25571394 0xf3f8cbce25cf088ee38b5fc7bebe04ee5de911459df135a9bf9b5272c1c50801
6 232 25571394 0xd2f92afd3b8f18ab066d5a396ae1f2030025c7548336f718b3e739232983f02b
7 264 25571394 0xd57c80fab08c835d67ecb69fcf272ffd934fdbcf762a7b8f3a1283f434217dfa
8 139 25571397 0x45fcbb36ad1457461370a30ef526bf4b96d2b074350d8b2ca24fb19179536eea
9 158 25571397 0x9a9a7d646cb4515ec8315a6b0329d5697a3c8f4f8af87bde023ba3886a49ba31

━━━━━━━━━━━━━━━━━
🔹 Smart‑wallet holders
━━━━━━━━━━━━━━━━━

Unchanged from the first post: NFTs addressed to Loopring smart wallets are not sent on‑chain and are returned manually for safety. A compromised wallet could hand an NFT straight to an attacker, and on‑chain alone we cannot tell a legitimate owner from a malicious one. Email [email protected] to verify your identity and we'll return them case by case. ⏳ The deadline is still August 15, 2026!

[LoopExchange @LoopExchange]

@H4llucinogenUsn Complete UXl/UI/performance overhaul in progress so it's truly fool- and futureproof. All L2 NFT-s backed up and safe, also on IPFS (we run our own node propagating everything via DTH, which actually wasn't the case with Loopring, funnily enough). Live tests next. Launch ETA: EoM

[LoopExchange @LoopExchange]

@TheCollector741 Catch: https://t.co/3zAf4YEaXl (valid 7 days)

[LoopExchange @LoopExchange]

@Ruudeeey Some of them were due to "undecodeable errors"-who knows what those & some other even mean. Only Loopring could shed some light, but it doesn't seem like they ever gave it a 2nd thought/try. Your last resort is [email protected] if it even still works and/or making a legit copy.

[LoopExchange @LoopExchange]

ELI5: 99.9% of all NFTs won't be redistributed (fine print: all L2 NFTs are excluded) 💀 Only things like Loopheads rooted in L1 will. No wonder comments are disabled! But they give us data of all L2 NFTs so you can redeploy'em at your own cost if you know how. We'll look into it

[Loopring @loopringorg]

https://t.co/IbZ9oGeAiN

[LoopExchange @LoopExchange]

@fudgebucket27 Congrats! ❤️

[LoopExchange @LoopExchange]

@Ruudeeey But Loophesds belong to Loopring proxy.Only they can canonically refurn 'em to holders.We'll provide a way for collectors to create legitimate L1 copies of L2 NFTs though(backed by contract tied to official Loopring NFT data)in case minters don't return/redeploy their collections

[LoopExchange @LoopExchange]

@H4llucinogenUsn Almost there. We've just backed up 1TB+ of all NFTs & metadata that were still alive 'cos IPFS nodes keep dying (around 2/3 are still responsive though), which took a week to back up + we're working on UX improvements, so it's as smooth as possible for everyone. ETA: 7 days or so

[LoopExchange @LoopExchange]

@JimQuin02654453 With quiet gas a 1000 holder collection = $20-25 for redeployment. Data integrity proofs were already posted by Loopring, we're simply referencing those, but you can download them yourself and use them directly instead.

[LoopExchange @LoopExchange]

@SatoshiRaver @AltcoinDaily Video is real (it's a known Polish dancer), but face is swapped.

[LoopExchange @LoopExchange]

@H4llucinogenUsn @loopringorg @gamestop As for the rest...

[LoopExchange @LoopExchange]

@H4llucinogenUsn @loopringorg @gamestop They're not the same for sure but if a minter is unreachable, unwilling or unable to redeploy (eg. lost their seed phrase) a copy backed by an official registry verifiable on-chain via our special contract is as legit as it gets and can't be disputed (only owners can mint those).

[LoopExchange @LoopExchange]

@H4llucinogenUsn @loopringorg @gamestop Redeploy, different thing, but it does include minting NFTs into people's wallets since they can't be withdrawn from L2 anymore. But they're gonna be canonically identical this way.

[LoopExchange @LoopExchange]

@H4llucinogenUsn @loopringorg @gamestop Yep. If you want it done this way, they'll have to listen, meaning you have to let them know it's what you want. We can help, we'll even open-source the scripts. But again, you'll be able to make legitimate copies backed by Loopring's data snapshot yourself (non-canonical though)

[LoopExchange @LoopExchange]

@H4llucinogenUsn @loopringorg It's not an edge case, it's the norm. The CANONICAL / ROOT contract of GMErica lives on L2. It's not the same thing as the contract you're talking about. The minter (GME) has never deployed it on L1 themselves & only such collections were returned (very few, 0.12% of all mints).

[LoopExchange @LoopExchange]

@H4llucinogenUsn @loopringorg We'll allow for canonical collection redeployment, so @gamestop can do that for cheap (then every holder will automatically receive their NFTs to their L1 wallets, but only minters can perform this). If they don't, you'll be able to make copies traceable to official Loopring data

[LoopExchange @LoopExchange]

@WrockFit @OhhGarrett Loopring has neither been hacked nor it is coming back. But your NFTs are :)

[LoopExchange @LoopExchange]

@Tyler85876933 @ThaSlaya2000 @loopringorg We'd be done already if it wasn't for making it as accessible as possible, actually. Core scripts have been operational for a week. It's UX & everything else that takes time but it's coming out nicely :) Instructions included of course! Also, we'll provide support, so no worries.

[LoopExchange @LoopExchange]

@haggar_1111 @loopringorg No, they're not 👇 https://t.co/KDq0dsVfAS

[LoopExchange @LoopExchange]

📢 Soon we'll launch a Loopring NFT Museum/Preservation project that lets everyone look at their wallets again, browse all L2 collections, redeploy to L1 for all holders or remint legitimate copies tied to official data & more. Work in progress (core ready & working). Stay tuned!