The ratio is 0.08634. Five significant figures. That is the entire event.
Binance's announcement feed carried it without ceremony: Stargate Finance's STG token merged into LayerZero's ZRO at a fixed conversion of 1 STG = 0.08634 ZRO. Old STG deposits and withdrawals were switched off in the same breath. No countdown clock. No governance theater. No price reference. The exchange executed a state transition and returned to its queue.
Most readers saw a housekeeping note and scrolled past. I saw a number that does not belong to a market. Market prices do not print five decimal places for long. They breathe, they tick, they mean-revert. A ratio with that many significant digits is the output of a function. Someone wrote it into a contract, tested it against a Merkle root, and deployed it once. The market had nothing to do with it.
That distinction — fixed conversion versus floating price — is where the real analysis begins. It is also where nearly every summary of this event stops short. The merge note tells you what was done. It does not tell you what was given up, and those are rarely the same thing.
Context: what LayerZero and Stargate actually are
Before the constant means anything, the plumbing has to be laid out, because the merge only makes sense against the architecture it sits inside.
LayerZero is not a bridge in the colloquial sense. It is a messaging layer — an omnichain interoperability protocol that passes arbitrary data between blockchains. It does not custody assets the way a lock-and-mint bridge does. It moves messages, and the security of those messages depends on a configuration called the Decentralized Verifier Network, or DVN. The DVN model replaces the classic single-relayer-plus-oracle design with a set of independent verifiers who attest to a message's validity before the destination chain accepts it. Change the DVN configuration and you change the trust assumption. That is the entire security surface, and it is configurable — which is simultaneously the elegance and the liability of the design.
The competitive field around that messaging layer is crowded, and the trust assumptions differ materially across it. Wormhole routes verification through a fixed set of nineteen guardians. Axelar runs a delegated proof-of-stake validator set. Chainlink's CCIP leans on the existing oracle network and a traditional-finance-style risk model. LayerZero's DVN approach is the most configurable of the set, which means its security is not a single number but a parameter that varies per pathway. When you audit a LayerZero integration, you are not auditing one trust model. You are auditing every configuration that touches the path.
Stargate sits one layer up. It is a cross-chain liquidity protocol built on top of LayerZero — a cross-chain AMM that lets users move native assets between chains without wrapping. Where LayerZero passes messages, Stargate supplies the pooled liquidity that makes those messages settle into real transfers. The two are structurally coupled: Stargate cannot function without LayerZero's messaging, and LayerZero gained a flagship application the moment Stargate existed. That coupling is why the acquisition was inevitable and why the token merge is the logical last step.
The acquisition history matters. LayerZero Labs acquired Stargate, and a token merge is the terminal phase of that integration. When one entity absorbs another, the absorbing entity's token becomes the single unit of account. The acquired protocol's token is retired. This is standard consolidation mechanics — the same pattern that appears whenever a platform swallows a product. What is worth examining is not that it happened, but how the mechanism was written, and what residue it leaves on the chains.
I have audited my share of these transitions, and the pattern is consistent. In 2017, at the height of the ICO boom, I spent six weeks dissecting the Crowdsale logic inside the Parity Wallet library. I did not read the whitepaper. I wrote Python harnesses to drive the multi-signature paths into edge cases, and I surfaced an integer overflow in the migration function that forced an emergency patch before mainnet deployment. The lesson that stuck was structural rather than specific: the migration path is always the least-tested surface of any token system, because it executes once and nobody rehearses it. Token merges are migration paths wearing a governance hat. That is the lens I brought to this one, and it is why the five-digit constant interests me more than the headline.
Core: the mechanics of a fixed conversion
Now the actual work. The details are where the value — and the risk — live, and they are the part the announcement omits.
The conversion function. A ratio of 0.08634 is a rational number baked into a contract. It is not derived from a time-weighted average price, an oracle feed, or an auction. That means it was chosen, and a choice implies a chooser. Three possibilities explain a fixed ratio this precise.
First, it mirrors a pre-agreed acquisition term. When LayerZero absorbed Stargate, the consideration was almost certainly denominated in a fixed STG-to-ZRO exchange — the same way a stock-for-stock merger fixes a share ratio at announcement and holds it. The five digits are the paper trail of that term.
Second, it reflects a snapshot of relative supplies. If the intent was to preserve the combined fully diluted valuation, the ratio would be a function of the two tokens' circulating supplies at a cut-off block, weighted to land on a defensible number. Five-digit precision is consistent with a supply-weighted calculation.
Third, and least flattering, it is simply an assignment chosen to land on a convenient quantity for the treasury. I cannot rule this out, and the announcement included no derivation. A constant without a published derivation is a claim without a proof.
The critical absence: no price comparison. The source material gives me the ratio and nothing else. No pre-merge STG price. No ZRO price at the cut-off. Without those two numbers, the fairness of 0.08634 is unverifiable. This is not a minor gap. It is the entire question a STG holder cares about. Was 0.08634 above or below the market-implied ratio on the day before the merge? The announcement is silent, and the silence is the shape of the information.
Verification is the only trustless truth. A holder who wants to know whether they were made whole has to reconstruct the ratio themselves: pull the STG and ZRO spot prices at the snapshot block, compute the market ratio, and compare. If the fixed ratio sits below the market ratio, the merge transferred value away from STG holders and toward ZRO's existing supply. If it sits above, the reverse. The announcement hands you the fixed side and withholds the floating side. That asymmetry is not an accident of reporting. It is how a favorable term is presented without being defended.
The supply question. ZRO is understood to carry a fixed total supply, on the order of one billion tokens. A merge that converts STG into ZRO requires those ZRO to come from somewhere. Two sources are possible. Either the conversion is drawn from an existing ecosystem or treasury allocation — in which case no new supply enters circulation and the merge is purely a redistribution of an already-allocated bucket — or the conversion involves minting against the cap, which would require the cap to be more elastic than advertised. The announcement does not say which. If the conversion ZRO were pulled from a treasury allocation, the marginal sell pressure is diluted across the schedule. If they were minted, the dilution is immediate. The difference between redistribution and issuance is the difference between a neutral merge and a dilutive one, and the announcement collapses both into a single number.
The migration surface: custodial versus on-chain. Here the mechanism splits into two populations, and they are not treated equally.
On Binance, the merge was automatic. The exchange held the STG, applied the ratio, credited ZRO, and disabled STG deposits and withdrawals. Clean. Deterministic. No user action required, and no window for error.
On-chain is the opposite. STG held in self-custody wallets, in DeFi liquidity pools, in lending markets as collateral, or in bridge contracts does not move unless someone moves it. There is no central operator to sweep the state. The migration has to be claimed, and claiming has a deadline, and deadlines are where assets die.
This is the failure mode I keep returning to across every protocol I analyze. The most dangerous state in any migration is neither the converted asset nor the unconverted asset — it is the asset sitting in a contract that nobody updated. A STG liquidity position in a pool whose router was never upgraded to recognize ZRO becomes an orphan. The liquidity is technically present and functionally frozen. I have watched this pattern since DeFi Summer 2020, when I built a local Ethereum testnet to simulate liquidation cascades and discovered that the fragility was never in the primary asset. It was always in the integrations one layer out.
Let me be concrete about where on-chain STG can be stranded, because the categories are finite and each one is a separate migration path that had to be handled independently.
Liquidity positions in Stargate's own pools. If the pools were migrated, fine. If not, the LP tokens reference a deprecated asset and the reserves go stale.
STG used as collateral in lending markets. Any market that priced STG needs a new oracle feed for ZRO. Until it updates, the collateral is either frozen or mispriced, and a mispriced collateral is a liquidation cascade waiting for a volatility spike.
STG held inside yield vaults and aggregators. Any vault that carried STG as a strategy asset inherits the same problem, and vaults are the hardest to migrate because the depositor may not even know the vault held STG.
Bridged or wrapped STG on chains where the merge tooling never deployed. The token exists, the redemption path does not.
Each of these is a distinct surface. The Binance announcement tells me exactly one of them — the custodial one — was clean. The other three are unaddressed by the note, and unaddressed surfaces are where the losses concentrate.
The zombie token problem. The source material notes that old STG no longer supports deposits or withdrawals on Binance. Consider what that does to the token's liquidity topology. A token's usable value depends on where it can be traded. If one major venue disables deposits and withdrawals, the token becomes locally trapped on that venue and un-settleable elsewhere. If other venues have not yet completed the merge, a spread opens between venues. Arbitrageurs would exploit it, but only if they can move the asset — and moving it is precisely what has been disabled on one side of the trade.
The more durable consequence is the emergence of a zombie token. A zombie token is an asset with a live contract, a dead market, and holders who believe it still has value. It trades on whatever thin venue remains, at a price disconnected from any fundamentals, because the only buyers are participants who have not yet learned the merge happened. I have seen this before — the post-migration residue of tokens everyone assumed would be cleaned up and never were. The residue is not harmless. It is a standing invitation to the exact audience that preys on uninformed holders.
Silence in the code speaks louder than hype. The code here said nothing about the zombies. The announcement said nothing about the zombies. The zombies exist regardless, and they will keep existing until someone writes a sweep function that nobody has announced.
Value capture: where does Stargate's revenue go now? The token merge is not only an accounting event. It is a statement about value capture, and this is the part of the event with the longest half-life.
Stargate, as a standalone protocol, had a fee surface. Cross-chain swaps paid fees, and those fees accrued to the protocol and, through the token, to STG holders. When STG is retired into ZRO, that fee surface has to be redirected somewhere, and the destination determines whether the merge created value or merely relocated it.
Path A — revenue flows to ZRO holders. Stargate's fees are routed into the LayerZero treasury or distributed to ZRO stakers. This is the value-preserving outcome. The combined entity captures more, and the absorbing token reflects it. A holder ends up with fewer tokens representing a larger claim.
Path B — revenue stays inside the product. Stargate's fees fund Stargate's own operations, and ZRO holders receive governance exposure without a claim on cash flow. This is the value-diluting outcome. ZRO's holder base widens through the merge, but its per-token claim on economic output stays flat or falls. A holder ends up with more holders chasing the same slice.
The announcement does not say which path was taken. That is the single most important unanswered question in the entire event, and it is invisible to anyone reading the merge note as a simple conversion. Metadata is just data waiting to be verified. The merge ratio is metadata about an economic decision. Until the value-capture mechanism is disclosed and checkable, that metadata is unverified — and an unverified claim about value capture is worth exactly the cost of the paper it is printed on.
I have benchmarked state transition functions across rollup designs, and I know how long finality actually takes once a settlement layer is added to an execution layer. A cross-chain fee that takes seconds to accrue but months to be reallocated is not a fee that flows to anyone in particular. It is a fee that flows to whoever controls the reallocation. When the reallocation destination is undisclosed, the honest assumption is that it flows to the party with the most control, not the most stake.
The DVN trust assumption, unchanged. One thing the merge did not touch is the security model. LayerZero's DVN configuration is the load-bearing element of its trust assumptions, and a token merge does not alter it. Stargate's liquidity now sits inside a stack whose message verification depends on whichever DVN set is active for each pathway.
This matters because the merge concentrates. Before, a failure in Stargate's liquidity logic was contained to Stargate. After, Stargate's liquidity is inside LayerZero's perimeter, and a DVN misconfiguration on a LayerZero pathway is now a Stargate pathway. Consolidation reduces the surface area for bugs while increasing the blast radius of the bugs that remain. That is the trade every integration makes, and it is almost never stated in the announcement. The announcement sells the efficiency. The efficiency is real. The concentration is also real.
Failure modes, ranked.
| Failure mode | Trigger | Probability | Impact | Observable signal | |---|---|---|---|---| | Un-migrated on-chain STG | Deadline passed, no claim | Medium | Medium | Stargate TVL drop; STG contract still receiving transfers | | Orphaned LP positions | Router never upgraded | Medium | Medium | Pool reserves stale; swap reverts | | Misoriented collateral | Oracle feed not updated | Medium | High | Liquidation cascade on volatility spike | | Cross-venue arbitrage residue | Venues on different merge timelines | Medium | Low | STG price spread across venues | | ZRO marginal sell pressure | Converted supply distributed | Medium | Medium | Exchange net inflow spike post-merge | | Governance concentration | STG voting power absorbed into ZRO | Medium | Medium | Top-holder concentration shift | | Taxable event misjudged | Holder treats swap as non-event | Low | Medium | Jurisdiction-dependent |
Contrarian: this is a governance event, not a liquidity event
The consensus read on this merge is economic. STG holders receive ZRO, ZRO supply expands, price does something. That framing misses the structural change entirely, and the structural change is the one that matters over a horizon longer than a week.
What actually happened is a governance consolidation. STG was a governance token. It carried voting rights over Stargate's parameters — pool fees, pathway selection, treasury allocation, and the right to veto changes to any of them. When STG is retired into ZRO, those rights do not evaporate. They migrate, and they dilute. A holder who held 1 STG now holds 0.08634 ZRO, and that ZRO carries governance weight inside a much larger system.
The effect is the dilution of voice. Before the merge, a STG holder had concentrated influence over a focused protocol. After, the same economic stake translates into a diluted fraction of control over a sprawling omnichain stack. The holder did not lose tokens. The holder lost leverage. Those are not the same thing, and only one of them shows up in a wallet balance.
This is the pattern that should concern anyone who cares about decentralized governance rather than decentralized branding. Token merges are the quietest form of centralization in the industry, because they arrive under the banner of integration and efficiency, and nobody frames a conversion ratio as a power grab. But a five-digit constant can be exactly that: the mathematical form of a decision made by a small group, applied to a large group, presented as arithmetic. A ratio is the least confrontational way to take something away from someone.
I wrote after my composability stress-testing work that the fragility was never in the primitive — it was in the integration. The same holds here. The fragility is not in ZRO or in STG. It is in the assumption that a merge preserves everything the two tokens represented. It preserves the supply. It does not automatically preserve the rights, the fee claim, or the governance leverage. Those have to be preserved deliberately, and deliberate preservation leaves a paper trail. This merge left a ratio and a completion notice.
Regulatory footnote. A token swap is, in several jurisdictions, a taxable disposal of the old asset and an acquisition of the new one at the fixed ratio. A holder who treated the merge as a neutral rebrand may have created a reportable event without a single trade, without a single decision, and without a single line of disclosure. The announcement did not mention this, because exchanges do not give tax advice and are not obligated to volunteer it. The obligation lands on the holder regardless, and a fixed ratio makes the cost basis easy to compute and hard to argue away.
Takeaway: what to watch now
The event is closed. The ratio is fixed. The migration window on Binance has shut. What remains is a set of open questions that will determine whether the merge was value-neutral or value-extractive, and each one resolves into an observable signal.
One — Stargate's on-chain TVL. If total value locked holds after the migration deadline, the integration preserved the protocol's economic function and the orphaned-residue thesis was overstated. If it bleeds, the un-migrated surface was larger than anyone admitted, and the zombies are real.
Two — ZRO exchange net inflow. Converted supply arriving on exchanges is potential sell pressure. A spike in net inflow in the days following distribution is the market telling you, in the only language that settles, how STG holders felt about 0.08634.
Three — the value-capture disclosure. Does Stargate's fee revenue reach ZRO holders? This single question determines whether the merge was a merger or an absorption. Until it is published and verifiable, the fair assumption is the less favorable one. Unverified value claims default to zero.
Four — the next integration. A platform that has absorbed one flagship protocol rarely stops at one. The merge of STG into ZRO is not an endpoint. It is a template. The interesting question is no longer what happened to Stargate. It is which protocol is next, and what constant will be written into its retirement.
I trust the null set, not the influencer. On this event the null set is loud: no price comparison, no value-capture disclosure, no governance record, no migration tally, no derivation for the ratio. The verified facts are three. The ratio. The completion. The disabled deposits. Everything else is narrative dressed as data.
The number is 0.08634. The code will tell you the rest, eventually. It always does — and it always tells you after the window has closed.
