Browsers with the Metamask wallet extension currently show a warning when users attempt to view the Multichain explorer, due to the fact that the protocol has been hacked. However, it can be viewed with a browser that does not have a Web3 wallet installed. Cointelegraph does not recommend connecting to Multichain with a wallet app<\/a>, and the site itself may also be unsafe.<\/p>\n The transactions appear to be coming from a small number of addresses, indicating that they may be an attempt by the attacker to move funds or else part of a recovery effort by the team. As of 9:30 pm UTC, only a single transaction is listed as pending on Multichain’s explorer.<\/p>\n According to the Multichain block explorer, transactions started confirming at approximately 9 am on November 1.<\/p>\n Some transactions have been confirmed on the destination chain. For example, a deposit of approximately 20 DAI was made<\/a> from Ethereum to Avalanche, which was confirmed<\/a>\u00a0on Avalanche at 1:56 pm UTC. However, a deposit of 0.1 BTC that was made<\/a>\u00a0from Ethereum to Polygon at 2:44 shows as confirmed on the Multichain block explorer but has<\/a> not been confirmed on Polygon.<\/p>\n Blockchain analytics platform Cyvers detected the resumption of transactions in the morning, and posted the info to X (formerly Twitter<\/a>).<\/p>\n UPDATE On July 6th, @MultichainOrg<\/a> faced a $126M hack! We have detected real time <\/p>\n But today exciting news<\/a>! @MultichainOrg<\/a> has resumed processing bridge transactions after 117 days of downtime. <\/p>\n Many bridge transactions successfully went through. \u2014 Cyvers Alerts (@CyversAlerts) November 1, 2023<\/a><\/p><\/blockquote>\n![](\"https:\/\/s3.cointelegraph.com\/uploads\/2023-11\/ffd976bf-33ee-43b6-814d-75365f045aaa.png\")
\n
\ufe0f We’re closely\u2026 https:\/\/t.co\/KoizCgXYeJ<\/a> pic.twitter.com\/Nw4muay5xE<\/a><\/p>\n