There was almost a four hours window, during which it was probably possible to save your tokens. All you had to do was to immediately create a new account with this name
When did you notice that mistake, @funshee ?
I did a similar mistake once, (simple keyboard misstype, fat finger?), staked my 1777 POB tokens to a non-existing account
@onwalfa.pob.
Once I noticed that , I immediately jumped into new account creation window, and created such account onwalfa.pob.
My 1777 POB's came back under my control.
I was quite surprised tokens were able to be sent to a non -existing account. No any error message has popped up.
But later, once such account was created - tokens were under my control no-problem
Good lesson for a future.
Posted Using LeoFinance Beta
Thank you for this lecture sir, I never knew it was possible.
At first I thought the token was just been delay due to the fact that it was been process manually. Not until after 24 hours that I got to check again and realised my mistake.
Wow, is this possible. Amazing, thanks for letting this know sir. Its a great discovery I guess. 😊👍 !LUV
(1/1) gave you LUV. | wallet | market | tools | connect | <><
@vikbuddy
@funshee I see that they are going to honour your transfer request anyway but have you tried this as suggested by @onealfa.leo . Perhaps you can regain control and send the token on to the correct account? All the very best, that must have been a gutting experience.
A bot already created the account and liquidated the tokens:
https://hiveblocks.com/@ax-1pob-2vyb https://peakd.com/@socrattic/wallet/hive-engine
We plan to make sure this problem cannot occur when using the Verify Your Brain front-end. We will configure the Hive-Engine 'send' feature to check to make sure the receiving account already exists before posting the transaction's JSON to the blockchain. If we can't get this change made before the front-end is launched, it will be a top priority immediately thereafter.
Thank you very much @samsmith1971 It is too late for the recovery process above I can only do that within. 7 hours of the transaction.
Yes, they already did.
It appears @socrattic has created a bot that looks for Hive-Engine tokens that have been sent to non-existent accounts, then swoops in and creates the errant account, then liquidates the tokens.
He's been doing that for almost a month now.
https://peakd.com/@socrattic/wallet/hive-engine
I spoke with @eonwarped about this. The 'send' feature could be modified to check the existence of the receiving account before posting the JSON transaction to the blockchain. However, that is a change that would need to be made at the front-end level, which means it would need to be made to every single front-end.
Not an insignificant task, but an important one, imho.