> For the complete documentation index, see [llms.txt](https://wiki.sidusheroes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.sidusheroes.com/sidus-senate-token-utilities/step-by-step-guide-on-bridging-sidus-to-ton.md).

# Step-by-Step Guide on Bridging SIDUS to TON

<figure><img src="/files/ZwQXTP8woKUyUVWWNcJR" alt=""><figcaption></figcaption></figure>

The SIDUS/TON pool on STON.fi is now live, offering you a new way to make your tokens work for you. This guide will take you through the essential steps to get started, ensuring you can easily bridge SIDUS tokens to the TON network and become a Liquidity Provider. Without further ado, let's get your SIDUS into the pool!

### Bridge from Ethereum to Tonchain

1. Open <https://bridge.ton.org>.
2. Click "Connect Ethereum" in the upper right corner and connect your address using Metamask or WalletConnect.
3. In the Asset field, select "Other tokens".
4. In the "Token address in ETH network" field, enter 0x549020a9Cb845220D66d3E9c6D9F9eF61C981102.
5. Enter the number of tokens in the Amount field. To exchange 10 Sidus, enter 10 (you can only bridge integer numbers of tokens).
6. In the "Destination address in ton network" field, enter your TON mainnet address. For example, UQDEYvty2KvuaThAVeWerzXTyfDOSPrH36La93ww1w\_sU9BU.
7. In the upper right corner, click the blue "Connect wallet" button and connect your TON wallet.
8. Click the ‘Approve’ button and confirm the transaction in Ethereum wallet.
9. Wait for the ‘approve’ transaction to be executed.
10. Сlick the button ‘Transfer’ and confirm the transaction in Ethereum wallet.
11. Wait for 65 confirmations. After that, click the Get button.
12. Confirm the transaction in the TON wallet (1 TON will be spent from your wallet).&#x20;
13. Wait for 9 confirmations.&#x20;
14. If the tokens do not appear in your wallet, you need to add them according to your wallet's instructions. The address to enter is EQAgrnWbYxQno9BMBiRxF41Ab3SSQ6AmUmz7NUbVCj5B7C0A.

### Bridge from Tonchain to Ethereum

1. Open <https://bridge.ton.org>.
2. Hover over "Ethereum network" and select "The open network".
3. Click "Connect Ethereum" in the upper right corner and connect your address using Metamask or WalletConnect.
4. In the upper right corner, click the blue "Connect wallet" button and connect your TON wallet.
5. In the Asset field, select "Other tokens".
6. In the "Destination address in ETH network" field, enter your ETH mainnet address. For example, 0x721d09419d625414b4fABCAAE5313e73E7C3Ddb2.
7. Click "transfer" and confirm the transaction in your TON wallet.
8. Wait for 9 confirmations
9. Click the Get button and confirm the transaction in your Ethereum wallet.

When your SIDUS tokens land on the TON network, you can proceed to the [SIDUS/TON pool on STON.fi](https://app.ston.fi/pools/EQDnltGGcbRPcxv9UlfDmCrXrkqWIj2HKe4GK0nQtC9tpsn6) and add liquidity for rewards!


---

# 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://wiki.sidusheroes.com/sidus-senate-token-utilities/step-by-step-guide-on-bridging-sidus-to-ton.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.