This new post from @LayerZero_Core directly contradicts Bryan's claim yesterday that the LayerZero Labs multisig signer who was trading the "McPepes" memecoin on Uniswap was just "testing the PEPE OFT integration" Turns out that gaslighting doesn't work when people can check the chain and verify for themselves Naturally, they attempt to minimize the issue by making it seem like this was a one time incident, involving only one signing key, and that the memecoin trader was quickly rotated off the multisig In reality, the multisig signer attempted multiple memecoin trades over the span of a year and stayed on the multisig for nearly two years after the first memecoin trade, before finally being rotated off Furthermore, there were actually 3 signing addresses that were engaged in non-multisig related activity (memecoin trading, DEX swaps, bridging, LP provisioning) on a 2-of-5 Gnosis Safe multisig Billions of dollars in OFT value was exposed to the risk of being exploited by a multisig whose majority threshold of signers failed to practice even the most basic opsec and key isolation practices, FOR YEARS This was not a one-time error oopsie, this was a complete disregard for opsec -- Timeline of events of the LayerZero memecoin trader multisig signer: March 1, 2023 - 0xf1f5E swaps 0.198548 ETH for 1,727,120 McPepes (PEPES) December 21, 2023 - 0xf1f5E calls approve() for Uniswap on the McPepes ERC20 contract April 20, 2024 - 0xf1f5E attempts to sell McPepes on Uniswap but the transaction reverts January 27, 2025 - 0xf1f5E is finally rotated off LayerZero’s Gnosis Safe multisigs and signing threshold changed -- More context in following tweets

In the last 48 hours, 14 protocols have either announced a migration away from LayerZero or paused bridging. Fully migrated to CCIP: KelpDAO, Solv Protocol, Re Protocol Bridges paused: Kamino, Ethena, Euler, Curve Markets frozen: Aave, SparkLend, Fluid, Lido, Pendle, Compound

On May 7th Coinbase experienced service disruptions. Here’s a quick summary of what happened: → Around 8PM ET, Coinbase systems flagged high error rates across multiple services. → We traced these errors to amazon failures in Availability Zone (use1-az4) in the AWS US-EAST-1 Region. → Coinbase systems are designed to be resilient to a single zone outage, and are designed to recover quickly if this happens. → In this case, we observed failures impacting multiple AWS zones, which caused an extended outage of core trading services. → Coinbase users experienced an extended outage while the AWS team worked to restore temperature controls and other Amazon Managed Services. This primary issue is now fully resolved - thank you for your patience. If you have any outstanding questions about your account, please reach out to Coinbase Support, we’re ready to help. Our team will conduct a full analysis. Details may change as our investigation progresses and more information is received from AWS’s official retrospective, once published.

With the help of Claude Mythos Preview, the Firefox team fixed more security bugs in April than in the past 15 months combined.