Post
Topic
Board Securities
Re: [BTC-TC] Virtual Community Exchange w/ Options, DRIP, 2FA, API, CSV, etc.
by
xubingde
on 19/07/2013, 23:48:16 UTC
Anyone has the same experience as I do?
Yesterday I transferred my shares on BTCT to 796 Exchange. The account should be xchange796, but I missed letter “e” and wrote xchang796. To my surprise, BTCT confirmed the transfer immediately. I don’t believe it’s such a coincidence that there’s an account xchang796 which really exists. Therefore, I filed a ticket. It’s been 2 days and no response from BTCT. What should I do? Anyone who can give some advice?


Hi there.  As mentioned (now a few pages back unfortunately.) I have been traveling.  So I apologize for not getting back to you sooner.  However...

"to my surprise" ... what?  You think people would use it if transfers to valid accounts were NOT transferred immediately?

The form asks, not once, but twice who you want to send it to.  Then, while you're looking at the form, with both users plugged in, you have to put in either your PIN or your 2FA before submitting.  I think I've done about everything I can to prevent mistakes such as these.

Someone else likely got your shares, unless 796 exchange happens to have both accounts, and I cannot undo it.

Very depressing... I try really hard to help people not make these kinds of mistakes.  I am very sad for you.  Sad

Perhaps a solution is to associate a 4 digit hash with the account name. In order to transfer assets or bitcoins to another account, you have to include the hash.

For example, the "796 Exchange" account would have a hash "1271", but the "xchange796" account would have the hash "4252". If the hash is required to transfer, it would be very unlikely that someone could transfer to the wrong account by mistake because the hashes wouldn't match. It would also be very difficult for someone to spoof an account using a misspelling .
Perhaps a Correct solution