News linked to both this project and an event.
the Polygon community has proposed draft proposal PIP-93, which aims to consolidate the Protocol Council, Polygon PoS, and AggLayer multisigs into a unified Polygon Security Council. The council will consist of 11 signers delegated by 10 institutions, adopting an 8/11 multisig strategy covering Ethereum and Polygon; Polygon Labs holds 2 seats, with the remaining institutions each holding 1 seat. Participating institutions include Sherlock, Hexens, Sigma Prime, Curve, QuickSwap, EthCC, L2Beat, and Coinbase, among others. Routine upgrades and parameter changes can be proposed by the Polygon Labs Operations multisig through a 7-day timelock, during which the Security Council may veto, or it can bypass the timelock to execute immediately or lift contract pauses. The proposal intends to replace the governance structure established by PIP-29, disclosing only the list of institutions holding seats rather than individual signer identities; it is currently in Draft status.
According to CoinDesk, researchers at blockchain security company Hexens discovered an "expired cache" type confusion vulnerability in the Aptos blockchain Move virtual machine. Attackers require only about $3,000 in server costs to launch attacks in a simulated environment with a success rate of nearly 90%, without needing validator privileges or internal knowledge. Researchers ran approximately 20 attacks in simulated tests, succeeding 17-18 times, and verified the potential ability to control management permissions of cross-chain protocols such as LayerZero, Wormhole, and USDC CCTP. Hexens assessed that the vulnerability directly threatens protocols on the Aptos chain such as DeFi, stablecoins, and liquid staking, involving assets in the low single-digit billions of dollars; if spread through paths such as cross-chain bridges, stablecoin minting, and centralized exchanges, the systemic risk exposure could reach up to $70 billion. The Aptos team completed the fix and deployed it to the mainnet within hours after receiving the vulnerability report on February 25, and currently no user funds have been compromised.