# CCIP Service Limits (TON)
Source: https://docs.chain.link/ccip/v1/ton/service-limits
Last Updated: 2026-04-13

> For the complete documentation index, see [llms.txt](/llms.txt).

> **NOTE: Contact for Exception Requests**
>
> If you consistently need more gas for your use case, please reach out to your Chainlink Labs point of contact or
> contact us via this [contact form](https://chain.link/ccip-contact).

## EVM to TON

These limits apply to messages sent from an EVM-compatible chain to the TON blockchain.

| Item                        | Description                                                                                                                | Limit                  |
| :-------------------------- | :------------------------------------------------------------------------------------------------------------------------- | :--------------------- |
| Maximum message data length | The data payload sent within the CCIP message.                                                                             | 30,000 bytes           |
| Message execution gas limit | The user-specified `gasLimit` (in nanoGRAM) in `extraArgs` for the execution of the `ccipReceive` function on TON.         | 4,200,000,000 nanoGRAM |
| Smart Execution time window | The maximum duration that CCIP will attempt to automatically execute a message on TON before manual execution is required. | 8 hours                |
| Out of Order execution      | The `allowOutOfOrderExecution` parameter in the `extraArgs` of a CCIP message from an EVM chain.                           | Must be `true`         |

## TON to EVM

These limits apply to messages sent from the TON blockchain to an EVM-compatible chain.

| Item                        | Description                                                                                                                | Limit          |
| :-------------------------- | :------------------------------------------------------------------------------------------------------------------------- | :------------- |
| Maximum message data length | The data payload sent within the CCIP message.                                                                             | 30,000 bytes   |
| Message execution gas limit | The user-specified `gasLimit` in `extraArgs` for the execution of the `ccipReceive` function on the destination EVM chain. | 3,000,000 gas  |
| Smart Execution time window | The maximum duration for the execution of a CCIP message on the destination EVM chain before manual execution is required. | 8 hours        |
| Out of Order execution      | The `allowOutOfOrderExecution` parameter in the `extraArgs` of a CCIP message from TON.                                    | Must be `true` |

> **CAUTION: Educational Example Disclaimer**
>
> Please note, this page contains community examples only — these are not Chainlink products or services and are not
> supported or maintained by Chainlink. This code represents an example of using a Chainlink product or service, and is
> intended for demonstration and educational purposes only. It is provided "AS IS" and "AS AVAILABLE" without warranties
> of any kind, may not have been audited, and may omit checks or error handling. Each party intending to use this
> example code does so entirely at their own risk and must perform its own audits, security and code review, key
> management, and testing before any production deployment and ensure the operation and performance of such code matches
> expectations. Neither Chainlink Labs nor the Chainlink Foundation deploys, operates, monitors, maintains or endorses
> any deployment of this code. Note that this is not a Chainlink product, feature or service, and there are no
> commitments made with respect to the code, including compatibility with future Chainlink releases. You should not rely
> on this code without first conducting your own technical, engineering, and security review. This code is also outside
> the scope of any Chainlink bug bounty programs. Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node
> operators are responsible for outcomes due to errors in this example or how it is deployed or operated, or liable for
> any resulting claims or damages. Use of the Chainlink Network is subject to the Chainlink Foundation [Terms of
> Service](https://chain.link/terms), which provides important information and disclosures. By using this code, you
> acknowledge and agree to these terms.