Skip to main content
Since June 25, 2026, deposits into the Sophon Chain have been disabled and Sophon is no longer connected to LayerZero. Use claim.sophon.com to withdraw SOPH from Sophon.

​
Current architecture

SOPH is an ERC-20 token native to Ethereum. The token at the system address on the Sophon Chain is a canonically bridged representation, not a separate token that needs to be migrated. As part of the chain wind-down, an Ethereum OFT adapter replaced the Sophon NativeOFTAdapter. The Ethereum adapter locks ERC-20 SOPH; it requires token approval before sending. SOPH can also move directly between the other supported LayerZero chains.

​
Supported flows

  • Sophon → Ethereum: use the canonical withdrawal route through claim.sophon.com.
  • Between Ethereum, Base, BNB Smart Chain, Arbitrum, Polygon and Beam: follow Bridge SOPH with LayerZero for contract addresses, endpoint IDs, approval, fee quoting and sending with the official CLI or a contract explorer.
  • Sophon → another chain: first withdraw SOPH canonically to Ethereum, then use LayerZero from Ethereum to the supported destination.
The following flows are no longer supported:
  • Ethereum → Sophon deposits;
  • LayerZero transfers to or from Sophon.

​
Official contract addresses

The previous Sophon NativeOFTAdapter address is a legacy contract and is not a current bridge entry point. For SOPH on Sophon, start from the claim portal. For the other chains, use the current contracts in the LayerZero guide.

​
Exchange and bridge integrations

For partners providing SOPH exchange or bridge services, the June 25 replacement of the Sophon NativeOFTAdapter with an Ethereum OFT adapter is the announced operational change. Existing non-Sophon routes otherwise remain unchanged. Do not treat the legacy Sophon adapter as an active endpoint. See the Sophon Chain migration guide for other assets, managed positions, and the transition timeline.