​
Overview

The SOPH token was minted on Ethereum mainnet and canonically bridged to Sophon as the native fee token. To enable seamless cross-chain functionality, we added an OFTAdapter (Omnichain Fungible Token Adapter) on Sophon that allows easy bridging to other supported chains.

​
Contract Addresses

ChainAddress
Ethereum0x6B7774CB12ed7573a7586E7D0e62a2A563dDd3f0 (link)
Sophon0x000000000000000000000000000000000000800A (link)
Sophon (WSOPH)0x2b1A859dE6A55c553520D7780Bc5805712B128F9 (link)
Sophon (NativeOFTAdapter)0x70ff61C1436d19090321A312b1f4be89D62ac55C (link)
BSC0x31DbA3c96481FDe3CD81C2aaF51F2D8bf618C742 (link)
Base0x31DbA3c96481FDe3CD81C2aaF51F2D8bf618C742 (link)
Arbitrum0x31DbA3c96481FDe3CD81C2aaF51F2D8bf618C742 (link)
Polygon0xEb971Fd26783f32694dbB392dD7289de23109148 (link)
Beam0x31DbA3c96481FDe3CD81C2aaF51F2D8bf618C742 (link)

​
Technical Implementation

Architecture:
  • Ethereum Mainnet: Original ERC20 token contract
  • Sophon: Canonically bridged as the native fee token with an additional OFTAdapter for cross-chain bridging
  • Other Chains: OFT (Omnichain Fungible Token) implementations that connect through LayerZero
This design ensures that SOPH maintains its native status on Sophon while providing users with the flexibility to bridge their tokens to other major blockchain networks for DeFi activities and broader ecosystem participation.

​
Bridging Flow

  • Ethereum ↔ Sophon: Use the canonical ZKsync bridge
  • Sophon ↔ Other Chains: LayerZero OFT bridging
  • Ethereum ↔ Other Chain: Currently not supported
We want to avoid having multiple SOPH addresses on the same chain

​
Key Features

  • Native Fee Token: SOPH serves as the native gas token on Sophon
  • Cross-Chain Compatibility: Seamless bridging to major blockchain networks
  • LayerZero Integration: Leverages LayerZero’s omnichain infrastructure for secure cross-chain transfers
  • Wrapped Version: WSOPH available for DeFi applications requiring ERC-20 compatibility

​
LayerZero OFT

To support the bridging with LayerZero, the OFT adapter and OFT tokens linked above were created.
  • The adapters are owned by a Sophon Foundation Multisig on each chain, which only has permission to set delegates.
  • The adapters’ main delegate is also the same Sophon Foundation Multisig, and the delegate has permission to add new routes for new chains.
This structure doesn’t give the Sophon Foundation any powers over the token itself. The security of minting and burning is still ensured by the LayerZero protocol itself. The foundation can just include new routes for new chains. A script that shows and validates the configurations above (and the approval needed) can be found here.