> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/common.md).

# TON Basics

Wallets, jettons, messages, and transaction sending for STON.fi integrations on TON.

STON.fi integrations on TON use wallets to sign and send messages to smart contracts. This section introduces the shared concepts used by the DEX, Farm, and Omniston guides.

## Wallets and jettons

A TON wallet is a smart contract that sends messages authorized by its owner. Applications connect user wallets through TonConnect or use a signing library for an application-controlled wallet.

Jettons are fungible tokens on TON. Each jetton has a master contract that identifies the token and separate jetton wallet contracts that hold each owner's balance. The jetton master address identifies the asset; a jetton wallet address identifies a specific owner's token holding.

See the [TON jetton documentation](https://docs.ton.org/contracts/standard/tokens/jettons/how-it-works) for the master and wallet model.

## Messages and transactions

A contract processes an incoming message and can send messages to other contracts. A single swap or liquidity operation can involve several transactions across those contracts. The product guides explain how to track the operation and read its result.

For the underlying model, see [Messages and transactions](https://docs.ton.org/foundations/messages/overview) in the TON documentation.

## Send a transaction

Start with [Transaction sending](/developer-section/common/transaction-sending.md) for the message parameters returned by product SDKs, then choose your wallet library:

* [TonConnect](/developer-section/common/transaction-sending/tonconnect.md): connected user wallets.
* [TON Core](/developer-section/common/transaction-sending/toncore.md): application-controlled wallets using `@ton/ton`.
* [TonWeb](/developer-section/common/transaction-sending/tonweb.md): TonWeb wallet integrations.

For transactions built by Omniston, use [TON wallet integration](/developer-section/omniston/sdk/ton.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 by asking a question.

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

```
GET https://docs.ston.fi/developer-section/common.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.