SSS β2.0: Multichain Funding, One Trading Account
How specified ICP, EVM and Solana funding routes connect to unified SSS balances, and what to check before depositing or withdrawing.
- Specified assets from ICP, Ethereum, BNB Smart Chain, Base, Arbitrum and Solana connect to unified SSS balances.
- A funding route and a trading market have separate availability and liquidity checks.
- Check the network, token identity, fees and current preview; verify the original operation before retrying.
Updated October 11, 2026. This article revisits the multichain funding infrastructure developed through β2.0. The app has since entered β3.0; current route status and limits always apply.
SSS aims to make on-chain trading easier to use: bring supported assets into one trading account, trade from a unified balance, and choose an available route when withdrawing.
The β2.0 infrastructure expanded funding beyond ICP to specified EVM and Solana assets. This gives users more ways to reach the same SSS balance, without treating every chain representation as a separate trading asset.
Which networks and assets are covered?
The implemented mainnet funding sources are:
| Network | Specified source assets | SSS balance assets |
|---|---|---|
| Internet Computer | ICP, ckBTC, ckETH, ckUSDC, ckUSDT | ICP, BTC, ETH, USDC, USDT |
| Ethereum Mainnet | ETH, USDC, USDT | ETH, USDC, USDT |
| BNB Smart Chain | BNB, BTCB, USDC, USDT | BNB, BTC, USDC, USDT |
| Base | ETH, USDC, USDT | ETH, USDC, USDT |
| Arbitrum One | ETH, USDC, USDT | ETH, USDC, USDT |
| Solana Mainnet | SOL, USDC, USDT | SOL, USDC, USDT |
EVM routes use native ETH or BNB and the specified token contracts. Solana routes use native SOL and the specified Classic SPL USDC/USDT mints. A matching token name is insufficient: the network and contract or mint must also match.
BTC funding here means ckBTC on ICP or BTCB on BNB Smart Chain. This table does not describe a direct Bitcoin-network route. Token-2022 and arbitrary Solana tokens are outside the listed routes.
These are implemented funding sources. The app shows whether a selected deposit or withdrawal route is currently enabled and usable for the requested amount.
Different sources, one trading balance
Supported USDT can enter through an ICP, EVM or Solana route and be represented as the same canonical USDT balance inside SSS. Likewise, supported ETH sources map to ETH, and ckBTC or BTCB sources map to BTC.
For example, a completed Solana USDT deposit credits the account’s SSS USDT balance. That balance can be used in an available USDT market. A later withdrawal selects its own supported route and passes that route’s current checks.
This simplifies the account experience while keeping the underlying asset and route distinctions visible where they matter: funding, fees and settlement. External wrapped assets retain the risks of their own underlying systems.
Funding support and trading availability
A listed asset is not a promise that every trading pair is open or liquid. Markets, pools and Wallet Swap Flow have their own eligibility, preview and liquidity checks.
Users should check the actual market and quote before trading. Wallets and bots should discover current assets, routes and pools through the developer documentation, rather than hard-code a static list.
SSS Core maintains the internal financial state. Asset Hub and Gateways record external execution, while Data API provides histories and receipts. A submitted request or wallet transaction hash alone does not prove that an SSS balance has been credited or a withdrawal has settled.
Before depositing or withdrawing
Use the app’s funding flow to check the exact network, supported token, destination, minimum amount, fee and expected result before confirming. Sending an unsupported token to an address does not make it a supported deposit.
Available balance and withdrawal capacity answer different questions. A user may own sufficient funds while a selected route has insufficient execution liquidity or an applicable outflow limit. If the app offers another route for the same asset, check its preview before choosing it; a smaller amount helps only when the indicated constraint can be satisfied that way.
If an operation times out or remains pending, open its original funding record and receipt first. Keep the original operation or request ID. Create another withdrawal only after the original result and the supported retry procedure are clear.
Integrating with SSS today
Wallets and bots can start with the Wallet Integration Guide and Funding API.
AI clients now connect through owner-authorized OAuth and Agent Gateway. The former Direct Agent Kit and dedicated Agent Principal execution path are retired. Per-action confirmation is the default, and the owner can revoke the connection. Current Agent capabilities depend on the grant and effective limits; they do not include funding execution, withdrawal or transfer. See the Agent Guide.
The direction remains CEX Experience · DEX Trust: a simpler account experience backed by verifiable on-chain records. SSS remains in public beta, and each funding or trading action uses its current runtime checks.