i hope that it will start to coming back soon, but who can know something in crypto 
indeed the reputation of team has improved after this attempt! The attack has concerned only the website of the ICO (passwords of dashboard of ICO ended by the end of January, only a problem on districts.io site caused by a WordPress bug!) and no harm was caused, the millions of coins of which you speak were only a "ransom request" that obviously nobody cares because the team had all the backups of ICO data... 
We must also consider that the 2fa authentication and the withdrawal functions had been activated for months and those who had participated in the ICO should have thought for several months now to make the withdrawal of their coin instead of leaving them on an ICO website for months... 
That said, NO PROBLEM HAS REGARDED 3DCOIN LOCAL WALLETS, MASTERNODES OR BLOCKCHAIN because the attack concerned only ICO data (not coins but only data!) by exploiting a WordPress vulnerability. Luckily there is a team of serious people who knew what to do, who had taken all the countermeasures so he simply blocked the withdraws from the ICO site (so they were always manually authorized ... eh eh ) and forced the users to reset their site passwords!
I do not care that the team is wasting time behind a site of an ICO over for months now just because the usual latecomers have forgot to withdraw their coin the 2fa is active if I remember correctly from February and the withdrawal from early March, I would have closed the site ICO site for some time... who is there is there and who is not there there is not ... when you participate in an ICO you have to follow the project and do not forget it in the drawer ... that said the team has solved everything without any problem ... no coin has been mistreated and no one has hurt stay tuned ... ) moreover for months the 2fa had been activated (the awake users knew it, who sleeps is not done for the cryptocurrencies sector... let's face it clearly we are honest with each other!) and the majority of users had already done withdrawals for some time. In short "A lot of noise from nothing"... indeed the reputation of team has improved after this attempt! The attack has concerned only the website of the ICO (passwords of dashboard of ICO ended by the end of January, only a problem on districts.io site caused by a WordPress bug!) and no harm was caused, the millions of coins of which you speak were only a "ransom request" that obviously nobody cares because the team had all the backups of ICO data... We must also consider that the 2fa authentication and the withdrawal functions had been activated for months and those who had participated in the ICO should have thought for several months now to make the withdrawal of their coin instead of leaving them on an ICO website for months... That said, NO PROBLEM HAS REGARDED 3DCOIN LOCAL WALLETS, MASTERNODES OR BLOCKCHAIN because the attack concerned only ICO data (not coins but only data!) by exploiting a WordPress vulnerability. Luckily there is a team of serious people who knew what to do, who had taken all the countermeasures so he simply blocked the withdraws from the ICO site (so they were always manually authorized ... eh eh ) and forced the users to reset their site passwords! I do not care that the team is wasting time behind a site of an ICO over for months now just because the usual latecomers have forgot to withdraw their coin the 2fa is active if I remember correctly from February and the withdrawal from early March, I would have closed the site ICO site for some time... who is there is there and who is not there there is not ... when you participate in an ICO you have to follow the project and do not forget it in the drawer ... that said the team has solved everything without any problem ... no coin has been mistreated and no one has hurt stay tuned ... indeed the reputation of team has improved after this attempt! The attack has concerned only the website of the ICO (passwords of dashboard of ICO ended by the end of January, only a problem on districts.io site caused by a WordPress bug!) and no harm was caused, the millions of coins of which you speak were only a "ransom request" that obviously nobody cares because the team had all the backups of ICO data... We must also consider that the 2fa authentication and the withdrawal functions had been activated for months and those who had participated in the ICO should have thought for several months now to make the withdrawal of their coin instead of leaving them on an ICO website for months... That said, NO PROBLEM HAS REGARDED 3DCOIN LOCAL WALLETS, MASTERNODES OR BLOCKCHAIN because the attack concerned only ICO data (not coins but only data!) by exploiting a WordPress vulnerability. Luckily there is a team of serious people who knew what to do, who had taken all the countermeasures so he simply blocked the withdraws from the ICO site (so they were always manually authorized ... eh eh ) and forced the users to reset their site passwords! I do not care that the team is wasting time behind a site of an ICO over for months now just because the usual latecomers have forgot to withdraw their coin the 2fa is active if I remember correctly from February and the withdrawal from early March, I would have closed the site ICO site for some time... who is there is there and who is not there there is not ... when you participate in an ICO you have to follow the project and do not forget it in the drawer ... that said the team has solved everything without any problem ... no coin has been mistreated and no one has hurt stay tuned ... indeed the reputation of team has improved after this attempt! The attack has concerned only the website of the ICO (passwords of dashboard of ICO ended by the end of January, only a problem on districts.io site caused by a WordPress bug!) and no harm was caused, the millions of coins of which you speak were only a "ransom request" that obviously nobody cares because the team had all the backups of ICO data... We must also consider that the 2fa authentication and the withdrawal functions had been activated for months and those who had participated in the ICO should have thought for several months now to make the withdrawal of their coin instead of leaving them on an ICO website for months... That said, NO PROBLEM HAS REGARDED 3DCOIN LOCAL WALLETS, MASTERNODES OR BLOCKCHAIN because the attack concerned only ICO data (not coins but only data!) by exploiting a WordPress vulnerability. Luckily there is a team of serious people who knew what to do, who had taken all the countermeasures so he simply blocked the withdraws from the ICO site (so they were always manually authorized ... eh eh ) and forced the users to reset their site passwords! I do not care that the team is wasting time behind a site of an ICO over for months now just because the usual latecomers have forgot to withdraw their coin the 2fa is active if I remember correctly from February and the withdrawal from early March, I would have closed the site ICO site for some time... who is there is there and who is not there there is not ... when you participate in an ICO you have to follow the project and do not forget it in the drawer ... that said the team has solved everything without any problem ... no coin has been mistreated and no one has hurt stay tuned ... indeed the reputation of team has improved after this attempt! The attack has concerned only the website of the ICO (passwords of dashboard of ICO ended by the end of January, only a problem on districts.io site caused by a WordPress bug!) and no harm was caused, the millions of coins of which you speak were only a "ransom request" that obviously nobody cares because the team had all the backups of ICO data... We must also consider that the 2fa authentication and the withdrawal functions had been activated for months and those who had participated in the ICO should have thought for several months now to make the withdrawal of their coin instead of leaving them on an ICO website for months... That said, NO PROBLEM HAS REGARDED 3DCOIN LOCAL WALLETS, MASTERNODES OR BLOCKCHAIN because the attack concerned only ICO data (not coins but only data!) by exploiting a WordPress vulnerability. Luckily there is a team of serious people who knew what to do, who had taken all the countermeasures so he simply blocked the withdraws from the ICO site (so they were always manually authorized ... eh eh ) and forced the users to reset their site passwords! I do not care that the team is wasting time behind a site of an ICO over for months now just because the usual latecomers have forgot to withdraw their coin the 2fa is active if I remember correctly from February and the withdrawal from early March, I would have closed the site ICO site for some time... who is there is there and who is not there there is not ... when you participate in an ICO you have to follow the project and do not forget it in the drawer ... that said the team has solved everything without any problem ... no coin has been mistreated and no one has hurt stay tuned ... 
