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

# TON Core

Send a complete SDK parameter array with an existing WalletContractV4 signer.

Use `@ton/ton` with an application-controlled wallet. Configure a `TonClient` for the intended network and open `WalletContractV4` using your existing signer's public key. Derive keys with `@ton/crypto` or your trusted signer setup; do not embed private material in example source.

The function below accepts the opened wallet, its existing signing key, and SDK `get*TxParams` messages built for that wallet. This Wallet V4 recipe supports one to four messages.

```ts
import { SendMode, internal, type WalletContractV4 } from "@ton/ton";
import type { OpenedContract, SenderArguments } from "@ton/core";

async function sendBuiltTransactions(
  wallet: OpenedContract<WalletContractV4>,
  secretKey: Buffer,
  txParams: SenderArguments[],
) {
  if (txParams.length < 1 || txParams.length > 4) {
    throw new Error("Wallet V4 requires one to four complete messages");
  }
  await wallet.sendTransfer({
    seqno: await wallet.getSeqno(),
    secretKey,
    timeout: Math.floor(Date.now() / 1000) + 300,
    sendMode: SendMode.PAY_GAS_SEPARATELY,
    messages: txParams.map((params) => internal(params)),
  });
}
```

Use the [official wallet example](https://github.com/ton-org/ton/blob/master/README.md) for initialization. Match the builder's sender to this wallet, preserve all messages, and coordinate wallet seqnos when concurrent requests share a signer. `sendTransfer()` does not return a completed product operation or a universal transaction hash; obtain the outgoing transaction through wallet/RPC lookup and use the product's result instructions.

Omniston hex message/state-init data needs its own adapter before a low-level wallet call; see [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/transaction-sending/toncore.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.