As mentioned in a previous article about CoinDash being hacked just over 5 days ago, the aftermath of the incident is being handled gracefully by the Isreali based company.
CEO's Statement to Public
In an interview with Bloomberg Markets earlier this week, Alon Muroch the CEO of CoinDash stated that the blockchain-technology company will still move forward with developing a portfolio tracking service and network for cryptocurrencies and ICOs.
Muroch stated that:
"...it doesn’t really cost anything to create a conspiracy theory. It’s very common in this industry to accuse everyone of being a scammer. We’re doing everything humanly possible to investigate all angles. Every scenario you can think of we’re investigating."
And that...
"Actions talk louder than words. At the end of the day, that’s what we’ll deliver."
Still Raised Cashed
Despite the hack, CoinDash was still able to raise $6.4 million from the token sale before the attack. In the hack, investors who had been instructed to pay with the digital currency ethereum were then forwarded to a fraudulent address, which effectively stole the coins.
Reimbursement Details
Contributors who have sent ETH to the fraudulent address during the token sale will also be credited in CDT, reflective of their contribution. The CDT tokens will be distributed to those who have filled out our form and have been verified as contributors.
(Claim form link - https://goo.gl/forms/9AX1Wp9tY69ifuLT2)
After getting all the information from the claim form sorted and with the data from the burn address, all the distribution addresses will be implemented in the new contract.
The timeline for the token distribution depends on the fraudulent address contributors and their cooperation providing us with all their information. Unclaimed tokens will be kept by the company for latecomers. Assuming full cooperation will be achieved, the distribution will take place next week.
SOURCE: CoinDash's Website
Thoughts/Questions
- Does yet another ICO hacking concern you in regards to the legitimacy of an address on a ICO's website?
- What solutions could be deployed to mitigate this sort of thing in the future?
- Will this hamper their development time and depth for the project?