> For the complete documentation index, see [llms.txt](https://docs.frontrun.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frontrun.pro/trading/ton-trading-beta.md).

# TON Trading (Beta)

Frontrun supports native TON trading from the sidepanel. TON wallets are [powered by Turnkey](https://turnkey.com/), so Frontrun never has access to your private keys.

{% embed url="<https://x.com/frontrunpro/status/2052825311536939230?s=20>" %}

### Getting in

* Bridge SOL to TON directly inside the sidepanel via [ChangeNow](https://changenow.io/). ETA is shown on every quote.
* Import an existing TON wallet via mnemonic or private key.

{% embed url="<https://www.youtube.com/watch?v=FyTs5AoV7LM>" %}

### Features

* Native TON trading panel with progressive fill toasts (Prepare, Sign, Send, Confirm)
* Auto-fee and slippage controls
* Wallet picker with Tonviewer links and one-click address copy
* Wallet labels and Smart Followers sync to TON addresses on X

### Status

TON trading is in active beta. Surfaces that include TON show a beta indicator in the sidepanel.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frontrun.pro/trading/ton-trading-beta.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.