# CCIP Service Limits (EVM) Source: https://docs.chain.link/ccip/evm/service-limits Last Updated: 2025-05-19 > For the complete documentation index, see [llms.txt](/llms.txt). CCIP enforces service limits to maintain reliable and predictable cross-chain execution. Limits are enforced during message processing and execution. Values vary by chain and deployment. ## EVM Chains | Item | Description | Limit | | :----------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------- | | Maximum message `data` length | `data` payload sent within the [CCIP message](/ccip/evm/api-reference/v2.0.0/client#evm2anymessage). | 32 kilobytes | | Maximum number of tokens | Maximum number of token transfers (entries in the message's `tokenAmounts` array) a user can include in a single message. | 1 | | Token Pool Execution Gas Limit | Maximum gas for executing the combined steps in token pools during cross-chain transfers, including (1) `balanceOf` check before minting/releasing, (2) `releaseOrMint` function, and (3) `balanceOf` check after minting/releasing. For more details on building custom token pools and handling gas constraints, refer to the [Token Pools documentation](/ccip/concepts/cross-chain-token/overview#token-pool-gas-requirements). | 90,000 | | Message Execution Gas Limit | User-specified [gas limit](/ccip/evm/api-reference/v2.0.0/client#genericextraargsv2). | Varies by destination chain (see table below) | ### Message Execution Gas Limit by destination chain > These limits are for CCIP 2.0 lanes. For CCIP V1 lanes, see the [V1 service limits](/ccip/v1/evm/service-limits). | Destination chain | Gas limit | | :---------------- | :-------- | | 0G | 15M | | Arbitrum | 15M | | Avalanche | 15M | | Base | 15M | | BNB Chain | 15M | | Ethereum | 15M | | HyperEVM | 15M | | Ink | 15M | | Mantle | 15M | | Plasma | 15M | | Plume | 15M | | Polygon | 15M | | Unichain | 6M | ## Network-Specific Limitations Some EVM networks have additional constraints beyond the standard limits above: | Network | Special Considerations | Documentation | | -------- | ------------------------------------------------- | ------------------------------------------------------------ | | HyperEVM | Data availability limitations during RPC downtime | [HyperEVM Service Limits](/ccip/evm/service-limits/hyperevm) | ## Private / Permissioned Network Limitations Some CCIP integrations are with private / permissioned networks. CCIP's integration with these networks depends on a single centralized RPC provider rather than a distinct set of local nodes or RPCs used by node operators. As a result: - Transaction data sourced from these networks cannot be independently verified across multiple nodes in the same way as public chains. - A compromised RPC provider could manipulate transaction data, up to and including theft of bridged funds. - Anomalous or malicious activity on these networks may be harder to detect and alert on, as monitoring infrastructure relies on the same private RPC layer. Developers and integrators building CCIP integrations on private / permissioned networks should review these constraints carefully and implement additional safeguards for their use case. Safeguards include, but are not limited to, more conservative token pool rate limits, monitoring of messages and token transfers, and emergency preparedness. > **CAUTION: Disclaimer** > > Chainlink CCIP is an interoperability messaging protocol. Chainlink does not hold or transfer any assets. The > performance and behaviour of applications using Chainlink CCIP may depend on coding, engineering, configuration, and > other technical implementation choices made by developers, token issuers, Cross-Chain Verifiers, and other > participants. Users remain responsible for evaluating, configuring, testing, deploying, operating, and maintaining > their own applications and integrations, including assessing any applicable operational, security, technical, and > legal or regulatory risks. Please review the [Chainlink Terms of Service](https://chain.link/terms) which provides > important information and disclosures. By using Chainlink CCIP, you expressly acknowledge and agree to accept these > terms. Cross-Chain Verifiers (CCVs) may be operated by third parties. The security, availability, governance, and > operational profile of a CCV varies depending on the verifier selected. Users are solely responsible for evaluating > any CCVs used in connection with their applications or integrations and determining whether they are appropriate for > their intended use case. This code represents an example of using a Chainlink product or service. It is provided "AS > IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may omit checks or error handling. > Each party intending to use this reference implementation must perform its own audits, security and code review, and > testing before any production deployment and ensure the operation and performance of such code matches expectations. > 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. Use of the Chainlink Network is subject to the Chainlink > Foundation Terms of Service, which provides important information and disclosures. By using this code, you acknowledge > and agree to these terms.