8.3 SOSO Token Cross-Chain Architecture

Overview

SOSO was originally deployed as an ERC-20 token on Ethereum and subsequently made available on Base through the official Base bridge. Following the launch of the ValueChain mainnet, SOSO is designated as the native gas token of ValueChain, currently used for transaction fees, staking and governance across the network.

To support the progressive migration of SOSO from Ethereum and Base to ValueChain, a cross-chain bridging infrastructure has been established.

Lock-and-Release Mechanism

SOSO employs a lock-and-release mechanism for cross-chain transfers, which differs from traditional lock-and-mint bridges that issue wrapped representations of the original asset, given SOSO exists as a native token on ValueChain. The bridging process operates as follows:

  • Source chain (Ethereum / Base): The user's ERC-20 SOSO is transferred to the bridge contract, where it is permanently locked in the bridge contract or the bridge multi-signature wallet.

  • Destination chain (ValueChain): An equivalent amount of native SOSO is released from the bridge reserve to the user's address on ValueChain.

This architecture ensures that every unit of native SOSO circulating on ValueChain is fully backed by an equivalent amount of ERC-20 SOSO locked on the source chain. The total circulating supply across all chains ("Total Supply") remains constant.

One-Way Bridge Design

The current bridge implementation supports one-way transfers from Ethereum and Base to ValueChain. This design reflects the long-term objective of designating ValueChain as the primary venue for SOSO liquidity and settlement while maintaining ERC-20 availability on Ethereum and Base for exchange listings and broader ecosystem accessibility.

Cross-Chain Bridge Contracts

Dedicated bridge contracts are deployed on both Ethereum and Base. Users interact with these contracts directly to initiate a cross-chain transfer. Upon confirmation on the source chain, the corresponding amount of native SOSO is released on ValueChain and delivered to the user's specified address.

SoDEX Deposit Gateway

Users depositing ERC-20 SOSO into the SoDEX trading platform benefit from an integrated bridging flow. The platform automatically handles the cross-chain lock-and-release mechanism, crediting the user's trading account with native SOSO on ValueChain. This abstraction eliminates the need for users to interact with bridge contracts directly.

Source-Chain Token Burn Schedule

Following a cross-chain transfer, the locked ERC-20 SOSO on Ethereum or Base is not immediately burned. Instead, these tokens are held in bridge contracts and secured wallets for an interim period.

This interim model is adopted to ensure the accuracy of Total Supply calculated by major third-party data aggregators such as CoinMarketCap and CoinGecko ("Major Aggregators"). Since these platforms are yet to index ValueChain natively, a premature burn of ERC-20 tokens would result in an undercount of SOSO's Total Supply.

Once Major Aggregators integrate ValueChain and are able to independently track on-chain native SOSO balances, the corresponding ERC-20 tokens locked in bridge contracts and secured wallets will be permanently burned on Ethereum and Base. At this point, Major Aggregators will be able to accurately report SOSO's Total Supply.

Contract Addresses

SOSO Token Contracts

Chain
Address

Ethereum

0x76A0e27618462bDAC7a29104bdcfFf4E6BFCea2D

Base

0x624e2e7fDc8903165F64891672267AB0FCB98831

Ethereum

Name
Address

Bridge Contract

0xCC7322A2f9f82251dA51584B1a89915dBc02185B

Bridge Multi-sign Wallet

0x6aF5c4bbCb468A6ccd0F28c6bf436653F75F7F9c

Base

Name
Address

Bridge Contract

0xCC7322A2f9f82251dA51584B1a89915dBc02185B

ValueChain

Name
Address

Genesis Wallet

0x78F9C66EE26D2d5781252451F2f3F9fbFc60701e

SoDEX Ecosystem Fund

0x3e8EBf6c0dBe8f37b236a7Fd8bF034CEE8B59B58

Bridge Contract

0xB37295d1ea21E65b76dCB2E85e035eE0dBFC70CB

Bridge Multi-sign Wallet

0xb66c5f712db7d679670c73202836709Gb34Ad8Fc

All contract and wallet addresses listed above are publicly verifiable on the respective chains.

Last updated