Ccip updates (#3282)

* nonce manager updates + billing bps update

* update llms

Author: gfletcher-cll

reports/llms-report.json

@@ -1,5 +1,5 @@
 {
-  "startedAt": "2025-12-12T16:45:20.957Z",
+  "startedAt": "2025-12-12T18:52:31.071Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
@@ -30,9 +30,9 @@
       "section": "ccip",
       "pagesProcessed": 260,
       "outputPath": "src/content/ccip/llms-full.txt",
-      "bytes": 2849877,
+      "bytes": 2848574,
       "prevBytes": 2849877,
-      "deltaBytes": 0
+      "deltaBytes": -1303
     },
     {
       "section": "data-feeds",
@@ -87,8 +87,8 @@
       "pagesProcessed": 12,
       "outputPath": "src/content/resources/llms-full.txt",
       "bytes": 341272,
-      "prevBytes": 339715,
-      "deltaBytes": 1557
+      "prevBytes": 341272,
+      "deltaBytes": 0
     },
     {
       "section": "architecture-overview",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-12-12T16:45:24.639Z"
+  "finishedAt": "2025-12-12T18:52:34.836Z"
 }

src/components/CCIP/ChainHero/LaneDetailsHero.tsx

@@ -147,7 +147,7 @@ function LaneDetailsHero({
             label="Out of Order Execution"
             clipboardType="out-of-order-execution"
             tooltip={
-              <StyledTooltip tip="Controls the execution order of your messages on the destination blockchain. Setting this to true allows messages to be executed in any order. Setting it to false ensures messages are executed in sequence, so a message will only be executed if the preceding one has been executed. On lanes where 'Out of Order Execution' is required, you must set this to true; otherwise, the transaction will revert." />
+              <StyledTooltip tip="Currently controls the execution order of your messages on the destination blockchain. Required = Must be set for all messages, and to True. Optional = Can be set, and if set to True, enables Out-of-Order messaging. Note: Being deprecated in early 2026; OOO becomes default and only option." />
             }
           >
             {getOutOfOrderText(enforceOutOfOrder)}

src/config/data/ccip/data.ts

@@ -171,7 +171,7 @@ export const events: VersionedEvents = {
 export const networkFees: NetworkFees = {
   tokenTransfers: {
     [TokenMechanism.LockAndUnlock]: {
-      allLanes: { gasTokenFee: "0.07 %", linkFee: "0.063 %" },
+      allLanes: { gasTokenFee: "0.05 %", linkFee: "0.063 %" },
     },
     [TokenMechanism.LockAndMint]: {
       fromEthereum: { gasTokenFee: "0.50 USD", linkFee: "0.45 USD" },

src/content/ccip/concepts/architecture/onchain/aptos/components.mdx

@@ -85,18 +85,9 @@ When the Router forwards a `ccip_send` request, the OnRamp performs the followin
   - If the message involves token transfers, it initiates a secure callback pattern by calling the `Token Admin Dispatcher`.
   - The dispatcher uses the `Token Admin Registry` to store the message context (sender, receiver, etc.) before invoking the correct `Token Pool` to `lock_or_burn` the assets.
 
-- **Nonce Management**
-  - For ordered messages, it calls the `Nonce Manager` to retrieve and increment the sender's nonce for that destination.
-
 - **Event Emission**
   - Generates a unique `messageId` and emits a `CCIPMessageSent` event containing the complete, sequenced message details.
 
-## Nonce Manager
-
-The `ccip::nonce_manager` module enables optional strict message ordering. It tracks outbound nonces on a per-sender and per-destination-chain basis.
-
-When out-of-order execution is disabled for a message, the `OnRamp` module uses the `Nonce Manager` to assign an incrementing nonce, which is then verified by the `OffRamp` on the destination chain.
-
 ## OffRamp
 
 The `ccip_offramp::offramp` module is an internal CCIP module that operates on the destination chain. It is the primary module that the offchain DONs interact with to deliver messages to Aptos.

src/content/ccip/concepts/architecture/onchain/evm/components.mdx

@@ -81,7 +81,7 @@ When the Router forwards a `ccipSend()` request to the OnRamp, the contract perf
    - If the message involves token transfers, it retrieves the correct Token Pool from the Token Admin Registry.
    - Initiates calls to lock or burn the token, based on the token handling mechanism.
 1. **Nonce Management**
-   - Uses the Nonce Manager to ensure messages requiring in-order execution are processed in the correct order.
+   - Uses the Nonce Manager to ensure messages requiring in-order execution are processed in the correct order. Note: In-Order enforcement using Nonce Manager will be deprecated in early 2026.
 1. **Message ID Generation**
    - Returns a unique message ID to the Router.
 1. **Event Emission**
@@ -151,17 +151,6 @@ The FeeQuoter is an internal CCIP smart contract that calculates and returns CCI
 
 For additional details on how CCIP fees are calculated, refer to the [CCIP Billing page](/ccip/billing).
 
-## NonceManager
-
-The NonceManager helps order messages in CCIP by tracking outbound nonces on the source blockchain and inbound nonces on the destination blockchain. It ensures strict ordering when the message's extraArgs parameter requires ordering, thus providing a flexible design.
-
-1. **Ordered Messages**
-   - **Non-zero Nonces:** When an OnRamp identifies a message that must preserve ordering, it increments and assigns a non-zero outbound nonce.
-   - **Inbound Validation:** On the destination blockchain, the OffRamp checks that the incoming message's nonce matches the expected inbound nonce. If there is a mismatch, the message is skipped or deferred for later retry.
-1. **Out-of-Order Messages**
-   - **Zero Nonces:** For messages marked "out of order," the OnRamp sets the nonce to **0**.
-   - **No Sequence Checks:** Because `nonce == 0` indicates no ordering, the OffRamp does not validate or increment inbound nonces. These messages can execute immediately without waiting for earlier messages.
-
 ## Token Admin Registry
 
 The Token Admin Registry is a user-facing CCIP smart contract that maintains a one-to-one mapping between token addresses and their corresponding token pool addresses on a given chain. The OnRamp and OffRamp contracts use the Token Admin Registry to retrieve a token's configured token pool address to call the appropriate functions:

src/content/ccip/concepts/best-practices/evm.mdx

@@ -4,7 +4,7 @@ date: Last Modified
 title: "CCIP Best Practices (EVM)"
 metadata:
   description: "Comprehensive security guide for CCIP on EVM chains covering message verification, gas optimization, token administration, liquidity management, multi-signature protection, and chain-specific considerations for building secure cross-chain applications."
-  image: "/images/ccip/ccip-hl-v1.6.gif"
+  image: "/images/ccip/ccip-hl-v1.6.png"
   excerpt: "ccip evm best practices ethereum security message verification gas limit optimization token administration liquidity management multi-signature contracts ccip receiver extra args defensive programming"
   datePublished: "2025-05-19T11:22:47Z"
   lastModified: "2025-05-19T11:22:47Z"
@@ -82,7 +82,7 @@ The `allowOutOfOrderExecution` parameter enables you to control the execution or
 - **When `allowOutOfOrderExecution` is Optional:**
   - You can set `allowOutOfOrderExecution` to either `true` or `false`, depending on your application's requirements.
     - **`true`:** Messages can be executed in any order relative to other messages from the same sender. If a previous message has not yet been executed on the destination chain, it does not block the execution of subsequent messages.
-    - **`false`:** Messages are executed in order. CCIP ensures that preceding messages are processed before executing the current message.
+    - **`false`:** Messages are executed in order. CCIP ensures that preceding messages are processed before executing the current message. Note: Functionality for `allowOutofOrderExecution` = `false` (ie., enforcing In-Order cross-chain messages) is being deprecated in early 2026.
 
 - **When `allowOutOfOrderExecution` is Required:**
   - You **must** set `allowOutOfOrderExecution` to `true`. This setting acknowledges that messages may be executed out of order. If set to `false`, the message will revert and will not be processed.

src/content/ccip/llms-full.txt

@@ -1096,7 +1096,7 @@ When the Router forwards a `ccipSend()` request to the OnRamp, the contract perf
    - If the message involves token transfers, it retrieves the correct Token Pool from the Token Admin Registry.
    - Initiates calls to lock or burn the token, based on the token handling mechanism.
 3. **Nonce Management**
-   - Uses the Nonce Manager to ensure messages requiring in-order execution are processed in the correct order.
+   - Uses the Nonce Manager to ensure messages requiring in-order execution are processed in the correct order. Note: In-Order enforcement using Nonce Manager will be deprecated in early 2026.
 4. **Message ID Generation**
    - Returns a unique message ID to the Router.
 5. **Event Emission**
@@ -1166,17 +1166,6 @@ The FeeQuoter is an internal CCIP smart contract that calculates and returns CCI
 
 For additional details on how CCIP fees are calculated, refer to the [CCIP Billing page](/ccip/billing).
 
-## NonceManager
-
-The NonceManager helps order messages in CCIP by tracking outbound nonces on the source blockchain and inbound nonces on the destination blockchain. It ensures strict ordering when the message's extraArgs parameter requires ordering, thus providing a flexible design.
-
-1. **Ordered Messages**
-   - **Non-zero Nonces:** When an OnRamp identifies a message that must preserve ordering, it increments and assigns a non-zero outbound nonce.
-   - **Inbound Validation:** On the destination blockchain, the OffRamp checks that the incoming message's nonce matches the expected inbound nonce. If there is a mismatch, the message is skipped or deferred for later retry.
-2. **Out-of-Order Messages**
-   - **Zero Nonces:** For messages marked "out of order," the OnRamp sets the nonce to **0**.
-   - **No Sequence Checks:** Because `nonce == 0` indicates no ordering, the OffRamp does not validate or increment inbound nonces. These messages can execute immediately without waiting for earlier messages.
-
 ## Token Admin Registry
 
 The Token Admin Registry is a user-facing CCIP smart contract that maintains a one-to-one mapping between token addresses and their corresponding token pool addresses on a given chain. The OnRamp and OffRamp contracts use the Token Admin Registry to retrieve a token's configured token pool address to call the appropriate functions:
@@ -1838,18 +1827,9 @@ When the Router forwards a `ccip_send` request, the OnRamp performs the followin
   - If the message involves token transfers, it initiates a secure callback pattern by calling the `Token Admin Dispatcher`.
   - The dispatcher uses the `Token Admin Registry` to store the message context (sender, receiver, etc.) before invoking the correct `Token Pool` to `lock_or_burn` the assets.
 
-- **Nonce Management**
-  - For ordered messages, it calls the `Nonce Manager` to retrieve and increment the sender's nonce for that destination.
-
 - **Event Emission**
   - Generates a unique `messageId` and emits a `CCIPMessageSent` event containing the complete, sequenced message details.
 
-## Nonce Manager
-
-The `ccip::nonce_manager` module enables optional strict message ordering. It tracks outbound nonces on a per-sender and per-destination-chain basis.
-
-When out-of-order execution is disabled for a message, the `OnRamp` module uses the `Nonce Manager` to assign an incrementing nonce, which is then verified by the `OffRamp` on the destination chain.
-
 ## OffRamp
 
 The `ccip_offramp::offramp` module is an internal CCIP module that operates on the destination chain. It is the primary module that the offchain DONs interact with to deliver messages to Aptos.
@@ -4381,7 +4361,7 @@ The `allowOutOfOrderExecution` parameter enables you to control the execution or
 - **When `allowOutOfOrderExecution` is Optional:**
   - You can set `allowOutOfOrderExecution` to either `true` or `false`, depending on your application's requirements.
     - **`true`:** Messages can be executed in any order relative to other messages from the same sender. If a previous message has not yet been executed on the destination chain, it does not block the execution of subsequent messages.
-    - **`false`:** Messages are executed in order. CCIP ensures that preceding messages are processed before executing the current message.
+    - **`false`:** Messages are executed in order. CCIP ensures that preceding messages are processed before executing the current message. Note: Functionality for `allowOutofOrderExecution` = `false` (ie., enforcing In-Order cross-chain messages) is being deprecated in early 2026.
 
 - **When `allowOutOfOrderExecution` is Required:**
   - You **must** set `allowOutOfOrderExecution` to `true`. This setting acknowledges that messages may be executed out of order. If set to `false`, the message will revert and will not be processed.