> For the complete documentation index, see [llms.txt](https://docs.symbiosis.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symbiosis.finance/main-concepts/wrapped-tokens.md). # Symbiosis sTokens and Supported Chains The Symbiosis protocol leverages sTokens, a form of wrapped tokens, to enable cross-chain operations. Discover more about sUSDC, sUSDT, sWETH, and sWBTC in this comprehensive document. ## sToken Introduction The Symbiosis protocol employs sTokens, which stand for synthetic or synthesized tokens. These tokens facilitate cross-chain operations. Despite their resemblance to wrapped tokens, we purposefully refrain from labeling them as such. This distinction ensures they are set apart from the myriad of wrapped tokens prevalent in the DeFi sector.
What is wrapped token? If you would like to refresh your knowledge about wrapped tokens, here is some basic information. Wrapped tokens play several crucial roles in the DeFi ecosystem. Since different blockchains have different technical specifications, not all tokens can interact with all platforms. Wrapping tokens allows them to be used on platforms where they couldn't be used otherwise. A wrapped token in decentralized finance (DeFi) is a type of token that represents an asset hosted on the same or different blockchain. It's called "wrapped" because the original asset is put into a wrapper, or a different blockchain layer. The process of wrapping and unwrapping tokens is typically done through certain organizations or smart contracts, depending on the specific wrapped token. For example, one of the most popular wrapped tokens is Wrapped Bitcoin (WBTC). WBTC is a token on the Ethereum blockchain that represents Bitcoin. Each WBTC is backed 1:1 with a real Bitcoin. This allows Bitcoin to be used directly in Ethereum's ecosystem, enabling it to be utilized in Ethereum's DeFi applications, smart contracts, and DApps. In order to assure the token's credibility, the equivalent amount of the underlying asset is usually locked in a smart contract or held by a custodian, which can be audited to confirm that each wrapped token is fully backed.
## **Transit Tokens: Choice of Tokens for Synthesis** While Symbiosis has the capability to take any token from one blockchain and mint a synthetic counterpart on another, the protocol primarily engages with a select group: namely stablecoins, WETH (Wrapped ETH), and WBTC (Wrapped BTC). {% hint style="info" %} **Transit tokens:** WBTC, WETH and specific stablecoins can be seen as transit tokens in the Symbiosis protocol, since they are used to enable cross-chain operations within the protocol. {% endhint %} But why the focus on just stablecoins, WETH and WBTC? The core objective of Symbiosis is to enable token exchanges across various blockchains. To fulfill this, the protocol prioritizes tokens that maintain consistent value and enjoy wide usage across all supported blockchains. The tokens that meet these criteria are stablecoins, WETH, and WBTC. In cases where multiple stablecoins are present on a blockchain, the Symbiosis protocol typically leans towards one, often opting for USDC, or USDT, based on the specific blockchain. ## **sTokens Usage** #### Stablecoins Let's consider an example: we want to exchange USDC from Ethereum for BUSD on the BNB chain via the Symbiosis protocol. The simplified algorithm of the bridging stablecoins is shown in Scheme 1 below.

Scheme 1. Mint-burn routing during a cross-chain operation performed via the Symbiosis protocol.

Thus, when sending 1 USDC on Ethereum, we would expect to receive 1 BUSD on the BNB chain in an ideal world without transaction fees or varying exchange rates. However, in reality, the amount received will likely be slightly less than the amount sent. #### WETH If we exchange WETH from Ethereum for WETH on Arbitrum, the bridging procedure will be the same with one exception: Octopool with sWETH will be used (Scheme 2).

Scheme 2. Mint-burn routing during a cross-chain operation performed via the Symbiosis protocol.

Thus, when sending 1 WETH on Ethereum, we would expect to receive 1 WETH on Arbitrum in an ideal world without transaction fees or varying exchange rates. However, in reality, the amount received will likely be slightly less than the amount sent. #### **About Symbiosis Host Chain** The Symbiosis contracts with mint-burn logic and Symbiosis Octopools are located on the Symbiosis host chain. {% hint style="info" %} sTokens are used for technical purposes only, and end-users cannot trade sTokens, although they can receive sTokens when adding/removing liquidity to/from Symbiosis Octopool. Comprehensive information on Octopools can be found here: [Symbiosis Octopools](/crosschain-liquidity-engine/symbiosis-octopools.md). {% endhint %} ## Supported Blockchains
The list of blockchains supported by the Symbiosis protocol 1. Abstract 2. ApeChain 3. Arbitrum One 4. Avalanche 5. Base 6. Berachain 7. Bitcoin 8. Bitcoin Cash 9. BNB 10. Boba Ethereum 11. B² Network 12. Citrea 13. Cronos 14. Cronos zkEVM 15. Dogecoin 16. Ethereum 17. Fraxtal 18. Gnosis 19. Goat 20. Gravity 21. HyperEVM 22. Hyperliquid 23. Katana 24. Lighter 25. Linea 26. Litecoin 27. Manta 28. Mantle 29. Merlin 30. Metis 31. Mode 32. Monad 33. Monero 34. Morph 35. opBNB 36. Optimism 37. Plasma 38. Polygon 39. Polygon zkEVM 40. Quai 41. Robinhood 42. Rootstock 43. Scroll 44. Sei v2 45. Solana 46. Soneium 47. Sonic 48. Stable 49. Symbiosis 50. Taiko 51. Telos 52. Tempo 53. TON 54. Tron 55. Unichain 56. XRP Ledger 57. Zcash 58. ZkLink 59. ZkSync Era **Important:** To access the most relevant information, use the [/v1/chains](https://api.symbiosis.finance/crosschain/docs/#/Chains/get_v1_chains) method.
## Next Steps * Use the Symbiosis WebApp: * Learn how sTokens are minted and burned: [Symbiosis Mint-Burn Process](/crosschain-liquidity-engine/synthesizing-process.md) * For integrators: [Symbiosis API](/developer-tools/symbiosis-api.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.symbiosis.finance/main-concepts/wrapped-tokens.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.