https://d4ha8vebfr.feishu.cn/space/api/box/stream/download/asynccode/?code=NzUxOTEwNjVmNTIxZWM4MDg0NmU2ZmFkZDcxZTY5M2ZfM3VEczdOU2hKWnhyczdrT2tkekJJdHhZMkVXS1IxRzVfVG9rZW46RTBmN2JKaFFqb2k1Y1Z4aW4xeWNiZE1Lbm9NXzE3MTE1MDU0NTc6MTcxMTUwOTA1N19WNA

User Demands:

1. Freeze assets 2. Change address

This kind of event has 2 possibilities:

1. The individual operates it
2. Hacker steals it and then operates it

To-do list:

1. Transfer a sum from this address to our specified address (proving this person indeed has the private key)
2. Freeze user assets, prohibit unstake/m-token mint: https://docs.google.com/spreadsheets/d/1ig8gwG89PN2sa-ZovBOOeDN9Hivs8_pYfDnoFniVbno/edit#gid=0, suggest putting it on notion (customer service issues are uniformly collected)
3. Self-prove it's the individual
   1. The history of this address, there are transfers from other addresses, especially exchanges. (Transfers before March, from 2 years ago to before March are the best, can be multi-link, ultimately pointing to an institution that can verify KYC)
   2. Open the exchange website to screen record, verify KYC (If there is no transfer from the exchange, request another transfer record from an institution with KYC)
   3. If the user cannot verify KYC, we cannot determine if this person is the individual.