Quote from: jabo38 on March 21, 2016, 08:21:01 AM

Quote from: richiela on March 21, 2016, 06:58:48 AM

I got a message from someone regarding this thread today. In the spirit of transparency, instead of privately answering them, i'm going to publicly post a response.

A couple of data points:

a) Bittrex was not notified of the failed attempt to attack our exchange. I was made aware of the attempt to social engineer our process on March 17th, around 1 am PST, when talking to the developers in the NEM slack.

b) Someone deposited funds to our exchange and tried to social engineer double crediting of a single deposit of coins. This is not a flaw with NEM; If an exchange isn't properly tracking txids, someone can try to double claim something deposited. We have multiple layers to safeguard against that.

c) The withdrawal of properly credited funds were coincidentally delayed that evening because the NEM wallet produced an error. "2016-03-16 06:35:57.936 INFO chain update of 4 blocks (0 transactions) needed 97767 ms (0 μs/tx) --> That means his system was basically dead. Might be memory problems or something else." After service was restored, we proceeded to wait 24 hours before crediting the account for withdrawal.

I hope this answers the query we got and sheds light on what happened from our side.

Thanks,
richie@bittrex

I can confirm this statement and would like to thank the owner of Bittrex taking his time to post.

It was me who sent the message to bittrex thats why richie took his time to post here. Do we get a thanks? No! Do we get an apology? No! We reported it and all we get is abused! And the reason Dev NEM team notified Richie it because I Notifed Dev Team in the first place and all the answers I got from the NEM team that was all ''bullshit'' to say in one simple word