Post
Topic
Board Scam Accusations
Re: CRYPTSY stopping withdraw locking accounts without notifying users! Class Action
by
ph4nt0m
on 16/01/2016, 01:04:05 UTC
Well fuck.... I don't even know what to say...

I found out about the blog post when a customer called me and told me it was up. I found that irritating to say the least....

Again, I never worked with any wallets, had access to any wallets or any code. I ran investigations and customer end security ( like 2fa and getting back into hacked accounts)

This is a really shitty situation. I understand people are upset and have every right to be. I admit, I drank the koolaid and when people told me things were alright, I believed them whole heartedly.  I don't know code or hardware at all, so when I was told it was a technical issue, I had faith.

Now I just look like an asshole for believing it, and for that I do apologize. Since I heard about this, Ive been sifting through dozens of emails from people with "tips" and it is exhausting to say the least. Although I am no longer paid by Cryptsy, I feel an obligation to try me best to help locate coins, whoever may have them.

In the mean time I don't mind trying to answer any questions I can and I know trolls are gonna troll hard at the moment. I'd be trolling too so I can't blame them.

I've always tried to help people since starting at Cryptsy and I find it a real shame it's come to an end like this.





I believe you. I also believe that Mullick did nothing wrong too. He had no business being responsible for the security of wallets, which is how i've always felt. Bare mimimum C++ expertise is required. People don't realize how easy it is to obfuscate C++. many of the backdoor's ive seen i wouldn't even have known they were there without someone pointing out the use of a disguised Macro. Hopefully future exchanges will hire an actual expert.

Those macros and code they executed looked weird. Of course if someone throws a bunch of files at you and says to go solve a puzzle to find a backdoor, it isn't a trivial task which may take days to complete. However the hacker told he was after a simple IRC fix which is just a few obvious lines of code replaced. Did he miss the fork button on GitHub in the process? And no one cared to educate him quickly? Yeah, right.