🚨 Bybit recharge lost coin event | Same address, different networks, 7000U cannot be retrieved!? This is a recent asset loss incident that I personally experienced, with a current value of around 7000U; Write it out in the hope of reminding everyone, I also hope that @ Bybit_official @ Bybit_ZH can take this issue seriously and see if there is a reasonable solution when encountering similar situations in the future. This is a transfer from Little Fox Wallet to BYBIT, but there was no sign of it being received after a long time, until I realized: I seem to have transferred to the wrong network; After multiple communications, Bybit's final response was that the token recharge could not be successfully retrieved, and they expressed sincere sympathy for my asset loss. one ️⃣ The situation is as follows: As one of the earliest staking users on StakeStone @ Stake_Stone, I unlocked the tokens after the launch of the PLUME mainnet. Due to past habits, I transferred this portion of tokens from Little Fox Wallet to Bybit's PLUME recharge address. However, the transfer was not received for a long time after completion - only then did I realize that it may have been transferred to the wrong network. After multiple email communications, Bybit's final response is: Recharge cannot be retrieved, and we sincerely sympathize with your asset loss two ️⃣ Why is that? To be honest, I think this kind of thing is quite easy to happen: it is actually a very easy "inertia operation" that can make users fall into the trap: 🔹 Previously, the unlocking of PLUME tokens was on the Ethereum mainnet; 🔹 After the main network goes online, the new tokens are on PLUME's own main network; 🔹 The problem is that the PLUME main network address and ETH main network address are completely identical (both are EVM series), making it easy for users to directly recharge using the original address. That is to say, the same recharge address but different chains result in asset loss. And there is no clear reminder about this detail. three ️⃣ Is this really reasonable? ❌ Bybit currently does not support PLUME mainnet, I think so. But: 👉 The address is the same! 👉 Blockchain assets are open and transparent! 👉 It's just the identification of assets under different chains! This is definitely not an unfeasible operation in terms of technology, because there is no difficulty at all - even though it is the same address and the asset has not been lost, it is easy for people to think that Bybit only chooses "not to retrieve". four ️⃣ How do other exchanges do it? For example, I checked @ bitgetglobal: ✅ They clearly distinguish between PLUME network and ETH network on the recharge interface; ✅ Same address, but will prompt you to choose the correct network; ✅ This is responsible for both user experience and security. five ️⃣ Some suggestions about Bybit: As a leading exchange, Bybit should be given an opportunity to solve this technically solvable problem, rather than just saying "sympathy". This is not a matter of right or wrong, but rather a question of whether users are willing to prioritize asset security. Because it's just a simple action, a small gesture! So here are some suggestions for @ benbybit boss: In my impression, the boss has always been a practical worker, and Bybit has also been in a state of rapid development. Therefore, everyone's suggestions will help you do better. I hope to listen to the voices of users! @Bybit_ZH @Bybit_Official @Bybit_Web3 six ️⃣ Reminder to everyone: Indeed, I also have a problem. I charged the wrong network and didn't even look at it. I assumed that the address was the same anyway, so just type it in! So I have a piece of advice for everyone: 📌 Before listing on the exchange, make sure to check if the network matches! 📌 Don't fall into the trap of habitual operation like me! Please also help to forward and spread the message, so that more people can see it. We also hope that Bybit can take this issue seriously and prevent more users from repeating the same mistake.