This blog post will provide updates on the situation and expected timelines for resolution as soon as they are available. Updates will also be shared via the official Vega Twitter and Discord channels. Date & Time 2024/02/17 15:40 (GMT) Status [Investigating] Classification Under investigation (Major/Critical) For full details of how incidents are classified, please see…

VEGA

<p>This blog post will provide updates on the situation and expected timelines for resolution as soon as they are available. Updates will also be shared via the official Vega<a href="https://twitter.com/vegaprotocol" target="_blank"> Twitter</a> and<a href="https://vega.xyz/discord" target="_blank"> Discord</a> channels.</p><img src="https://sosovalue.s3.us-west-2.amazonaws.com/sosponge/web3image/24/02/18/e286tmic7w85.png" alt=""/><h3>Date & Time</h3><p>2024/02/17 15:40 (GMT)</p><h3>Status</h3><p>[Investigating]</p><h3>Classification</h3><p>Under investigation <strong>(Major/Critical)</strong></p><p>For full details of how incidents are classified, please see this <a href="https://blog.vega.xyz/mainnet-incident-classification-8efa5f927b7a" target="_blank">blog</a>.</p><h3>Description</h3><p>On the 17th February at 11:18 (GMT) the Vega to Ethereum bridge was stopped by validator actions following reports from the community of a potential intentional exploit and/or manipulation of markets targeting one or more liquidity providers.</p><p>This means that both deposits to, and withdrawals from the Vega network are not possible at this time. This includes withdrawals that were started on Vega but not completed.</p><p>Given the timing of the reported attack, we do not believe that any funds from this attack have left the network, as any withdrawals will have been subject to the 24 hour withdrawal delay present in the alpha version, and are now on hold while the bridge is stopped.</p><p>The Vega team and impacted community members are investigating these events and will provide updates along with any recommendations (such as reverting certain transfers), and if bugs are found, fixes will be made available.</p><p>The validators are expected to re-enable the bridge once they are happy that the issue is resolved, or if they decide that no further action should be taken.</p><p>Note that any resolutions, as well as control of the bridge are outside of the control of the Vega team, which can only investigate using the publicly available chain data and make recommendations.</p><p>The bridge stop transaction can be seen here:</p><p><a href="https://etherscan.io/tx/0xde22bcbaa2408265d9835b1b05eec99b9e3713a3ec4e367f9efbdd1e77a695d0" target="_blank">https://etherscan.io/tx/0xde22bcbaa2408265d9835b1b05eec99b9e3713a3ec4e367f9efbdd1e77a695d0</a></p><p>There is no immediate risk to any funds held on the Vega mainnet, as the bridge has been stopped. There is no risk to user’s staked VEGA tokens due to this incident. Staked tokens are never under the control of the Vega network and are always held only in users’ Ethereum wallets.</p><p>Since this incident involves validator actions and the possibility of a patch release to Vega, validators and node operators are requested to be on high alert in case of the need to coordinate a deployment of the protocol between themselves if the project team publishes an updated release.</p><p>This blog post will provide updates on the situation and expected timelines for resolution as soon as they are available. Updates will also be shared via our usual Twitter and Discord channels.</p>

Incident Report: Bridge stopped by validators