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 help@loopring.org to verify your identity and we'll return them case by case. ⏳ The deadline is still August 15, 2026!