[Bridge Error] Tokens stuck on Plume Network (No Token Transfer on L2 after Binance withdrawal) #239
Description
Description
I accidentally withdrew PLUME tokens from Binance using the Plume Network instead of Ethereum (ERC-20).
The transaction succeeded on Plume Explorer but shows “No Token Transfer” on L2, meaning the tokens never bridged to Ethereum.
Currently, the funds appear to be locked inside the Plume L2 bridge contract and not accessible from either Binance or Upbit.
Transaction Details
- Source Exchange: Binance
- Destination Exchange: Upbit
- Intended Network: Ethereum (ERC-20)
- Actual Network Used: Plume Network
- Date: 2025-10-12 (KST)
- Token: PLUME
- Amount: 200,199.32242053 PLUME
- L2 TX Hash:
0xa650c9adf5dd758ccd2711f28ab7dc3b03fa39129d8141f2a09716c5482f3b31 - Destination Address (Upbit):
0x2bEb40221d8696180Cef733C225db447E4efC73A - Batch Number:
#20082 - Commitment TX (Ethereum):
0x7d7843d6fedd0302cc14b49950162d67a6029306cffe60d9cfa4672688e83165 - Confirmation TX (Ethereum):
0x7f70cecfb06c73455be24b4d993cb857bca802d5c95f64f7f7b57c4748709e1b
Current Status
- ✅ Plume Explorer shows "Success"
⚠️ Plume Explorer also shows "No Token Transfer"- ⛔ No ERC-20 transfer event on Etherscan
- 🧊 Tokens appear to be locked in the Plume L2 bridge contract
- ⛔ Upbit has not received any deposit (no ERC-20 event to detect)
Expected Behavior
Tokens should either:
- Complete bridging to Ethereum (ERC-20),
or - Be released/refunded to my originating Binance wallet.
Request
Please help verify whether this transaction is still pending or stuck in the L2 bridge queue.
If so, I kindly request your engineering team to manually finalize or unlock the transaction so I can recover the funds.
Evidence
- Screenshot: Plume Explorer showing "Success" + "No Token Transfer"
- Screenshot: Etherscan (no token movement)
- Screenshot: Upbit address (no incoming PLUME)
Thank you very much for your help! 🙏