Author

Topic: Yobit TUSD deposit - 12 days still not in my wallet (Read 175 times)

newbie
Activity: 11
Merit: 0
on yobit, when I click Deposit on the TUSD screen I see the same adress 0xb5b612115dd5034fe1eb707bf5bca43e5d4736e1.

and

What does it mean same coins but different contracts and one of it has no value. I must wait or do something?

Nobody can know that there are different contracts while sending.
full member
Activity: 590
Merit: 116
I see your transaction successful and there are 2 same tokens but different contracts, the status is the old TUSD with the existing value in the market and the other TUSD that has no value.


check the following transactions:

if you see the transaction above, then Binance has successfully carried out the withdrawal order that you made. So it seems that binance cannot cancel or revise your transaction, this means you cannot complain with binance

Try checking again, destination address "0xb5b612115dd5034fe1eb707bf5bca43e5d4736e1" you are using the same as the address on your yobit account.
legendary
Activity: 1302
Merit: 1000
When you write my yobit TUSD wallet number 0xb5b612115dd5034fe1eb707bf5bca43e5d4736e1 to etherscan you see "IN" but you can not see "OUT". When you click ERC20 Token also you can not see "OUT". In my other TUSD transactions, there is also "OUT". "IN" and "OUT"

Maybe something is missing from your end because you have to check twice before sending any payment to bit exchanges. Previously many people experience the same problems with this exchange, if you send them perfectly it is better to contact the Yobit team.
newbie
Activity: 11
Merit: 0
When you write my yobit TUSD wallet number 0xb5b612115dd5034fe1eb707bf5bca43e5d4736e1 to etherscan you see "IN" but you can not see "OUT". When you click ERC20 Token also you can not see "OUT". In my other TUSD transactions there is also "OUT". "IN" and "OUT"
legendary
Activity: 2758
Merit: 6830
I asked it also to Binance.
They wouldn't be able to tell.

And when you looked the name of the coin from https://yobit.net/en/coinsinfo  you see it is right.
That's not what I meant. TUSD is an Ethereum token, which means that its a token running over the Ethereum chain. This means that the address used to deposit TUSD is also an Ethereum address, so you could, for example, send ETH to that address; the same way, an Ethereum deposit address at Yobit can also receive TUSD or any other ETH token.

The problem is that the system only works to detect the token it was designed to detect. I can have 2 ETH addresses, one used to detect TUSD deposits, and the other to detect ETH. If I send the coin/token to the wrong address, it will be there but it won't be detected by the system.

If you are sure you really sent the TUSD to a TUSD deposit address, only Yobit can help you. If they want to scam you right now, they can; and unfortunately, there is nothing you can do other than wait/pray for that to be a legit mistake and for them to credit your account.

But if you actually got an ETH/other ERC20 token deposit address and mistakenly sent your TUSD to it, contact the support and tell what you did. Again, if they want to help you, they will.
newbie
Activity: 11
Merit: 0
no, it is TUSD adress. TrueUSD. I asked it also to Binance to solve. Last day when I tried to send NULS to yobit account it was written it is not a valid adress. No problem about the adress. And when you looked the name of the coin from https://yobit.net/en/coinsinfo  you see it is right. I sent TUSD to TUSD adress.
legendary
Activity: 2758
Merit: 6830
Can you double-check if the address you sent to is a TUSD deposit address and not a regular ETH/other token deposit address by mistake?
newbie
Activity: 11
Merit: 0
I sent my yobit acoount 499.07 TUSD 12 days ago. but it is not in my wallet yet. I sent it from Binance. I talked with binance and etherscan. They looked at my transaction and said that "it is successfully send. You must talk to yobit" It is 12 days and i need help. Yobit doesn't answer me.  My transaction ID is: 0x9c79158e69a6ca14cc01b7eb89563be7432fbb32a135eee9a0c16a08cb5eba62
Jump to: