Accidentally sent USDT Omnia from Binance to Bread (BRD wallet) BTC Address

[thomasxyc]

Dear members of bitcointalk,
I have made an incredible big and stupid mistake....
I send 33.950 USDT to my BRD bitcoin wallet instead of my USDT wallet...
It never arrived, but if i check the Omni Explorer it is there available in balance. I contacted Binance who told me to get in touch with BRD support to return the transaction to Binance. However BRD just waved me off and told me theres nothing they can do for me.

I came across another topic where the steps below were mentioned:
by @TryNinja in another topic:
1. Go to https://iancoleman.io/bip39/ (or download its source code and run locally for better security);
2. Write your recovery seed in the "BIP39 Mnemonic" field;
3. Scroll down a little bit and find your address in the list (the one you sent the USDT);
4. When you find it, copy its Private Key;
5. Now go to https://www.omniwallet.org/ and create an account;
6. Log in, go to My Wallet -> My Addresses;
7. Click on the "Add Address" button -> "Import Address with Private Key";
8. Paste your private key from step 4 -> "Add Address".
9. You should see your USDT balance and be able to send them somewhere else.

I didnt have any success there, the wallet address didnt came up (not even after loading over 30.000 rows of wallets)
I have my recovery seed and submit it into the BIP39 Mnemonic field but it seems its loading random wallet addresses some how...

If somebody can help me out i would really really appreciate that.
i will give a good compensation for the one who can assist me with getting my USDT back.

Im currently in process of getting the omni core to sync which takes a couple of hours, i figured loading my recovery seed there might help...
It could be i still need my private key, but im not entirely sure of that.

Any suggestions are well appreciated, as im cluelessly trying and testing everything to get it back.
I hope somebody can help me here

[1715315608]

1715315608

[1715315608]

1715315608

[1715315608]

1715315608

[1715315608]

1715315608

[OmegaStarScream]

I could be wrong (maybe someone could correct me?) but AFAIK, bech32 addresses are not supported by the Omni protocol. If the address you sent the funds to starts with "1" maybe you can try the following:

1. Restore your wallet using Electrum. Here's a guide (make sure to choose "legacy" instead of "native segwit"): https://bitcointalk.org/index.php?topic=5204223.0
2. Go to the "Addresses" tab, locate the address you sent funds to then right-click and choose "private key".
3. You're good to go. You can go back to Omniwallet.org and proceed as explained by TryNinja.

[Lucius]

OmegaStarScream, SegWit addresses seem to be supported though - at least from what I found on GitHub. According to the described procedure, it is possible to recover tokens sent to the SegWit address, but the procedure is not simple at first glance.


thomasxyc, try first with the advice of OmegaStarScream and @TryNinja tutorial, and if you fail to do so, try following the instructions at the following link with the maximum dose of caution, because in the process you can completely destroy your chance to return the tokens.

https://github.com/OmniLayer/omniwallet/wiki/Recovering-funds-from-a-Segwit-Address

[thomasxyc]

Hey OmegaStarScream and Lucius,
I reached out to Yogg, and he helped me step by step to get my USDT back and it worked!!
Such a nice guy! He helped me go through the method mentioned by TryNinja, it works but we needed to make some changes to the settings of the software.
If anyone has a similar issue with USDT stuck or lost because of sending it to a BTC wallet i would definitely recommend sending him a message.

Thanks again for your replies guys! sorry me responding abit late!

Case closed!

[hugeblack]

Such a nice guy! He helped me go through the method mentioned by TryNinja, it works but we needed to make some changes to the settings of the software.
If anyone has a similar issue with USDT stuck or lost because of sending it to a BTC wallet i would definitely recommend sending him a message.

It's a great thing, instead of wasting time waiting for @Yogg response (or PM him,) why not share the settings that worked with you, so that future members can get more details about the solution.
Next time you should be careful when sending, especially if the wallet was a platform or a closed source wallet.

[yogg]

Such a nice guy! He helped me go through the method mentioned by TryNinja, it works but we needed to make some changes to the settings of the software.
If anyone has a similar issue with USDT stuck or lost because of sending it to a BTC wallet i would definitely recommend sending him a message.

Thanks thomasxyc for your kind words.
It's been a pleasure chatting with you and guiding you through the steps.
I'm glad we figured it all out !

It's a great thing, instead of wasting time waiting for @Yogg response (or PM him,) why not share the settings that worked with you, so that future members can get more details about the solution.
Next time you should be careful when sending, especially if the wallet was a platform or a closed source wallet.

Well, in this case it was an uncommon derivation method that was used by the BRD wallet.
The settings were in the "BIP32 tab",
"Client" : "MultiBit HD",
and "BIP32 derivation path" : "m/0'/0"

This is why Thomas' public address was not showing on the default page.
I believe this to be specific to this user's case and not a generic solution for everyone facing a similar issue.

I have also helped someone else who got mistakenly their USDT sent on the Binance Smart Chain as a BEP-20 Token.

With all these tokens, sidechains, tokens on sidechains, this is getting confusing.

Anyway, if someone is stuck in a similar situation, do not hesitate to send me a PM.
I will never ask for your seed or your private key.
(If someone does, this is not me but likely an impersonator.)