Balancer announces on-chain message to hackers, demanding the return of funds by November 9th to receive a bounty.

GateNews
BAL-3,64%

PANews November 8th reported that Balancer tweeted that on Wednesday, November 5th, they sent an on-chain message to all known addresses involved in the attack and provided a way for hackers to contact them and return the funds.
“Balancer hopes to resolve the issue without an upgrade. If willing to cooperate, please reply to this message and contact us before 5:00 AM (UTC+8) on November 9th. If there is no reply by then, it will be considered unwilling to assist in compensating liquidity providers’ losses, and the issue will be escalated.”
“Balancer proposes: returning the funds to the DAO multi-signature address in exchange for a bounty. Specific details will be negotiated privately. After confirming that the returned funds meet relevant standards, Balancer will not take legal action or investigative measures. If this proposal is not accepted or there is no timely reply, Balancer will take all technical, on-chain, and legal measures to identify and hold the attacker accountable. In this case, the bounty will be used to reward verified informants to help identify and ultimately prosecute the attacker.”
Previously, it was reported that the amount lost in the Balancer attack has risen to $116.6 million.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments