Skip to article content Sophon

Sophon withdrawals during the chain wind-down

Updated

Sophon withdrawals follow different paths for liquid tokens and managed positions during the wind-down of the legacy chain. Liquid SOPH exits canonically to Ethereum; other liquid tokens use the routes available for their asset. Staked SOPH and vSOPH follow automatic Ethereum transition arrangements. New deposits closed on June 25, 2026, while withdrawals remain available during operation. Completing a canonical exit requires a final Ethereum claim after batch settlement. The late-2026 operating estimate is not a fixed shutdown deadline.

Deposit closure and the remaining exit window

June 25, 2026 marked the closure of new canonical deposits from Ethereum into Sophon. It did not mark the completion of the chain shutdown. Existing holders retained the ability to withdraw through the operational network.

The transition plan expects operation into late 2026, with the final decommissioning date announced in advance. That estimate concerns the chain's availability, not the processing time of an individual withdrawal. Liquid assets need to leave before the final cutoff; the absence of a fixed date does not establish indefinite access.


Liquid balances and positions under automatic transition

A liquid token balance requires a withdrawal, while managed positions follow separate transition arrangements. A staking total or vesting allocation does not automatically equal the SOPH available to claim.

Staked SOPH and vSOPH

Principal released by unstaking

Staked SOPH positions transition to Ethereum automatically. SOPH released by unstaking during the transition is claimable on Ethereum mainnet. Staking ends when the Sophon Chain is decommissioned. The position's migration does not require a new staking action.

Unlocked vesting and rewards

vSOPH represents vesting SOPH and transitions automatically, with existing schedules continuing. The transition schedule set September 29, 2026 at 00:00 GMT as the final Sophon vesting unlock, followed by vesting and claims on Ethereum. That network change does not accelerate vesting. Check the transition portal for unlocked SOPH and outstanding staking rewards, and claim any available amounts.

Guardian NFTs

Guardian NFTs follow an automatic Ethereum transition too. Claim any available Guardian rewards through the transition portal. The transition schedule places node reward accrual and claims on Ethereum after September 29, 2026 at 00:00 GMT. An NFT and its unclaimed rewards are separate from liquid tokens already available in a Sophon wallet.


The canonical SOPH route to Ethereum

SOPH is an ERC-20 token native to Ethereum. Its representation on Sophon came through the canonical bridge, so leaving the chain does not require exchanging it for a replacement token. The transition portal provides the canonical Sophon-to-Ethereum withdrawal route for liquid SOPH. Its withdrawal controls show the selected asset, amount, destination address, and fees before authorization.

LayerZero transfers to and from the Sophon Chain ended on June 25, 2026. The studio's move to building applications on Base does not automatically move a wallet's liquid SOPH there. Ethereum remains the canonical exit destination; a supported onward bridge is a separate choice after that exit.

Visual summary: Sophon withdrawals - The canonical SOPH route to Ethereum

Open full-size image

Routes for ETH, USN, and other balances

Other liquid assets use routes suited to the particular token and destination. The transition portal's Withdraw from Sophon action presents options through Jumper. Those options may reach another chain directly or pass through Ethereum, depending on the asset and available liquidity. A direct route for a non-SOPH token does not change the documented canonical exit for SOPH.

Each route applies to its selected asset and destination. A route offered for one wallet balance does not establish compatibility for its other tokens.


Batch settlement and the final Ethereum claim

A canonical Sophon withdrawal requires its batch and corresponding chain state to be finalized and proven on Ethereum before completion. The source transaction can therefore succeed before the withdrawal becomes claimable. Batch processing, proof generation, and Ethereum finalization determine the wait.

Once the withdrawal becomes ready, the remaining action is the final claim transaction on Ethereum. A source transaction hash identifies the submitted withdrawal; it does not establish that the recipient has received tokens. No fixed hour count replaces the withdrawal's actual settlement status.

A liquid SOPH exit with a pending final claim

