LayerZero Ends STG to ZRO Swap Service on December 15

STG to ZRO Swaps End December 15

LayerZero will retire the service that exchanges Stargate (STG) for LayerZero (ZRO) on December 15, a cutoff that leaves remaining STG holders 41 days from today to complete their conversion. The date comes from a LayerZero ecosystem update published this week, and it is the only deadline the notice fixes. After December 15, the swap service will no longer process STG into ZRO, and the announcement states no alternative route, no extension mechanism and no grace period for balances that miss the date. LayerZero said it will manage the transition together with exchanges, market makers, custodians and ecosystem partners, so holders who keep STG on a venue should expect venue-specific instructions rather than one universal process. The notice leaves several holder questions open: it gives no figure for outstanding STG, no breakdown of how much has already converted, and no statement on whether the legacy token keeps any function once the service closes. The conversion route was created during LayerZero's acquisition of Stargate last year, when the cross-chain liquidity protocol was folded into the LayerZero stack and STG holders were offered ZRO as the successor asset. The swap service has run since then as the official path between the two tokens, and its closure ends that path outright. For anyone still holding STG, the practical reading is direct: conversion after the announced date is not offered through the official service. The ZRO price is not addressed in the update, which also carries no tokenomics figures such as circulating supply or unlock schedules. What the notice does carry is a package of contract-level changes with a longer tail for ZRO holders, and that is where its substance sits.

OneSig Transfer and a 4/4 Verifier Rule

The same announcement schedules two changes to how the ZRO contract is owned and secured, and both are tied to preparations for the Zero mainnet launch. First, LayerZero will transfer ownership of the ZRO contract to OneSig, the protocol's own signature scheme. Contract ownership is the administrative authority over a smart contract: whoever controls it can change parameters, upgrade logic or, in some designs, pause operations. Moving that authority into OneSig ties control of ZRO to LayerZero's own signing infrastructure rather than an externally managed key. Second, the configuration of ZRO's decentralized verifier networks will be updated so the required verification threshold rises to 4/4, meaning all four configured networks must attest to a message before it counts. In LayerZero's security model these networks are independent parties that verify messages moving across the blockchain connections LayerZero maintains. A 4/4 setting is the strictest arrangement of this kind: no single verifier can approve a message on its own, at the cost of requiring unanimous sign-off. The December 15 date does double duty in the notice, which separates the two tracks explicitly: LayerZero V1 relayer support also ends that day, but that retirement concerns legacy messaging infrastructure and is unrelated to the token swap service. The notice ties both contract actions to the Zero mainnet timeline rather than to any security incident. Market reaction to the announcement has been measured but positive. Market data shows ZRO about 11% higher over the past 24 hours, adding to a 29% weekly rebound the token staged from a $1.42 low. Supply mechanics sit alongside the security news: a previously announced schedule put a 23.63 million ZRO unlock on October 20. For readers weighing entry and exit levels, support and resistance for the token are tracked in our ongoing ZRO technical analysis.

Contract Control Consolidates Before Zero Launch

Our reading is that this update consolidates control ahead of a network release rather than simply sunsetting a service. The primary document, the ecosystem announcement itself, fixes exactly one date and two contract actions: the swap ends on December 15, and before the Zero mainnet the ZRO contract moves under OneSig with a 4/4 verifier rule that leaves no single network able to approve a message alone. That combination tightens the operational surface around ZRO at the same moment the legacy STG path closes, a pairing that matters because interoperability has become core web3 infrastructure. For STG holders the actionable item is the calendar, not the security change. The item the notice leaves open, and undated, is the status of STG that stays unconverted once the service stops.