> 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/user-guide-webapp/dealing-with-stokens.md).

# Bridge sUSDC,  sWETH, sWBTC

## sTokens Overview

**sTokens** (sUSDC, sUSDC.e, sWETH, sWBTC) are minted on the **Symbiosis chain** (the Symbiosis Host Chain) and are used within the Symbiosis protocol to enable cross‑chain operations.&#x20;

Users cannot trade sTokens directly, but they may receive them when adding or removing liquidity in **Symbiosis Octopools**.

If you have sTokens and don’t want to simply hold them, you have two options:

1. **Provide liquidity:**\
   Add your sTokens (sUSDC, sWETH, sWBTC, etc.) to a Symbiosis liquidity pool and earn rewards.\
   See [Farming on Octopools](/reward-programs/farming-on-octopools.md) for details.
2. **Bridge back to native tokens:**\
   sUSDC, sWETH, sWBTC, etc. can be bridged 1:1 to USDC, WETH, WBTC, and other supported tokens (see instructions below).

## **About gas on the Symbiosis chain**

The Symbiosis chain uses **SIS** as its native gas token (bridged from Ethereum). SIS can be obtained in two ways:

1. Via the official L2 bridge at <https://symbiosis.bridge.caldera.xyz/>
2. Via [Symbiosis WebApp](https://app.symbiosis.finance/swap?chainIn=Symbiosis\&chainOut=Symbiosis\&tokenIn=SIS\&tokenOut=SIS)

## Bridging sUSDC, sWETH, sWBTC, etc.

sUSDC, sWETH, sWBTC, etc. can be bridged 1:1 back to their native tokens (USDC, WETH, WBTC, etc.) on a corresponding networks.

&#x20;

1. Go to the **Mint and Burn** section in Symbiosis WebApp: <https://app.symbiosis.finance/bridge>\
   \
   **Important:** \
   The **Mint and Burn** section is different from the **Swap** section:\
   ![](/files/Zg9cMnXtPDbNjJBGM3Pe)<br>
2. Connect your wallet.
3. In the **From** field, choose the sToken to bridge (e.g., sWETH on the Symbiosis chain):\
   ![](/files/hrsswqpPUYtL4aXIriZv)<br>
4. In the **To** field, select the destination token (only one option is available for each sToken type, e.g., sWETH → WETH on Arbitrum One).\
   ![](/files/COO19g2IFLnnYQ34NcdO)<br>
5. Enter the amount to bridge:\
   ![](/files/y2WFqQ6C610r18ExpH93)<br>
6. Switch to the Symbiosis chain: click the **Switch network to Symbiosis button**.
7. Press **Burn**, then confirm the transaction in your wallet.
8. Wait for confirmation: the tokens are bridged to the destination network.

{% hint style="info" %}
You can always check status of your cross-chain operations in [Symbiosis Explorer](https://explorer.symbiosis.finance/transactions).
{% endhint %}

Done \
\&#xNAN;**∎**

## Support

{% hint style="warning" %}
Never share your seed phrase, private keys, or wallet recovery information with anyone.
{% endhint %}

If you have any questions, please contact [our support team on Discord](<https://discord.com/invite/ymbRx6ADvR >).&#x20;


---

# 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/user-guide-webapp/dealing-with-stokens.md?ask=<question>&goal=<endgoal>
```

`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.
