A sigh - 1.3 million U lost in wrong chain transfer
1. Customers who sent to the wrong chain
Today I encountered a customer who, half a year ago, wanted to transfer 1.3 million U worth of SUI coins from an exchange to his SUI address in his wallet but accidentally transferred to his wallet's APTOS chain address, asking if it could be retrieved.
At first, I thought it would be easier to handle like the previous Bitcoin series and EVM series of wrong chain transfers, but after research, I found it was not that simple.
With the same private key, SUI and APTOS use different hash functions when generating addresses: the former uses Blake2b-256, and the latter uses SHA3-256. The generated address length is a 0x + 64-byte hexadecimal string.
Today I encountered a customer who, half a year ago, wanted to transfer 1.3 million U worth of SUI coins from an exchange to his SUI address in his wallet but accidentally transferred to his wallet's APTOS chain address, asking if it could be retrieved.
At first, I thought it would be easier to handle like the previous Bitcoin series and EVM series of wrong chain transfers, but after research, I found it was not that simple.
With the same private key, SUI and APTOS use different hash functions when generating addresses: the former uses Blake2b-256, and the latter uses SHA3-256. The generated address length is a 0x + 64-byte hexadecimal string.
Disclaimer: Includes third-party opinions. No financial advice. May include sponsored content. See T&Cs.
SAFEUSDT
Perp
0.4324
-2.74%
