Conversation with creators
• After finding the problem, Bleutrade placed an alert message on the html5 trade page.
• April 28:
◦ Devs open a ticket and with information that the fix is already being performed.
◦ Bleutrade informs the size of the problem and asks how this will be resolved.
◦ Devs report that they can resolve the insolvency issue or create a swap for a new coin.
◦ Bleutrade accepts the proposal, informs users that the developers are working on a fix
and wait for the update.
• April 29 to 02 may: We provide all data for the correction to be healthy.
• June 08 and 09:
◦ Bleutrade asks for progress information.
◦ It is informed that progress is good.
◦ Bleutrade provides more details of the blockchain attack.
• June 12:
◦ Devs request to inform users that attacker has been deleted from the network.
◦ Bleutrade informs that the source code still does not present the solution.
• June 14 to 17:
◦ Devs request further information about the attack.
◦ Bleutrade provides full access to the hacker's account.
◦ Bleutrade again provides an explanation of what has happened.
◦ Developers understand the problem but do not care more about Bleutrade.
◦ Bleutrade informs that without the original proposal there is no solution.