Back to top
  • 공유 Share
  • 인쇄 Print
  • 글자크기 Font size
URL copied.

Crypto exchange DragonEx lost $7M in hack, announces compensation plan

작성자 기본 이미지
Shampa Mani reporter

Mon, 01 Apr 2019, 10:54 am UTC

DragonEx, a Singapore-based cryptocurrency exchange, has published an update of the funds it lost in a hack that took place on March 24.

According to the March 30th report on stolen assets, the exchange said:

“On March 24th, DragonEx suffered APT attack, which is the greatest challenge since DragonEx was first launched in the year of 2017. 7.09million USDT assets are stolen (based on the price when it was hacked), details are as below.”

The lost funds include 135 bitcoins, 2,738.12 ether, 247,000 XRP, 1,464,319.32 USDT, 64,121.00 XEM, and 426,314.70 EOS, among others.

DragonEx said that it is working with overseas and domestic Safety company to do system inspection and upgrade its safety measures as it prepares to reopen its platform.

Although it is trying to track and retrieve back the stolen assets with the help from multiple parties, the exchange said that “it seems not likely to retrieve back the stolen assets.” That said, the exchange has announced its plans to compensate affected users:

“DragonEx will issue 7million USDT value of DB, Dragon Bond which is 1:1 with USDT. The stolen assets of users will be calculated at the price when it was hacked, DragonEx will compensate 10% of the stolen assets as original currencies and the other 90% will be compensated with DB.

“DragonEx Team will give out 3.65million DT to set up DB Rewards Pool, the dividends from which will be used to compensate the DB holders until DB is bought back all.”

The exchange further said that it is also seeking outside financing, which if successful, would enable it to “purchase back all stolen assets for users and recover the trading, deposit and withdrawal as usual.”

<Copyright ⓒ TokenPost, unauthorized reproduction and redistribution prohibited>

Most Popular

Comment 20

0/1000

alert("SQLSTATE[42S02]: Base table or view not found: 1146 Table \'tokenpostcom.ExperienceClient\' doesn\'t exist");