Hi BenTheAnonMod
If Cryptopia states that 47% LTC and 14% BTC were stolen. Can you post hacker's transactions ids here or on the website. It will allow people track those monies, and if they hit some btc/ltc accepting services people can freeze hackers funds and contact local law enforcement agencies or NZ police.
Client: Can you post hacker's transactions ids?
Cryptopia: "Can't answer because ongoing investigation".
{It's a public ledger and secrecy only aids the criminal and prevents tracking}
Client: Can you post an account of the stolen property?
Cryptopia: "Can't answer because ongoing syncing of our wallets".
{So they are saying they don't even know what was stolen to this day}
sure.
Client: Can you post a date and time that BTC, LTC, Doge can be withdrawn?
Cryptopia: "What? What is withdraw? I don't understand the question".
--
Totally the same, Ben.
Totally the same, Ben. yep yep.
here's the point (which you went great to lengths to deflect and avoid mentioning)
"the stolen assets from DragonEx were transferred to the following address"
Transparency vs. Skunks
Cryptopia isn't accepting Deposits... so why would the hacker send anything to Cryptopia and the known ETH/ERC20 addresses were posted within the Cryptopia discord immediately following the breach.
Staff weren't able to enter the building or work at that time, so how could Cryptopia immediately following the event release anything you've suggested they should have officially?
Again, you're trolling right because no one is this dense...
Yes, it's totally the same Ben, returning clients money versus aplying a haircut to ETH(100%), BTC(15%) and LTC(35%).
They haven't said they will return clients "money", they haven't said they will return ANYTHING yet specifically. So again your example fails.
That is a good point though, the ONLY thing Cryptopia didn't do that DragonEx did is say
"DragonEx will take the responsibility no matter what."
This early they can't guarantee that, Dragonex says it will take responsibility no matter what - which is a silly thing to do because liability may be elsewhere.
show the exact hack amounts and tx's