火星财经消息,Polygon Labs announced that it will shut down the Polygon zkEVM Mainnet Beta sequencer on July 1, 2026, a timeline first disclosed in June 2025. The official reminder states that on-chain wallet assets must be bridged to Ethereum Mainnet via ui.agglayer.dev before this date; unbridged balances will be automatically migrated to Ethereum L1, after which users can claim them via a dedicated interface. Polygon emphasized that it does not control any DeFi protocols on zkEVM—assets locked in DeFi contracts cannot be automatically migrated, and protocol teams and users must proactively withdraw and migrate liquidity before July 1. Any automatically migrated assets not claimed after December 31, 2027, will be considered abandoned.
Polygon zkEVM Mainnet Beta will be decommissioned on July 1, 2026.
MarsBitShare
Polygon Labs announced the decommissioning of the Polygon zkEVM Mainnet Beta sequencer on July 1, 2026, as part of on-chain news shared in June 2025. Users are urged to bridge assets to Ethereum via ui.agglayer.dev before the deadline. Unbridged funds will be migrated to Ethereum L1 and can be claimed later. Polygon reiterated that it has no control over DeFi protocols on zkEVM, noting that assets in DeFi contracts are vulnerable to exploits and must be manually withdrawn. Liquidity must be moved by July 1, 2026. Unclaimed assets will be abandoned after December 31, 2027.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.