> 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/transaction-sending.md).

# Transaction sending

Submit complete TON transactions built by DEX, Farm, or an Omniston wallet adapter.

Product guides build an operation; this section submits it through a TON wallet. Use [TonConnect](/developer-section/common/transaction-sending/tonconnect.md) for a connected user wallet, [TON Core](/developer-section/common/transaction-sending/toncore.md) for an application-controlled signer, or [TonWeb](/developer-section/common/transaction-sending/tonweb.md) for an existing TonWeb wallet integration.

## Inputs from product builders

DEX and Farm `get*TxParams` methods return parameters shaped as:

```ts
import type { Address, Cell } from "@ton/core";

type TransactionParams = {
  to: Address;
  value: bigint;
  body?: Cell | null;
};
```

`to` is the target contract, `value` is TON in nanotons attached to the message, and `body` describes the contract operation. The amount includes the value required by that operation; it is not always only gas.

For operations with several messages, such as a two-sided liquidity deposit, send the complete ordered list through a wallet that supports the required message count.

Omniston `TonTransaction` uses a different shape: target/send amount and hex BoC strings, including optional state init. Use the [Omniston TON adapter](/developer-section/omniston/sdk/ton.md) to convert it to wallet input.

## Wallet and network context

Build the operation for the sending wallet and configure its RPC connection for the same network. For TonConnect, configure your application’s public manifest URL and specify transaction validity in Unix seconds.

## Completion and recovery

After submission, record the identifier returned by the wallet/RPC and track the contract operation using the product guide: [DEX swap](/developer-section/dex/sdk/swap.md#check-the-result), [liquidity](/developer-section/dex/sdk/provide-liquidity.md#check-the-result), [Farm](/developer-section/dex/sdk/farm.md), or [Omniston](/developer-section/omniston/sdk/ton.md#track-an-order-and-its-result).

TON contracts process messages asynchronously. Handle wallet rejection, RPC errors, and contract errors separately. Before retrying a submitted operation, query its state to avoid a duplicate submission. See [TON Basics](/developer-section/common.md#messages-and-transactions) for the message model.


---

# 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/transaction-sending.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.