Consider a hypothetical withdrawal of liquid SOPH. Sophon's removal from LayerZero rules out a direct LayerZero exit. The portal offers the canonical Ethereum route for this wallet's balance, so the holder selects that path. The source transaction succeeds while the batch still awaits Ethereum settlement. The holder cannot complete the Ethereum claim at this stage.

When the portal shows readiness after batch settlement, the holder submits the final Ethereum claim. The claim succeeds, and SOPH reaches the intended Ethereum address. That destination credit confirms the withdrawal's completion; the earlier Sophon confirmation established only the source-side transaction.

Illustration: Sophon withdrawals: A liquid SOPH exit with a pending final claim

Open full-size image

Withdrawal amounts and the cost of execution

While the legacy chain operates, its transactions use SOPH for gas. ZKsync paymasters can sponsor or customize fees, allowing an application to pay for a user. Sponsorship depends on the application configuration; it does not make every withdrawal free. When a wallet withdraws SOPH and pays its source-chain gas in SOPH, its available SOPH must cover both the withdrawal amount and that gas charge.

The token quantity leaving the chain and the cost of executing the transfer answer different questions. Review each fee in its stated currency alongside the selected amount. The canonical flow includes a later Ethereum claim transaction, so confirming the source operation does not finish the work required for delivery. A changing fee quote cannot supply a permanent withdrawal cost.


Farm balances and permanently committed boosts

Liquid assets left from the former Sophon Farm can use the current withdrawal flow if they remain in the holder's wallet on Sophon. The old farming interface and instructions are archived. The farm programme ended on June 30, 2025; its closure did not turn every former position into an unrestricted liquid balance.

Boosted portions carried a different restriction. The original mechanism permanently committed those assets to an ownerless liquidity position and burned the associated liquidity provider (LP) tokens. Those terms did not permit withdrawal of the committed portion. The chain wind-down does not reverse that commitment, so a route available for a liquid farm balance does not establish recoverability for its permanently boosted portion.

Visual outline: Farm balances and permanently committed boosts (Sophon withdrawals)
Image: Farm balances and permanently committed boosts - diagram

Open full-size image


Onward SOPH transfers after the Ethereum exit

Onward SOPH transfers through LayerZero connect Ethereum, Base, BNB Smart Chain, Arbitrum, Polygon, and Beam. Stopping on Ethereum completes the canonical exit without another bridge.

A successful source transaction for an onward transfer does not confirm destination delivery. The recipient's SOPH balance on the selected destination must reflect the delivered tokens. Keeping the Ethereum withdrawal and any later bridge distinct prevents an unfinished second transfer from being mistaken for a failed chain exit.

What to know about Sophon withdrawals

How can I identify the Sophon network before signing a withdrawal?

The legacy Sophon network uses chain ID 50104 and SOPH as its currency symbol. If the transition portal asks for a connection to that network, the wallet should show that chain ID. The chain name or a familiar token ticker alone does not identify the network of the transaction.

Do I need a fresh SOPH approval for every onward transfer from Ethereum?

An onward Ethereum LayerZero transfer needs sufficient SOPH allowance for the Ethereum adapter. An existing allowance can cover the selected amount, so a fresh approval is unnecessary when it already suffices. This authorization concerns the optional onward transfer, separate from the completed canonical withdrawal.

Can I use the former Sophon LayerZero adapter to withdraw?

The former Sophon NativeOFTAdapter is a legacy contract, not an active withdrawal entry point. The current SOPH architecture uses an Ethereum adapter for supported LayerZero transfers outside Sophon. Liquid SOPH still on the legacy chain leaves through the canonical withdrawal route in the transition portal.

Where can I resolve a farm position that does not appear as a liquid balance?

Sophon directs position-specific farm problems to its own Discord or X accounts. An unsolicited farm-migration or claim message does not establish a valid recovery route.

How precise can the SOPH amount be when I bridge onward after withdrawing?

The documented SOPH LayerZero routes accept amounts with at most six decimal places without dust rounding. SOPH has 18 token decimals, while its LayerZero token contracts use six shared decimals. This precision rule concerns the onward LayerZero transfer; it does not establish a universal minimum withdrawal amount.