diff --git a/public/changelog.json b/public/changelog.json
index cb73ffce227..ac221b76b22 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -402,6 +402,26 @@
     }
   },
   "data": [
+    {
+      "category": "integration",
+      "date": "2026-07-14",
+      "description": "- This release continues CCIP's expansion to non-EVMs by adding support for the Canton blockchain. \n - Canton is now interoperable with Ethereum using the latest [CCIP architecture](https://docs.chain.link/ccip/concepts/canton/overview). \n - More lanes to and from Canton will be added in the future. \n - No change to any existing EVM Router addresses. \n - Canton CCIP details can be seen on the [CCIP Directory](https://docs.chain.link/ccip/directory).",
+      "newNetworks": [
+        {
+          "displayName": "Canton Mainnet",
+          "network": "canton",
+          "url": "https://docs.chain.link/ccip/directory/mainnet/chain/canton-mainnet"
+        },
+        {
+          "displayName": "Canton Testnet",
+          "network": "canton",
+          "url": "https://docs.chain.link/ccip/directory/testnet/chain/canton-testnet"
+        }
+      ],
+      "relatedNetworks": ["canton"],
+      "title": "CCIP on Canton",
+      "topic": "CCIP"
+    },
     {
       "category": "integration",
       "date": "2026-07-13",
diff --git a/public/images/ccip/concepts/architecture/ccip-canton-destination-chain.png b/public/images/ccip/concepts/architecture/ccip-canton-destination-chain.png
new file mode 100644
index 00000000000..ec6e116a9a2
Binary files /dev/null and b/public/images/ccip/concepts/architecture/ccip-canton-destination-chain.png differ
diff --git a/public/images/ccip/concepts/architecture/ccip-canton-package-dependencies.svg b/public/images/ccip/concepts/architecture/ccip-canton-package-dependencies.svg
new file mode 100644
index 00000000000..73a6f07beb7
--- /dev/null
+++ b/public/images/ccip/concepts/architecture/ccip-canton-package-dependencies.svg
@@ -0,0 +1,160 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1120 720" role="img" aria-labelledby="title desc">
+  <title id="title">CCIP Canton package dependencies</title>
+  <desc id="desc">Layered dependency diagram for CCIP Canton Daml packages, showing un-upgradeable base packages, interface packages, core packages, and third-party owned packages.</desc>
+
+  <defs>
+    <style>
+      .label { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; fill: #1f2937; }
+      .section-title { font-size: 13px; font-weight: 700; letter-spacing: 0.02em; text-transform: uppercase; }
+      .pkg-name { font-size: 12px; font-weight: 600; }
+      .pkg-version { font-size: 10px; font-weight: 500; opacity: 0.85; }
+      .legend-text { font-size: 11px; font-weight: 500; }
+      .arrow { stroke: #4b5563; stroke-width: 1.5; fill: none; marker-end: url(#arrowhead); }
+    </style>
+    <marker id="arrowhead" markerWidth="8" markerHeight="8" refX="6" refY="3" orient="auto">
+      <path d="M0,0 L6,3 L0,6 Z" fill="#4b5563"/>
+    </marker>
+    <filter id="shadow" x="-4%" y="-4%" width="108%" height="108%">
+      <feDropShadow dx="0" dy="1" stdDeviation="1.5" flood-color="#000000" flood-opacity="0.08"/>
+    </filter>
+  </defs>
+
+  <!-- Background -->
+  <rect width="1120" height="720" fill="#ffffff"/>
+
+  <!-- Legend -->
+  <g transform="translate(760, 24)">
+    <rect x="0" y="0" width="340" height="118" rx="8" fill="#f3f4f6" stroke="#d1d5db" stroke-width="1.5"/>
+    <text x="16" y="24" class="label legend-text" font-weight="700">Legend</text>
+
+    <rect x="16" y="36" width="14" height="14" rx="3" fill="#fecaca" stroke="#dc2626" stroke-width="1.25"/>
+    <text x="38" y="47" class="label legend-text">Un-upgradeable</text>
+
+    <rect x="16" y="58" width="14" height="14" rx="3" fill="#bbf7d0" stroke="#16a34a" stroke-width="1.25"/>
+    <text x="38" y="69" class="label legend-text">Contains interfaces</text>
+
+    <rect x="16" y="80" width="14" height="14" rx="3" fill="#e5e7eb" stroke="#6b7280" stroke-width="1.25"/>
+    <text x="38" y="91" class="label legend-text">Core implementation</text>
+
+    <rect x="180" y="36" width="14" height="14" rx="3" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+    <text x="202" y="47" class="label legend-text">Third-party owned</text>
+
+    <text x="16" y="110" class="label legend-text" fill="#6b7280">Downstream packages import upstream packages.</text>
+  </g>
+
+  <!-- Layer 1: Un-upgradeable -->
+  <g transform="translate(40, 40)">
+    <rect x="0" y="0" width="680" height="92" rx="10" fill="#eceff1" stroke="#bdbdbd" stroke-width="1.5" filter="url(#shadow)"/>
+    <rect x="0" y="0" width="680" height="28" rx="10" fill="#dc2626"/>
+    <rect x="0" y="18" width="680" height="10" fill="#dc2626"/>
+    <text x="16" y="19" class="label section-title" fill="#ffffff">Un-upgradeable</text>
+
+    <g transform="translate(24, 42)">
+      <rect x="0" y="0" width="190" height="38" rx="6" fill="#fecaca" stroke="#dc2626" stroke-width="1.25"/>
+      <text x="12" y="18" class="label pkg-name">chainlink-api</text>
+      <text x="12" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="214" y="0" width="190" height="38" rx="6" fill="#fecaca" stroke="#dc2626" stroke-width="1.25"/>
+      <text x="226" y="18" class="label pkg-name">ccip-codec</text>
+      <text x="226" y="31" class="label pkg-version">1.0.0</text>
+    </g>
+  </g>
+
+  <!-- Arrow -->
+  <path class="arrow" d="M 380 132 L 380 158"/>
+
+  <!-- Layer 2: Interfaces -->
+  <g transform="translate(40, 158)">
+    <rect x="0" y="0" width="680" height="104" rx="10" fill="#eceff1" stroke="#bdbdbd" stroke-width="1.5" filter="url(#shadow)"/>
+    <rect x="0" y="0" width="680" height="28" rx="10" fill="#16a34a"/>
+    <rect x="0" y="18" width="680" height="10" fill="#16a34a"/>
+    <text x="16" y="19" class="label section-title" fill="#ffffff">Interface packages</text>
+
+    <g transform="translate(24, 42)">
+      <rect x="0" y="0" width="196" height="38" rx="6" fill="#bbf7d0" stroke="#16a34a" stroke-width="1.25"/>
+      <text x="12" y="18" class="label pkg-name">ccip-api</text>
+      <text x="12" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="212" y="0" width="210" height="38" rx="6" fill="#bbf7d0" stroke="#16a34a" stroke-width="1.25"/>
+      <text x="224" y="18" class="label pkg-name">ccip-extension-api</text>
+      <text x="224" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="438" y="0" width="210" height="38" rx="6" fill="#bbf7d0" stroke="#16a34a" stroke-width="1.25"/>
+      <text x="450" y="18" class="label pkg-name">ccip-client-api</text>
+      <text x="450" y="31" class="label pkg-version">1.0.0</text>
+    </g>
+  </g>
+
+  <path class="arrow" d="M 380 262 L 380 288"/>
+
+  <!-- Layer 3: Core -->
+  <g transform="translate(40, 288)">
+    <rect x="0" y="0" width="680" height="104" rx="10" fill="#eceff1" stroke="#bdbdbd" stroke-width="1.5" filter="url(#shadow)"/>
+    <rect x="0" y="0" width="680" height="28" rx="10" fill="#546e7a"/>
+    <rect x="0" y="18" width="680" height="10" fill="#546e7a"/>
+    <text x="16" y="19" class="label section-title" fill="#ffffff">Core packages</text>
+
+    <g transform="translate(24, 42)">
+      <rect x="0" y="0" width="118" height="38" rx="6" fill="#e5e7eb" stroke="#6b7280" stroke-width="1.25"/>
+      <text x="10" y="18" class="label pkg-name">ccip-events</text>
+      <text x="10" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="130" y="0" width="118" height="38" rx="6" fill="#e5e7eb" stroke="#6b7280" stroke-width="1.25"/>
+      <text x="140" y="18" class="label pkg-name">ccip-tickets</text>
+      <text x="140" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="260" y="0" width="104" height="38" rx="6" fill="#e5e7eb" stroke="#6b7280" stroke-width="1.25"/>
+      <text x="270" y="18" class="label pkg-name">ccip-core</text>
+      <text x="270" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="376" y="0" width="104" height="38" rx="6" fill="#e5e7eb" stroke="#6b7280" stroke-width="1.25"/>
+      <text x="386" y="18" class="label pkg-name">ccip-utils</text>
+      <text x="386" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="492" y="0" width="118" height="38" rx="6" fill="#e5e7eb" stroke="#6b7280" stroke-width="1.25"/>
+      <text x="502" y="18" class="label pkg-name">ccip-runtime</text>
+      <text x="502" y="31" class="label pkg-version">1.0.0</text>
+    </g>
+  </g>
+
+  <path class="arrow" d="M 380 392 L 380 418"/>
+
+  <!-- Layer 4: Third-party -->
+  <g transform="translate(40, 418)">
+    <rect x="0" y="0" width="1040" height="262" rx="10" fill="#eceff1" stroke="#bdbdbd" stroke-width="1.5" filter="url(#shadow)"/>
+    <rect x="0" y="0" width="1040" height="28" rx="10" fill="#1565c0"/>
+    <rect x="0" y="18" width="1040" height="10" fill="#1565c0"/>
+    <text x="16" y="19" class="label section-title" fill="#ffffff">Third-party owned</text>
+
+    <g transform="translate(24, 42)">
+      <rect x="0" y="0" width="170" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="12" y="18" class="label pkg-name">ccip-executor</text>
+      <text x="12" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="186" y="0" width="220" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="198" y="18" class="label pkg-name">ccip-committee-verifier</text>
+      <text x="198" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="422" y="0" width="180" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="434" y="18" class="label pkg-name">ccip-rate-limiter</text>
+      <text x="434" y="31" class="label pkg-version">1.0.0</text>
+
+      <rect x="0" y="54" width="250" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="12" y="72" class="label pkg-name">ccip-lock-release-token-pool</text>
+      <text x="12" y="85" class="label pkg-version">1.0.0</text>
+
+      <rect x="266" y="54" width="230" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="278" y="72" class="label pkg-name">ccip-burn-mint-token-pool</text>
+      <text x="278" y="85" class="label pkg-version">1.0.0</text>
+
+      <rect x="0" y="118" width="160" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="12" y="136" class="label pkg-name">CCIPReceiver</text>
+
+      <rect x="176" y="118" width="150" height="38" rx="6" fill="#c5d9e8" stroke="#1565c0" stroke-width="1.25"/>
+      <text x="188" y="136" class="label pkg-name">CCIPSender</text>
+
+      <text x="0" y="182" class="label legend-text" fill="#4b5563">Operators deploy and upgrade these packages on their own participants.</text>
+      <text x="0" y="202" class="label legend-text" fill="#6b7280">CCIPSender and CCIPReceiver import through ccip-utils; other third-party packages import through ccip-runtime.</text>
+    </g>
+  </g>
+</svg>
diff --git a/public/images/ccip/concepts/architecture/ccip-canton-source-chain.png b/public/images/ccip/concepts/architecture/ccip-canton-source-chain.png
new file mode 100644
index 00000000000..7d2f4ba9774
Binary files /dev/null and b/public/images/ccip/concepts/architecture/ccip-canton-source-chain.png differ
diff --git a/src/components/AddressReact.tsx b/src/components/AddressReact.tsx
index 43fe2c11437..d55a129a843 100644
--- a/src/components/AddressReact.tsx
+++ b/src/components/AddressReact.tsx
@@ -42,6 +42,20 @@ const AddressComponent = ({ contractUrl, address, endLength, urlClass, urlId }:
       </button>
 
       <style>{`
+        a.addressLink {
+          color: var(--color-text-link);
+          text-decoration: none;
+        }
+
+        a.addressLink:hover {
+          color: var(--color-text-link-hover);
+          text-decoration: underline;
+        }
+
+        a.addressLink:visited {
+          color: var(--color-text-link);
+        }
+
         .addressLink {
           padding: 1px 0px;
           border-radius: var(--border-radius-10);
diff --git a/src/components/CCIP/Chain/Chain.astro b/src/components/CCIP/Chain/Chain.astro
index 470231de727..5d1b76dec5c 100644
--- a/src/components/CCIP/Chain/Chain.astro
+++ b/src/components/CCIP/Chain/Chain.astro
@@ -17,7 +17,6 @@ import ChainTokenGrid from "./ChainTokenGrid"
 import { generateChainStructuredData } from "~/utils/ccipStructuredData"
 import StructuredData from "~/components/StructuredData.astro"
 import { DOCS_BASE_URL } from "~/utils/structuredData"
-
 interface Props {
   environment: Environment
   network: Network
@@ -127,16 +126,19 @@ const chainStructuredData = generateChainStructuredData(
       <div class="ccip-heading">
         <h2>Tokens <span>({allTokens.length})</span></h2>
         {
-          network.chainType !== "solana" && network.chainType !== "aptos" && network.chainType !== "ton" && (
-            <a class="button secondary" href="/ccip/tutorials/evm/token-manager#verifying-your-token">
-              <img
-                src="/assets/icons/plus.svg"
-                alt="Add"
-                style={{ width: "1em", height: "1em", marginRight: "0.5em", verticalAlign: "middle" }}
-              />
-              Add my token
-            </a>
-          )
+          network.chainType !== "solana" &&
+            network.chainType !== "aptos" &&
+            network.chainType !== "ton" &&
+            network.chainType !== "canton" && (
+              <a class="button secondary" href="/ccip/tutorials/evm/token-manager#verifying-your-token">
+                <img
+                  src="/assets/icons/plus.svg"
+                  alt="Add"
+                  style={{ width: "1em", height: "1em", marginRight: "0.5em", verticalAlign: "middle" }}
+                />
+                Add my token
+              </a>
+            )
         }
       </div>
       <ChainTokenGrid tokens={allTokens} network={network} client:only="react" environment={environment} />
diff --git a/src/components/CCIP/Chain/DecommissionedChain.astro b/src/components/CCIP/Chain/DecommissionedChain.astro
index c049fb327fc..e0e20a0bc34 100644
--- a/src/components/CCIP/Chain/DecommissionedChain.astro
+++ b/src/components/CCIP/Chain/DecommissionedChain.astro
@@ -38,7 +38,6 @@ const heroNetwork: Network = networkDetails ?? {
   key: network.chain,
   totalLanes: 0,
   totalTokens: 0,
-  routerExplorerUrl: "",
   armProxy: {
     address: "",
     version: "",
diff --git a/src/components/CCIP/ChainHero/ChainHero.css b/src/components/CCIP/ChainHero/ChainHero.css
index e7ffccfa26f..c085332c5dc 100644
--- a/src/components/CCIP/ChainHero/ChainHero.css
+++ b/src/components/CCIP/ChainHero/ChainHero.css
@@ -158,6 +158,25 @@
     row-gap: var(--space-12x);
   }
 
+  .ccip-chain-hero__details--canton {
+    grid-template-columns: repeat(3, 1fr);
+    column-gap: var(--space-8x);
+    row-gap: var(--space-8x);
+  }
+
+  .ccip-chain-hero__details--canton .ccip-chain-hero__details__item {
+    min-width: 0;
+  }
+
+  .ccip-chain-hero__details--canton .ccip-chain-hero__details__value {
+    font-size: 14px;
+    line-height: 22px;
+  }
+
+  .ccip-chain-hero__details__item--wide {
+    grid-column: 1 / -1;
+  }
+
   .ccip-chain-hero__content {
     --gutter: var(--space-10x);
     grid-template-columns: 1fr 1fr;
@@ -170,6 +189,12 @@
 }
 
 /* Pool Programs Styles */
+.ccip-chain-hero__indexer-list {
+  display: flex;
+  flex-direction: column;
+  gap: var(--space-3x);
+}
+
 .ccip-chain-hero__pool-programs-container {
   display: grid;
   grid-template-columns: repeat(auto-fit, minmax(250px, 1fr));
diff --git a/src/components/CCIP/ChainHero/ChainHero.tsx b/src/components/CCIP/ChainHero/ChainHero.tsx
index 9570c1a6512..3daf21bb294 100644
--- a/src/components/CCIP/ChainHero/ChainHero.tsx
+++ b/src/components/CCIP/ChainHero/ChainHero.tsx
@@ -6,11 +6,12 @@ import Search from "../Search/Search.tsx"
 import "./ChainHero.css"
 import CopyValue from "../CopyValue/CopyValue.tsx"
 import {
-  getExplorerAddressUrl,
   getTokenIconUrl,
   getNativeCurrency,
   directoryToSupportedChain,
   fallbackTokenIconUrl,
+  getContractExplorerUrl,
+  isCantonNativeFeeToken,
 } from "~/features/utils/index.ts"
 import { Tooltip } from "~/features/common/Tooltip/Tooltip.tsx"
 import { getChainTooltip } from "../Tooltip/index.ts"
@@ -64,6 +65,10 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
   const chainTooltipConfig = network?.chain && !isDecommissioned ? getChainTooltip(network.chain) : null
   const hasFullNetworkDetails = Boolean(network?.router?.address)
   const showNetworkConfiguration = !isDecommissioned || hasFullNetworkDetails
+  const isCanton = network?.chainType === "canton"
+  const addressEndLength = isCanton ? 10 : 4
+  const cantonWideAddressEndLength = 14
+  const networkContractUrl = network ? getContractExplorerUrl(network.explorer, network.chainType) : undefined
 
   const feeTokensWithAddress =
     network?.feeTokens?.map((feeToken) => {
@@ -73,9 +78,11 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
         version: Version.V1_2_0,
         tokenId: feeToken.name,
       })
-      const explorer = network.explorer || {}
       const address = token[network.chain]?.tokenAddress
-      const contractUrl = address ? getExplorerAddressUrl(explorer, network.chainType)(address) : ""
+      const contractUrl =
+        address && !(isCanton && isCantonNativeFeeToken(network.chain, feeToken.name))
+          ? networkContractUrl?.(address)
+          : undefined
 
       return {
         logo,
@@ -173,20 +180,38 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
             {isDecommissioned && network && <span className="ccip-chain-hero__decom-subtitle">Inactive</span>}
           </div>
         </div>
+
+        {isCanton && (
+          <aside className="ccip-chain-hero__decom-banner" aria-label="Canton address caution">
+            <div className="ccip-chain-hero__decom-banner__icon" aria-hidden="true">
+              !
+            </div>
+            <div className="ccip-chain-hero__decom-banner__content">
+              <p className="ccip-chain-hero__decom-banner__title">Caution</p>
+              <p>
+                Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and
+                contract addresses with{" "}
+                <a href="https://chain.link/ccip-contact" target="_blank" rel="noopener noreferrer">
+                  Chainlink CCIP
+                </a>
+                .
+              </p>
+            </div>
+          </aside>
+        )}
+
         {network && (
-          <div className="ccip-chain-hero__details">
+          <div className={`ccip-chain-hero__details${isCanton ? " ccip-chain-hero__details--canton" : ""}`}>
             {showNetworkConfiguration && (
               <>
                 <div className="ccip-chain-hero__details__item">
-                  <div className="ccip-chain-hero__details__label">Router</div>
+                  <div className="ccip-chain-hero__details__label">
+                    {isCanton ? "Per party factory router" : "Router"}
+                  </div>
                   <div className="ccip-chain-hero__details__value" data-clipboard-type="router">
                     <Address
-                      endLength={4}
-                      contractUrl={
-                        network.router?.address
-                          ? getExplorerAddressUrl(network.explorer, network.chainType)(network.router.address)
-                          : ""
-                      }
+                      endLength={addressEndLength}
+                      contractUrl={networkContractUrl?.(network.router?.address)}
                       address={network.router?.address}
                     />
                   </div>
@@ -230,11 +255,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                   <div className="ccip-chain-hero__details__value" data-clipboard-type="rmn">
                     {network.armProxy ? (
                       <Address
-                        endLength={4}
-                        contractUrl={getExplorerAddressUrl(
-                          network.explorer,
-                          network.chainType
-                        )(network.armProxy.address)}
+                        endLength={addressEndLength}
+                        contractUrl={networkContractUrl?.(network.armProxy.address)}
                         address={network.armProxy.address}
                       />
                     ) : (
@@ -265,11 +287,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                       <div className="ccip-chain-hero__details__value" data-clipboard-type="token-registry">
                         {network.tokenAdminRegistry ? (
                           <Address
-                            endLength={4}
-                            contractUrl={getExplorerAddressUrl(
-                              network.explorer,
-                              network.chainType
-                            )(network.tokenAdminRegistry)}
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.tokenAdminRegistry)}
                             address={network.tokenAdminRegistry}
                           />
                         ) : (
@@ -296,11 +315,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                       <div className="ccip-chain-hero__details__value" data-clipboard-type="registry">
                         {network.registryModule ? (
                           <Address
-                            endLength={4}
-                            contractUrl={getExplorerAddressUrl(
-                              network.explorer,
-                              network.chainType
-                            )(network.registryModule)}
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.registryModule)}
                             address={network.registryModule}
                           />
                         ) : (
@@ -332,11 +348,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                       <div className="ccip-chain-hero__details__value" data-clipboard-type="token-registry">
                         {network.tokenAdminRegistry ? (
                           <Address
-                            endLength={4}
-                            contractUrl={getExplorerAddressUrl(
-                              network.explorer,
-                              network.chainType
-                            )(network.tokenAdminRegistry)}
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.tokenAdminRegistry)}
                             address={network.tokenAdminRegistry}
                           />
                         ) : (
@@ -364,8 +377,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                         </div>
                         <div className="ccip-chain-hero__details__value" data-clipboard-type="mcms">
                           <Address
-                            endLength={4}
-                            contractUrl={getExplorerAddressUrl(network.explorer, network.chainType)(network.mcms)}
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.mcms)}
                             address={network.mcms}
                           />
                         </div>
@@ -374,6 +387,177 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                   </>
                 )}
 
+                {network.chainType === "canton" && (
+                  <>
+                    {network.ccipOwnerParty && (
+                      <div className="ccip-chain-hero__details__item ccip-chain-hero__details__item--wide">
+                        <div className="ccip-chain-hero__details__label">
+                          CCIP owner party
+                          <Tooltip
+                            label=""
+                            tip="The CCIP owner party is the signatory and owner of core CCIP contracts on Canton."
+                            labelStyle={{
+                              marginRight: "8px",
+                            }}
+                            style={{
+                              display: "inline-block",
+                              verticalAlign: "middle",
+                              marginBottom: "2px",
+                            }}
+                          />
+                        </div>
+                        <div className="ccip-chain-hero__details__value" data-clipboard-type="ccip-owner-party">
+                          <Address
+                            endLength={cantonWideAddressEndLength}
+                            contractUrl={networkContractUrl?.(network.ccipOwnerParty)}
+                            address={network.ccipOwnerParty}
+                          />
+                        </div>
+                      </div>
+                    )}
+
+                    {network.committeeVerifier && (
+                      <div className="ccip-chain-hero__details__item">
+                        <div className="ccip-chain-hero__details__label">
+                          Committee verifier
+                          <Tooltip
+                            label=""
+                            tip="The Committee Verifier contract (CCVS) validates cross-chain message proofs on Canton."
+                            labelStyle={{
+                              marginRight: "8px",
+                            }}
+                            style={{
+                              display: "inline-block",
+                              verticalAlign: "middle",
+                              marginBottom: "2px",
+                            }}
+                          />
+                        </div>
+                        <div className="ccip-chain-hero__details__value" data-clipboard-type="committee-verifier">
+                          <Address
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.committeeVerifier.address)}
+                            address={network.committeeVerifier.address}
+                          />
+                        </div>
+                      </div>
+                    )}
+
+                    {network.feeQuoterModule && (
+                      <div className="ccip-chain-hero__details__item">
+                        <div className="ccip-chain-hero__details__label">
+                          Fee quoter module
+                          <Tooltip
+                            label=""
+                            tip="The Fee Quoter module calculates CCIP fees for cross-chain messages on Canton."
+                            labelStyle={{
+                              marginRight: "8px",
+                            }}
+                            style={{
+                              display: "inline-block",
+                              verticalAlign: "middle",
+                              marginBottom: "2px",
+                            }}
+                          />
+                        </div>
+                        <div className="ccip-chain-hero__details__value" data-clipboard-type="fee-quoter-module">
+                          <Address
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.feeQuoterModule.address)}
+                            address={network.feeQuoterModule.address}
+                          />
+                        </div>
+                      </div>
+                    )}
+
+                    {network.chain === "canton-testnet" && network.tokenAdminRegistry && (
+                      <div className="ccip-chain-hero__details__item">
+                        <div className="ccip-chain-hero__details__label">
+                          Token admin registry
+                          <Tooltip
+                            label=""
+                            tip="The Token Admin Registry manages token pool configuration for cross-chain tokens on Canton."
+                            labelStyle={{
+                              marginRight: "8px",
+                            }}
+                            style={{
+                              display: "inline-block",
+                              verticalAlign: "middle",
+                              marginBottom: "2px",
+                            }}
+                          />
+                        </div>
+                        <div className="ccip-chain-hero__details__value" data-clipboard-type="token-registry">
+                          <Address
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.tokenAdminRegistry)}
+                            address={network.tokenAdminRegistry}
+                          />
+                        </div>
+                      </div>
+                    )}
+
+                    {network.ccipExplicitDisclosureServer && (
+                      <div className="ccip-chain-hero__details__item ccip-chain-hero__details__item--wide">
+                        <div className="ccip-chain-hero__details__label">
+                          Explicit disclosure server
+                          <Tooltip
+                            label=""
+                            tip="The Explicit Disclosure Server (EDS) endpoint for Canton CCIP disclosures."
+                            labelStyle={{
+                              marginRight: "8px",
+                            }}
+                            style={{
+                              display: "inline-block",
+                              verticalAlign: "middle",
+                              marginBottom: "2px",
+                            }}
+                          />
+                        </div>
+                        <div className="ccip-chain-hero__details__value" data-clipboard-type="eds-server">
+                          <CopyValue value={network.ccipExplicitDisclosureServer} />
+                        </div>
+                      </div>
+                    )}
+
+                    {network.indexer?.primary && (
+                      <div className="ccip-chain-hero__details__item ccip-chain-hero__details__item--wide">
+                        <div className="ccip-chain-hero__details__label">
+                          Indexer
+                          <Tooltip
+                            label=""
+                            tip="The CCIP indexer endpoint used to retrieve Merkle proofs for manual execution on Canton."
+                            labelStyle={{
+                              marginRight: "8px",
+                            }}
+                            style={{
+                              display: "inline-block",
+                              verticalAlign: "middle",
+                              marginBottom: "2px",
+                            }}
+                          />
+                        </div>
+                        <div className="ccip-chain-hero__details__value" data-clipboard-type="indexer">
+                          {network.indexer.backup ? (
+                            <div className="ccip-chain-hero__indexer-list">
+                              <div className="ccip-chain-hero__pool-program-entry">
+                                <span className="ccip-chain-hero__pool-program-type">Primary:</span>
+                                <CopyValue value={network.indexer.primary} />
+                              </div>
+                              <div className="ccip-chain-hero__pool-program-entry">
+                                <span className="ccip-chain-hero__pool-program-type">Backup:</span>
+                                <CopyValue value={network.indexer.backup} />
+                              </div>
+                            </div>
+                          ) : (
+                            <CopyValue value={network.indexer.primary} />
+                          )}
+                        </div>
+                      </div>
+                    )}
+                  </>
+                )}
+
                 {network.chainType === "solana" && (
                   <div className="ccip-chain-hero__details__item">
                     <div className="ccip-chain-hero__details__label">
@@ -394,8 +578,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                     <div className="ccip-chain-hero__details__value" data-clipboard-type="fee-quoter">
                       {network.feeQuoter ? (
                         <Address
-                          endLength={4}
-                          contractUrl={getExplorerAddressUrl(network.explorer, network.chainType)(network.feeQuoter)}
+                          endLength={addressEndLength}
+                          contractUrl={networkContractUrl?.(network.feeQuoter)}
                           address={network.feeQuoter}
                         />
                       ) : (
@@ -416,10 +600,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                         <div className="ccip-chain-hero__pool-program-entry">
                           <span className="ccip-chain-hero__pool-program-type">BurnMint:</span>
                           <Address
-                            endLength={4}
-                            contractUrl={getExplorerAddressUrl(network.explorer)(
-                              network.poolPrograms.BurnMintTokenPool
-                            )}
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.poolPrograms.BurnMintTokenPool)}
                             address={network.poolPrograms.BurnMintTokenPool}
                           />
                         </div>
@@ -428,10 +610,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                         <div className="ccip-chain-hero__pool-program-entry">
                           <span className="ccip-chain-hero__pool-program-type">LockRelease:</span>
                           <Address
-                            endLength={4}
-                            contractUrl={getExplorerAddressUrl(network.explorer)(
-                              network.poolPrograms.LockReleaseTokenPool
-                            )}
+                            endLength={addressEndLength}
+                            contractUrl={networkContractUrl?.(network.poolPrograms.LockReleaseTokenPool)}
                             address={network.poolPrograms.LockReleaseTokenPool}
                           />
                         </div>
@@ -459,8 +639,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                     </div>
                     <div className="ccip-chain-hero__details__value" data-clipboard-type="ccip-home">
                       <Address
-                        endLength={4}
-                        contractUrl={getExplorerAddressUrl(network.explorer, network.chainType)(network.ccipHome)}
+                        endLength={addressEndLength}
+                        contractUrl={networkContractUrl?.(network.ccipHome)}
                         address={network.ccipHome}
                       />
                     </div>
@@ -486,11 +666,8 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                     </div>
                     <div className="ccip-chain-hero__details__value" data-clipboard-type="token-pool-factory">
                       <Address
-                        endLength={4}
-                        contractUrl={getExplorerAddressUrl(
-                          network.explorer,
-                          network.chainType
-                        )(network.tokenPoolFactory)}
+                        endLength={addressEndLength}
+                        contractUrl={networkContractUrl?.(network.tokenPoolFactory)}
                         address={network.tokenPoolFactory}
                       />
                     </div>
@@ -526,7 +703,7 @@ function ChainHero({ chains, tokens, network, token, environment, lanes, isDecom
                                 </object>
                                 <div>{token.name}</div>
                                 <Address
-                                  endLength={4}
+                                  endLength={token.name === "TON" ? undefined : addressEndLength}
                                   contractUrl={token.name === "TON" ? undefined : contractUrl}
                                   address={address}
                                 />
diff --git a/src/components/CCIP/ChainHero/LaneDetailsHero.tsx b/src/components/CCIP/ChainHero/LaneDetailsHero.tsx
index 1239dcc3dd1..d4464e06d17 100644
--- a/src/components/CCIP/ChainHero/LaneDetailsHero.tsx
+++ b/src/components/CCIP/ChainHero/LaneDetailsHero.tsx
@@ -1,7 +1,7 @@
 import { Tooltip } from "~/features/common/Tooltip/Tooltip.tsx"
 import AddressComponent from "~/components/AddressReact.tsx"
 import "./LaneDetailsHero.css"
-import { getExplorerAddressUrl } from "~/features/utils/index.ts"
+import { getContractExplorerUrl } from "~/features/utils/index.ts"
 import CopyValue from "../CopyValue/CopyValue.tsx"
 import { LaneFilter } from "~/config/data/ccip/types.ts"
 import { ChainType, ExplorerInfo } from "@config/types.ts"
@@ -121,7 +121,7 @@ function LaneDetailsHero({
             <AddressComponent
               address={offRamp}
               endLength={6}
-              contractUrl={getExplorerAddressUrl(explorer, destinationNetwork.chainType)(offRamp)}
+              contractUrl={getContractExplorerUrl(explorer, destinationNetwork.chainType)(offRamp)}
             />
           </DetailItem>
         ) : (
@@ -133,7 +133,7 @@ function LaneDetailsHero({
             <AddressComponent
               address={onRamp}
               endLength={6}
-              contractUrl={getExplorerAddressUrl(explorer, sourceNetwork.chainType)(onRamp)}
+              contractUrl={getContractExplorerUrl(explorer, sourceNetwork.chainType)(onRamp)}
             />
           </DetailItem>
         )}
diff --git a/src/components/CCIP/ChainHero/TokenDetailsHero.tsx b/src/components/CCIP/ChainHero/TokenDetailsHero.tsx
index 94ce250d01f..7ee8016c4f2 100644
--- a/src/components/CCIP/ChainHero/TokenDetailsHero.tsx
+++ b/src/components/CCIP/ChainHero/TokenDetailsHero.tsx
@@ -1,5 +1,5 @@
 import Address from "~/components/AddressReact.tsx"
-import { getExplorerAddressUrl, fallbackTokenIconUrl } from "~/features/utils/index.ts"
+import { getContractExplorerUrl, fallbackTokenIconUrl, isCantonNativeFeeToken } from "~/features/utils/index.ts"
 import { PoolType } from "~/config/data/ccip/types.ts"
 import { tokenPoolDisplay } from "~/config/data/ccip/utils.ts"
 import "./ChainHero.css"
@@ -11,6 +11,7 @@ interface TokenDetailsHeroProps {
     logo: string
     explorer: ExplorerInfo
     chainType?: ChainType
+    chain?: string
   }
   token: {
     id: string
@@ -25,6 +26,13 @@ interface TokenDetailsHeroProps {
 }
 
 function TokenDetailsHero({ network, token }: TokenDetailsHeroProps) {
+  const chainType = network?.chainType
+  const tokenContractUrl =
+    network?.chain && chainType === "canton" && isCantonNativeFeeToken(network.chain, token.id)
+      ? undefined
+      : getContractExplorerUrl(network?.explorer, chainType)(token.address)
+  const poolContractUrl = getContractExplorerUrl(network?.explorer, chainType)(token.poolAddress)
+
   return (
     <section className="ccip-chain-hero">
       <div className="ccip-chain-hero__content">
@@ -58,11 +66,7 @@ function TokenDetailsHero({ network, token }: TokenDetailsHeroProps) {
           <div className="ccip-chain-hero__details__item">
             <div className="ccip-chain-hero__details__label">Token address</div>
             <div className="ccip-chain-hero__details__value" data-clipboard-type="token">
-              <Address
-                endLength={4}
-                contractUrl={getExplorerAddressUrl(network?.explorer, network?.chainType)(token.address)}
-                address={token.address}
-              />
+              <Address endLength={4} contractUrl={tokenContractUrl} address={token.address} />
             </div>
           </div>
           <div className="ccip-chain-hero__details__item">
@@ -72,11 +76,7 @@ function TokenDetailsHero({ network, token }: TokenDetailsHeroProps) {
           <div className="ccip-chain-hero__details__item">
             <div className="ccip-chain-hero__details__label">Token pool address</div>
             <div className="ccip-chain-hero__details__value" data-clipboard-type="token-pool">
-              <Address
-                endLength={4}
-                contractUrl={getExplorerAddressUrl(network?.explorer, network?.chainType)(token.poolAddress)}
-                address={token.poolAddress}
-              />
+              <Address endLength={4} contractUrl={poolContractUrl} address={token.poolAddress} />
             </div>
           </div>
         </div>
diff --git a/src/components/CCIP/CopyValue/CopyValue.tsx b/src/components/CCIP/CopyValue/CopyValue.tsx
index 2f78f81ace8..d064bdbeca5 100644
--- a/src/components/CCIP/CopyValue/CopyValue.tsx
+++ b/src/components/CCIP/CopyValue/CopyValue.tsx
@@ -4,9 +4,10 @@ export type Props = {
   value?: string
   valueClass?: string
   valueId?: string
+  href?: string
 }
 
-const CopyValue = ({ value, valueClass, valueId }: Props) => {
+const CopyValue = ({ value, valueClass, valueId, href }: Props) => {
   if (!value) return null
 
   const handleClick = (e) => {
@@ -16,7 +17,13 @@ const CopyValue = ({ value, valueClass, valueId }: Props) => {
 
   return (
     <span className={`addressContainer ${valueClass || ""}`} id={valueId}>
-      <span className="valueCopy">{value}</span>
+      {href ? (
+        <a className="valueCopy valueCopy--link" href={href} target="_blank" rel="noopener noreferrer">
+          {value}
+        </a>
+      ) : (
+        <span className="valueCopy">{value}</span>
+      )}
       <button
         className={clsx("copyBtn", "copy-iconbutton")}
         style={{ height: "16px", width: "16px", minWidth: "12px" }}
@@ -32,6 +39,15 @@ const CopyValue = ({ value, valueClass, valueId }: Props) => {
           word-break: break-word;
         }
 
+        .valueCopy--link {
+          color: var(--color-text-link);
+          text-decoration: none;
+        }
+
+        .valueCopy--link:hover {
+          text-decoration: underline;
+        }
+
         .addressContainer {
           display: inline-flex;
           align-items: center;
diff --git a/src/components/CCIP/Drawer/LaneDrawer.tsx b/src/components/CCIP/Drawer/LaneDrawer.tsx
index e906a337816..894263befc3 100644
--- a/src/components/CCIP/Drawer/LaneDrawer.tsx
+++ b/src/components/CCIP/Drawer/LaneDrawer.tsx
@@ -5,7 +5,7 @@ import { getNetwork, getTokenData } from "~/config/data/ccip/data.ts"
 import { displayCapacity, determineTokenMechanism, isTokenPaused } from "~/config/data/ccip/utils.ts"
 import { useState } from "react"
 import LaneDetailsHero from "../ChainHero/LaneDetailsHero.tsx"
-import { getExplorerAddressUrl, getTokenIconUrl, fallbackTokenIconUrl } from "~/features/utils/index.ts"
+import { getContractExplorerUrl, getTokenIconUrl, fallbackTokenIconUrl } from "~/features/utils/index.ts"
 import TableSearchInput from "../Tables/TableSearchInput.tsx"
 import RateTooltip from "../Tooltip/RateTooltip.tsx"
 import { Tooltip } from "~/features/common/Tooltip/Tooltip.tsx"
@@ -166,7 +166,10 @@ function LaneDrawer({
                           <Address
                             address={data[sourceNetwork.key].tokenAddress}
                             endLength={6}
-                            contractUrl={getExplorerAddressUrl(explorer)(data[sourceNetwork.key].tokenAddress)}
+                            contractUrl={getContractExplorerUrl(
+                              explorer,
+                              sourceNetwork.chainType
+                            )(data[sourceNetwork.key].tokenAddress)}
                           />
                         </td>
                         <td>{data[sourceNetwork.key].decimals}</td>
diff --git a/src/components/CCIP/Drawer/TokenDrawer.tsx b/src/components/CCIP/Drawer/TokenDrawer.tsx
index 46c0d283d71..5dd08dcf3ab 100644
--- a/src/components/CCIP/Drawer/TokenDrawer.tsx
+++ b/src/components/CCIP/Drawer/TokenDrawer.tsx
@@ -198,6 +198,7 @@ function TokenDrawer({
           logo: network.logo,
           explorer: network.explorer,
           chainType: network.chainType,
+          chain: network.key,
         }}
       />
       <div className="ccip-table__drawer-container">
diff --git a/src/components/CCIP/Tables/ChainTable.tsx b/src/components/CCIP/Tables/ChainTable.tsx
index d487faf20ee..9aac17431db 100644
--- a/src/components/CCIP/Tables/ChainTable.tsx
+++ b/src/components/CCIP/Tables/ChainTable.tsx
@@ -3,7 +3,7 @@ import "./Table.css"
 import Tabs from "./Tabs.tsx"
 import TableSearchInput from "./TableSearchInput.tsx"
 import { useEffect, useState } from "react"
-import { getExplorerAddressUrl } from "~/features/utils/index.ts"
+import { getContractExplorerUrl, getChainTypeAndFamily, fallbackTokenIconUrl } from "~/features/utils/index.ts"
 import { drawerContentStore } from "../Drawer/drawerStore.ts"
 import LaneDrawer from "../Drawer/LaneDrawer.tsx"
 import { Environment, Version, LaneFilter } from "~/config/data/ccip/types.ts"
@@ -116,59 +116,61 @@ function ChainTable({ lanes, explorer, sourceNetwork, environment }: TableProps)
             {lanes
               ?.filter((network) => network.name.toLowerCase().includes(search.toLowerCase()))
               .slice(0, seeMore ? lanes.length : BEFORE_SEE_MORE)
-              .map((network, index) => (
-                <tr key={index}>
-                  <td>
-                    <button
-                      type="button"
-                      className="ccip-table__network-name"
-                      onClick={() => {
-                        const laneData = getLane({
-                          sourceChain: sourceNetwork.key as SupportedChain,
-                          destinationChain: network.key as SupportedChain,
-                          environment,
-                          version: Version.V1_2_0,
-                        })
+              .map((network, index) => {
+                const remoteChainType = network.chainType ?? getChainTypeAndFamily(network.directory).chainType
+                const addressChainType = inOutbound === LaneFilter.Outbound ? sourceNetwork.chainType : remoteChainType
+                const laneAddress =
+                  inOutbound === LaneFilter.Outbound ? network.onRamp?.address : network.offRamp?.address
 
-                        drawerContentStore.set(() => (
-                          <LaneDrawer
-                            environment={environment}
-                            lane={laneData}
-                            sourceNetwork={sourceNetwork}
-                            destinationNetwork={{
-                              name: network?.name || "",
-                              logo: network?.logo || "",
-                              key: network.key,
-                            }}
-                            inOutbound={inOutbound}
-                            explorer={explorer}
-                          />
-                        ))
-                      }}
-                      aria-label={`View lane details for ${network.name}`}
+                return (
+                  <tr key={index}>
+                    <td>
+                      <button
+                        type="button"
+                        className="ccip-table__network-name"
+                        onClick={() => {
+                          const laneData = getLane({
+                            sourceChain: sourceNetwork.key as SupportedChain,
+                            destinationChain: network.key as SupportedChain,
+                            environment,
+                            version: Version.V1_2_0,
+                          })
+
+                          drawerContentStore.set(() => (
+                            <LaneDrawer
+                              environment={environment}
+                              lane={laneData}
+                              sourceNetwork={sourceNetwork}
+                              destinationNetwork={{
+                                name: network?.name || "",
+                                logo: network?.logo || "",
+                                key: network.key,
+                              }}
+                              inOutbound={inOutbound}
+                              explorer={explorer}
+                            />
+                          ))
+                        }}
+                        aria-label={`View lane details for ${network.name}`}
+                      >
+                        <img src={network.logo} alt={`${network.name} blockchain logo`} className="ccip-table__logo" />
+                        {network.name}
+                      </button>
+                    </td>
+                    <td
+                      style={{ textAlign: "right" }}
+                      data-clipboard-type={inOutbound === LaneFilter.Outbound ? "onramp" : "offramp"}
                     >
-                      <img src={network.logo} alt={`${network.name} blockchain logo`} className="ccip-table__logo" />
-                      {network.name}
-                    </button>
-                  </td>
-                  <td
-                    style={{ textAlign: "right" }}
-                    data-clipboard-type={inOutbound === LaneFilter.Outbound ? "onramp" : "offramp"}
-                  >
-                    <Address
-                      address={inOutbound === LaneFilter.Outbound ? network.onRamp?.address : network.offRamp?.address}
-                      endLength={4}
-                      contractUrl={getExplorerAddressUrl(
-                        explorer,
-                        inOutbound === LaneFilter.Outbound ? sourceNetwork.chainType : network.chainType
-                      )(
-                        (inOutbound === LaneFilter.Outbound ? network.onRamp?.address : network.offRamp?.address) || ""
-                      )}
-                    />
-                  </td>
-                  <td>{inOutbound === LaneFilter.Outbound ? network.onRamp?.version : network.offRamp?.version}</td>
-                </tr>
-              ))}
+                      <Address
+                        address={laneAddress}
+                        endLength={4}
+                        contractUrl={getContractExplorerUrl(explorer, addressChainType)(laneAddress)}
+                      />
+                    </td>
+                    <td>{inOutbound === LaneFilter.Outbound ? network.onRamp?.version : network.offRamp?.version}</td>
+                  </tr>
+                )
+              })}
           </tbody>
         </table>
       </div>
diff --git a/src/components/CCIP/Tables/TokenChainsTable.tsx b/src/components/CCIP/Tables/TokenChainsTable.tsx
index 88ff14844ef..c52f115e3c9 100644
--- a/src/components/CCIP/Tables/TokenChainsTable.tsx
+++ b/src/components/CCIP/Tables/TokenChainsTable.tsx
@@ -6,7 +6,7 @@ import { areAllLanesPaused } from "~/config/data/ccip/utils.ts"
 import { ChainType, ExplorerInfo } from "~/config/types.ts"
 import TableSearchInput from "./TableSearchInput.tsx"
 import { useState } from "react"
-import { getExplorerAddressUrl, fallbackTokenIconUrl } from "~/features/utils/index.ts"
+import { getContractExplorerUrl, fallbackTokenIconUrl, isCantonNativeFeeToken } from "~/features/utils/index.ts"
 import TokenDrawer from "../Drawer/TokenDrawer.tsx"
 
 interface TableProps {
@@ -124,7 +124,11 @@ function TokenChainsTable({ networks, token, lanes, environment }: TableProps) {
                     <td>{network.tokenDecimals}</td>
                     <td data-clipboard-type="token">
                       <Address
-                        contractUrl={getExplorerAddressUrl(network.explorer, network.chainType)(network.tokenAddress)}
+                        contractUrl={
+                          isCantonNativeFeeToken(network.key, network.tokenId)
+                            ? undefined
+                            : getContractExplorerUrl(network.explorer, network.chainType)(network.tokenAddress)
+                        }
                         address={network.tokenAddress}
                         endLength={6}
                       />
@@ -132,7 +136,7 @@ function TokenChainsTable({ networks, token, lanes, environment }: TableProps) {
                     <td>{tokenPoolDisplay(network.tokenPoolType)}</td>
                     <td data-clipboard-type="token-pool">
                       <Address
-                        contractUrl={getExplorerAddressUrl(
+                        contractUrl={getContractExplorerUrl(
                           network.explorer,
                           network.chainType
                         )(network.tokenPoolAddress)}
diff --git a/src/config/chainTypes.ts b/src/config/chainTypes.ts
index a4af3e010b1..ad3e3659e3d 100644
--- a/src/config/chainTypes.ts
+++ b/src/config/chainTypes.ts
@@ -84,9 +84,9 @@ export const CHAIN_TYPE_CONFIGS: Record<ChainType, ChainTypeConfig> = {
 
 /**
  * Chain types supported in CCIP
- * Currently: EVM, Solana, Aptos, TON
+ * Currently: EVM, Solana, Aptos, TON, Canton
  */
-export const CCIP_SUPPORTED_CHAINS: ChainType[] = ["evm", "solana", "aptos", "ton"]
+export const CCIP_SUPPORTED_CHAINS: ChainType[] = ["evm", "solana", "aptos", "ton", "canton"]
 
 /**
  * Sections that support chain type filtering (OPT-IN)
diff --git a/src/config/data/ccip/data.ts b/src/config/data/ccip/data.ts
index ca03b8535d1..4cfa6c8acd7 100644
--- a/src/config/data/ccip/data.ts
+++ b/src/config/data/ccip/data.ts
@@ -20,7 +20,6 @@ import {
   directoryToSupportedChain,
   getChainIcon,
   getExplorer,
-  getExplorerAddressUrl,
   getTitle,
   getChainTypeAndFamily,
   supportedChainToChainInRdd,
@@ -513,7 +512,6 @@ const buildNetworkForChain = ({ chain, filter }: { chain: string; filter: Enviro
 
   const { chainType } = getChainTypeAndFamily(supportedChain)
 
-  const routerExplorerUrl = getExplorerAddressUrl(explorer, chainType)(router.address)
   const nativeToken = getNativeCurrency(supportedChain)
   if (!nativeToken) throw Error(`Native token not found for ${supportedChain}`)
 
@@ -535,7 +533,6 @@ const buildNetworkForChain = ({ chain, filter }: { chain: string; filter: Enviro
     ccipHome: chainConfig.ccipHome?.address,
     registryModule: chainConfig.registryModule?.address,
     router,
-    routerExplorerUrl,
     chainSelector: chainConfig.chainSelector,
     nativeToken: {
       name: nativeToken.name,
@@ -550,6 +547,15 @@ const buildNetworkForChain = ({ chain, filter }: { chain: string; filter: Enviro
     feeQuoter: chainType === "solana" ? chainConfig.feeQuoter : undefined,
     mcms: chainType === "aptos" ? chainConfig.mcms?.address : undefined,
     poolPrograms: chainType === "solana" ? chainConfig.poolPrograms : undefined,
+    ...(chainType === "canton"
+      ? {
+          ccipOwnerParty: chainConfig.ccipOwnerParty,
+          ccipExplicitDisclosureServer: chainConfig.ccipExplicitDisclosureServer,
+          committeeVerifier: chainConfig.committeeVerifier,
+          feeQuoterModule: chainConfig.feeQuoterModule,
+          indexer: chainConfig.indexer,
+        }
+      : {}),
   }
 }
 
diff --git a/src/config/data/ccip/types.ts b/src/config/data/ccip/types.ts
index 51eaf5e0646..f5c7a95fe08 100644
--- a/src/config/data/ccip/types.ts
+++ b/src/config/data/ccip/types.ts
@@ -82,6 +82,20 @@ export type ChainConfig = {
   mcms?: {
     address: string
   }
+  ccipOwnerParty?: string
+  ccipExplicitDisclosureServer?: string
+  committeeVerifier?: {
+    address: string
+    version: string
+  }
+  feeQuoterModule?: {
+    address: string
+    version: string
+  }
+  indexer?: {
+    primary: string
+    backup: string | null
+  }
   poolPrograms?: {
     BurnMintTokenPool?: string
     LockReleaseTokenPool?: string
@@ -216,7 +230,6 @@ export interface Network {
     address: string
     version: string
   }
-  routerExplorerUrl: string
   feeQuoter?: string
   mcms?: string
   poolPrograms?: {
@@ -224,6 +237,20 @@ export interface Network {
     LockReleaseTokenPool?: string
     CCTPTokenPool?: string
   }
+  ccipOwnerParty?: string
+  ccipExplicitDisclosureServer?: string
+  committeeVerifier?: {
+    address: string
+    version: string
+  }
+  feeQuoterModule?: {
+    address: string
+    version: string
+  }
+  indexer?: {
+    primary: string
+    backup: string | null
+  }
 }
 
 export type DecomConfig = {
diff --git a/src/config/data/ccip/v1_2_0/mainnet/chains.json b/src/config/data/ccip/v1_2_0/mainnet/chains.json
index f3a8547546d..5ebac590486 100644
--- a/src/config/data/ccip/v1_2_0/mainnet/chains.json
+++ b/src/config/data/ccip/v1_2_0/mainnet/chains.json
@@ -374,6 +374,36 @@
       "version": "1.5.1"
     }
   },
+  "canton-mainnet": {
+    "armProxy": {
+      "address": "rmn_remote-mnprd@rmnOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093",
+      "version": "2.0.0"
+    },
+    "ccipExplicitDisclosureServer": "https://eds.ccip.chain.link",
+    "ccipOwnerParty": "ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093",
+    "chainSelector": "2308837218439511688",
+    "committeeVerifier": {
+      "address": "committeeverifier-mnprd@ccvOwner::122096accf0a84fc7d80d5fce5ea3135317a03eb22e62e0d8cdd7548865f984f11ff",
+      "version": "2.0.0"
+    },
+    "feeQuoterModule": {
+      "address": "feequoter-fpxih@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093",
+      "version": "2.0.0"
+    },
+    "feeTokens": ["CC", "LINK"],
+    "indexer": {
+      "backup": "https://indexer-2.ccip.chain.link",
+      "primary": "https://indexer-1.ccip.chain.link"
+    },
+    "router": {
+      "address": "perpartyrouterfactory-woxhm@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093",
+      "version": "2.0.0"
+    },
+    "tokenAdminRegistry": {
+      "address": "",
+      "version": ""
+    }
+  },
   "celo-mainnet": {
     "armProxy": {
       "address": "0x56e0507d4E69D98bE7Eb4ada01d2315596F9f281",
diff --git a/src/config/data/ccip/v1_2_0/mainnet/lanes.json b/src/config/data/ccip/v1_2_0/mainnet/lanes.json
index de45b90ff78..bc59e59a2fd 100644
--- a/src/config/data/ccip/v1_2_0/mainnet/lanes.json
+++ b/src/config/data/ccip/v1_2_0/mainnet/lanes.json
@@ -153,20 +153,6 @@
               "rate": "32000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -348,20 +334,6 @@
               "rate": "13880000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -1221,6 +1193,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -1290,20 +1276,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -1541,6 +1513,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -1596,20 +1582,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -1939,20 +1911,6 @@
             }
           }
         },
-        "USDM": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            },
-            "out": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            }
-          }
-        },
         "USDC": {
           "rateLimiterConfig": {
             "in": {
@@ -1966,6 +1924,20 @@
               "rate": "0"
             }
           }
+        },
+        "USDM": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            },
+            "out": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            }
+          }
         }
       }
     },
@@ -2527,6 +2499,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -2624,20 +2610,6 @@
               "rate": "1388888888888888888"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -2721,6 +2693,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -2776,20 +2762,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -4604,20 +4576,6 @@
               "rate": "1160"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "50000000000",
-              "isEnabled": true,
-              "rate": "10000000"
-            }
-          }
         }
       }
     },
@@ -5165,20 +5123,6 @@
               "rate": "11574074074074"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -9548,6 +9492,35 @@
       }
     }
   },
+  "canton-mainnet": {
+    "mainnet": {
+      "offRamp": {
+        "address": "offramp-tyazo@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093",
+        "version": "2.0.0"
+      },
+      "onRamp": {
+        "address": "onramp-kpyig@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093",
+        "enforceOutOfOrder": true,
+        "version": "2.0.0"
+      },
+      "supportedTokens": {
+        "LINK": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "550000000000000",
+              "isEnabled": true,
+              "rate": "152680000000"
+            },
+            "out": {
+              "capacity": "500000000000000",
+              "isEnabled": true,
+              "rate": "138800000000"
+            }
+          }
+        }
+      }
+    }
+  },
   "celo-mainnet": {
     "ethereum-mainnet-arbitrum-1": {
       "offRamp": {
@@ -10442,6 +10415,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -10511,20 +10498,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -11472,6 +11445,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -11681,20 +11668,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -12104,6 +12077,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -12187,20 +12174,6 @@
               "rate": "5787000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -13132,6 +13105,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDFI": {
           "rateLimiterConfig": {
             "in": {
@@ -13467,20 +13454,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -13606,6 +13579,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -13675,20 +13662,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -14010,6 +13983,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "W0G": {
           "rateLimiterConfig": {
             "in": {
@@ -14051,20 +14038,6 @@
               "rate": "277770000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -14584,6 +14557,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -14639,20 +14626,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -16034,6 +16007,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -16243,20 +16230,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -16694,6 +16667,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -16791,20 +16778,6 @@
               "rate": "5787000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -17928,6 +17901,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDf": {
           "rateLimiterConfig": {
             "in": {
@@ -18277,20 +18264,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -18514,6 +18487,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -18597,20 +18584,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -19260,6 +19233,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "VIRTUAL": {
           "rateLimiterConfig": {
             "in": {
@@ -19343,20 +19330,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -22481,20 +22454,6 @@
             }
           }
         },
-        "USDM": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            },
-            "out": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            }
-          }
-        },
         "USDC": {
           "rateLimiterConfig": {
             "in": {
@@ -22508,6 +22467,20 @@
               "rate": "0"
             }
           }
+        },
+        "USDM": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            },
+            "out": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            }
+          }
         }
       }
     },
@@ -22741,6 +22714,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -22824,20 +22811,6 @@
               "rate": "5787000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -22992,6 +22965,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -23089,20 +23076,6 @@
               "rate": "5787000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -23482,6 +23455,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -23593,20 +23580,6 @@
               "rate": "5787000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -23663,20 +23636,6 @@
             }
           }
         },
-        "USDM": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            },
-            "out": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            }
-          }
-        },
         "USDC": {
           "rateLimiterConfig": {
             "in": {
@@ -23690,6 +23649,20 @@
               "rate": "0"
             }
           }
+        },
+        "USDM": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            },
+            "out": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            }
+          }
         }
       }
     },
@@ -26121,20 +26094,6 @@
               "rate": "3472000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -26310,20 +26269,6 @@
               "rate": "32000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -26419,20 +26364,6 @@
               "rate": "13880000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -26919,7 +26850,7 @@
             }
           }
         },
-        "TREE": {
+        "USDC": {
           "rateLimiterConfig": {
             "in": {
               "capacity": "0",
@@ -27030,20 +26961,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -27347,20 +27264,6 @@
               "rate": "1160"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -27444,20 +27347,6 @@
               "rate": "11574074074074"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -28572,6 +28461,33 @@
         }
       }
     },
+    "canton-mainnet": {
+      "offRamp": {
+        "address": "0x408428bca0e24A25ac8baAc1b70f64AF257717c3",
+        "version": "2.0.0"
+      },
+      "onRamp": {
+        "address": "0x2613cc57F3ac4a054D79a04618Fb62589b8a4b26",
+        "enforceOutOfOrder": false,
+        "version": "2.0.0"
+      },
+      "supportedTokens": {
+        "LINK": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "550000000000000",
+              "isEnabled": true,
+              "rate": "152680000000"
+            },
+            "out": {
+              "capacity": "49999999999999995805696",
+              "isEnabled": true,
+              "rate": "13880000000000000000"
+            }
+          }
+        }
+      }
+    },
     "celo-mainnet": {
       "offRamp": {
         "address": "0x794aE32b63b8a82a6e2Ec5017bbC6bfbddA5ce96",
@@ -29619,6 +29535,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDFI": {
           "rateLimiterConfig": {
             "in": {
@@ -29954,20 +29884,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -30920,6 +30836,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDf": {
           "rateLimiterConfig": {
             "in": {
@@ -31269,20 +31199,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -32244,6 +32160,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -32355,20 +32285,6 @@
               "rate": "5787000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -33138,20 +33054,6 @@
               "rate": "5787000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -33467,6 +33369,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -33578,20 +33494,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -34069,20 +33971,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "2",
-              "isEnabled": true,
-              "rate": "1"
-            }
-          }
         }
       }
     },
@@ -34777,20 +34665,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -35319,20 +35193,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -35993,20 +35853,6 @@
               "rate": "55550000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -36251,6 +36097,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -36306,20 +36166,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -36751,6 +36597,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -36820,20 +36680,6 @@
               "rate": "1"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -37057,6 +36903,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -37140,20 +37000,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -37289,20 +37135,6 @@
             }
           }
         },
-        "USDM": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            },
-            "out": {
-              "capacity": "1000000000000000000000000",
-              "isEnabled": true,
-              "rate": "11600000000000000000"
-            }
-          }
-        },
         "USDC": {
           "rateLimiterConfig": {
             "in": {
@@ -37316,6 +37148,20 @@
               "rate": "0"
             }
           }
+        },
+        "USDM": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            },
+            "out": {
+              "capacity": "1000000000000000000000000",
+              "isEnabled": true,
+              "rate": "11600000000000000000"
+            }
+          }
         }
       }
     },
@@ -37695,6 +37541,20 @@
             }
           }
         },
+        "USDC": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        },
         "USDM": {
           "rateLimiterConfig": {
             "in": {
@@ -37806,20 +37666,6 @@
               "rate": "1388888888888888888"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -39822,20 +39668,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "2",
-              "isEnabled": true,
-              "rate": "1"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
@@ -42168,20 +42000,6 @@
               "rate": "0"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     }
@@ -47130,20 +46948,6 @@
               "rate": "55550000000000000000"
             }
           }
-        },
-        "USDC": {
-          "rateLimiterConfig": {
-            "in": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            },
-            "out": {
-              "capacity": "0",
-              "isEnabled": false,
-              "rate": "0"
-            }
-          }
         }
       }
     },
diff --git a/src/config/data/ccip/v1_2_0/mainnet/tokens.json b/src/config/data/ccip/v1_2_0/mainnet/tokens.json
index 9ee7b70b01a..0a8925b5bd8 100644
--- a/src/config/data/ccip/v1_2_0/mainnet/tokens.json
+++ b/src/config/data/ccip/v1_2_0/mainnet/tokens.json
@@ -1539,6 +1539,16 @@
       "typeAndVersion": "BurnMintTokenPool 1.6.1"
     }
   },
+  "CC": {
+    "canton-mainnet": {
+      "allowListEnabled": false,
+      "decimals": 10,
+      "name": "Canton Coin",
+      "poolType": "feeTokenOnly",
+      "symbol": "CC",
+      "tokenAddress": "Amulet@DSO::1220b1431ef217342db44d516bb9befde802be7d8899637d290895fa58880f19accc"
+    }
+  },
   "CGX": {
     "mainnet": {
       "allowListEnabled": false,
@@ -3342,6 +3352,16 @@
       "symbol": "LINK",
       "tokenAddress": "0x404460C6A5EdE2D891e8297795264fDe62ADBB75"
     },
+    "canton-mainnet": {
+      "allowListEnabled": false,
+      "decimals": 10,
+      "name": "ChainLink Token",
+      "poolAddress": "0xe24b90175fcc5be6cec6b6a107064a128f44c836f277aa4c3b280d25a5277946",
+      "poolType": "burnMint",
+      "symbol": "LINK",
+      "tokenAddress": "0xa218e95e9abb1e7cd52aabd8249ea78d6f71fa12b95dd1bc4c996d5e34f1790d",
+      "typeAndVersion": "BurnMintTokenPool 2.0.0"
+    },
     "celo-mainnet": {
       "allowListEnabled": false,
       "decimals": 18,
@@ -5669,16 +5689,6 @@
       "symbol": "savUSD",
       "tokenAddress": "0xb9827268eBCc4EA7b105cfC787A92c612629A3f1",
       "typeAndVersion": "BurnMintTokenPool 1.5.1"
-    },
-    "sei-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 18,
-      "name": "Staked avUSD",
-      "poolAddress": "0x25fa35c9672ea3eF762704AC4f77bC2f9D4D3598",
-      "poolType": "burnMint",
-      "symbol": "savUSD",
-      "tokenAddress": "0xd84A49df125F6744018518117FE59A86D39eAE75",
-      "typeAndVersion": "BurnMintTokenPool 1.5.1"
     }
   },
   "SD": {
@@ -7878,26 +7888,6 @@
     }
   },
   "USDC": {
-    "0g-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "Bridged USDC",
-      "poolAddress": "0x0A3d8eD619ECF1E984488710eB2cEcE4FDbd83CA",
-      "poolType": "burnMint",
-      "symbol": "USDC.e",
-      "tokenAddress": "0x1f3AA82227281cA364bFb3d253B0f1af1Da6473E",
-      "typeAndVersion": "BurnMintTokenPool 1.6.1"
-    },
-    "adi-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "USDC.e",
-      "poolAddress": "0x8a6fA014cf9D55345c71891326e7347feb742E84",
-      "poolType": "burnMint",
-      "symbol": "USDC.e",
-      "tokenAddress": "0x9cb8142aEBBcdc60AF7c97Af897A67A8f3CA71C2",
-      "typeAndVersion": "BurnMintTokenPool 1.6.1"
-    },
     "avalanche-mainnet": {
       "allowListEnabled": false,
       "decimals": 6,
@@ -7908,26 +7898,6 @@
       "tokenAddress": "0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E",
       "typeAndVersion": "USDCTokenPool 1.6.2"
     },
-    "bitcoin-mainnet-bitlayer-1": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "USD Coin",
-      "poolAddress": "0xff170aD8f1d86eFAC90CA7a2E1204bA64aC5e0f9",
-      "poolType": "burnMint",
-      "symbol": "USDC",
-      "tokenAddress": "0xf8C374CE88A3BE3d374e8888349C7768B607c755",
-      "typeAndVersion": "BurnMintTokenPool 1.5.1"
-    },
-    "bitcoin-mainnet-bob-1": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "Bridged USDC (BOB)",
-      "poolAddress": "0x554652E7F10fB8aa3e12226213c6826F98B09CF0",
-      "poolType": "burnMint",
-      "symbol": "USDC.e",
-      "tokenAddress": "0xe75D0fB2C24A55cA1e3F96781a2bCC7bdba058F0",
-      "typeAndVersion": "BurnMintTokenPool 1.5.1"
-    },
     "ethereum-mainnet-arbitrum-1": {
       "allowListEnabled": false,
       "decimals": 6,
@@ -7968,16 +7938,6 @@
       "tokenAddress": "0x078D782b760474a361dDA0AF3839290b0EF57AD6",
       "typeAndVersion": "USDCTokenPool 1.6.2"
     },
-    "jovay-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "Bridged USDC (Jovay)",
-      "poolAddress": "0xe2712A0C09DfB8031857Adb8D73Eb04997D271bA",
-      "poolType": "burnMint",
-      "symbol": "USDC.e",
-      "tokenAddress": "0xE12DaAB5E61b3CF6ca38a99612b5C2d9626d50C7",
-      "typeAndVersion": "BurnMintTokenPool 1.6.1"
-    },
     "mainnet": {
       "allowListEnabled": false,
       "decimals": 6,
@@ -7998,26 +7958,6 @@
       "tokenAddress": "0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359",
       "typeAndVersion": "USDCTokenPool 1.6.2"
     },
-    "pharos-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "Bridged USDC (Pharos)",
-      "poolAddress": "0xaA5f3511e309E410726ea65837C476188A84a46c",
-      "poolType": "burnMint",
-      "symbol": "USDC.e",
-      "tokenAddress": "0x7126C3FeF4e6a680eeE09Fb039B2236F638384B0",
-      "typeAndVersion": "BurnMintTokenPool 1.6.1"
-    },
-    "ronin-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "USD Coin",
-      "poolAddress": "0xe26D9c68cF6d284367C5e90EC834C6Ec0051f73C",
-      "poolType": "burnMint",
-      "symbol": "USDC",
-      "tokenAddress": "0x0B7007c13325C48911F73A2daD5FA5dCBf808aDc",
-      "typeAndVersion": "BurnMintTokenPool 1.5.1"
-    },
     "solana-mainnet": {
       "allowListEnabled": false,
       "decimals": 6,
@@ -8027,16 +7967,6 @@
       "symbol": "USDC",
       "tokenAddress": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
       "typeAndVersion": "CctpTokenPool 1.6.2"
-    },
-    "wemix-mainnet": {
-      "allowListEnabled": false,
-      "decimals": 6,
-      "name": "Bridged USDC",
-      "poolAddress": "0x5937c7096b054564c6F17B7e61D9Abf1256B0593",
-      "poolType": "burnMint",
-      "symbol": "USDC.e",
-      "tokenAddress": "0x44bB111010DfFfb3695F9a1B66aa879976199e7b",
-      "typeAndVersion": "BurnMintTokenPool 1.5.1"
     }
   },
   "USDf": {
diff --git a/src/config/data/ccip/v1_2_0/testnet/chains.json b/src/config/data/ccip/v1_2_0/testnet/chains.json
index ea8f903edb4..f73139918a7 100644
--- a/src/config/data/ccip/v1_2_0/testnet/chains.json
+++ b/src/config/data/ccip/v1_2_0/testnet/chains.json
@@ -326,6 +326,36 @@
       "version": "1.5.1"
     }
   },
+  "canton-testnet": {
+    "armProxy": {
+      "address": "rmn_remote-nzvtd@rmnOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+      "version": "2.0.0"
+    },
+    "ccipExplicitDisclosureServer": "https://eds.testnet.ccip.chain.link",
+    "ccipOwnerParty": "ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+    "chainSelector": "9268731218649498074",
+    "committeeVerifier": {
+      "address": "committeeverifier-tqkny@ccvOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+      "version": "2.0.0"
+    },
+    "feeQuoterModule": {
+      "address": "feequoter-scxln@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+      "version": "2.0.0"
+    },
+    "feeTokens": ["Amulet", "LINK"],
+    "indexer": {
+      "backup": null,
+      "primary": "https://indexer-1.testnet.ccip.chain.link"
+    },
+    "router": {
+      "address": "perpartyrouterfactory-ahrar@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+      "version": "2.0.0"
+    },
+    "tokenAdminRegistry": {
+      "address": "tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+      "version": "2.0.0"
+    }
+  },
   "core-testnet": {
     "armProxy": {
       "address": "0xF39a1260F4E3345D810e1b8aA569200e1D27A998",
diff --git a/src/config/data/ccip/v1_2_0/testnet/lanes.json b/src/config/data/ccip/v1_2_0/testnet/lanes.json
index 4ec7a0d2a56..469a6b05e7f 100644
--- a/src/config/data/ccip/v1_2_0/testnet/lanes.json
+++ b/src/config/data/ccip/v1_2_0/testnet/lanes.json
@@ -1691,6 +1691,35 @@
       }
     }
   },
+  "canton-testnet": {
+    "ethereum-testnet-sepolia": {
+      "offRamp": {
+        "address": "offramp-dajww@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+        "version": "2.0.0"
+      },
+      "onRamp": {
+        "address": "onramp-vwcfo@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+        "enforceOutOfOrder": true,
+        "version": "2.0.0"
+      },
+      "supportedTokens": {
+        "LINK": {
+          "rateLimiterConfig": {
+            "in": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            },
+            "out": {
+              "capacity": "0",
+              "isEnabled": false,
+              "rate": "0"
+            }
+          }
+        }
+      }
+    }
+  },
   "core-testnet": {
     "ethereum-testnet-sepolia": {
       "offRamp": {
@@ -2262,6 +2291,16 @@
         }
       }
     },
+    "canton-testnet": {
+      "offRamp": {
+        "address": "0xc6A246A9AcdAaE651708706494720F79C3E5d0A1",
+        "version": "2.0.0"
+      },
+      "onRamp": {
+        "address": "0x181Ac7dC295f1C8C87342d07CFaBA90bC477DB5d",
+        "version": "2.0.0"
+      }
+    },
     "core-testnet": {
       "offRamp": {
         "address": "0x20E65b919da86201Ff95C070bd17291D2761Ac6c",
diff --git a/src/config/data/ccip/v1_2_0/testnet/tokens.json b/src/config/data/ccip/v1_2_0/testnet/tokens.json
index c3ac5daf775..cad8e67df2a 100644
--- a/src/config/data/ccip/v1_2_0/testnet/tokens.json
+++ b/src/config/data/ccip/v1_2_0/testnet/tokens.json
@@ -9,6 +9,16 @@
       "tokenAddress": "0x20C0000000000000000000000000000000000001"
     }
   },
+  "Amulet": {
+    "canton-testnet": {
+      "allowListEnabled": false,
+      "decimals": 10,
+      "name": "Amulet",
+      "poolType": "feeTokenOnly",
+      "symbol": "Amulet",
+      "tokenAddress": "Amulet@DSO::1220f22a8b8f2d813c25b9a684dc4dd52b532a0174d8e73a13cdf2baabfff7518337"
+    }
+  },
   "APT": {
     "aptos-testnet": {
       "allowListEnabled": false,
@@ -866,6 +876,16 @@
       "symbol": "LINK",
       "tokenAddress": "0x84b9B910527Ad5C03A9Ca831909E21e236EA7b06"
     },
+    "canton-testnet": {
+      "allowListEnabled": false,
+      "decimals": 10,
+      "name": "ChainLink Token",
+      "poolAddress": "0x6ac67a53d53ac425440550d27afeb1da16f6d41c224dcd1ed8e9ab1ae20f7ace",
+      "poolType": "burnMint",
+      "symbol": "LINK",
+      "tokenAddress": "0x39c6212f2291365bed155b2533abbd7ddf340498ccbbb358cee07b83106986ad",
+      "typeAndVersion": "BurnMintTokenPool 2.0.0"
+    },
     "core-testnet": {
       "allowListEnabled": false,
       "decimals": 18,
@@ -926,9 +946,11 @@
       "allowListEnabled": false,
       "decimals": 18,
       "name": "ChainLink Token",
-      "poolType": "feeTokenOnly",
+      "poolAddress": "0x4f3DF8bF87EfC7ef2076571e0d2e4F762F1d06c0",
+      "poolType": "lockRelease",
       "symbol": "LINK",
-      "tokenAddress": "0x779877A7B0D9E8603169DdbD7836e478b4624789"
+      "tokenAddress": "0x779877A7B0D9E8603169DdbD7836e478b4624789",
+      "typeAndVersion": "LockReleaseTokenPool 1.5.1"
     },
     "ethereum-testnet-sepolia-andromeda-1": {
       "allowListEnabled": false,
diff --git a/src/config/data/chain-to-technology.json b/src/config/data/chain-to-technology.json
index aba51f4e363..71c60226bd8 100644
--- a/src/config/data/chain-to-technology.json
+++ b/src/config/data/chain-to-technology.json
@@ -183,5 +183,7 @@
   "ROBINHOOD_MAINNET": "ROBINHOOD_CHAIN",
   "TON_TESTNET": "TON",
   "TON_MAINNET": "TON",
+  "CANTON_TESTNET": "CANTON",
+  "CANTON_MAINNET": "CANTON",
   "CREDITCOIN_MAINNET": "CREDITCOIN"
 }
diff --git a/src/config/data/chains.json b/src/config/data/chains.json
index f0e3b0f54f5..0af7889e2ea 100644
--- a/src/config/data/chains.json
+++ b/src/config/data/chains.json
@@ -2885,6 +2885,37 @@
       }
     }
   },
+  "CANTON": {
+    "title": "Canton",
+    "icon": "/assets/chains/canton.svg",
+    "chainType": "canton",
+    "chains": {
+      "CANTON_MAINNET": {
+        "chainId": "MainNet",
+        "title": "Canton Mainnet",
+        "explorer": {
+          "baseUrl": "https://lighthouse.cantonloop.com"
+        },
+        "nativeCurrency": {
+          "name": "Canton Coin",
+          "symbol": "CC",
+          "decimals": 10
+        }
+      },
+      "CANTON_TESTNET": {
+        "chainId": "TestNet",
+        "title": "Canton Testnet",
+        "explorer": {
+          "baseUrl": "https://lighthouse.testnet.cantonloop.com"
+        },
+        "nativeCurrency": {
+          "name": "Amulet",
+          "symbol": "Amulet",
+          "decimals": 10
+        }
+      }
+    }
+  },
   "CREDITCOIN": {
     "title": "Creditcoin",
     "icon": "/assets/chains/creditcoin.svg",
diff --git a/src/config/sidebar/__tests__/__snapshots__/ccip-dynamic.test.ts.snap b/src/config/sidebar/__tests__/__snapshots__/ccip-dynamic.test.ts.snap
index 52b27a98a5c..1c5ea216255 100644
--- a/src/config/sidebar/__tests__/__snapshots__/ccip-dynamic.test.ts.snap
+++ b/src/config/sidebar/__tests__/__snapshots__/ccip-dynamic.test.ts.snap
@@ -34,6 +34,13 @@ exports[`CCIP Sidebar Configuration Snapshot should match the expected sidebar s
         "title": "Getting Started",
         "url": "ccip/getting-started/aptos",
       },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Getting Started",
+        "url": "ccip/getting-started/canton",
+      },
       {
         "children": [
           {
@@ -81,6 +88,12 @@ exports[`CCIP Sidebar Configuration Snapshot should match the expected sidebar s
         "url": "ccip/service-responsibility",
       },
       {
+        "chainTypes": [
+          "evm",
+          "solana",
+          "aptos",
+          "ton",
+        ],
         "title": "Execution Latency",
         "url": "ccip/ccip-execution-latency",
       },
@@ -250,6 +263,12 @@ exports[`CCIP Sidebar Configuration Snapshot should match the expected sidebar s
         "url": "ccip/concepts/architecture/onchain/ton",
       },
       {
+        "chainTypes": [
+          "evm",
+          "solana",
+          "aptos",
+          "ton",
+        ],
         "title": "Offchain Architecture",
         "url": "ccip/concepts/architecture/offchain/overview",
       },
@@ -485,6 +504,48 @@ exports[`CCIP Sidebar Configuration Snapshot should match the expected sidebar s
         "title": "Best Practices",
         "url": "ccip/concepts/best-practices/ton",
       },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Key Concepts",
+        "url": "ccip/concepts/canton/key-concepts",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Overview",
+        "url": "ccip/concepts/canton/overview",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Manual execution",
+        "url": "ccip/concepts/canton/manual-execution",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Token Pools",
+        "url": "ccip/concepts/canton/token-pools",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Explicit Disclosure API",
+        "url": "ccip/concepts/canton/explicit-disclosure",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "title": "Upgradability",
+        "url": "ccip/concepts/canton/upgradability",
+      },
     ],
     "section": "Concepts",
   },
@@ -528,6 +589,12 @@ exports[`CCIP Sidebar Configuration Snapshot should match the expected sidebar s
         "url": "ccip/test-tokens",
       },
       {
+        "chainTypes": [
+          "evm",
+          "solana",
+          "aptos",
+          "ton",
+        ],
         "title": "Offchain",
         "url": "ccip/tutorials/offchain",
       },
@@ -939,6 +1006,110 @@ exports[`CCIP Sidebar Configuration Snapshot should match the expected sidebar s
         "title": "Destination",
         "url": "ccip/tutorials/ton/destination",
       },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "children": [
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Registry Issuer Guide",
+            "url": "ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "BurnMint Token Pool Deployment",
+            "url": "ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "LockRelease Token Pool Deployment",
+            "url": "ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool",
+          },
+        ],
+        "title": "Cross-Chain Token (CCT)",
+        "url": "ccip/tutorials/canton/cross-chain-tokens",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "children": [
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Prerequisites",
+            "url": "ccip/tutorials/canton/source/prerequisites",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Token Transfers",
+            "url": "ccip/tutorials/canton/source/token-transfers",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Arbitrary Messaging",
+            "url": "ccip/tutorials/canton/source/arbitrary-messaging",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Programmable Token Transfers",
+            "url": "ccip/tutorials/canton/source/programmable-token-transfers",
+          },
+        ],
+        "title": "Source",
+        "url": "ccip/tutorials/canton/source",
+      },
+      {
+        "chainTypes": [
+          "canton",
+        ],
+        "children": [
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Prerequisites",
+            "url": "ccip/tutorials/canton/destination/prerequisites",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Token Transfers",
+            "url": "ccip/tutorials/canton/destination/token-transfers",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Arbitrary Messaging",
+            "url": "ccip/tutorials/canton/destination/arbitrary-messaging",
+          },
+          {
+            "chainTypes": [
+              "canton",
+            ],
+            "title": "Programmable Token Transfers",
+            "url": "ccip/tutorials/canton/destination/programmable-token-transfers",
+          },
+        ],
+        "title": "Destination",
+        "url": "ccip/tutorials/canton/destination",
+      },
     ],
     "section": "Tutorials",
   },
diff --git a/src/config/sidebar/__tests__/ccip-dynamic.test.ts b/src/config/sidebar/__tests__/ccip-dynamic.test.ts
index b40469cbf03..0d3b66d30a3 100644
--- a/src/config/sidebar/__tests__/ccip-dynamic.test.ts
+++ b/src/config/sidebar/__tests__/ccip-dynamic.test.ts
@@ -2,6 +2,7 @@ import { describe, it, expect } from "@jest/globals"
 import { CCIP_SIDEBAR_CONTENT } from "../ccip-dynamic.ts"
 import type { SectionEntry, SectionContent } from "../../sidebar.ts"
 import type { ChainType } from "../../types.ts"
+import { CCIP_SUPPORTED_CHAINS } from "../../chainTypes.ts"
 
 describe("CCIP Sidebar Configuration", () => {
   describe("Structural Integrity", () => {
@@ -43,7 +44,7 @@ describe("CCIP Sidebar Configuration", () => {
         if (item.chainTypes !== undefined) {
           expect(Array.isArray(item.chainTypes)).toBe(true)
           item.chainTypes.forEach((chainType: ChainType) => {
-            expect(["evm", "solana", "aptos", "ton"]).toContain(chainType)
+            expect(CCIP_SUPPORTED_CHAINS).toContain(chainType)
           })
         }
       }
@@ -56,7 +57,7 @@ describe("CCIP Sidebar Configuration", () => {
     })
 
     it("should only contain valid chainTypes", () => {
-      const validChainTypes = ["evm", "solana", "aptos", "ton"]
+      const validChainTypes = CCIP_SUPPORTED_CHAINS
 
       const checkChainTypes = (item: SectionContent) => {
         if (item.chainTypes) {
diff --git a/src/config/sidebar/ccip-dynamic.ts b/src/config/sidebar/ccip-dynamic.ts
index 3705c121914..ef8711c6fa4 100644
--- a/src/config/sidebar/ccip-dynamic.ts
+++ b/src/config/sidebar/ccip-dynamic.ts
@@ -51,6 +51,11 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
         url: "ccip/getting-started/aptos",
         chainTypes: ["aptos"],
       },
+      {
+        title: "Getting Started",
+        url: "ccip/getting-started/canton",
+        chainTypes: ["canton"],
+      },
       {
         title: "CCIP Directory",
         url: "ccip/directory",
@@ -93,6 +98,7 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
       {
         title: "Execution Latency",
         url: "ccip/ccip-execution-latency",
+        chainTypes: ["evm", "solana", "aptos", "ton"],
       },
       {
         title: "Billing",
@@ -218,7 +224,7 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
       {
         title: "Offchain Architecture",
         url: "ccip/concepts/architecture/offchain/overview",
-        // Universal
+        chainTypes: ["evm", "solana", "aptos", "ton"],
       },
       {
         title: "Cross-Chain Token (CCT)",
@@ -369,6 +375,37 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
         url: "ccip/concepts/best-practices/ton",
         chainTypes: ["ton"],
       },
+      // Canton — minimal, enterprise-focused IA (independent of other chain families)
+      {
+        title: "Key Concepts",
+        url: "ccip/concepts/canton/key-concepts",
+        chainTypes: ["canton"],
+      },
+      {
+        title: "Overview",
+        url: "ccip/concepts/canton/overview",
+        chainTypes: ["canton"],
+      },
+      {
+        title: "Manual execution",
+        url: "ccip/concepts/canton/manual-execution",
+        chainTypes: ["canton"],
+      },
+      {
+        title: "Token Pools",
+        url: "ccip/concepts/canton/token-pools",
+        chainTypes: ["canton"],
+      },
+      {
+        title: "Explicit Disclosure API",
+        url: "ccip/concepts/canton/explicit-disclosure",
+        chainTypes: ["canton"],
+      },
+      {
+        title: "Upgradability",
+        url: "ccip/concepts/canton/upgradability",
+        chainTypes: ["canton"],
+      },
     ],
   },
   {
@@ -402,7 +439,7 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
       {
         title: "Offchain",
         url: "ccip/tutorials/offchain",
-        // Universal - supports all chain families
+        chainTypes: ["evm", "solana", "aptos", "ton"],
       },
       {
         title: "Transfer Tokens",
@@ -716,6 +753,83 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
       //   url: "ccip/tutorials/ton/cross-chain-tokens",
       //   chainTypes: ["ton"],
       // },
+      // Canton tutorials — minimal set for initial public release
+      {
+        title: "Cross-Chain Token (CCT)",
+        url: "ccip/tutorials/canton/cross-chain-tokens",
+        chainTypes: ["canton"],
+        children: [
+          {
+            title: "Registry Issuer Guide",
+            url: "ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "BurnMint Token Pool Deployment",
+            url: "ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "LockRelease Token Pool Deployment",
+            url: "ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool",
+            chainTypes: ["canton"],
+          },
+        ],
+      },
+      {
+        title: "Source",
+        url: "ccip/tutorials/canton/source",
+        chainTypes: ["canton"],
+        children: [
+          {
+            title: "Prerequisites",
+            url: "ccip/tutorials/canton/source/prerequisites",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "Token Transfers",
+            url: "ccip/tutorials/canton/source/token-transfers",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "Arbitrary Messaging",
+            url: "ccip/tutorials/canton/source/arbitrary-messaging",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "Programmable Token Transfers",
+            url: "ccip/tutorials/canton/source/programmable-token-transfers",
+            chainTypes: ["canton"],
+          },
+        ],
+      },
+      {
+        title: "Destination",
+        url: "ccip/tutorials/canton/destination",
+        chainTypes: ["canton"],
+        children: [
+          {
+            title: "Prerequisites",
+            url: "ccip/tutorials/canton/destination/prerequisites",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "Token Transfers",
+            url: "ccip/tutorials/canton/destination/token-transfers",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "Arbitrary Messaging",
+            url: "ccip/tutorials/canton/destination/arbitrary-messaging",
+            chainTypes: ["canton"],
+          },
+          {
+            title: "Programmable Token Transfers",
+            url: "ccip/tutorials/canton/destination/programmable-token-transfers",
+            chainTypes: ["canton"],
+          },
+        ],
+      },
     ],
   },
   {
diff --git a/src/config/types.ts b/src/config/types.ts
index d6ed1131ede..ae92c77be14 100644
--- a/src/config/types.ts
+++ b/src/config/types.ts
@@ -85,6 +85,7 @@ export type SupportedTechnology =
   | "ADI_NETWORK"
   | "EDGE"
   | "ROBINHOOD_CHAIN"
+  | "CANTON"
   | "CREDITCOIN"
 
 export type ChainType = "evm" | "solana" | "aptos" | "sui" | "canton" | "ton" | "tron" | "stellar" | "starknet"
@@ -276,6 +277,8 @@ export type SupportedChain =
   | "ROBINHOOD_MAINNET"
   | "TON_TESTNET"
   | "TON_MAINNET"
+  | "CANTON_TESTNET"
+  | "CANTON_MAINNET"
   | "CREDITCOIN_MAINNET"
 
 export type ExplorerInfo = {
diff --git a/src/config/web3Providers.ts b/src/config/web3Providers.ts
index 108deab7b9b..395bcca5d78 100644
--- a/src/config/web3Providers.ts
+++ b/src/config/web3Providers.ts
@@ -154,6 +154,8 @@ export const chainToProvider: Record<SupportedChain, () => Provider> = {
   BOTANIX_MAINNET: () => new JsonRpcProvider("https://rpc.botanix.org"),
   APTOS_MAINNET: () => new JsonRpcProvider("https://fullnode.mainnet.aptoslabs.com/v1"),
   APTOS_TESTNET: () => new JsonRpcProvider("https://fullnode.testnet.aptoslabs.com/v1"),
+  CANTON_MAINNET: () => new JsonRpcProvider(),
+  CANTON_TESTNET: () => new JsonRpcProvider(),
   KAIA_MAINNET: () => new JsonRpcProvider("https://public-en.node.kaia.io"),
   KAIA_TESTNET_KAIROS: () => new JsonRpcProvider("https://public-en-kairos.node.kaia.io"),
   TAC_MAINNET: () => new JsonRpcProvider("https://rpc.tac.build"),
diff --git a/src/content/ccip/concepts/canton/explicit-disclosure.mdx b/src/content/ccip/concepts/canton/explicit-disclosure.mdx
new file mode 100644
index 00000000000..0c03e6c89e6
--- /dev/null
+++ b/src/content/ccip/concepts/canton/explicit-disclosure.mdx
@@ -0,0 +1,100 @@
+---
+section: ccip
+date: Last Modified
+title: "Explicit Disclosure API (Canton)"
+metadata:
+  description: "Explicit Disclosure Services for CCIP on Canton: global CCIP API, token pool operator APIs, CNS discovery, and reference EDS deployment."
+  excerpt: "CCIP Canton EDS, explicit disclosure, token pool API, Global CCIP API, CNS discovery, chainlink-canton"
+  datePublished: "2026-06-27"
+  lastModified: "2026-06-27"
+  difficulty: "intermediate"
+  estimatedTime: "10 minutes"
+whatsnext:
+  "Token pools": "/ccip/concepts/canton/token-pools"
+  "BurnMint deployment (Go Live step)": "/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+On Canton, users must be given explicit access to contracts they interact with but are not stakeholders of. Token pool operators run an **Explicit Disclosure Service (EDS)** API that returns these disclosures so users can include them in ledger transactions.
+
+## Global CCIP API
+
+The Global CCIP API is **operated by Chainlink Labs** and provides disclosures for the core CCIP contracts (FeeQuoter, OnRamp, OffRamp, PerPartyRouterFactory, RMNRemote, TokenAdminRegistry, etc.). This API is made available to all users and does not need to be operated by third parties.
+
+| Environment | URL                                   |
+| :---------- | :------------------------------------ |
+| Testnet     | `https://eds.testnet.ccip.chain.link` |
+| Mainnet     | `https://eds.ccip.chain.link`         |
+
+Example — fetch TAR disclosure via batch endpoint:
+
+```shell
+curl --request POST \
+  --url https://eds.testnet.ccip.chain.link/ccip/v1/global/disclosure/batch \
+  --header 'content-type: application/json' \
+  --data '{
+  "addresses": [
+    "tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551"
+  ]
+}'
+```
+
+OpenAPI spec: [`eds-global.yaml`](https://github.com/smartcontractkit/chainlink-canton/blob/main/openapi/src/eds/global/eds-global.yaml) (`postGetExplicitDisclosureBatch` on `/ccip/v1/global/disclosure/batch`).
+
+## External APIs (third-party operated)
+
+Third-party operators of Token Pools, CommitteeVerifiers, and Executors are each responsible for running their own EDS API so that users can obtain the disclosures needed to interact with their contracts. These APIs follow a standardized API definition:
+
+| API                                              | Endpoints                                                                                                                                                                                                                     |
+| :----------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Token Pool**                                   | `POST /ccip/v1/external/tokenPool/{address}/send` — called before sending a message that includes a transfer of the operator's token; returns disclosures for the token pool along with a list of required CommitteeVerifiers |
+|                                                  | `POST /ccip/v1/external/tokenPool/{address}/execute` — called before executing an incoming message that includes a transfer of the operator's token; returns disclosures and inputs for the token pool                        |
+| **CommitteeVerifier API (optional coming soon)** | Provides disclosures and inputs for the CommitteeVerifier contract during send and execute flows                                                                                                                              |
+
+Full API reference: [`openapi/src/eds/README.md`](https://github.com/smartcontractkit/chainlink-canton/blob/main/openapi/src/eds/README.md).
+
+## EDS URL discovery
+
+Users need the token pool operator's EDS URL. Recommended approach:
+
+1. Operator creates a **Canton Name Service (CNS)** entry for their party with key `ccip.chain.link/edsUrls` and a comma-separated list of API URLs.
+2. CCIP SDK/CLI discovers the URL automatically from the pool's `RawInstanceAddress` party ID.
+
+Alternatively, communicate the EDS URL out-of-band via documentation or direct coordination.
+
+## Reference implementation
+
+A reference EDS is available as a [Docker image](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/eds.Dockerfile). It supports BurnMint and LockRelease token pools, default Token Pool / CommitteeVerifier / Executor APIs, and native Canton Token Standard APIs — configured via a single TOML file.
+
+Example config: [`eds/testdata/config.toml`](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/testdata/config.toml).
+
+<Aside type="tip">
+
+Most issuers only need the `token_pool_api` block. Set `type = ""` or omit the block to disable token pool API serving during development.
+
+</Aside>
+
+### Configuration reference
+
+| Field                        | Meaning                                                                                       |
+| :--------------------------- | :-------------------------------------------------------------------------------------------- |
+| `chain_selector`             | Local Canton chain selector (distinct from remote selectors in `ApplyChainUpdates`).          |
+| `[node].url`                 | Participant gRPC Ledger API endpoint. EDS reads the Active Contract Set over this connection. |
+| `[node.auth].type`           | `static`, `insecureStatic`, `clientCredentials`, or `authorizationCode`.                      |
+| `map key / instance_address` | Each pool keyed by instance address hex; map key **must** equal `instance_address`.           |
+| `type`                       | `burnMint` or `lockRelease`.                                                                  |
+| `pool_owner`                 | Pool owner party (should equal `instrumentId.admin`).                                         |
+
+Operators using the provided token pool contracts can run the reference implementation without custom code. **Custom pool implementations** must implement the standardized API endpoints or adapt the reference.
+
+## Operator responsibilities
+
+- **Availability** — EDS must stay reachable; users cannot send or execute token transfers involving your pool if it is down.
+- **TLS** — Terminate TLS at a reverse proxy or load balancer; expose HTTPS publicly.
+- **Participant connectivity** — EDS connects to your Canton participant via gRPC; configure permissions for ACS reads.
+- **Authentication (optional)** — Default is unauthenticated; restrict at the proxy if needed.
+- **CNS registration (recommended)** — Register `ccip.chain.link/edsUrls` for SDK/CLI discovery.
diff --git a/src/content/ccip/concepts/canton/key-concepts.mdx b/src/content/ccip/concepts/canton/key-concepts.mdx
new file mode 100644
index 00000000000..e3e882ffe92
--- /dev/null
+++ b/src/content/ccip/concepts/canton/key-concepts.mdx
@@ -0,0 +1,119 @@
+---
+section: ccip
+date: Last Modified
+title: "Key Concepts (Canton)"
+metadata:
+  description: "Canton Network and CCIP concepts for cross-chain integration: parties, privacy, explicit disclosure, manual execution, fees, and on-ledger components."
+  excerpt: "Canton CCIP key concepts, parties, stakeholders, privacy, PerPartyRouter, Committee Verifier, manual execution, fees, EDS, tooling"
+  datePublished: "2026-07-07"
+  lastModified: "2026-07-07"
+  difficulty: "beginner"
+  estimatedTime: "15 minutes"
+whatsnext:
+  "Manual execution": "/ccip/concepts/canton/manual-execution"
+  "Cross-chain flows": "/ccip/concepts/canton/overview"
+  "Token pools": "/ccip/concepts/canton/token-pools"
+  "Explicit Disclosure API": "/ccip/concepts/canton/explicit-disclosure"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+Read this page before the [flow overview](/ccip/concepts/canton/overview) or the tutorials. It defines Canton-specific terms and CCIP-on-Canton behavior that appear throughout the docs.
+
+## Who this is for
+
+Engineers at enterprises and institutions who need to:
+
+- Send or receive CCIP messages and token transfers on Canton
+- Connect CIP-56 instruments to CCIP token pools
+- Operate token pool disclosure infrastructure
+
+You do not need Chainlink to permission your party to use CCIP — any party can send to supported lanes programmatically once your participant, validator user, and disclosures are configured.
+
+## Canton fundamentals
+
+Canton is a privacy-preserving network for regulated institutions. Smart contracts are written in **Daml** and run on **participant** nodes operated by institutions.
+
+| Term            | Meaning                                                                                                                                     |
+| :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Party**       | An on-ledger identity that owns rights and obligations in contracts. Your `party` in `canton-config.json` is the party your scripts act as. |
+| **User**        | A human or system account that authenticates to a participant and is granted permission to act as one or more parties.                      |
+| **Participant** | A node that hosts contract data for its parties and enforces privacy — it only stores data relevant to those parties.                       |
+| **Signatory**   | A party that owns a contract and must authorize its creation or archival.                                                                   |
+| **Observer**    | A party that can see a contract and its updates but does not own it unless given a specific choice.                                         |
+| **Stakeholder** | Any signatory or observer on a contract — stakeholders can see contract creation and updates.                                               |
+| **Choice**      | An authorized action on a Daml contract (Canton's equivalent of a contract function).                                                       |
+| **DAR**         | A packaged Daml archive deployed to a participant. CCIP and Registry DARs must be present before you can create CCIP contracts.             |
+
+### Privacy and explicit disclosure
+
+Unlike public chains, Canton **compartmentalizes data**: parties only see contracts they are stakeholders on. CCIP core contracts are not visible to arbitrary users by default.
+
+**Explicit disclosure** grants a submitting party temporary visibility into contracts they are not a stakeholder on, so they can exercise choices in a single transaction. Off-ledger **Explicit Disclosure Services (EDS)** return these disclosures before send and execute — see [Explicit Disclosure API](/ccip/concepts/canton/explicit-disclosure).
+
+## Manual execution on Canton
+
+<Aside type="caution" title="No automatic execution on Canton">
+
+When Canton is the **destination**, Chainlink does **not** automatically execute incoming messages. The **receiver** (or a party they authorize via disclosures) must **manually execute** each message after proofs are on the indexer.
+
+</Aside>
+
+This is a core integration requirement on Canton — not an error-recovery path like manual execution on EVM chains. See [Manual Execution (Canton)](/ccip/concepts/canton/manual-execution) for the full workflow and tutorial links.
+
+When Canton is the **source**, remote destination chains may still auto-execute unless you skip execution in your send script.
+
+## Fees on Canton
+
+CCIP fees are quoted and collected by the on-ledger **FeeQuoter** contract as part of the send flow.
+
+| Direction                 | Who pays                   | Typical fee token (testnet starter kit)                                           |
+| :------------------------ | :------------------------- | :-------------------------------------------------------------------------------- |
+| **Canton → remote chain** | Sender party on Canton     | **Amulet** (default) or **LINK** (`--feeToken link`)                              |
+| **Remote chain → Canton** | Sender on the source chain | Native gas token on source (e.g. Sepolia **ETH**) or **LINK** (`--feeToken link`) |
+
+Before sending from Canton, fund your party with the fee token you plan to use. Token transfer demos may also require holdings of the instrument you are bridging (for example LINK on Canton for `canton2any:token`).
+
+Fee rates depend on lane configuration in FeeQuoter. Coordinate with **Chainlink CCIP operations** for production fee tokens and quoting details on your lanes.
+
+## CCIP on-ledger components
+
+Terms you will see in the [overview](/ccip/concepts/canton/overview) and tutorials:
+
+| Component                         | Role                                                                                                                                         |
+| :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
+| **PerPartyRouter**                | Per-party CCIP state (sequence numbers, execution tracking). One router per party; create via `PerPartyRouterFactory` on first use.          |
+| **CCIPSender** / **CCIPReceiver** | Contracts your party uses to send from or execute on Canton.                                                                                 |
+| **Committee Verifier**            | Validates cross-chain proofs. The default verifier is operated by Chainlink NOPs; custom verifiers may be required for some lanes or assets. |
+| **Committee Verifier ticket**     | Returned when forwarding a message to a Committee Verifier during a Canton send.                                                             |
+| **Token pool ticket**             | Issued by the token pool when locking or burning tokens on send.                                                                             |
+| **Token receive ticket**          | Issued by the OffRamp after successful execution; used to claim tokens from the pool.                                                        |
+| **TransferInstruction**           | CIP-56 token transfer object. Receivers **accept** it to take custody after a token message executes.                                        |
+| **Token Admin Registry (TAR)**    | Maps each instrument to its CCIP token pool.                                                                                                 |
+| **Indexer**                       | Aggregates Committee Verifier proofs so clients know when a message is ready to execute.                                                     |
+| **EDS**                           | Off-ledger API that returns explicit disclosures for CCIP and token pool contracts.                                                          |
+
+### Finality modes
+
+Senders set requested finality in the message. Receivers configure `receiverFinalityConfig` on `CCIPReceiver` to allow:
+
+- **FTF** — faster than finality
+- **FCR** — safe confirmation
+- **Default** — standard finality tag for the lane
+
+The receiver configuration must permit the finality level the sender requested.
+
+## Tooling
+
+| Tool                                                                                     | What it is                                                   | When to use it                                                                                            |
+| :--------------------------------------------------------------------------------------- | :----------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------- |
+| [`ccip-tools-ts`](https://github.com/smartcontractkit/ccip-tools-ts)                     | Source repo for **`@chainlink/ccip-sdk`** and **`ccip-cli`** | Library and CLI for production integrations — disclosures, send, execute, proofs                          |
+| [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) | Tutorial scripts and testnet config                          | Learn Canton ↔ Sepolia flows; `cct:*` pool deployment helpers                                             |
+| **`ccip-cli`**                                                                           | CLI in `ccip-tools-ts`                                       | Same underlying SDK as the starter kit — direct ledger submit with `canton-config.json` and JWT/OIDC auth |
+
+The starter kit is a thin wrapper around `@chainlink/ccip-sdk`. Scripts load `canton-config.json`, authenticate to your participant, and call the same send/execute paths documented for `ccip-cli` (without `--wallet`).
+
+**Suggested path:** skim this page → [Getting Started (Canton)](/ccip/getting-started/canton) → [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) → a tutorial matching your direction.
diff --git a/src/content/ccip/concepts/canton/manual-execution.mdx b/src/content/ccip/concepts/canton/manual-execution.mdx
new file mode 100644
index 00000000000..f55f9ddae4b
--- /dev/null
+++ b/src/content/ccip/concepts/canton/manual-execution.mdx
@@ -0,0 +1,123 @@
+---
+section: ccip
+date: Last Modified
+title: "Manual Execution (Canton)"
+metadata:
+  description: "Manual execution on Canton: why incoming CCIP messages are not auto-executed, and how receivers execute messages after indexer verification."
+  excerpt: "Canton CCIP manual execution, any2canton, CCIPReceiver, indexer, EDS, TransferInstruction, destination chain"
+  image: "/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  datePublished: "2026-07-07"
+  lastModified: "2026-07-07"
+  difficulty: "intermediate"
+  estimatedTime: "10 minutes"
+whatsnext:
+  "Canton as Destination tutorials": "/ccip/tutorials/canton/destination"
+  "Cross-chain flows": "/ccip/concepts/canton/overview"
+  "Key concepts": "/ccip/concepts/canton/key-concepts"
+---
+
+import { Aside, ClickToZoom } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+<Aside type="note" title="Prerequisites">
+
+Read [Key Concepts](/ccip/concepts/canton/key-concepts) and the [flow overview](/ccip/concepts/canton/overview) before this page.
+
+</Aside>
+
+On Canton, **manual execution is required** when Canton is the **destination** chain. This is different from EVM-style CCIP, where manual execution is usually a fallback when automatic execution fails.
+
+## Why Canton requires manual execution
+
+Canton enforces **data privacy**: parties only see contracts they are stakeholders on. Incoming messages may involve private receiver contracts, token DARs, and token pool contracts that Chainlink operators cannot access on your participant.
+
+Chainlink does **not** provide automatic execution of receiver contracts on Canton. The **receiver party** (or a party the receiver authorizes via [explicit disclosure](/ccip/concepts/canton/explicit-disclosure)) must execute each message after Committee Verifier proofs are aggregated on the indexer.
+
+## When manual execution applies
+
+| Scenario                  | Execution on Canton                                                                                                                          |
+| :------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Remote chain → Canton** | **Always manual** — receiver runs execute after proofs are ready                                                                             |
+| **Canton → remote chain** | Not applicable on Canton for inbound; destination chain may auto-execute (for example Sepolia via Chainlink NOPs) unless the sender skips it |
+
+Plan every inbound integration for: send on source → wait for verification → **manual execute on Canton**.
+
+## Execution workflow (remote chain → Canton)
+
+<ClickToZoom
+  src="/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  alt="CCIP execute flow when Canton is the destination chain"
+/>
+
+_Figure 1. Execute flow when Canton is the destination (receiving) chain._
+
+### 1. Wait for the message to be ready
+
+1. Track the message in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer) or CCIP API.
+2. Committee Verifier operators (for the default verifier, Chainlink NOPs) validate the source `CCIPMessageSent` event, generate proofs, and submit them to the **indexer**.
+3. Once all required Committee Verifiers have submitted proofs, the message is ready for you to execute on Canton.
+
+### 2. Prepare disclosures and proofs
+
+Before submitting to the ledger, gather:
+
+- **Proofs** from the indexer for the target transaction
+- **Explicit disclosures** from the Global CCIP **EDS** for CCIP contracts
+- Your **`PerPartyRouter`** (or create one via `PerPartyRouterFactory` on first use)
+- For custom Committee Verifiers: disclosures from the verifier's EDS
+- For token transfers: disclosures from the asset's Token Standard Registry and the **token pool operator's EDS**
+
+See [Explicit Disclosure API](/ccip/concepts/canton/explicit-disclosure) for EDS endpoints.
+
+### 3. Execute on Canton
+
+Using the [CCIP CLI](https://github.com/smartcontractkit/ccip-tools-ts/blob/main/ccip-cli/README.md) or [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) `any2canton:manual-exec`, interact with [`CCIPReceiver`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/receiver/daml/CCIP/CCIPReceiver.daml):
+
+1. Deploy and configure a `CCIPReceiver` if needed. Set `receiverFinalityConfig` to match how you handle finality (FTF, FCR, or default — the sender's requested finality must be allowed).
+2. Call the receiver with the message and message proof.
+3. The receiver validates proofs via each Committee Verifier and calls `PerPartyRouter_Execute`.
+4. On success, the OffRamp marks the message executed (preventing double execution).
+
+The SDK **finds or creates** a compatible `CCIPReceiver` on the default path — see [Canton as Destination](/ccip/tutorials/canton/destination) tutorials.
+
+### 4. Token transfers — accept holdings
+
+If the message included a token transfer:
+
+1. The token pool creates a **`TransferInstruction`** to the receiver party.
+2. The receiver party must **accept** the `TransferInstruction` to take custody — this is separate from the CCIP execute step.
+
+For programmable token transfers, your receiver logic runs after tokens are available.
+
+<Aside type="note" title="Which identifier to pass">
+
+The manual-exec scripts accept **either** the source-chain transaction **or** the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) from the send output:
+
+- **Sepolia → Canton** (`any2canton:manual-exec`): Sepolia tx hash (`📜 Source transaction`) **or** the CCIP Message ID
+- **Canton → Sepolia** (`canton2any:manual-exec`): Canton update ID (`📜 Canton transaction` / Lighthouse link) **or** the CCIP Message ID
+
+Passing the **source transaction / update ID** builds the OffRamp and proofs locally from on-chain data (the indexer aggregates Committee Verifier proofs by transaction). Passing the **CCIP Message ID** lets the SDK fetch the OffRamp and verifications from the CCIP API instead. A Sepolia tx hash and a CCIP Message ID share the same `0x`+64-hex shape, so the script resolves the message from whichever matches.
+
+</Aside>
+
+## Tooling
+
+| Tool                        | Execute command (starter kit)                                                            |
+| :-------------------------- | :--------------------------------------------------------------------------------------- |
+| Data-only message           | `npm run any2canton:manual-exec -- <sepoliaTxHash \| messageId>` after `any2canton:data` |
+| Token transfer              | Same after `any2canton:token`                                                            |
+| Programmable token transfer | Same after `any2canton:data-and-token`                                                   |
+
+Scripts use `@chainlink/ccip-sdk` with `canton-config.json` and ledger auth — the same model as `ccip-cli` without `--wallet`.
+
+## Tutorials
+
+Step-by-step walkthroughs:
+
+- [Arbitrary Messaging (destination)](/ccip/tutorials/canton/destination/arbitrary-messaging)
+- [Token Transfers (destination)](/ccip/tutorials/canton/destination/token-transfers)
+- [Programmable Token Transfers (destination)](/ccip/tutorials/canton/destination/programmable-token-transfers)
+
+Complete [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites) before running them.
diff --git a/src/content/ccip/concepts/canton/overview.mdx b/src/content/ccip/concepts/canton/overview.mdx
new file mode 100644
index 00000000000..4aa641f399d
--- /dev/null
+++ b/src/content/ccip/concepts/canton/overview.mdx
@@ -0,0 +1,137 @@
+---
+section: ccip
+date: Last Modified
+title: "CCIP on Canton — Overview"
+metadata:
+  description: "End-to-end CCIP flows on Canton Network: sending and receiving cross-chain messages and token transfers between Canton and other supported chains."
+  excerpt: "CCIP Canton, cross-chain flows, CCIPSender, CCIPReceiver, PerPartyRouter, explicit disclosure, manual execution, enterprise interoperability"
+  image: "/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  datePublished: "2026-06-27"
+  lastModified: "2026-06-27"
+  difficulty: "intermediate"
+  estimatedTime: "15 minutes"
+whatsnext:
+  "Manual execution": "/ccip/concepts/canton/manual-execution"
+  "Key concepts": "/ccip/concepts/canton/key-concepts"
+  "Token pools": "/ccip/concepts/canton/token-pools"
+  "Explicit Disclosure API": "/ccip/concepts/canton/explicit-disclosure"
+  "Registry Issuer Guide": "/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide"
+---
+
+import { Aside, ClickToZoom } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+<Aside type="note">
+
+Examples below may use a public chain (such as Ethereum) illustratively. CCIP supports 85+ chains and can connect Canton to any supported chain family.
+
+</Aside>
+
+<Aside type="caution" title="Manual execution on Canton">
+
+When Canton is the **destination**, messages are **not** auto-executed. The receiver must [manually execute](/ccip/concepts/canton/manual-execution) each message after proofs are on the indexer.
+
+</Aside>
+
+For definitions of parties, stakeholders, tickets, and other terms used below, see [Key Concepts](/ccip/concepts/canton/key-concepts).
+
+The following outlines the end-to-end data journey between a public chain and Canton addresses, including execution responsibilities and the components involved at each step.
+
+## Public chain → Canton
+
+When Canton is the **destination** (receiving) chain.
+
+<ClickToZoom
+  src="/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  alt="CCIP Onchain Canton Destination Chain"
+/>
+
+_Figure 1. Execute flow, on Canton, when Canton is the destination (receiving) chain._
+
+### 1. On the source chain
+
+Using the [CCIP SDK/CLI](https://github.com/smartcontractkit/ccip-tools-ts), the sending user or dApp calls the Router on the source chain, which forwards the message to the chain's OnRamp. The OnRamp:
+
+- Validates the message structure and contents.
+- Forwards the message to all specified CommitteeVerifiers for additional validation if required.
+- For token transfers: forwards the message to the token pool, which locks or burns tokens to be sent.
+- Calculates the message fee and collects payment.
+- Emits a [`CCIPMessageSent`](https://github.com/smartcontractkit/chainlink-ccip/blob/6ea6cc1d3db9c6075133dfc45fc4a8a5d1ca6abf/chains/evm/contracts/onRamp/OnRamp.sol#L58-L67) event containing the message payload.
+
+CommitteeVerifier operators (for the default verifier, Chainlink NOPs) observe the event, validate it, generate proofs, sign with their signer keys, and aggregate proofs to the indexer.
+
+Once all requested CommitteeVerifiers have submitted proofs, the message is ready for the **receiver to execute on Canton** — there is no automatic execution on Canton.
+
+### 2. On Canton
+
+Using the [CCIP API](/ccip/tools-resources/ccip-explorer), the status of messages destined for Canton can be retrieved. When a message is ready to execute, the receiver uses the [CCIP CLI](https://github.com/smartcontractkit/ccip-tools-ts/blob/main/ccip-cli/README.md) to manually execute it. Preparation includes:
+
+- Fetching proofs from the indexer for the target transaction.
+- Querying the CCIP EDS for explicit disclosures of CCIP contracts.
+- Looking up the `PerPartyRouter` (or creating one via `PerPartyRouterFactory` on first use).
+- For custom CommitteeVerifiers: querying the verifier's EDS for disclosures.
+- For token transfers: querying the asset's Token Standard Registry and token pool operator's EDS.
+
+To execute, the user interacts with the [`CCIPReceiver` contract](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/receiver/daml/CCIP/CCIPReceiver.daml):
+
+1. Deploy and configure a `CCIPReceiver`. Set `receiverFinalityConfig` according to how the receiver handles finality. The sender chooses requested finality in the message; the receiver config must allow it (FTF = faster than finality, FCR = safe confirmation, or default finality tag).
+2. Call the receiver with the message and message proof.
+3. The receiver calls each CommitteeVerifier; each verifies its proof and returns validation.
+4. The receiver calls `PerPartyRouter_Execute` with CommitteeVerifier validations:
+   - `PerPartyRouter` forwards to the OffRamp, which verifies all required CommitteeVerifiers have validated.
+   - On success, the OffRamp/TokenPool consumes tickets and, for token transfers, issues a `TokenReceiveTicket`.
+   - `PerPartyRouter` marks the message executed to prevent double execution.
+
+If the message contained a token transfer, the receiver uses the `TokenReceiveTicket` to call the token pool:
+
+1. The token pool verifies the ticket was issued by the CCIP owner and creates an outgoing `TransferInstruction` to the token receiver party.
+2. The receiver party accepts the `TransferInstruction` to gain access to the transferred tokens.
+
+## Canton → Public chain
+
+When Canton is the **source** (sending) chain.
+
+<ClickToZoom
+  src="/images/ccip/concepts/architecture/ccip-canton-source-chain.png"
+  alt="CCIP Onchain Canton Source Chain"
+/>
+
+_Figure 2. Execute flow, on Canton, when Canton is the source (sending) chain._
+
+### 1. On Canton
+
+Before sending, fetch explicit disclosures and prerequisites using the CCIP CLI:
+
+- Query the CCIP EDS for disclosures of CCIP contracts.
+- For custom CommitteeVerifiers: query the verifier's EDS.
+- For token transfers: query the token pool operator's EDS and the asset registry API to create a `TransferInstruction` to the token pool owner party.
+- Retrieve or create the current `PerPartyRouter` via `PerPartyRouterFactory`.
+
+Using the CCIP CLI, create a `CCIPSender` contract and send a message:
+
+- Call each CommitteeVerifier's `CommitteeVerifier_ForwardToVerifier`, returning a `CCVTicket`. Each verifier includes observer parties on the `CCIPMessageSent` event.
+- For token transfers: call the token pool to lock/burn tokens; the pool issues a `TokenPoolTicket`.
+- Call `PerPartyRouter_CCIPSend` with `CCVTicket`(s) and `TokenPoolTicket`(s). `PerPartyRouter` forwards to the OnRamp, which validates tickets and emits `CCIPMessageSent`.
+- CommitteeVerifier operators observe, validate, generate proofs, and submit to the indexer.
+- Once proofs are aggregated, the indexer marks the message ready for destination execution.
+
+The message is written to the destination chain OffRamp by a custom executor or automatically by Chainlink NOPs (default executor).
+
+### 2. On the destination chain
+
+The OffRamp calls the receiving contract's `ccipReceive`. The OffRamp:
+
+- Validates message structure and contents.
+- Forwards to CommitteeVerifiers for signature validation.
+- For token transfers: forwards to the token pool to unlock or mint received tokens.
+
+## Key tools
+
+| Tool                                                                | Role                                                             |
+| :------------------------------------------------------------------ | :--------------------------------------------------------------- |
+| [CCIP CLI / SDK](https://github.com/smartcontractkit/ccip-tools-ts) | Assemble disclosures, build messages, send and execute on Canton |
+| [Global CCIP EDS](https://eds.ccip.chain.link)                      | Disclosures for Chainlink-hosted CCIP contracts                  |
+| [CCIP Explorer](/ccip/tools-resources/ccip-explorer)                | Track message status                                             |
+| Token pool operator EDS                                             | Disclosures for issuer token pools during send/execute           |
diff --git a/src/content/ccip/concepts/canton/token-pools.mdx b/src/content/ccip/concepts/canton/token-pools.mdx
new file mode 100644
index 00000000000..598e99e5e2d
--- /dev/null
+++ b/src/content/ccip/concepts/canton/token-pools.mdx
@@ -0,0 +1,96 @@
+---
+section: ccip
+date: Last Modified
+title: "Token Pools (Canton)"
+metadata:
+  description: "CCIP token pools on Canton: BurnMint and LockRelease pool types, CIP-56 integration, trust model, and Token Admin Registry registration."
+  excerpt: "CCIP Canton token pools, CIP-56, BurnMint, LockRelease, Token Admin Registry, instrument admin, cross-chain tokens"
+  datePublished: "2026-06-27"
+  lastModified: "2026-06-27"
+  difficulty: "intermediate"
+  estimatedTime: "10 minutes"
+whatsnext:
+  "Upgradability": "/ccip/concepts/canton/upgradability"
+  "BurnMint deployment guide": "/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool"
+  "LockRelease deployment guide": "/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool"
+  "Explicit Disclosure API": "/ccip/concepts/canton/explicit-disclosure"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+CCIP supports the [CIP-56 Token Standard](https://github.com/canton-foundation/cips/blob/main/cip-0056/cip-0056.md). Making tokens transferable via CCIP is unpermissioned: the owner of a token or asset can deploy and configure a token pool to allow users to transfer the underlying asset to and from Canton.
+
+A token pool deployment consists of:
+
+- **On-ledger**: Token pool contract and Token Admin Registry (TAR) entry.
+- **Off-ledger**: [Explicit Disclosure Service](/ccip/concepts/canton/explicit-disclosure) for the pool so users can obtain contract disclosures during send and execute flows.
+
+## Token pool types
+
+### BurnMint Token Pool
+
+Designed for tokens whose supply can vary across chains. Requires the optional [`BurnMintFactory`](https://docs.canton.network/sdks-tools/api-reference/splice-daml/splice-api-token-burn-mint-v1/splice-api-token-burnmintv1) interface on the underlying token.
+
+| Direction                 | Behavior                                                                               |
+| :------------------------ | :------------------------------------------------------------------------------------- |
+| **Send (source)**         | Sender tokens are **burned**; supply decreases on the source chain.                    |
+| **Receive (destination)** | New tokens are **minted** for the receiver; supply increases on the destination chain. |
+
+**Characteristics:**
+
+- No pool liquidity required — mints on demand on receive.
+- Underlying token must support `BurnMintFactory`.
+- Pool owner **must** be the instrument admin (`instrumentId.admin == poolOwner`).
+
+[Deploy a BurnMint pool →](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)
+
+### LockRelease Token Pool
+
+Designed for fixed-supply tokens where cross-chain transfers are backed by locked liquidity. Uses the CIP-56 `TransferFactory` interface.
+
+| Direction                 | Behavior                                                                                                         |
+| :------------------------ | :--------------------------------------------------------------------------------------------------------------- |
+| **Send (source)**         | Sender tokens are **locked** (transferred to the pool owner via pre-approval).                                   |
+| **Receive (destination)** | Tokens are **released** from pool holdings to the receiver — immediately or via a pending `TransferInstruction`. |
+
+**Characteristics:**
+
+- Pool must hold sufficient liquidity for inbound releases.
+- Total supply remains constant; tokens move between pool and users.
+- Token must support transfer pre-approvals.
+- Pool owner is not enforced to be instrument admin, but **strongly recommended** (see trust model below).
+- Caller must provide pool holdings via `extraContext` on execute.
+
+[Deploy a LockRelease pool →](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool)
+
+## Token pool owner trust model
+
+<Aside type="caution" title="Trust boundary">
+
+CCIP fully trusts the **token pool owner party**. The pool owner controls remote-chain configuration, rate limits, fees, and how tokens are locked, burned, released, or minted. CCIP is not a stakeholder of the pool contract and delegates all token handling to the owner. CCIP cannot verify on Canton that tokens were actually locked or burned — it only verifies that the pool owner signed the outgoing transfer.
+
+</Aside>
+
+**Recommendations:**
+
+- Use the **same party** for pool owner and instrument admin.
+- **Decentralize** the party across multiple nodes so no single node is a point of failure. See [Digital Asset decentralization docs](https://docs.digitalasset.com/overview/3.5/explanations/canton/decentralization.html#decentralized-parties) and [Canton Foundation validators](https://canton.foundation/validators/).
+
+## Registering on the Token Admin Registry
+
+The Token Admin Registry maps each instrument to a single token pool. Registration is a three-step flow:
+
+1. **Propose an administrator** — Instrument admin or CCIP owner calls `ProposeAdministrator` with a proposed admin party.
+2. **Accept the admin role** — Proposed admin calls `AcceptAdminRole`.
+3. **Set the pool** — Admin calls `SetPool` to link the instrument to the pool.
+
+The admin role can be transferred via `TransferAdminRole` followed by `AcceptAdminRole`.
+
+Deployment guides walk through TAR registration step by step:
+
+- [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)
+- [LockRelease Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool)
+- [Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide) (includes `SetBurnMintFactory` for Registry instruments)
diff --git a/src/content/ccip/concepts/canton/upgradability.mdx b/src/content/ccip/concepts/canton/upgradability.mdx
new file mode 100644
index 00000000000..fd5b9a5f438
--- /dev/null
+++ b/src/content/ccip/concepts/canton/upgradability.mdx
@@ -0,0 +1,74 @@
+---
+section: ccip
+date: Last Modified
+title: "Upgradability (Canton)"
+metadata:
+  description: "How CCIP on Canton evolves: DAR package updates, rollout expectations, and what users and operators need to upgrade."
+  excerpt: "Canton CCIP upgradability, DAR packages, package vetting, token pool updates"
+  datePublished: "2026-07-09"
+  lastModified: "2026-07-10"
+  difficulty: "advanced"
+  estimatedTime: "8 minutes"
+whatsnext:
+  "Token pools": "/ccip/concepts/canton/token-pools"
+  "Cross-chain flows": "/ccip/concepts/canton/overview"
+  "BurnMint deployment guide": "/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool"
+---
+
+import { Aside, ClickToZoom } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+On Canton, CCIP logic ships as **Daml packages** packaged in **DAR** files. Participants load and **vet** packages on their nodes before they can interpret transactions. CCIP evolves by publishing new DAR versions — see the [chainlink-canton](https://github.com/smartcontractkit/chainlink-canton) repository for contract sources.
+
+For participant operations (uploading DARs, vetting, and unvetting packages), see the [Canton Network documentation](https://docs.canton.network/) — for example [Manage Daml packages and archives](https://docs.canton.network/global-synchronizer/production-operations/manage-packages).
+
+## Package structure
+
+CCIP on Canton is organized as a tree of Daml packages with stable **interface** packages at the top, **core** implementations in the middle, and **third-party owned** packages — such as token pools, executors, and Committee Verifier operators — at the bottom.
+
+<ClickToZoom
+  src="/images/ccip/concepts/architecture/ccip-canton-package-dependencies.svg"
+  alt="CCIP Canton package dependency layers: un-upgradeable base, interface packages, core packages, and third-party owned packages"
+/>
+
+_Figure 1. CCIP Canton package dependencies. Downstream packages import upstream packages._
+
+Interface packages are not modified in place. When an implementation package is updated, any **downstream** package that imports it must be rebuilt and released. CCIP minimizes this by keeping extension points behind stable interfaces.
+
+## Upgrading DARs on your participant
+
+When Chainlink CCIP communicates a new version, **every validator that interacts with the updated contracts must upload and vet the new DARs**. In practice:
+
+- **Users** who send or execute CCIP messages must vet new DARs for packages their workflows depend on.
+- **Third-party operators** — token pool owners, Committee Verifier operators, executors, and similar parties — must upgrade when packages they operate are updated.
+
+Typical rollout:
+
+1. Chainlink builds the new DAR and communicates it to affected parties.
+2. Chainlink uploads the DAR on its validators.
+3. After a coordination window, affected parties upload the DAR on their own participants.
+4. Depending on urgency, operators may **unvet** the previous package version so validators still on the old DAR can no longer interpret new transactions.
+
+For low-impact enhancements, step 4 may be skipped — both versions can coexist until participants choose to upgrade.
+
+Upload new DARs on your participant using the process in [Upload a DAR](https://docs.canton.network/global-synchronizer/production-operations/manage-packages#upload-a-dar).
+
+### Token pools
+
+If a new DAR affecting token pools is released, **deploy a new token pool**, register it in the [Token Admin Registry](/ccip/concepts/canton/token-pools#registering-on-the-token-admin-registry), and retire the old pool once traffic has moved.
+
+<Aside type="note" title="No liquidity migration on Canton">
+
+Canton token pools do **not** custody liquidity on-ledger — LockRelease pools use the pool owner's holdings; BurnMint pools mint and burn against instrument supply. As long as there are **no pending cross-chain messages** for the old pool, there is no on-ledger liquidity to migrate. Coordinate the cutover using the [CCIP Explorer](/ccip/tools-resources/ccip-explorer) and complete or execute any in-flight transfers before switching TAR registration to the new pool.
+
+</Aside>
+
+See the [BurnMint](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool) and [LockRelease](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool) deployment guides for pool setup and TAR registration.
+
+## Staying current
+
+- Monitor communications from Chainlink CCIP operations for required DAR versions on your lanes.
+- Confirm your participant has the CCIP DARs your workflows need before sending or executing — see [Key Concepts](/ccip/concepts/canton/key-concepts) and [source prerequisites](/ccip/tutorials/canton/source/prerequisites).
+- Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact) when deployments change.
diff --git a/src/content/ccip/getting-started/canton.mdx b/src/content/ccip/getting-started/canton.mdx
new file mode 100644
index 00000000000..8234e27722c
--- /dev/null
+++ b/src/content/ccip/getting-started/canton.mdx
@@ -0,0 +1,88 @@
+---
+section: ccip
+date: Last Modified
+title: "Getting Started (Canton)"
+metadata:
+  description: "Get started with Chainlink CCIP on Canton Network. Learn key concepts, configure tooling, and run your first cross-chain message or token transfer."
+  excerpt: "Chainlink CCIP, Canton Network, cross-chain interoperability, enterprise blockchain, CIP-56, token pools, institutional tokens"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-07"
+  estimatedTime: "30 minutes"
+whatsnext:
+  "Key concepts": "/ccip/concepts/canton/key-concepts"
+  "Cross-chain flows on Canton": "/ccip/concepts/canton/overview"
+  "Canton as Source prerequisites": "/ccip/tutorials/canton/source/prerequisites"
+---
+
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+import { Aside } from "@components"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+**Connect a Canton party to CCIP and run a cross-chain workflow on testnet.**
+
+In this guide, you will:
+
+1. Learn Canton-specific concepts CCIP relies on ([Key Concepts](/ccip/concepts/canton/key-concepts))
+2. Choose the right tooling ([`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) tutorials vs [`ccip-tools-ts`](https://github.com/smartcontractkit/ccip-tools-ts) SDK/CLI for production)
+3. Complete prerequisites and run your first **Canton ↔ Sepolia** tutorial (send or receive, including **manual execution** when Canton is the destination)
+
+<Aside type="caution" title="Manual execution required on Canton">
+
+When Canton is the **destination**, incoming messages are **not** executed automatically. The **receiver** must [manually execute](/ccip/concepts/canton/manual-execution) each message after proofs are on the indexer.
+
+</Aside>
+
+## Who this is for
+
+Institution and enterprise engineers who need to:
+
+- Bridge **CIP-56** instruments or Registry-issued tokens across CCIP lanes
+- Send arbitrary data or programmable token transfers to or from Canton
+- Operate token pool and Explicit Disclosure Service (EDS) infrastructure for their instruments
+
+No permission from Chainlink is required for your party to send messages on a configured lane — you need participant access, disclosures, and fee-token holdings.
+
+## What you can build
+
+| Goal                                             | Start here                                                                                                       |
+| :----------------------------------------------- | :--------------------------------------------------------------------------------------------------------------- |
+| First testnet send or receive (Canton ↔ Sepolia) | [Canton as Source](/ccip/tutorials/canton/source) or [Canton as Destination](/ccip/tutorials/canton/destination) |
+| Deploy a token pool and register on TAR          | [Cross-Chain Token (CCT)](/ccip/tutorials/canton/cross-chain-tokens)                                             |
+| Issue a Registry token end to end                | [Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide)                         |
+| Understand send/execute flows                    | [Overview](/ccip/concepts/canton/overview)                                                                       |
+| Operate pool EDS                                 | [Explicit Disclosure API](/ccip/concepts/canton/explicit-disclosure)                                             |
+
+## Tooling
+
+| Tool                                                                                                                                         | Role                                                                                                                |
+| :------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------ |
+| [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) / [`ccip-cli`](https://github.com/smartcontractkit/ccip-tools-ts) | Production library and CLI — disclosures, fees, send, execute, proofs                                               |
+| [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton)                                                     | Testnet tutorial scripts (`canton2any:*`, `any2canton:*`, `cct:*`) pre-configured for Canton CCIP testnet ↔ Sepolia |
+
+The starter kit uses the same SDK and ledger submit model as `ccip-cli` with `canton-config.json`. Use the starter kit to learn; use the SDK or CLI directly for your own applications.
+
+## Fees (summary)
+
+- **Sending from Canton:** CCIP fees are paid on-ledger in **Amulet** by default, or **LINK** with `--feeToken link`. See [Key Concepts — Fees](/ccip/concepts/canton/key-concepts#fees-on-canton).
+- **Sending to Canton:** Fees are paid on the **source** chain (Sepolia ETH or LINK in the starter kit).
+
+Fund your party before running tutorials — `npm run check-balance` in the starter kit.
+
+## Quick start (testnet tutorial)
+
+1. Read [Key Concepts](/ccip/concepts/canton/key-concepts) (parties, privacy, manual execution, fees).
+2. Clone and configure the [starter kit](/ccip/tutorials/canton/source/prerequisites) (`party`, ledger URL, validator user, `transferInstructionUrl`).
+3. Pick a direction and tutorial:
+   - **Canton → Sepolia:** [Arbitrary Messaging](/ccip/tutorials/canton/source/arbitrary-messaging), [Token Transfers](/ccip/tutorials/canton/source/token-transfers), or [Programmable Token Transfers](/ccip/tutorials/canton/source/programmable-token-transfers)
+   - **Sepolia → Canton:** [Arbitrary Messaging](/ccip/tutorials/canton/destination/arbitrary-messaging), [Token Transfers](/ccip/tutorials/canton/destination/token-transfers), or [Programmable Token Transfers](/ccip/tutorials/canton/destination/programmable-token-transfers) — each ends with `any2canton:manual-exec`
+
+## Before you begin
+
+Coordinate with **Chainlink CCIP operations** for:
+
+- CCIP owner party ID and hosted contract addresses (Token Admin Registry, FeeQuoter, RMNRemote)
+- Remote chain selectors and lane configuration for your target networks
+- CCIP DAR packages on your participant (typically provisioned by ops)
+
+<CcipCommon callout="talkToExpert" />
diff --git a/src/content/ccip/llms-full.txt b/src/content/ccip/llms-full.txt
index ac35db8761d..c2e5e77ea07 100644
--- a/src/content/ccip/llms-full.txt
+++ b/src/content/ccip/llms-full.txt
@@ -660,6 +660,86 @@ Aptos tutorials can be found [here](/ccip/tutorials/aptos).
 
 ---
 
+# Getting Started (Canton)
+Source: https://docs.chain.link/ccip/getting-started/canton
+Last Updated: 2026-07-07
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+**Connect a Canton party to CCIP and run a cross-chain workflow on testnet.**
+
+In this guide, you will:
+
+1. Learn Canton-specific concepts CCIP relies on ([Key Concepts](/ccip/concepts/canton/key-concepts))
+2. Choose the right tooling ([`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) tutorials vs [`ccip-tools-ts`](https://github.com/smartcontractkit/ccip-tools-ts) SDK/CLI for production)
+3. Complete prerequisites and run your first **Canton ↔ Sepolia** tutorial (send or receive, including **manual execution** when Canton is the destination)
+
+<Aside type="caution" title="Manual execution required on Canton">
+  When Canton is the **destination**, incoming messages are **not** executed automatically. The **receiver** must [manually execute](/ccip/concepts/canton/manual-execution) each message after proofs are on the indexer.
+</Aside>
+
+## Who this is for
+
+Institution and enterprise engineers who need to:
+
+- Bridge **CIP-56** instruments or Registry-issued tokens across CCIP lanes
+- Send arbitrary data or programmable token transfers to or from Canton
+- Operate token pool and Explicit Disclosure Service (EDS) infrastructure for their instruments
+
+No permission from Chainlink is required for your party to send messages on a configured lane — you need participant access, disclosures, and fee-token holdings.
+
+## What you can build
+
+| Goal                                             | Start here                                                                                                       |
+| :----------------------------------------------- | :--------------------------------------------------------------------------------------------------------------- |
+| First testnet send or receive (Canton ↔ Sepolia) | [Canton as Source](/ccip/tutorials/canton/source) or [Canton as Destination](/ccip/tutorials/canton/destination) |
+| Deploy a token pool and register on TAR          | [Cross-Chain Token (CCT)](/ccip/tutorials/canton/cross-chain-tokens)                                             |
+| Issue a Registry token end to end                | [Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide)                         |
+| Understand send/execute flows                    | [Overview](/ccip/concepts/canton/overview)                                                                       |
+| Operate pool EDS                                 | [Explicit Disclosure API](/ccip/concepts/canton/explicit-disclosure)                                             |
+
+## Tooling
+
+| Tool                                                                                                                                         | Role                                                                                                                |
+| :------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------ |
+| [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) / [`ccip-cli`](https://github.com/smartcontractkit/ccip-tools-ts) | Production library and CLI — disclosures, fees, send, execute, proofs                                               |
+| [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton)                                                     | Testnet tutorial scripts (`canton2any:*`, `any2canton:*`, `cct:*`) pre-configured for Canton CCIP testnet ↔ Sepolia |
+
+The starter kit uses the same SDK and ledger submit model as `ccip-cli` with `canton-config.json`. Use the starter kit to learn; use the SDK or CLI directly for your own applications.
+
+## Fees (summary)
+
+- **Sending from Canton:** CCIP fees are paid on-ledger in **Amulet** by default, or **LINK** with `--feeToken link`. See [Key Concepts — Fees](/ccip/concepts/canton/key-concepts#fees-on-canton).
+- **Sending to Canton:** Fees are paid on the **source** chain (Sepolia ETH or LINK in the starter kit).
+
+Fund your party before running tutorials — `npm run check-balance` in the starter kit.
+
+## Quick start (testnet tutorial)
+
+1. Read [Key Concepts](/ccip/concepts/canton/key-concepts) (parties, privacy, manual execution, fees).
+2. Clone and configure the [starter kit](/ccip/tutorials/canton/source/prerequisites) (`party`, ledger URL, validator user, `transferInstructionUrl`).
+3. Pick a direction and tutorial:
+   - **Canton → Sepolia:** [Arbitrary Messaging](/ccip/tutorials/canton/source/arbitrary-messaging), [Token Transfers](/ccip/tutorials/canton/source/token-transfers), or [Programmable Token Transfers](/ccip/tutorials/canton/source/programmable-token-transfers)
+   - **Sepolia → Canton:** [Arbitrary Messaging](/ccip/tutorials/canton/destination/arbitrary-messaging), [Token Transfers](/ccip/tutorials/canton/destination/token-transfers), or [Programmable Token Transfers](/ccip/tutorials/canton/destination/programmable-token-transfers) — each ends with `any2canton:manual-exec`
+
+## Before you begin
+
+Coordinate with **Chainlink CCIP operations** for:
+
+- CCIP owner party ID and hosted contract addresses (Token Admin Registry, FeeQuoter, RMNRemote)
+- Remote chain selectors and lane configuration for your target networks
+- CCIP DAR packages on your participant (typically provisioned by ops)
+
+<Aside type="note" title="Talk to a CCIP expert">
+  If you require technical advice or wish to consult on your project's implementation, please contact a CCIP expert. Our
+  dedicated team is ready to support your projects and ensure their success. For expert guidance, visit the [Chainlink
+  CCIP Contact form](https://chain.link/ccip-contact).
+</Aside>
+
+---
+
 # CCIP Service Limits (EVM)
 Source: https://docs.chain.link/ccip/service-limits/evm
 Last Updated: 2025-05-19
@@ -7121,6 +7201,548 @@ Maintain thorough documentation of multisig operations and provide training for
 
 ---
 
+# Key Concepts (Canton)
+Source: https://docs.chain.link/ccip/concepts/canton/key-concepts
+Last Updated: 2026-07-07
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+Read this page before the [flow overview](/ccip/concepts/canton/overview) or the tutorials. It defines Canton-specific terms and CCIP-on-Canton behavior that appear throughout the docs.
+
+## Who this is for
+
+Engineers at enterprises and institutions who need to:
+
+- Send or receive CCIP messages and token transfers on Canton
+- Connect CIP-56 instruments to CCIP token pools
+- Operate token pool disclosure infrastructure
+
+You do not need Chainlink to permission your party to use CCIP — any party can send to supported lanes programmatically once your participant, validator user, and disclosures are configured.
+
+## Canton fundamentals
+
+Canton is a privacy-preserving network for regulated institutions. Smart contracts are written in **Daml** and run on **participant** nodes operated by institutions.
+
+| Term            | Meaning                                                                                                                                     |
+| :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Party**       | An on-ledger identity that owns rights and obligations in contracts. Your `party` in `canton-config.json` is the party your scripts act as. |
+| **User**        | A human or system account that authenticates to a participant and is granted permission to act as one or more parties.                      |
+| **Participant** | A node that hosts contract data for its parties and enforces privacy — it only stores data relevant to those parties.                       |
+| **Signatory**   | A party that owns a contract and must authorize its creation or archival.                                                                   |
+| **Observer**    | A party that can see a contract and its updates but does not own it unless given a specific choice.                                         |
+| **Stakeholder** | Any signatory or observer on a contract — stakeholders can see contract creation and updates.                                               |
+| **Choice**      | An authorized action on a Daml contract (Canton's equivalent of a contract function).                                                       |
+| **DAR**         | A packaged Daml archive deployed to a participant. CCIP and Registry DARs must be present before you can create CCIP contracts.             |
+
+### Privacy and explicit disclosure
+
+Unlike public chains, Canton **compartmentalizes data**: parties only see contracts they are stakeholders on. CCIP core contracts are not visible to arbitrary users by default.
+
+**Explicit disclosure** grants a submitting party temporary visibility into contracts they are not a stakeholder on, so they can exercise choices in a single transaction. Off-ledger **Explicit Disclosure Services (EDS)** return these disclosures before send and execute — see [Explicit Disclosure API](/ccip/concepts/canton/explicit-disclosure).
+
+## Manual execution on Canton
+
+<Aside type="caution" title="No automatic execution on Canton">
+  When Canton is the **destination**, Chainlink does **not** automatically execute incoming messages. The **receiver** (or a party they authorize via disclosures) must **manually execute** each message after proofs are on the indexer.
+</Aside>
+
+This is a core integration requirement on Canton — not an error-recovery path like manual execution on EVM chains. See [Manual Execution (Canton)](/ccip/concepts/canton/manual-execution) for the full workflow and tutorial links.
+
+When Canton is the **source**, remote destination chains may still auto-execute unless you skip execution in your send script.
+
+## Fees on Canton
+
+CCIP fees are quoted and collected by the on-ledger **FeeQuoter** contract as part of the send flow.
+
+| Direction                 | Who pays                   | Typical fee token (testnet starter kit)                                           |
+| :------------------------ | :------------------------- | :-------------------------------------------------------------------------------- |
+| **Canton → remote chain** | Sender party on Canton     | **Amulet** (default) or **LINK** (`--feeToken link`)                              |
+| **Remote chain → Canton** | Sender on the source chain | Native gas token on source (e.g. Sepolia **ETH**) or **LINK** (`--feeToken link`) |
+
+Before sending from Canton, fund your party with the fee token you plan to use. Token transfer demos may also require holdings of the instrument you are bridging (for example LINK on Canton for `canton2any:token`).
+
+Fee rates depend on lane configuration in FeeQuoter. Coordinate with **Chainlink CCIP operations** for production fee tokens and quoting details on your lanes.
+
+## CCIP on-ledger components
+
+Terms you will see in the [overview](/ccip/concepts/canton/overview) and tutorials:
+
+| Component                         | Role                                                                                                                                         |
+| :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
+| **PerPartyRouter**                | Per-party CCIP state (sequence numbers, execution tracking). One router per party; create via `PerPartyRouterFactory` on first use.          |
+| **CCIPSender** / **CCIPReceiver** | Contracts your party uses to send from or execute on Canton.                                                                                 |
+| **Committee Verifier**            | Validates cross-chain proofs. The default verifier is operated by Chainlink NOPs; custom verifiers may be required for some lanes or assets. |
+| **Committee Verifier ticket**     | Returned when forwarding a message to a Committee Verifier during a Canton send.                                                             |
+| **Token pool ticket**             | Issued by the token pool when locking or burning tokens on send.                                                                             |
+| **Token receive ticket**          | Issued by the OffRamp after successful execution; used to claim tokens from the pool.                                                        |
+| **TransferInstruction**           | CIP-56 token transfer object. Receivers **accept** it to take custody after a token message executes.                                        |
+| **Token Admin Registry (TAR)**    | Maps each instrument to its CCIP token pool.                                                                                                 |
+| **Indexer**                       | Aggregates Committee Verifier proofs so clients know when a message is ready to execute.                                                     |
+| **EDS**                           | Off-ledger API that returns explicit disclosures for CCIP and token pool contracts.                                                          |
+
+### Finality modes
+
+Senders set requested finality in the message. Receivers configure `receiverFinalityConfig` on `CCIPReceiver` to allow:
+
+- **FTF** — faster than finality
+- **FCR** — safe confirmation
+- **Default** — standard finality tag for the lane
+
+The receiver configuration must permit the finality level the sender requested.
+
+## Tooling
+
+| Tool                                                                                     | What it is                                                   | When to use it                                                                                            |
+| :--------------------------------------------------------------------------------------- | :----------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------- |
+| [`ccip-tools-ts`](https://github.com/smartcontractkit/ccip-tools-ts)                     | Source repo for **`@chainlink/ccip-sdk`** and **`ccip-cli`** | Library and CLI for production integrations — disclosures, send, execute, proofs                          |
+| [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) | Tutorial scripts and testnet config                          | Learn Canton ↔ Sepolia flows; `cct:*` pool deployment helpers                                             |
+| **`ccip-cli`**                                                                           | CLI in `ccip-tools-ts`                                       | Same underlying SDK as the starter kit — direct ledger submit with `canton-config.json` and JWT/OIDC auth |
+
+The starter kit is a thin wrapper around `@chainlink/ccip-sdk`. Scripts load `canton-config.json`, authenticate to your participant, and call the same send/execute paths documented for `ccip-cli` (without `--wallet`).
+
+**Suggested path:** skim this page → [Getting Started (Canton)](/ccip/getting-started/canton) → [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) → a tutorial matching your direction.
+
+---
+
+# CCIP on Canton — Overview
+Source: https://docs.chain.link/ccip/concepts/canton/overview
+Last Updated: 2026-06-27
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+<Aside type="note">
+  Examples below may use a public chain (such as Ethereum) illustratively. CCIP supports 85+ chains and can connect Canton to any supported chain family.
+</Aside>
+
+<Aside type="caution" title="Manual execution on Canton">
+  When Canton is the **destination**, messages are **not** auto-executed. The receiver must [manually execute](/ccip/concepts/canton/manual-execution) each message after proofs are on the indexer.
+</Aside>
+
+For definitions of parties, stakeholders, tickets, and other terms used below, see [Key Concepts](/ccip/concepts/canton/key-concepts).
+
+The following outlines the end-to-end data journey between a public chain and Canton addresses, including execution responsibilities and the components involved at each step.
+
+## Public chain → Canton
+
+When Canton is the **destination** (receiving) chain.
+
+*Figure 1. Execute flow, on Canton, when Canton is the destination (receiving) chain.*
+
+### 1. On the source chain
+
+Using the [CCIP SDK/CLI](https://github.com/smartcontractkit/ccip-tools-ts), the sending user or dApp calls the Router on the source chain, which forwards the message to the chain's OnRamp. The OnRamp:
+
+- Validates the message structure and contents.
+- Forwards the message to all specified CommitteeVerifiers for additional validation if required.
+- For token transfers: forwards the message to the token pool, which locks or burns tokens to be sent.
+- Calculates the message fee and collects payment.
+- Emits a [`CCIPMessageSent`](https://github.com/smartcontractkit/chainlink-ccip/blob/6ea6cc1d3db9c6075133dfc45fc4a8a5d1ca6abf/chains/evm/contracts/onRamp/OnRamp.sol#L58-L67) event containing the message payload.
+
+CommitteeVerifier operators (for the default verifier, Chainlink NOPs) observe the event, validate it, generate proofs, sign with their signer keys, and aggregate proofs to the indexer.
+
+Once all requested CommitteeVerifiers have submitted proofs, the message is ready for the **receiver to execute on Canton** — there is no automatic execution on Canton.
+
+### 2. On Canton
+
+Using the [CCIP API](/ccip/tools-resources/ccip-explorer), the status of messages destined for Canton can be retrieved. When a message is ready to execute, the receiver uses the [CCIP CLI](https://github.com/smartcontractkit/ccip-tools-ts/blob/main/ccip-cli/README.md) to manually execute it. Preparation includes:
+
+- Fetching proofs from the indexer for the target transaction.
+- Querying the CCIP EDS for explicit disclosures of CCIP contracts.
+- Looking up the `PerPartyRouter` (or creating one via `PerPartyRouterFactory` on first use).
+- For custom CommitteeVerifiers: querying the verifier's EDS for disclosures.
+- For token transfers: querying the asset's Token Standard Registry and token pool operator's EDS.
+
+To execute, the user interacts with the [`CCIPReceiver` contract](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/receiver/daml/CCIP/CCIPReceiver.daml):
+
+1. Deploy and configure a `CCIPReceiver`. Set `receiverFinalityConfig` according to how the receiver handles finality. The sender chooses requested finality in the message; the receiver config must allow it (FTF = faster than finality, FCR = safe confirmation, or default finality tag).
+2. Call the receiver with the message and message proof.
+3. The receiver calls each CommitteeVerifier; each verifies its proof and returns validation.
+4. The receiver calls `PerPartyRouter_Execute` with CommitteeVerifier validations:
+   - `PerPartyRouter` forwards to the OffRamp, which verifies all required CommitteeVerifiers have validated.
+   - On success, the OffRamp/TokenPool consumes tickets and, for token transfers, issues a `TokenReceiveTicket`.
+   - `PerPartyRouter` marks the message executed to prevent double execution.
+
+If the message contained a token transfer, the receiver uses the `TokenReceiveTicket` to call the token pool:
+
+1. The token pool verifies the ticket was issued by the CCIP owner and creates an outgoing `TransferInstruction` to the token receiver party.
+2. The receiver party accepts the `TransferInstruction` to gain access to the transferred tokens.
+
+## Canton → Public chain
+
+When Canton is the **source** (sending) chain.
+
+*Figure 2. Execute flow, on Canton, when Canton is the source (sending) chain.*
+
+### 1. On Canton
+
+Before sending, fetch explicit disclosures and prerequisites using the CCIP CLI:
+
+- Query the CCIP EDS for disclosures of CCIP contracts.
+- For custom CommitteeVerifiers: query the verifier's EDS.
+- For token transfers: query the token pool operator's EDS and the asset registry API to create a `TransferInstruction` to the token pool owner party.
+- Retrieve or create the current `PerPartyRouter` via `PerPartyRouterFactory`.
+
+Using the CCIP CLI, create a `CCIPSender` contract and send a message:
+
+- Call each CommitteeVerifier's `CommitteeVerifier_ForwardToVerifier`, returning a `CCVTicket`. Each verifier includes observer parties on the `CCIPMessageSent` event.
+- For token transfers: call the token pool to lock/burn tokens; the pool issues a `TokenPoolTicket`.
+- Call `PerPartyRouter_CCIPSend` with `CCVTicket`(s) and `TokenPoolTicket`(s). `PerPartyRouter` forwards to the OnRamp, which validates tickets and emits `CCIPMessageSent`.
+- CommitteeVerifier operators observe, validate, generate proofs, and submit to the indexer.
+- Once proofs are aggregated, the indexer marks the message ready for destination execution.
+
+The message is written to the destination chain OffRamp by a custom executor or automatically by Chainlink NOPs (default executor).
+
+### 2. On the destination chain
+
+The OffRamp calls the receiving contract's `ccipReceive`. The OffRamp:
+
+- Validates message structure and contents.
+- Forwards to CommitteeVerifiers for signature validation.
+- For token transfers: forwards to the token pool to unlock or mint received tokens.
+
+## Key tools
+
+| Tool                                                                | Role                                                             |
+| :------------------------------------------------------------------ | :--------------------------------------------------------------- |
+| [CCIP CLI / SDK](https://github.com/smartcontractkit/ccip-tools-ts) | Assemble disclosures, build messages, send and execute on Canton |
+| [Global CCIP EDS](https://eds.ccip.chain.link)                      | Disclosures for Chainlink-hosted CCIP contracts                  |
+| [CCIP Explorer](/ccip/tools-resources/ccip-explorer)                | Track message status                                             |
+| Token pool operator EDS                                             | Disclosures for issuer token pools during send/execute           |
+
+---
+
+# Manual Execution (Canton)
+Source: https://docs.chain.link/ccip/concepts/canton/manual-execution
+Last Updated: 2026-07-07
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+<Aside type="note" title="Prerequisites">
+  Read [Key Concepts](/ccip/concepts/canton/key-concepts) and the [flow overview](/ccip/concepts/canton/overview) before this page.
+</Aside>
+
+On Canton, **manual execution is required** when Canton is the **destination** chain. This is different from EVM-style CCIP, where manual execution is usually a fallback when automatic execution fails.
+
+## Why Canton requires manual execution
+
+Canton enforces **data privacy**: parties only see contracts they are stakeholders on. Incoming messages may involve private receiver contracts, token DARs, and token pool contracts that Chainlink operators cannot access on your participant.
+
+Chainlink does **not** provide automatic execution of receiver contracts on Canton. The **receiver party** (or a party the receiver authorizes via [explicit disclosure](/ccip/concepts/canton/explicit-disclosure)) must execute each message after Committee Verifier proofs are aggregated on the indexer.
+
+## When manual execution applies
+
+| Scenario                  | Execution on Canton                                                                                                                          |
+| :------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Remote chain → Canton** | **Always manual** — receiver runs execute after proofs are ready                                                                             |
+| **Canton → remote chain** | Not applicable on Canton for inbound; destination chain may auto-execute (for example Sepolia via Chainlink NOPs) unless the sender skips it |
+
+Plan every inbound integration for: send on source → wait for verification → **manual execute on Canton**.
+
+## Execution workflow (remote chain → Canton)
+
+*Figure 1. Execute flow when Canton is the destination (receiving) chain.*
+
+### 1. Wait for the message to be ready
+
+1. Track the message in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer) or CCIP API.
+2. Committee Verifier operators (for the default verifier, Chainlink NOPs) validate the source `CCIPMessageSent` event, generate proofs, and submit them to the **indexer**.
+3. Once all required Committee Verifiers have submitted proofs, the message is ready for you to execute on Canton.
+
+### 2. Prepare disclosures and proofs
+
+Before submitting to the ledger, gather:
+
+- **Proofs** from the indexer for the target transaction
+- **Explicit disclosures** from the Global CCIP **EDS** for CCIP contracts
+- Your **`PerPartyRouter`** (or create one via `PerPartyRouterFactory` on first use)
+- For custom Committee Verifiers: disclosures from the verifier's EDS
+- For token transfers: disclosures from the asset's Token Standard Registry and the **token pool operator's EDS**
+
+See [Explicit Disclosure API](/ccip/concepts/canton/explicit-disclosure) for EDS endpoints.
+
+### 3. Execute on Canton
+
+Using the [CCIP CLI](https://github.com/smartcontractkit/ccip-tools-ts/blob/main/ccip-cli/README.md) or [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) `any2canton:manual-exec`, interact with [`CCIPReceiver`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/receiver/daml/CCIP/CCIPReceiver.daml):
+
+1. Deploy and configure a `CCIPReceiver` if needed. Set `receiverFinalityConfig` to match how you handle finality (FTF, FCR, or default — the sender's requested finality must be allowed).
+2. Call the receiver with the message and message proof.
+3. The receiver validates proofs via each Committee Verifier and calls `PerPartyRouter_Execute`.
+4. On success, the OffRamp marks the message executed (preventing double execution).
+
+The SDK **finds or creates** a compatible `CCIPReceiver` on the default path — see [Canton as Destination](/ccip/tutorials/canton/destination) tutorials.
+
+### 4. Token transfers — accept holdings
+
+If the message included a token transfer:
+
+1. The token pool creates a **`TransferInstruction`** to the receiver party.
+2. The receiver party must **accept** the `TransferInstruction` to take custody — this is separate from the CCIP execute step.
+
+For programmable token transfers, your receiver logic runs after tokens are available.
+
+<Aside type="note" title="Which identifier to pass">
+  The manual-exec scripts accept **either** the source-chain transaction **or** the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) from the send output:
+
+  - **Sepolia → Canton** (`any2canton:manual-exec`): Sepolia tx hash (`📜 Source transaction`) **or** the CCIP Message ID
+  - **Canton → Sepolia** (`canton2any:manual-exec`): Canton update ID (`📜 Canton transaction` / Lighthouse link) **or** the CCIP Message ID
+
+  Passing the **source transaction / update ID** builds the OffRamp and proofs locally from on-chain data (the indexer aggregates Committee Verifier proofs by transaction). Passing the **CCIP Message ID** lets the SDK fetch the OffRamp and verifications from the CCIP API instead. A Sepolia tx hash and a CCIP Message ID share the same `0x`+64-hex shape, so the script resolves the message from whichever matches.
+</Aside>
+
+## Tooling
+
+| Tool                        | Execute command (starter kit)                                                            |
+| :-------------------------- | :--------------------------------------------------------------------------------------- |
+| Data-only message           | `npm run any2canton:manual-exec -- <sepoliaTxHash \| messageId>` after `any2canton:data` |
+| Token transfer              | Same after `any2canton:token`                                                            |
+| Programmable token transfer | Same after `any2canton:data-and-token`                                                   |
+
+Scripts use `@chainlink/ccip-sdk` with `canton-config.json` and ledger auth — the same model as `ccip-cli` without `--wallet`.
+
+## Tutorials
+
+Step-by-step walkthroughs:
+
+- [Arbitrary Messaging (destination)](/ccip/tutorials/canton/destination/arbitrary-messaging)
+- [Token Transfers (destination)](/ccip/tutorials/canton/destination/token-transfers)
+- [Programmable Token Transfers (destination)](/ccip/tutorials/canton/destination/programmable-token-transfers)
+
+Complete [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites) before running them.
+
+---
+
+# Token Pools (Canton)
+Source: https://docs.chain.link/ccip/concepts/canton/token-pools
+Last Updated: 2026-06-27
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+CCIP supports the [CIP-56 Token Standard](https://github.com/canton-foundation/cips/blob/main/cip-0056/cip-0056.md). Making tokens transferable via CCIP is unpermissioned: the owner of a token or asset can deploy and configure a token pool to allow users to transfer the underlying asset to and from Canton.
+
+A token pool deployment consists of:
+
+- **On-ledger**: Token pool contract and Token Admin Registry (TAR) entry.
+- **Off-ledger**: [Explicit Disclosure Service](/ccip/concepts/canton/explicit-disclosure) for the pool so users can obtain contract disclosures during send and execute flows.
+
+## Token pool types
+
+### BurnMint Token Pool
+
+Designed for tokens whose supply can vary across chains. Requires the optional [`BurnMintFactory`](https://docs.canton.network/sdks-tools/api-reference/splice-daml/splice-api-token-burn-mint-v1/splice-api-token-burnmintv1) interface on the underlying token.
+
+| Direction                 | Behavior                                                                               |
+| :------------------------ | :------------------------------------------------------------------------------------- |
+| **Send (source)**         | Sender tokens are **burned**; supply decreases on the source chain.                    |
+| **Receive (destination)** | New tokens are **minted** for the receiver; supply increases on the destination chain. |
+
+**Characteristics:**
+
+- No pool liquidity required — mints on demand on receive.
+- Underlying token must support `BurnMintFactory`.
+- Pool owner **must** be the instrument admin (`instrumentId.admin == poolOwner`).
+
+[Deploy a BurnMint pool →](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)
+
+### LockRelease Token Pool
+
+Designed for fixed-supply tokens where cross-chain transfers are backed by locked liquidity. Uses the CIP-56 `TransferFactory` interface.
+
+| Direction                 | Behavior                                                                                                         |
+| :------------------------ | :--------------------------------------------------------------------------------------------------------------- |
+| **Send (source)**         | Sender tokens are **locked** (transferred to the pool owner via pre-approval).                                   |
+| **Receive (destination)** | Tokens are **released** from pool holdings to the receiver — immediately or via a pending `TransferInstruction`. |
+
+**Characteristics:**
+
+- Pool must hold sufficient liquidity for inbound releases.
+- Total supply remains constant; tokens move between pool and users.
+- Token must support transfer pre-approvals.
+- Pool owner is not enforced to be instrument admin, but **strongly recommended** (see trust model below).
+- Caller must provide pool holdings via `extraContext` on execute.
+
+[Deploy a LockRelease pool →](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool)
+
+## Token pool owner trust model
+
+<Aside type="caution" title="Trust boundary">
+  CCIP fully trusts the **token pool owner party**. The pool owner controls remote-chain configuration, rate limits, fees, and how tokens are locked, burned, released, or minted. CCIP is not a stakeholder of the pool contract and delegates all token handling to the owner. CCIP cannot verify on Canton that tokens were actually locked or burned — it only verifies that the pool owner signed the outgoing transfer.
+</Aside>
+
+**Recommendations:**
+
+- Use the **same party** for pool owner and instrument admin.
+- **Decentralize** the party across multiple nodes so no single node is a point of failure. See [Digital Asset decentralization docs](https://docs.digitalasset.com/overview/3.5/explanations/canton/decentralization.html#decentralized-parties) and [Canton Foundation validators](https://canton.foundation/validators/).
+
+## Registering on the Token Admin Registry
+
+The Token Admin Registry maps each instrument to a single token pool. Registration is a three-step flow:
+
+1. **Propose an administrator** — Instrument admin or CCIP owner calls `ProposeAdministrator` with a proposed admin party.
+2. **Accept the admin role** — Proposed admin calls `AcceptAdminRole`.
+3. **Set the pool** — Admin calls `SetPool` to link the instrument to the pool.
+
+The admin role can be transferred via `TransferAdminRole` followed by `AcceptAdminRole`.
+
+Deployment guides walk through TAR registration step by step:
+
+- [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)
+- [LockRelease Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool)
+- [Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide) (includes `SetBurnMintFactory` for Registry instruments)
+
+---
+
+# Explicit Disclosure API (Canton)
+Source: https://docs.chain.link/ccip/concepts/canton/explicit-disclosure
+Last Updated: 2026-06-27
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+On Canton, users must be given explicit access to contracts they interact with but are not stakeholders of. Token pool operators run an **Explicit Disclosure Service (EDS)** API that returns these disclosures so users can include them in ledger transactions.
+
+## Global CCIP API
+
+The Global CCIP API is **operated by Chainlink Labs** and provides disclosures for the core CCIP contracts (FeeQuoter, OnRamp, OffRamp, PerPartyRouterFactory, RMNRemote, TokenAdminRegistry, etc.). This API is made available to all users and does not need to be operated by third parties.
+
+| Environment | URL                                   |
+| :---------- | :------------------------------------ |
+| Testnet     | `https://eds.testnet.ccip.chain.link` |
+| Mainnet     | `https://eds.ccip.chain.link`         |
+
+Example — fetch TAR disclosure via batch endpoint:
+
+```shell
+curl --request POST \
+  --url https://eds.testnet.ccip.chain.link/ccip/v1/global/disclosure/batch \
+  --header 'content-type: application/json' \
+  --data '{
+  "addresses": [
+    "tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551"
+  ]
+}'
+```
+
+OpenAPI spec: [`eds-global.yaml`](https://github.com/smartcontractkit/chainlink-canton/blob/main/openapi/src/eds/global/eds-global.yaml) (`postGetExplicitDisclosureBatch` on `/ccip/v1/global/disclosure/batch`).
+
+## External APIs (third-party operated)
+
+Third-party operators of Token Pools, CommitteeVerifiers, and Executors are each responsible for running their own EDS API so that users can obtain the disclosures needed to interact with their contracts. These APIs follow a standardized API definition:
+
+| API                                              | Endpoints                                                                                                                                                                                                                     |
+| :----------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Token Pool**                                   | `POST /ccip/v1/external/tokenPool/{address}/send` — called before sending a message that includes a transfer of the operator's token; returns disclosures for the token pool along with a list of required CommitteeVerifiers |
+|                                                  | `POST /ccip/v1/external/tokenPool/{address}/execute` — called before executing an incoming message that includes a transfer of the operator's token; returns disclosures and inputs for the token pool                        |
+| **CommitteeVerifier API (optional coming soon)** | Provides disclosures and inputs for the CommitteeVerifier contract during send and execute flows                                                                                                                              |
+
+Full API reference: [`openapi/src/eds/README.md`](https://github.com/smartcontractkit/chainlink-canton/blob/main/openapi/src/eds/README.md).
+
+## EDS URL discovery
+
+Users need the token pool operator's EDS URL. Recommended approach:
+
+1. Operator creates a **Canton Name Service (CNS)** entry for their party with key `ccip.chain.link/edsUrls` and a comma-separated list of API URLs.
+2. CCIP SDK/CLI discovers the URL automatically from the pool's `RawInstanceAddress` party ID.
+
+Alternatively, communicate the EDS URL out-of-band via documentation or direct coordination.
+
+## Reference implementation
+
+A reference EDS is available as a [Docker image](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/eds.Dockerfile). It supports BurnMint and LockRelease token pools, default Token Pool / CommitteeVerifier / Executor APIs, and native Canton Token Standard APIs — configured via a single TOML file.
+
+Example config: [`eds/testdata/config.toml`](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/testdata/config.toml).
+
+<Aside type="tip">
+  Most issuers only need the `token_pool_api` block. Set `type = ""` or omit the block to disable token pool API serving during development.
+</Aside>
+
+### Configuration reference
+
+| Field                        | Meaning                                                                                       |
+| :--------------------------- | :-------------------------------------------------------------------------------------------- |
+| `chain_selector`             | Local Canton chain selector (distinct from remote selectors in `ApplyChainUpdates`).          |
+| `[node].url`                 | Participant gRPC Ledger API endpoint. EDS reads the Active Contract Set over this connection. |
+| `[node.auth].type`           | `static`, `insecureStatic`, `clientCredentials`, or `authorizationCode`.                      |
+| `map key / instance_address` | Each pool keyed by instance address hex; map key **must** equal `instance_address`.           |
+| `type`                       | `burnMint` or `lockRelease`.                                                                  |
+| `pool_owner`                 | Pool owner party (should equal `instrumentId.admin`).                                         |
+
+Operators using the provided token pool contracts can run the reference implementation without custom code. **Custom pool implementations** must implement the standardized API endpoints or adapt the reference.
+
+## Operator responsibilities
+
+- **Availability** — EDS must stay reachable; users cannot send or execute token transfers involving your pool if it is down.
+- **TLS** — Terminate TLS at a reverse proxy or load balancer; expose HTTPS publicly.
+- **Participant connectivity** — EDS connects to your Canton participant via gRPC; configure permissions for ACS reads.
+- **Authentication (optional)** — Default is unauthenticated; restrict at the proxy if needed.
+- **CNS registration (recommended)** — Register `ccip.chain.link/edsUrls` for SDK/CLI discovery.
+
+---
+
+# Upgradability (Canton)
+Source: https://docs.chain.link/ccip/concepts/canton/upgradability
+Last Updated: 2026-07-10
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+On Canton, CCIP logic ships as **Daml packages** packaged in **DAR** files. Participants load and **vet** packages on their nodes before they can interpret transactions. CCIP evolves by publishing new DAR versions — see the [chainlink-canton](https://github.com/smartcontractkit/chainlink-canton) repository for contract sources.
+
+For participant operations (uploading DARs, vetting, and unvetting packages), see the [Canton Network documentation](https://docs.canton.network/) — for example [Manage Daml packages and archives](https://docs.canton.network/global-synchronizer/production-operations/manage-packages).
+
+## Package structure
+
+CCIP on Canton is organized as a tree of Daml packages with stable **interface** packages at the top, **core** implementations in the middle, and **third-party owned** packages — such as token pools, executors, and Committee Verifier operators — at the bottom.
+
+*Figure 1. CCIP Canton package dependencies. Downstream packages import upstream packages.*
+
+Interface packages are not modified in place. When an implementation package is updated, any **downstream** package that imports it must be rebuilt and released. CCIP minimizes this by keeping extension points behind stable interfaces.
+
+## Upgrading DARs on your participant
+
+When Chainlink CCIP communicates a new version, **every validator that interacts with the updated contracts must upload and vet the new DARs**. In practice:
+
+- **Users** who send or execute CCIP messages must vet new DARs for packages their workflows depend on.
+- **Third-party operators** — token pool owners, Committee Verifier operators, executors, and similar parties — must upgrade when packages they operate are updated.
+
+Typical rollout:
+
+1. Chainlink builds the new DAR and communicates it to affected parties.
+2. Chainlink uploads the DAR on its validators.
+3. After a coordination window, affected parties upload the DAR on their own participants.
+4. Depending on urgency, operators may **unvet** the previous package version so validators still on the old DAR can no longer interpret new transactions.
+
+For low-impact enhancements, step 4 may be skipped — both versions can coexist until participants choose to upgrade.
+
+Upload new DARs on your participant using the process in [Upload a DAR](https://docs.canton.network/global-synchronizer/production-operations/manage-packages#upload-a-dar).
+
+### Token pools
+
+If a new DAR affecting token pools is released, **deploy a new token pool**, register it in the [Token Admin Registry](/ccip/concepts/canton/token-pools#registering-on-the-token-admin-registry), and retire the old pool once traffic has moved.
+
+<Aside type="note" title="No liquidity migration on Canton">
+  Canton token pools do **not** custody liquidity on-ledger — LockRelease pools use the pool owner's holdings; BurnMint pools mint and burn against instrument supply. As long as there are **no pending cross-chain messages** for the old pool, there is no on-ledger liquidity to migrate. Coordinate the cutover using the [CCIP Explorer](/ccip/tools-resources/ccip-explorer) and complete or execute any in-flight transfers before switching TAR registration to the new pool.
+</Aside>
+
+See the [BurnMint](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool) and [LockRelease](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool) deployment guides for pool setup and TAR registration.
+
+## Staying current
+
+- Monitor communications from Chainlink CCIP operations for required DAR versions on your lanes.
+- Confirm your participant has the CCIP DARs your workflows need before sending or executing — see [Key Concepts](/ccip/concepts/canton/key-concepts) and [source prerequisites](/ccip/tutorials/canton/source/prerequisites).
+- Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact) when deployments change.
+
+---
+
 # CCIP Tutorials (EVM)
 Source: https://docs.chain.link/ccip/tutorials/evm
 Last Updated: 2025-05-19
@@ -26223,6 +26845,2153 @@ You can also verify delivery directly on the TON Testnet block explorer:
 
 ---
 
+# Cross-Chain Token (CCT) — Canton
+Source: https://docs.chain.link/ccip/tutorials/canton/cross-chain-tokens
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+Connect a Canton instrument to CCIP by deploying a token pool, registering on the Token Admin Registry (TAR), and enabling a cross-chain lane.
+
+<Aside type="note" title="Testnet only">
+  Starter kit `cct:*` scripts target **Canton testnet** only.
+</Aside>
+
+## Choose your guide
+
+| Guide                                                                                                  | When to use                                                              |
+| :----------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------- |
+| [Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide)               | Issue a new token via Digital Asset Registry and connect CCIP end to end |
+| [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)       | Existing CIP-56 instrument with burn/mint authority                      |
+| [LockRelease Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool) | Fixed-supply instrument with transfer pre-approvals                      |
+
+## Starter kit (`cct:*` scripts)
+
+The [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) automates pool deployment and TAR registration on Canton testnet. Each BurnMint and LockRelease guide includes **Starter kit** and **Manual** paths for those steps.
+
+### Setup
+
+1. Clone and install:
+
+   ```bash filename="Terminal"
+   git clone https://github.com/smartcontractkit/ccip-starter-kit-canton.git
+   cd ccip-starter-kit-canton
+   npm install
+   ```
+
+2. Configure environment — follow [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) for `.env`, `canton-config.json`, and ledger auth.
+
+3. In `config/canton-config.json`, set **`party`** (pool owner/admin) and **`transferInstructionUrl`** (your validator API) — see [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites#understanding-canton-configuration-canton-configjson).
+
+### Scripts
+
+| Script                  | Command                           | What it does                                                                                                                                                                                    |
+| :---------------------- | :-------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Deploy BurnMint pool    | `npm run cct:deploy-burn-mint`    | Creates a [`BurnMintTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/burn-mint-token-pool/daml/CCIP/BurnMintTokenPoolV2.daml) on-ledger          |
+| Deploy LockRelease pool | `npm run cct:deploy-lock-release` | Creates a [`LockReleaseTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/lock-release-token-pool/daml/CCIP/LockReleaseTokenPoolV2.daml) on-ledger |
+| Register on TAR         | `npm run cct:set-token`           | Runs `ProposeAdministrator` → `AcceptAdminRole` → `SetPool` on the Token Admin Registry                                                                                                         |
+
+### Typical flow (BurnMint)
+
+```bash filename="Terminal"
+# 1. Deploy pool
+npm run cct:deploy-burn-mint -- \
+  --instanceId acme-eur-bm-pool \
+  --instrument 'yourParty::1220…::token-id'
+
+# 2. Register on TAR (poolOwner defaults to party in canton-config.json)
+npm run cct:set-token -- \
+  --instrument 'yourParty::1220…::token-id' \
+  --poolInstanceId acme-eur-bm-pool
+
+# 3. Enable lane — manual Ledger API (see guide Step 3)
+```
+
+<Aside type="note" title="Script scope">
+  Starter kit scripts cover **pool creation** and **TAR registration** only. You still configure **rate limiters**, **`ApplyChainUpdates`**, **LockRelease liquidity and pre-approval**, **EDS**, and **lane validation** manually — each guide documents those steps.
+</Aside>
+
+## On-ledger checklist (all guides)
+
+Every CCT deployment ends with the same verification path:
+
+1. Pool deployed at `{instanceId}@{poolOwner}` with the correct `InstrumentId`.
+2. TAR maps the instrument to your pool; your party is token admin.
+3. Lane enabled — three rate limiters plus `ApplyChainUpdates` on the pool.
+4. [Explicit Disclosure Service](/ccip/concepts/canton/explicit-disclosure) running for your pool operator.
+5. Test transfers — see [CCIP on Canton — Overview](/ccip/concepts/canton/overview) and [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+Cross-chain send and receive are validated by Chainlink operations once your token is registered and lanes are configured.
+
+## Prerequisites (all CCT guides)
+
+- [Starter kit setup](/ccip/tutorials/canton/source/prerequisites) for `cct:*` scripts (`.env`, `canton-config.json`, ledger auth)
+- The token pool DAR for your pool type on your participant — [`ccip-burn-mint-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-burn-mint-token-pool-1.0.0.dar) or [`ccip-lock-release-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-lock-release-token-pool-1.0.0.dar) (each bundles its CCIP dependencies — the only DAR you upload).
+- CCIP contract references from Chainlink ops (owner party, TAR, RMNRemote, FeeQuoter) — EDS and indexer URLs are pre-filled in the starter kit
+- A validator user with `can_act_as` rights for your ledger parties
+- Understanding of [token pools](/ccip/concepts/canton/token-pools) and [explicit disclosure](/ccip/concepts/canton/explicit-disclosure)
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Registry Issuer Guide (Canton)
+Source: https://docs.chain.link/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+**Audience:** Engineers who understand Canton and want to issue a token through Digital Asset's Registry utility and connect it to Chainlink CCIP.
+
+**Outcome:** A live Registry instrument on Canton, initial token supply on-ledger, a registrar-owned CCIP BurnMint token pool, and registration in the Token Admin Registry (TAR) so Chainlink can bridge the token once lane configuration is complete.
+
+## 1. Overview
+
+Two on-ledger systems connect at a single **instrument identity**:
+
+| Layer              | Purpose                                                  | Analog                               |
+| :----------------- | :------------------------------------------------------- | :----------------------------------- |
+| **DA Registry**    | Who may issue this token and how much exists on Canton   | Transfer agent + securities registry |
+| **Chainlink CCIP** | How this Canton token enters and exits cross-chain lanes | Bridge + router + token pool         |
+
+**Flow:** Provider onboards Registrar → Registrar creates instrument and mints → Registrar deploys CCIP BurnMint pool → TAR links instrument to pool → Chainlink ops validates cross-chain lanes.
+
+### Critical identity rule
+
+CCIP identifies your token with an **InstrumentId**:
+
+```
+InstrumentId = { admin: <registrar party>, id: "<your instrument string>" }
+```
+
+The `admin` field **must** be your **registrar** party. Wrong party → TAR and pool will not recognize your token.
+
+### What Chainlink ops handles
+
+This guide covers **issuer/registrar** steps only. Chainlink operations must have deployed CCIP core contracts, configured lanes, and provided contract references before you begin. Cross-chain send/receive (`CCIPSender.Send`, `CCIPReceiver.Execute`) are validated separately once your token is registered.
+
+## 2. Parties and roles
+
+| Party           | Organization              | Role in this guide                                                   |
+| :-------------- | :------------------------ | :------------------------------------------------------------------- |
+| **DA Operator** | Digital Asset             | Accepts Provider onboarding; Operator Backend for context/disclosure |
+| **Provider**    | Token program owner (you) | Onboards registrars; credential requirements                         |
+| **Registrar**   | Transfer agent / treasury | Creates instrument, mints, owns CCIP pool, TAR admin                 |
+| **Issuer**      | Mint requester (optional) | Requests mint when credentials apply                                 |
+| **Holder**      | Investor / end user       | Holds balances — no Registry service onboarding required             |
+| **CCIP owner**  | Chainlink                 | Owns TAR, OnRamp, OffRamp, shared CCIP infrastructure                |
+
+**Recommended:** three parties under your org — Provider, Registrar, Holder — plus Chainlink's CCIP owner on the participant.
+
+Registry onboarding: [DA Registry onboarding guide](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/onboarding-offboarding.html).
+
+## 3. Prerequisites
+
+### 3.1 Values from Chainlink ops
+
+| Value                               | Used for                              |
+| :---------------------------------- | :------------------------------------ |
+| CCIP owner party ID                 | TAR `ProposeAdministrator`            |
+| TokenAdminRegistry contract ID      | TAR exercises                         |
+| RMNRemote / FeeQuoter addresses     | Pool dependencies                     |
+| Remote chain selector               | Pool `RemoteChainConfig`              |
+| Remote pool / token addresses (hex) | Pool lane config                      |
+| EDS and indexer URLs                | Disclosures and proofs for CCIP lanes |
+
+### 3.2 Values from your participant operator
+
+| Value                            | Used for                                                                                      |
+| :------------------------------- | :-------------------------------------------------------------------------------------------- |
+| Ledger JSON API URL              | All ledger submissions                                                                        |
+| Validator user with `can_act_as` | Acts on behalf of Provider, Registrar, optional Issuer/Holder — do not use shared admin users |
+| DA Operator party ID             | Registry onboarding                                                                           |
+
+### 3.3 Values you choose
+
+| Value                     | Guidance                                  |
+| :------------------------ | :---------------------------------------- |
+| Instrument ID             | Short uppercase, e.g. `ACME-USD`          |
+| Pool instance ID          | e.g. `acme-usd-ccip-pool`                 |
+| Rate limiter instance IDs | Inbound default, inbound custom, outbound |
+| Initial mint amount       | e.g. `1000000.0`                          |
+
+### 3.4 Environment requirements
+
+Devnet, testnet, and mainnet are **provisioned by operators**. Issuers do **not** upload DAR packages.
+
+| Responsibility                   | Provider                  | What you get                                |
+| :------------------------------- | :------------------------ | :------------------------------------------ |
+| Registry utility DARs (≥ 0.12.5) | Participant / DA operator | Registry template code on-ledger            |
+| CCIP DAR packages                | Chainlink ops             | TAR, pools, OnRamp, OffRamp templates       |
+| Registry choice context          | DA Operator Backend       | `extraArgs.context`, `disclosedContracts`   |
+| CCIP choice context              | CCIP EDS                  | Disclosures for TAR, pool, router exercises |
+
+**DARs vs disclosures:** DARs must exist before contracts can be created (infrastructure). Disclosures are fetched at request time for contracts your party is not a stakeholder on — include them in JSON API submissions.
+
+### 3.5 Optional tooling — `canton-registry-kit`
+
+Chainlink provides a CLI automating many Registry and TAR steps on devnet. Every automated step maps to an on-ledger exercise documented below.
+
+Example `registry-kit.toml`:
+
+```toml
+network = "devnet-cv1"
+
+[ledger]
+json_api_url = "https://<your-participant>/api/json"
+grpc_ledger_api_url = "<your-participant>:443"
+admin_api_url = "<your-participant>:443"
+user_id = "your-ledger-user-id"
+synchronizer_id = "global-domain::1220..."
+
+[ledger.auth]
+type = "authorizationCode"
+auth_url = "https://your-idp/oauth2/default"
+client_id = "your-oauth-client-id"
+
+[parties]
+operator = "operator-party::1220..."
+provider = "provider-party::1220..."
+registrar = "registrar-party::1220..."
+
+[ccip]
+token_admin_registry_cid = "00..."
+ccip_party = "ccip-owner-party::1220..."
+burn_mint_pool_instance_id = "your-pool-instance-id"
+
+[operator_backend]
+base_url = "https://api.utilities.digitalasset-dev.com/api/utilities"
+```
+
+Global flags: `canton-registry-kit --config registry-kit.toml [--state registry-kit.state.json]`
+
+## 4. End-to-end workflow
+
+| Phase                   | Steps | Actor                    |
+| :---------------------- | :---- | :----------------------- |
+| A — Registry onboarding | 1–6   | Provider (+ DA Operator) |
+| B — Instrument and mint | 7–9   | Registrar                |
+| C — CCIP pool deploy    | 10–13 | Registrar (pool owner)   |
+| D — TAR registration    | 14–17 | CCIP owner + Registrar   |
+| E — Verification        | 18    | Registrar                |
+
+Hand off to Chainlink ops for lane testing after Phase E.
+
+## 5. Phase A — Registry onboarding
+
+Request/accept workflow on-ledger. UI walkthrough: [DA issuance onboarding tutorial](https://docs.digitalasset.com/utilities/mainnet/tutorials/issuance/1-onboarding.html).
+
+### Step 1 — Verify environment
+
+```shell
+canton-registry-kit onboarding check-packages
+```
+
+If packages missing, contact participant operator — do not upload DARs unless you operate the validator.
+
+### Step 2 — Request Provider service
+
+| Field     | Value                                                |
+| :-------- | :--------------------------------------------------- |
+| Template  | `ProviderServiceRequest`                             |
+| Create as | Provider                                             |
+| Fields    | `operator` = DA Operator, `provider` = your Provider |
+
+CLI: `canton-registry-kit onboarding request-provider-service`
+
+### Step 3 — Wait for Provider acceptance
+
+DA Operator exercises `ProviderServiceRequest_Accept` → creates `ProviderService`.
+
+CLI: `canton-registry-kit onboarding wait-provider-service --timeout 15m`
+
+### Step 4 — Create Provider configuration
+
+Choice: `ProviderService_CreateProviderConfiguration` (Provider). Use empty `registrarRequirements` / `holderRequirements` for simplest path.
+
+### Step 5 — Request Registrar service
+
+Template: `RegistrarServiceRequest` (Provider). Set `createAllocationFactory = true`, `createTransferRule = true`.
+
+The `AllocationFactory` implements Splice `BurnMintFactory` — CCIP uses it for burn/mint on Registry holdings.
+
+### Step 6 — Accept Registrar service
+
+Choice: `ProviderService_AcceptRegistrarServiceRequest` → creates `RegistrarService`, **`AllocationFactory`**, `TransferRule`.
+
+CLI (Steps 4–6): `canton-registry-kit onboarding onboard-registrar`
+
+**Record:** `RegistrarService`, `AllocationFactory`, `TransferRule` CIDs.
+
+Inspect: `canton-registry-kit onboarding discover-registry-factories`
+
+## 6. Phase B — Create instrument and mint
+
+Registry **0.12.5+** uses AllocationFactory two-step mint (`RequestMint` → `Accept`).
+
+### Step 7 — Create instrument
+
+Choice: `RegistrarService_CreateInstrumentConfiguration` (Registrar). `instrumentId` e.g. `ACME-USD`.
+
+Your CCIP InstrumentId: `{ admin: <registrar>, id: "ACME-USD" }`
+
+CLI: `canton-registry-kit issuer create-instrument ACME-USD`
+
+### Step 8 — Request mint
+
+Choice: `AllocationFactory_RequestMint`. Fetch Operator Backend context first:
+
+```
+POST {operator_backend}/v0/registry/mint/v0/request
+Body: { "holder": "<holder>", "instrumentId": { "admin": "<registrar>", "id": "ACME-USD" } }
+```
+
+Include `choiceContextData` and `disclosedContracts` in ledger submission.
+
+CLI: `canton-registry-kit issuer mint --amount 1000000.0 --holder <holder-party>`
+
+### Step 9 — Accept mint
+
+Choice: `MintRequest_Accept` with Operator Backend context:
+
+```
+POST {operator_backend}/v0/registry/mint/v0/request/{mintRequestCid}/choice-contexts/accept
+```
+
+CLI: `canton-registry-kit issuer accept-mint`
+
+Verify: `canton-registry-kit issuer query-supply`
+
+## 7. Phase C — Deploy CCIP token pool
+
+Deploy rate limiters first, then the BurnMint pool. For **pool creation** on Canton testnet, you can use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) (`cct:deploy-burn-mint`) or submit Ledger API commands directly — see [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool).
+
+### Steps 10–12 — Rate limiters
+
+Deploy three [`RateLimiter`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/rate-limiter/daml/CCIP/RateLimiterV2.daml) contracts:
+
+- Inbound, `mode = DefaultFinality`
+- Inbound, `mode = CustomFinality`
+- Outbound
+
+### Step 13 — Deploy BurnMintTokenPool
+
+| Field                          | Value                                  |
+| :----------------------------- | :------------------------------------- |
+| `instanceId`                   | e.g. `acme-usd-ccip-pool`              |
+| `poolOwner`                    | Registrar                              |
+| `ccipOwner`                    | From Chainlink ops                     |
+| `instrumentId`                 | `{ admin: registrar, id: "ACME-USD" }` |
+| `decimals`                     | `10`                                   |
+| `deps.*`                       | TAR, RMNRemote, FeeQuoter bindings     |
+| `remoteChainConfigs[selector]` | Remote pool/token addresses from ops   |
+
+Record pool address `{poolInstanceId}@{registrarParty}` and all rate limiter CIDs.
+
+**Starter kit (testnet):**
+
+```bash filename="Terminal"
+npm run cct:deploy-burn-mint -- \
+  --instanceId acme-usd-ccip-pool \
+  --instrument 'registrarParty::1220…::ACME-USD' \
+  --poolOwner 'registrarParty::1220…'
+```
+
+Full field reference and manual Ledger API path: [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool).
+
+## 8. Phase D — Register in Token Admin Registry
+
+### Steps 14–16 — Propose, accept, set pool
+
+| Step | Choice                 | Act as     |
+| :--- | :--------------------- | :--------- |
+| 14   | `ProposeAdministrator` | CCIP owner |
+| 15   | `AcceptAdminRole`      | Registrar  |
+| 16   | `SetPool`              | Registrar  |
+
+Steps 15–16 require TAR disclosed to registrar (CCIP EDS or starter kit).
+
+**Starter kit (testnet):**
+
+```bash filename="Terminal"
+npm run cct:set-token -- \
+  --instrument 'registrarParty::1220…::ACME-USD' \
+  --poolInstanceId acme-usd-ccip-pool \
+  --poolOwner 'registrarParty::1220…' \
+  --proposeCaller 'ccipOwner::1220…'
+```
+
+**Registry kit alternative:** `canton-registry-kit operator link-token-to-pool`
+
+### Step 17 — SetBurnMintFactory (required)
+
+**Mandatory** for Registry tokens — links TAR to your `AllocationFactory` from Step 6.
+
+| Field             | Value                                      |
+| :---------------- | :----------------------------------------- |
+| Choice            | `SetBurnMintFactory` on TokenAdminRegistry |
+| Act as            | Registrar                                  |
+| `burnMintFactory` | **AllocationFactory CID** from Step 6      |
+
+Without this, cross-chain transfers fail at execution. CCIP EDS assembles Registry-specific pool context at runtime.
+
+Reference: [DA burn-mint how-to](https://docs.digitalasset.com/utilities/mainnet/how-tos/registry/burn-mint/burn-mint.html).
+
+## 9. Phase E — Verification
+
+```shell
+canton-registry-kit operator validate
+```
+
+| Check               | How                                                            |
+| :------------------ | :------------------------------------------------------------- |
+| Instrument identity | `InstrumentId.admin` = registrar; `id` matches Registry config |
+| Holdings            | Active `Holding`(s); supply matches mint                       |
+| TAR mapping         | `TokenConfig` references your pool and registrar as admin      |
+| Factory link        | `TokenConfig.burnMintFactory` = AllocationFactory CID          |
+| Pool active         | `BurnMintTokenPool` at `{poolInstanceId}@{registrarParty}`     |
+
+## 10. CLI command reference
+
+All commands: `--config registry-kit.toml [--state registry-kit.state.json]`
+
+### Onboarding
+
+| Command                                  | Description                                                  |
+| :--------------------------------------- | :----------------------------------------------------------- |
+| `onboarding check-packages`              | Verify Registry DARs (read-only)                             |
+| `onboarding request-provider-service`    | Submit ProviderServiceRequest                                |
+| `onboarding wait-provider-service`       | Poll until DA accepts                                        |
+| `onboarding onboard-registrar`           | ProviderConfiguration + RegistrarService + AllocationFactory |
+| `onboarding discover-registry-factories` | List Registry contracts for registrar                        |
+
+### Issuer
+
+| Command                                       | Description                      |
+| :-------------------------------------------- | :------------------------------- |
+| `issuer create-instrument <ID>`               | Create InstrumentConfiguration   |
+| `issuer mint --amount <N> [--holder <party>]` | RequestMint via Operator Backend |
+| `issuer accept-mint`                          | AcceptMint                       |
+| `issuer query-supply`                         | Sum Holding balances             |
+
+### Operator (CCIP linking)
+
+| Command                       | Description                                      |
+| :---------------------------- | :----------------------------------------------- |
+| `operator link-token-to-pool` | ProposeAdministrator → AcceptAdminRole → SetPool |
+| `operator validate`           | Read-only TAR and instrument checks              |
+
+### CLI gaps (Ledger API only)
+
+- Deploy RateLimiter contracts
+- Deploy BurnMintTokenPool
+- `SetBurnMintFactory`
+
+## 11. Troubleshooting
+
+| Symptom                      | Cause                             | Resolution                                                                                                                                                 |
+| :--------------------------- | :-------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mint credential error        | Missing issuer credentials        | Issue per [DA credential docs](https://docs.digitalasset.com/utilities/mainnet/overview/credential-user-guide/introduction.html) or use empty requirements |
+| Bridge fails after SetPool   | `SetBurnMintFactory` not called   | Exercise Step 17 with AllocationFactory CID                                                                                                                |
+| Pool doesn't recognize token | Wrong `InstrumentId.admin`        | Must be registrar, not Provider or CCIP owner                                                                                                              |
+| Registry choice fails        | Missing Operator Backend context  | Call Operator Backend before submission                                                                                                                    |
+| Missing utility packages     | Participant not provisioned       | Contact operator                                                                                                                                           |
+| TAR exercise fails           | TAR not disclosed                 | Use CCIP EDS or `link-token-to-pool`                                                                                                                       |
+| 403 from Ledger API          | User lacks `can_act_as` for party | Use a validator user scoped to your parties                                                                                                                |
+
+## 12. Glossary
+
+| Term                   | Definition                                               |
+| :--------------------- | :------------------------------------------------------- |
+| **InstrumentId**       | CCIP token ID: `{ admin: party, id: string }`            |
+| **Holding**            | Registry balance record for an instrument                |
+| **AllocationFactory**  | Registry factory implementing Splice `BurnMintFactory`   |
+| **TAR**                | TokenAdminRegistry — maps instrument → pool + admin      |
+| **EDS**                | Chainlink Execution Disclosure Service                   |
+| **Disclosed contract** | Contract blob in submission for non-stakeholder exercise |
+
+## 13. Further reading
+
+| Topic                      | Link                                                                                                                  |
+| :------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
+| Registry introduction      | [Registry user guide](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/introduction.html) |
+| Token Standard integration | [Token Standard](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/token-standard.html)    |
+| Issuance tutorial          | [Issuance onboarding](https://docs.digitalasset.com/utilities/mainnet/tutorials/issuance/1-onboarding.html)           |
+| Utility DAR versions       | [DAR versions](https://docs.digitalasset.com/utilities/mainnet/reference/dar-versions/dar-versions.html)              |
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# BurnMint Token Pool Deployment (Canton)
+Source: https://docs.chain.link/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+Deploy a **BurnMint** token pool on Canton, register it on the Token Admin Registry (TAR), and enable a cross-chain lane. Use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) for pool deployment and TAR registration, or submit Ledger API commands directly.
+
+This guide assumes you already have a token instrument live on Canton with supply minted on-ledger — for example a Registry instrument from Digital Asset's [Registry utility](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/index.html), or any instrument supporting CIP-56 with the `BurnMintFactory` interface.
+
+**Scope:** On-ledger pool connection — deploy, TAR registration, and lane enablement. Does not cover [EDS setup](/ccip/concepts/canton/explicit-disclosure) or end-to-end transfer tests.
+
+<Aside type="note" title="Testnet only">
+  Starter kit `cct:*` scripts target **Canton testnet** only.
+</Aside>
+
+## Prerequisites
+
+- **Instrument (token managed on Canton Ledger)** with known `InstrumentId = { admin, id }`. The admin party must be the same party that will own the token pool.
+- **Burn/mint authority** — `instrumentId.admin == poolOwner` (enforced by the BurnMint template and by the starter kit).
+- **BurnMint token pool DAR** on your participant — [`ccip-burn-mint-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-burn-mint-token-pool-1.0.0.dar) (bundles its CCIP dependencies — the only DAR you upload).
+- **CCIP contract references** from Chainlink ops: CCIP owner party, Token Admin Registry, RMNRemote, FeeQuoter.
+- **Starter kit setup** (if using `cct:*` scripts) — complete [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) and the [CCT overview](/ccip/tutorials/canton/cross-chain-tokens#starter-kit-cct-scripts).
+
+<Aside type="caution" title="Pool owner trust">
+  CCIP fully trusts the pool owner party. Whoever owns the pool controls remote-chain configuration, rate limits, fees, and token handling. We strongly recommend pool owner and instrument admin be the same party, decentralized across multiple nodes.
+</Aside>
+
+## Deployment overview
+
+| Step | Action                     | Starter kit            | Manual                              |
+| :--- | :------------------------- | :--------------------- | :---------------------------------- |
+| 1    | Deploy `BurnMintTokenPool` | `cct:deploy-burn-mint` | Ledger API `CreateCommand`          |
+| 2    | Register on TAR            | `cct:set-token`        | TAR choices via Ledger API          |
+| 3    | Enable lane                | —                      | Rate limiters + `ApplyChainUpdates` |
+| 4    | Go live                    | —                      | EDS + verification                  |
+
+## Step 1 — Deploy the BurnMint Token Pool
+
+Create one [`BurnMintTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/burn-mint-token-pool/daml/CCIP/BurnMintTokenPoolV2.daml). `poolOwner` + `instanceId` uniquely identifies the pool. Signatory: `poolOwner`.
+
+### Transfer-fee fields
+
+When setting `tokenTransferFeeConfigs` (map keyed by destination chain selector):
+
+| Field               | Meaning                                                 |
+| :------------------ | :------------------------------------------------------ |
+| `isEnabled`         | Must be `true` to apply the config                      |
+| `feeUSDCents`       | Flat fee in USD cents (non-negative)                    |
+| `destGasOverhead`   | Gas for destination execution (> 0 when set via choice) |
+| `destBytesOverhead` | Data-availability bytes overhead (≥ 32)                 |
+| `feeBps`            | Proportional fee in basis points (\< 10000)             |
+
+### CCIP hosted addresses
+
+| Field                     | Testnet                                                                                                    | Mainnet                                                                                                                |
+| :------------------------ | :--------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
+| Token Admin Registry      | `tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551` | Contact the [CCIP team](https://chain.link/ccip-contact) for the Token Admin Registry address to register a token pool |
+| RMNRemote                 | `rmn_remote-nzvtd@rmnOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `rmn_remote-mnprd@rmnOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| FeeQuoter                 | `feequoter-scxln@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `feequoter-fpxih@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| CCIP owner party          | `ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`                          | `ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                                      |
+| Global EDS                | `https://eds.testnet.ccip.chain.link`                                                                      | `https://eds.ccip.chain.link`                                                                                          |
+| Indexer                   | `https://indexer-1.testnet.ccip.chain.link`                                                                | Primary: `https://indexer-1.ccip.chain.link` · Backup: `https://indexer-2.ccip.chain.link`                             |
+| Canton chain selector     | `9268731218649498074`                                                                                      | `2308837218439511688`                                                                                                  |
+| Default CommitteeVerifier | `committeeverifier-tqkny@ccvOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`   | `committeeverifier-mnprd@ccvOwner::122096accf0a84fc7d80d5fce5ea3135317a03eb22e62e0d8cdd7548865f984f11ff`               |
+
+## Step 2 — Register on the Token Admin Registry
+
+TAR maps each instrument to a single token pool. Registration: **propose → accept → set pool**.
+
+## Step 3 — Enable a lane
+
+Lane enablement is **not** automated by the starter kit. Deploy rate limiters and call `ApplyChainUpdates` on your pool via the Ledger API.
+
+### 1. Deploy three rate limiters
+
+Each lane requires [`RateLimiter`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/rate-limiter/daml/CCIP/RateLimiterV2.daml) contracts (for testing, deploy disabled with zero capacity/rate):
+
+- **Inbound (default finality)**
+- **Inbound (custom finality)**
+- **Outbound**
+
+Created by `poolOwner` with matching `poolInstanceId`, `poolOwner`, and `remoteChainSelector`.
+
+### 2. Apply the chain update
+
+Call [`ApplyChainUpdates`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/burn-mint-token-pool/daml/CCIP/BurnMintTokenPoolV2.daml) on the pool:
+
+| ChainUpdate field                            | Guidance                                                                   |
+| :------------------------------------------- | :------------------------------------------------------------------------- |
+| `remoteChainSelector`                        | Destination chain selector — see [CCIP Directory](/ccip/directory/testnet) |
+| `remotePools`                                | Remote token pool address(es)                                              |
+| `remoteTokenAddress`                         | Remote token address                                                       |
+| `inboundCCVs` / `outboundCCVs`               | Default CommitteeVerifier (testnet address above) unless custom            |
+| `finalityConfig`                             | `WaitForFinality` for default finalized source tx                          |
+| `inboundRateLimiter`                         | Inbound default limiter CID                                                |
+| `inboundCustomBlockConfirmationsRateLimiter` | Inbound custom limiter CID                                                 |
+| `outboundRateLimiter`                        | Outbound limiter CID                                                       |
+
+Once applied, the on-ledger lane is complete.
+
+## Step 4 — Go live
+
+### Verification checklist
+
+1. `InstrumentId.admin` equals pool owner.
+2. TAR maps your instrument to your pool with your party as admin.
+3. Pool exists at `{instanceId}@{poolOwner}` with matching `InstrumentId`.
+4. Lane rate limiters are in place.
+
+### Stand up EDS for your pool
+
+Users need [explicit disclosures](/ccip/concepts/canton/explicit-disclosure) for your pool to send and execute transfers. The [reference EDS Docker image](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/eds.Dockerfile) supports BurnMint out of the box.
+
+### Test transactions
+
+See [CCIP on Canton — Overview](/ccip/concepts/canton/overview) for user flows. Track messages in [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+For Registry-issued tokens, also complete [`SetBurnMintFactory`](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide) with your `AllocationFactory` contract ID.
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# LockRelease Token Pool Deployment (Canton)
+Source: https://docs.chain.link/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+Deploy a **LockRelease** token pool on Canton, fund pool-owner liquidity, register on the Token Admin Registry (TAR), and enable a cross-chain lane. Use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) for pool deployment and TAR registration, or submit Ledger API commands directly.
+
+This guide assumes you have a token instrument live on Canton with supply minted on-ledger, supporting the CIP-56 `TransferFactory` interface and transfer pre-approvals.
+
+**LockRelease** is for **fixed total supply** tokens where cross-chain transfers are backed by locked liquidity — not mint/burn. On send, tokens lock to the pool owner; on receive, the pool releases from its holdings.
+
+**Scope:** Deploy pool, fund liquidity, register on TAR, enable a lane. Excludes [EDS setup](/ccip/concepts/canton/explicit-disclosure) and end-to-end transfer tests.
+
+<Aside type="note" title="Testnet only">
+  Starter kit `cct:*` scripts target **Canton testnet** only.
+</Aside>
+
+## Prerequisites
+
+- **Instrument (token managed on Canton Ledger)** with known `InstrumentId = { admin, id }` supporting `TransferFactory` and pre-approvals.
+- Token liquidity held by the pool owner party for expected release volume.
+- **LockRelease token pool DAR** on your participant — [`ccip-lock-release-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-lock-release-token-pool-1.0.0.dar) (bundles its CCIP dependencies — the only DAR you upload).
+- CCIP contract references from Chainlink ops.
+- **Starter kit setup** (if using `cct:*` scripts) — complete [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) and the [CCT overview](/ccip/tutorials/canton/cross-chain-tokens#starter-kit-cct-scripts).
+
+<Aside type="caution" title="Pool owner trust">
+  CCIP fully trusts the pool owner. Strongly recommend pool owner equals instrument admin, decentralized across nodes.
+</Aside>
+
+## Deployment overview
+
+| Step | Action                           | Starter kit               | Manual                              |
+| :--- | :------------------------------- | :------------------------ | :---------------------------------- |
+| 1    | Deploy `LockReleaseTokenPool`    | `cct:deploy-lock-release` | Ledger API `CreateCommand`          |
+| 2    | Fund holdings + set pre-approval | —                         | Ledger API choices                  |
+| 3    | Register on TAR                  | `cct:set-token`           | TAR choices via Ledger API          |
+| 4    | Enable lane                      | —                         | Rate limiters + `ApplyChainUpdates` |
+| 5    | Go live                          | —                         | EDS + verification                  |
+
+## Step 1 — Deploy the LockRelease Token Pool
+
+Create one [`LockReleaseTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/lock-release-token-pool/daml/CCIP/LockReleaseTokenPoolV2.daml). Signatory: `poolOwner`.
+
+### Transfer-fee fields
+
+When setting `tokenTransferFeeConfigs` (map keyed by destination chain selector):
+
+| Field               | Meaning                                                 |
+| :------------------ | :------------------------------------------------------ |
+| `isEnabled`         | Must be `true` to apply the config                      |
+| `feeUSDCents`       | Flat fee in USD cents (non-negative)                    |
+| `destGasOverhead`   | Gas for destination execution (> 0 when set via choice) |
+| `destBytesOverhead` | Data-availability bytes overhead (≥ 32)                 |
+| `feeBps`            | Proportional fee in basis points (\< 10000)             |
+
+### CCIP hosted addresses
+
+| Field                     | Testnet                                                                                                    | Mainnet                                                                                                                |
+| :------------------------ | :--------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
+| Token Admin Registry      | `tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551` | Contact the [CCIP team](https://chain.link/ccip-contact) for the Token Admin Registry address to register a token pool |
+| RMNRemote                 | `rmn_remote-nzvtd@rmnOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `rmn_remote-mnprd@rmnOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| FeeQuoter                 | `feequoter-scxln@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `feequoter-fpxih@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| CCIP owner party          | `ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`                          | `ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                                      |
+| Global EDS                | `https://eds.testnet.ccip.chain.link`                                                                      | `https://eds.ccip.chain.link`                                                                                          |
+| Indexer                   | `https://indexer-1.testnet.ccip.chain.link`                                                                | Primary: `https://indexer-1.ccip.chain.link` · Backup: `https://indexer-2.ccip.chain.link`                             |
+| Canton chain selector     | `9268731218649498074`                                                                                      | `2308837218439511688`                                                                                                  |
+| Default CommitteeVerifier | `committeeverifier-tqkny@ccvOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`   | `committeeverifier-mnprd@ccvOwner::122096accf0a84fc7d80d5fce5ea3135317a03eb22e62e0d8cdd7548865f984f11ff`               |
+
+## Step 2 — Fund the pool and configure pre-approval
+
+LockRelease liquidity comes from the **pool owner's token holdings**. Top up those holdings to match expected outbound volume — there is no separate on-pool deposit step. When a receiver executes an inbound transfer on Canton, tokens move from the pool owner's holdings to the recipient.
+
+<Aside type="note" title="Manual step">
+  The starter kit does not automate funding or pre-approval. Complete this step via the Ledger API before registering on TAR.
+</Aside>
+
+### Set pool receive preapproval
+
+Record the token's transfer preapproval in `poolReceiveContext` so inbound transfers to the pool owner succeed atomically on send:
+
+```shell
+curl --request POST \
+  --url https://<your-participant>/api/json/v2/commands/submit-and-wait-for-transaction-tree \
+  --header "authorization: Bearer $JWT" \
+  --header 'content-type: application/json' \
+  --data '{
+  "commands": [
+    {
+      "ExerciseCommand": {
+        "templateId": "#ccip-lock-release-token-pool:CCIP.LockReleaseTokenPool:LockReleaseTokenPool",
+        "contractId": "<POOL_CONTRACT_ID>",
+        "choice": "AddPoolReceiveContextContractValue",
+        "choiceArgument": {
+          "contextKey": "transfer-preapproval",
+          "referredContract": "<PREAPPROVAL_CONTRACT_ID>"
+        }
+      }
+    }
+  ],
+  "commandId": "set-pool-receive-preapproval",
+  "actAs": ["<POOL_OWNER_PARTY>"]
+}'
+```
+
+| Field              | Value                                                        |
+| :----------------- | :----------------------------------------------------------- |
+| `contextKey`       | Key the TransferFactory expects, e.g. `transfer-preapproval` |
+| `referredContract` | ContractId of the pool owner's transfer preapproval          |
+
+Related choices: `AddPoolReceiveContextNonContractValue`, `RemovePoolReceiveContextValue`, `ClearPoolReceiveContext`.
+
+## Step 3 — Register on the Token Admin Registry
+
+TAR maps each instrument to a single token pool. Registration: **propose → accept → set pool**.
+
+## Step 4 — Enable a lane
+
+Lane enablement is **not** automated by the starter kit.
+
+### 1. Deploy three rate limiters
+
+Each lane requires [`RateLimiter`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/rate-limiter/daml/CCIP/RateLimiterV2.daml) contracts (for testing, deploy disabled with zero capacity/rate):
+
+- **Inbound (default finality)**
+- **Inbound (custom finality)**
+- **Outbound**
+
+Created by `poolOwner` with matching `poolInstanceId`, `poolOwner`, and `remoteChainSelector`.
+
+### 2. Apply the chain update
+
+Call [`ApplyChainUpdates`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/lock-release-token-pool/daml/CCIP/LockReleaseTokenPoolV2.daml) on the pool:
+
+| ChainUpdate field                            | Guidance                                                                   |
+| :------------------------------------------- | :------------------------------------------------------------------------- |
+| `remoteChainSelector`                        | Destination chain selector — see [CCIP Directory](/ccip/directory/testnet) |
+| `remotePools`                                | Remote token pool address(es)                                              |
+| `remoteTokenAddress`                         | Remote token address                                                       |
+| `inboundCCVs` / `outboundCCVs`               | Default CommitteeVerifier (testnet address above) unless custom            |
+| `finalityConfig`                             | `WaitForFinality` for default finalized source tx                          |
+| `inboundRateLimiter`                         | Inbound default limiter CID                                                |
+| `inboundCustomBlockConfirmationsRateLimiter` | Inbound custom limiter CID                                                 |
+| `outboundRateLimiter`                        | Outbound limiter CID                                                       |
+
+Once applied, the on-ledger lane is complete.
+
+## Step 5 — Go live
+
+### Verification checklist
+
+1. TAR maps instrument to pool with your party as admin.
+2. Pool at `{instanceId}@{poolOwner}` with matching `InstrumentId`.
+3. Pool owner holds sufficient liquidity; receive preapproval set in `poolReceiveContext`.
+4. Lane rate limiters in place.
+
+### Stand up EDS
+
+The [reference EDS](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/eds.Dockerfile) supports LockRelease, including holdings and TransferFactory context for pre-approvals.
+
+### Test transactions
+
+See [CCIP on Canton — Overview](/ccip/concepts/canton/overview) and [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# CCIP Tutorials: Canton as Source
+Source: https://docs.chain.link/ccip/tutorials/canton/source
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+**Canton as Source** (`canton2any`) tutorials cover sending from Canton — Canton is the source chain, a remote CCIP-supported chain (Ethereum Sepolia in the starter kit) is the destination.
+
+<Aside type="note" title="Testnet only">
+  These tutorials run on **Canton testnet** and **Ethereum Sepolia** only. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites) with testnet credentials and tokens before starting.
+</Aside>
+
+Tutorials use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) on [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk).
+
+## Getting Started
+
+- [Prerequisites for Canton as Source](/ccip/tutorials/canton/source/prerequisites) — Clone the starter kit, configure Canton ledger access, and fund Amulet/LINK.
+- [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain) — On-ledger send path in the overview.
+
+## Tutorials by Use Case
+
+| Tutorial                                                                                   | Script                      | Description                                   |
+| :----------------------------------------------------------------------------------------- | :-------------------------- | :-------------------------------------------- |
+| [Arbitrary Messaging](/ccip/tutorials/canton/source/arbitrary-messaging)                   | `canton2any:data`           | Send a data-only message from Canton          |
+| [Token Transfers](/ccip/tutorials/canton/source/token-transfers)                           | `canton2any:token`          | Bridge LINK from Canton to Sepolia            |
+| [Programmable Token Transfers](/ccip/tutorials/canton/source/programmable-token-transfers) | `canton2any:data-and-token` | Send LINK plus calldata to a Sepolia receiver |
+
+## Common Flow (all canton2any tutorials)
+
+1. Fetch explicit disclosures from Global CCIP EDS (and token pool operator EDS for token messages)
+2. Create or reuse `CCIPSender` and `PerPartyRouter` on Canton
+3. Submit via `PerPartyRouter_CCIPSend` with CommitteeVerifier tickets (and token pool tickets when applicable)
+4. Track delivery in [CCIP Explorer](/ccip/tools-resources/ccip-explorer)
+5. Destination execution on Sepolia runs automatically by default, or via `canton2any:manual-exec` with `--no-exec`
+
+## Prerequisites
+
+- [Starter kit setup](/ccip/tutorials/canton/source/prerequisites)
+- **Amulet** (default) or **LINK** on Canton for CCIP fees
+- **LINK** on Canton for token transfer and PTT tutorials
+- Token pool registered on TAR for token messages — see [CCT guides](/ccip/tutorials/canton/cross-chain-tokens)
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Prerequisites for Canton as Source Tutorials
+Source: https://docs.chain.link/ccip/tutorials/canton/source/prerequisites
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+Before starting the **Canton as Source** (`canton2any`) tutorials, ensure you have the following. New to Canton? Read [Key Concepts](/ccip/concepts/canton/key-concepts) first (parties, fees, tooling).
+
+<Aside type="note" title="Tooling">
+  These tutorials use [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) — tutorial scripts on top of [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) (same send/execute model as [`ccip-cli`](https://github.com/smartcontractkit/ccip-tools-ts)). For production integrations, use the SDK or CLI directly.
+</Aside>
+
+<Aside type="note" title="Testnet only">
+  These tutorials use **Canton testnet** and **Ethereum Sepolia** only. The starter kit's `helperConfig.ts` and `canton-config.example.json` are pre-configured for the Canton CCIP testnet lane.
+</Aside>
+
+## Development Environment
+
+- **Node.js v20 or higher**: You can use the [nvm package](http://nvm.sh/) to install and switch between Node.js versions. Once installed, verify the node version with:
+
+  ```bash filename="Terminal"
+  node -v
+  ```
+
+  Example output:
+
+  ```text
+  $ node -v
+  v22.15.0
+  ```
+
+- **npm**: For installing and managing dependencies.
+
+- **Git**: For cloning the repository.
+
+## Starter Kit Repository
+
+1. Clone the [CCIP Canton Starter Kit](https://github.com/smartcontractkit/ccip-starter-kit-canton):
+
+   ```bash filename="Terminal"
+   git clone https://github.com/smartcontractkit/ccip-starter-kit-canton.git
+   ```
+
+2. Navigate to the directory:
+
+   ```bash filename="Terminal"
+   cd ccip-starter-kit-canton
+   ```
+
+3. Install dependencies:
+
+   ```bash filename="Terminal"
+   npm install
+   ```
+
+The starter kit uses [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) v1.10+ for Canton and Ethereum Sepolia interactions.
+
+## Understanding Canton Configuration (`canton-config.json`)
+
+Canton deployment fields live in `config/canton-config.json`. Copy the example file and replace the **two placeholder fields**:
+
+```bash filename="Terminal"
+cp config/canton-config.example.json config/canton-config.json
+```
+
+Replace **`party`** with your Canton testnet party ID (it must match your validator user). Replace **`transferInstructionUrl`** with your validator's transfer-instruction API (Amulet fee transfers and token metadata — not EDS). Chainlink provides shared CCIP endpoints (`edsUrl`, `indexerUrl`, `ccipParty`, `ccvs`, etc.) in the starter kit; you supply your own participant Ledger API access and validator configuration.
+
+All other fields (`edsUrl`, `indexerUrl`, `ccipParty`, `ccvs`, `senderInstanceId`, etc.) are pre-configured for the Canton CCIP testnet lane in `canton-config.example.json`.
+
+**Example `canton-config.json`:**
+
+```json filename="config/canton-config.json"
+{
+  "party": "YOUR_LEDGER_PARTY::1220…",
+  "ccipParty": "ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+  "edsUrl": "https://eds.testnet.ccip.chain.link",
+  "transferInstructionUrl": "https://validator.example.com/api/validator",
+  "indexerUrl": "https://indexer-1.testnet.ccip.chain.link",
+  "chainId": "canton:TestNet",
+  "senderInstanceId": "prod-ccipsender",
+  "ccvs": ["0xec1e288bcf8bbf034ac2d31b67f9b15a3f1f828d086c5b9d8fc2866129cd02fe"]
+}
+```
+
+Key fields:
+
+- **`party`**: Your ledger party — the sender for `canton2any` scripts and the default Canton receiver for `any2canton` scripts.
+- **`transferInstructionUrl`**: Your validator's transfer-instruction API. Depends on which validator hosts your party (not the Global CCIP EDS at `edsUrl`).
+- **`senderInstanceId`**: The `CCIPSender` instance used when sending from Canton.
+- **`ccvs`**: CommitteeVerifier contract IDs required for message validation.
+- **`edsUrl`** / **`indexerUrl`**: Global CCIP Explicit Disclosure Service and indexer endpoints for proofs and disclosures.
+
+Network selectors, router addresses, token instruments, and the default **`--gasLimit`** (`200000` for destination `ccipReceive`) are defined in [`helperConfig.ts`](https://github.com/smartcontractkit/ccip-starter-kit-canton/blob/main/helperConfig.ts).
+
+## Optional script flags
+
+Send scripts (`canton2any:*` and `any2canton:*`) share these common flags:
+
+| Flag                                 | Default      | Description                                                                                                                              |
+| :----------------------------------- | :----------- | :--------------------------------------------------------------------------------------------------------------------------------------- |
+| `--gasLimit`                         | `200000`     | Gas limit for `ccipReceive` on the destination chain (Sepolia for `canton2any`, Canton for `any2canton`)                                 |
+| `--feeToken`                         | `native`     | CCIP fee token on the source chain (`native`: Amulet on Canton, ETH on Sepolia; or `link`)                                               |
+| `--evmReceiver` / `--cantonReceiver` | See config   | Override the default receiver on the destination chain                                                                                   |
+| `--no-exec`                          | auto-exec on | `canton2any` only — skip automatic execution on Sepolia; run `canton2any:manual-exec` after Committee Verifier proofs are on the indexer |
+| `--finality`                         | `finalized`  | `any2canton` only — requested source finality (`finalized` or block depth, e.g. `32`)                                                    |
+
+## Canton Ledger Access
+
+Canton sends and executes use **OIDC bearer-token authentication** and direct ledger submit (same as `ccip-cli` without `--wallet`). No local signing key is required for participant-hosted parties.
+
+Canton uses standard [OpenID Connect (OIDC)](https://openid.net/connect/). You can authenticate with any compatible identity provider (Okta, Keycloak, Microsoft Azure, Auth0, and others) or a local user on development nodes — see the [Canton validator documentation](https://docs.canton.network/) for setup. Local or development nodes do not require an external identity provider.
+
+The starter kit resolves a bearer token from `.env` before each run:
+
+1. `CANTON_JWT` in `.env` (explicit override)
+2. OIDC client credentials (`CANTON_AUTH_URL`, `CANTON_CLIENT_ID`, `CANTON_CLIENT_SECRET`)
+3. `jwt` field in `canton-config.json` (fallback only)
+
+<Aside type="tip" title="What Chainlink provides">
+  Chainlink provides shared CCIP infrastructure for Canton lanes — **EDS**, **indexer**, and on-ledger contract references. These are pre-filled in `canton-config.example.json`. Contact Chainlink ops for contract references (owner party, TAR, RMNRemote, FeeQuoter). You supply your own participant Ledger API access, validator user, and `transferInstructionUrl`.
+</Aside>
+
+## Wallets and Accounts
+
+- **Canton party**: Your on-ledger party ID in `canton-config.json`. Scripts submit commands on behalf of this party via `submit-and-wait-for-transaction`.
+
+- **Ethereum Sepolia account** (optional for source sends): Required only if you run `canton2any:manual-exec` on Sepolia or want to verify token delivery on the destination chain. Set `EVM_PRIVATE_KEY` and `ETHEREUM_SEPOLIA_RPC_URL` in `.env`. For data-only sends with default auto-execution, you only need the **receiver contract address** on Sepolia (the starter kit provides a default).
+
+## Environment Configuration (`.env` file)
+
+Create `.env` from the example and replace every placeholder:
+
+```bash filename="Terminal"
+cp .env.example .env
+```
+
+| Variable                   | Description                                                           |
+| :------------------------- | :-------------------------------------------------------------------- |
+| `EVM_PRIVATE_KEY`          | Sepolia signer private key (hex, with or without `0x`)                |
+| `ETHEREUM_SEPOLIA_RPC_URL` | Your Sepolia JSON-RPC URL                                             |
+| `CANTON_LEDGER_URL`        | Canton participant **JSON Ledger API** URL (not EDS or the validator) |
+| `CANTON_CONFIG_PATH`       | Path to `canton-config.json` (default: `./config/canton-config.json`) |
+| `CANTON_AUTH_URL`          | OIDC authorization server URL (from your validator setup)             |
+| `CANTON_CLIENT_ID`         | OIDC client ID for your validator user                                |
+| `CANTON_CLIENT_SECRET`     | OIDC client secret — scripts fetch a fresh bearer token on each run   |
+
+**Example `.env` file:**
+
+```bash filename=".env"
+EVM_PRIVATE_KEY=0xYourSepoliaPrivateKey
+ETHEREUM_SEPOLIA_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/YOUR_API_KEY
+CANTON_LEDGER_URL=https://your-canton-ledger-api.example.com
+CANTON_CONFIG_PATH=./config/canton-config.json
+CANTON_AUTH_URL=https://auth.example.com
+CANTON_CLIENT_ID=your_client_id
+CANTON_CLIENT_SECRET=your_client_secret
+```
+
+<Aside type="caution" title="Keep your secrets safe">
+  Never commit `.env`, OIDC secrets, or private keys to version control.
+</Aside>
+
+## Testnet Tokens
+
+### Amulet (default CCIP fee token on Canton)
+
+`canton2any` scripts pay CCIP fees in **Amulet** by default. Fund your Canton party with Amulet holdings before sending.
+
+Check balances:
+
+```bash filename="Terminal"
+npm run check-balance
+```
+
+Or check Amulet only:
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token amulet
+```
+
+### LINK on Canton (token transfer tutorials)
+
+Token transfer and programmable token transfer tutorials send **LINK** from Canton to Sepolia. Your party needs LINK (`link-token`) holdings on Canton.
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token link
+```
+
+Pass `--feeToken link` on send scripts to pay CCIP fees in LINK instead of Amulet.
+
+### Sepolia ETH (optional)
+
+If you run `canton2any:manual-exec` yourself, your Sepolia account needs test ETH for gas. Use the [Chainlink Faucet](https://faucet.chain.link) to obtain test ETH.
+
+## Verify Setup
+
+From the starter kit root, confirm Canton connectivity and balances:
+
+```bash filename="Terminal"
+npm run check-balance
+```
+
+You should see LINK and Amulet balances for your Canton party. If you configured `EVM_PRIVATE_KEY`, Sepolia LINK and TEST balances are shown as well.
+
+When setup is complete, continue to the [Canton as Source tutorials](/ccip/tutorials/canton/source).
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Token Transfers: Canton as Source
+Source: https://docs.chain.link/ccip/tutorials/canton/source/token-transfers
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+This tutorial demonstrates how to transfer **LINK** tokens from Canton testnet to Ethereum Sepolia using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+  Complete the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites). For token transfers you also need:
+
+  - **LINK** holdings on your Canton party (the token being sent).
+  - **Amulet** (or LINK with `--feeToken link`) for CCIP fees.
+  - A registered token pool on the Token Admin Registry — the prod testnet **LINK ↔ TEST** lane is pre-configured. For custom instruments, see [Cross-Chain Token guides](/ccip/tutorials/canton/cross-chain-tokens).
+
+  These steps use **Canton testnet** and **Ethereum Sepolia** only.
+</Aside>
+
+## Introduction
+
+This tutorial covers a token-only transfer from Canton to Ethereum Sepolia without an attached data payload. When you transfer tokens using CCIP:
+
+1. Tokens are burned or locked in the token pool on Canton.
+2. Equivalent tokens are minted or released on Sepolia after destination execution.
+3. CCIP fees are collected on Canton in Amulet (default) or LINK.
+
+The prod testnet lane maps Canton **LINK** to Sepolia **TEST**.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Run `canton2any:token` to send LINK from Canton to Sepolia.
+- Pay CCIP fees in Amulet or LINK.
+- Monitor the transfer in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+- Verify TEST token balance on Sepolia after execution.
+
+## Understanding Token Transfers (canton2any)
+
+Key points for token-only transfers from Canton:
+
+- **Burn and mint**: LINK is burned on Canton; TEST is minted on Sepolia for the configured lane.
+- **Fee payment**: CCIP fees are paid on Canton. Default fee token is **Amulet**; pass `--feeToken link` to pay in LINK.
+- **No data payload**: Token-only transfers omit the `data` field.
+- **Token pool**: The SDK fetches disclosures from the token pool operator EDS and obtains a `TokenPoolTicket` during send.
+
+See the [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain) in the overview.
+
+## How the Script Works
+
+The `scripts/canton2any/ccipSendToken.ts` script:
+
+1. Loads Canton config, authenticates to the ledger, and connects.
+2. Parses `--amount` (human-readable LINK, e.g. `0.001`), `--feeToken`, `--evmReceiver`, and `--no-exec`.
+3. Builds a message with `tokenAmounts` for the Canton LINK instrument and submits via `CantonChain.sendMessage`.
+4. Prints the CCIP Message ID, explorer links, and optional manual-exec hint.
+
+## Running the Token Transfer
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites).
+
+2. Verify LINK and Amulet balances:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain canton --token link
+   npm run check-balance -- --chain canton --token amulet
+   ```
+
+3. Set `EVM_PRIVATE_KEY` if you will verify Sepolia balances or run manual execution.
+
+### Execute the Script
+
+Send `0.001` LINK from Canton to Sepolia (default receiver):
+
+```bash filename="Terminal"
+npm run canton2any:token -- --amount 0.001
+```
+
+Pay CCIP fee in LINK:
+
+```bash filename="Terminal"
+npm run canton2any:token -- --amount 0.001 --feeToken link
+```
+
+Skip auto-execution on Sepolia:
+
+```bash filename="Terminal"
+npm run canton2any:token -- --amount 0.001 --no-exec
+```
+
+### Understanding the Output
+
+```text
+🪙 Sending 0.001 LINK from Canton → Sepolia
+   Executor: default (auto-execution on Sepolia when an executor is configured)
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+📜 Canton transaction: https://lighthouse.testnet.cantonloop.com/transactions/…
+```
+
+## Verification and Monitoring
+
+### CCIP Explorer
+
+Track the full message lifecycle using the CCIP Explorer URL from the output.
+
+### Manual execution on Sepolia
+
+If you used `--no-exec`:
+
+```bash filename="Terminal"
+npm run canton2any:manual-exec -- <cantonUpdateId | messageId>
+```
+
+Pass either the Canton **update ID** (`📜 Canton transaction` / Lighthouse link) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) from the send output — `canton2any:manual-exec` accepts both.
+
+### Verify TEST balance on Sepolia
+
+After successful execution, check the Sepolia wallet that received TEST:
+
+```bash filename="Terminal"
+npm run check-balance -- --chain sepolia --token test
+```
+
+Or inspect the receiver address on [Sepolia Etherscan](https://sepolia.etherscan.io/).
+
+<Aside type="note" title="Decimals">
+  Canton LINK uses **10** decimal places in the starter kit configuration (`helperConfig.ts`), not the 18 decimals used on Sepolia ERC-20 tokens.
+</Aside>
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Arbitrary Messaging: Canton as Source
+Source: https://docs.chain.link/ccip/tutorials/canton/source/arbitrary-messaging
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+This tutorial demonstrates how to send a data-only CCIP message from Canton testnet to a receiver contract on Ethereum Sepolia using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+  Complete the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) before starting this tutorial. Your Canton party needs **Amulet** holdings to pay CCIP fees (or use `--feeToken link`).
+
+  These steps use **Canton testnet** and **Ethereum Sepolia** only.
+</Aside>
+
+## Introduction
+
+This tutorial covers sending arbitrary data from Canton to Ethereum Sepolia without any token transfer. When you send a message using CCIP:
+
+1. The SDK fetches explicit disclosures from Global CCIP EDS and creates or reuses `CCIPSender` and `PerPartyRouter` on Canton.
+2. The message is submitted via `PerPartyRouter_CCIPSend` with CommitteeVerifier tickets.
+3. CommitteeVerifier operators validate the message and aggregate proofs to the indexer.
+4. The message is executed on Sepolia — automatically by default, or manually with `canton2any:manual-exec`.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Run `canton2any:data` to send a UTF-8 data payload from Canton to Sepolia.
+- Pay CCIP fees in Amulet (default) or LINK.
+- Track delivery in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+- Optionally execute manually on Sepolia with `canton2any:manual-exec`.
+
+## Understanding Arbitrary Messaging (canton2any)
+
+Key points for data-only sends from Canton:
+
+- **Data only**: No `tokenAmounts` — only a `data` payload is delivered to the Sepolia receiver contract's `ccipReceive` function.
+- **Fee payment**: CCIP fees are paid on Canton in **Amulet** by default. Pass `--feeToken link` to pay in CCIP LINK instead.
+- **Auto-execution**: By default, the starter kit allows automatic execution on Sepolia when an executor is configured. Pass `--no-exec` to skip auto-execution and run `canton2any:manual-exec` after Committee Verifier proofs are on the indexer.
+- **Receiver**: Defaults to the starter kit's demo receiver on Sepolia. Override with `--evmReceiver`.
+
+See the [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain) in the overview for the full on-ledger and off-ledger path.
+
+## How the Script Works
+
+The `scripts/canton2any/ccipSendData.ts` script uses `@chainlink/ccip-sdk` `CantonChain.sendMessage`:
+
+1. **Context initialization**: Loads `canton-config.json`, authenticates to the Ledger API, and connects.
+2. **Argument parsing**: Reads `--dataString`, `--feeToken`, `--evmReceiver`, `--gasLimit` (default `200000`), and `--no-exec`.
+3. **Message construction**: Builds a CCIP message with encoded data, fee token, and `extraArgs` (gas limit and optional `executorMode: 'none'`).
+4. **Ledger submit**: Submits the send via authenticated direct ledger submit — no local Canton signing key required.
+5. **Output**: Prints the CCIP Message ID, CCIP Explorer URL, and Canton Lighthouse transaction link.
+
+## Running the Arbitrary Message
+
+### Prerequisites Check
+
+Before running the script:
+
+1. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites) setup (`npm install`, `.env`, `canton-config.json`).
+
+2. Confirm Amulet balance for fees:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain canton --token amulet
+   ```
+
+3. Ensure `ETHEREUM_SEPOLIA_RPC_URL` and `EVM_PRIVATE_KEY` are set if you plan to run `canton2any:manual-exec`.
+
+### Execute the Script
+
+Send a data-only message from Canton to Sepolia:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia"
+```
+
+Pay the CCIP fee in LINK instead of Amulet:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia" --feeToken link
+```
+
+Skip automatic execution on Sepolia and execute manually after Committee Verifier proofs are on the indexer:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia" --no-exec
+```
+
+Override the Sepolia receiver contract:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia" --evmReceiver 0xYourReceiverAddress
+```
+
+### Understanding the Output
+
+On success, you should see output similar to:
+
+```text
+📧 Sending data from Canton → Sepolia: "Hello Sepolia"
+   Executor: default (auto-execution on Sepolia when an executor is configured)
+Canton bearer token obtained via OIDC client credentials.
+🆔 CCIP Message ID: 0x1220e4133ede8f2daf2e665b53321da54d1bd0b8e00fb1cece20b63079c1d48d6a5b
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x1220…
+📜 Canton transaction: https://lighthouse.testnet.cantonloop.com/transactions/…
+```
+
+If you used `--no-exec`, the script also prints a copy-pasteable `canton2any:manual-exec` command.
+
+## Verification and Monitoring
+
+### Track on CCIP Explorer
+
+Open the CCIP Explorer URL from the script output to monitor message status from send through destination execution.
+
+### Manual execution on Sepolia
+
+If you passed `--no-exec`, wait until proofs are on the indexer (check the CCIP Explorer), then run:
+
+```bash filename="Terminal"
+npm run canton2any:manual-exec -- <cantonUpdateId | messageId>
+```
+
+Pass either the Canton **update ID** from the send output (`📜 Canton transaction` / Lighthouse link) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`). `canton2any:manual-exec` accepts both — resolving by message ID lets the SDK fetch the OffRamp and Committee Verifier proofs from the CCIP API automatically.
+
+On success:
+
+```text
+⚙️  Executing on Sepolia OffRamp 0x…
+✅ Execution transaction: https://sepolia.etherscan.io/tx/0x…
+```
+
+<Aside type="note" title="Execution timing">
+  End-to-end delivery time depends on Canton finality and CommitteeVerifier proof aggregation. Allow several minutes before manual execution if the message is not yet ready.
+</Aside>
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Programmable Token Transfers: Canton as Source
+Source: https://docs.chain.link/ccip/tutorials/canton/source/programmable-token-transfers
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+This tutorial demonstrates how to send a **programmable token transfer (PTT)** — tokens plus arbitrary data — from Canton testnet to Ethereum Sepolia using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+  Complete the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) and the [Token Transfers (Canton as Source)](/ccip/tutorials/canton/source/token-transfers) tutorial concepts. You need LINK and Amulet (or LINK fee token) on your Canton party.
+
+  These steps use **Canton testnet** and **Ethereum Sepolia** only.
+</Aside>
+
+## Introduction
+
+A programmable token transfer combines a token transfer with a data payload delivered to the destination receiver contract. On Sepolia, the receiver's `ccipReceive` function receives both the tokens and the calldata.
+
+This tutorial uses the `canton2any:data-and-token` script to send LINK plus a UTF-8 string in a single CCIP message.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Run `canton2any:data-and-token` with `--dataString` and `--amount`.
+- Pay CCIP fees in Amulet or LINK.
+- Track delivery in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+- Verify token delivery and optional manual execution on Sepolia.
+
+## Understanding Programmable Token Transfers (canton2any)
+
+| Aspect          | Token-only         | Programmable token transfer                         |
+| :-------------- | :----------------- | :-------------------------------------------------- |
+| **Data**        | Empty              | UTF-8 string (or `0x:` prefixed ABI-encoded string) |
+| **Tokens**      | LINK only          | LINK + data in one message                          |
+| **Destination** | Tokens to receiver | Tokens + `ccipReceive` calldata on Sepolia          |
+
+The send path on Canton combines token pool lock/burn (`TokenPoolTicket`) with CommitteeVerifier tickets in a single `PerPartyRouter_CCIPSend`, as described in the [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain).
+
+## How the Script Works
+
+`scripts/canton2any/ccipSendDataAndToken.ts` builds a message with both `data` (from `encodeMessageData`) and `tokenAmounts` (Canton LINK instrument), then submits via `CantonChain.sendMessage` with the same fee and execution options as the other `canton2any` scripts.
+
+## Running the Programmable Token Transfer
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites).
+2. Confirm LINK and fee-token balances:
+
+   ```bash filename="Terminal"
+   npm run check-balance
+   ```
+
+### Execute the Script
+
+Send `0.001` LINK with a data payload:
+
+```bash filename="Terminal"
+npm run canton2any:data-and-token -- --dataString "Hello" --amount 0.001
+```
+
+Pay fee in LINK and skip auto-execution:
+
+```bash filename="Terminal"
+npm run canton2any:data-and-token -- --dataString "Hello" --amount 0.001 --feeToken link --no-exec
+```
+
+Custom Sepolia receiver and a higher gas limit (default is `200000`):
+
+```bash filename="Terminal"
+npm run canton2any:data-and-token -- \
+  --dataString "Hello" \
+  --amount 0.001 \
+  --evmReceiver 0xYourReceiverAddress \
+  --gasLimit 300000
+```
+
+### Understanding the Output
+
+```text
+📧🪙 Sending data + 0.001 LINK from Canton → Sepolia: "Hello"
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+```
+
+## Verification and Monitoring
+
+### CCIP Explorer
+
+Monitor message status and destination execution state in the CCIP Explorer.
+
+### Manual execution on Sepolia
+
+After `--no-exec` sends, run manual execution once Committee Verifier proofs are on the indexer:
+
+```bash filename="Terminal"
+npm run canton2any:manual-exec -- <cantonUpdateId | messageId>
+```
+
+Pass either the Canton **update ID** (`📜 Canton transaction` / Lighthouse link) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) from the send output — `canton2any:manual-exec` accepts both.
+
+### Verify on Sepolia
+
+Check TEST token balance and inspect the receiver contract's events on [Sepolia Etherscan](https://sepolia.etherscan.io/) to confirm both token delivery and data processing.
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# CCIP Tutorials: Canton as Destination
+Source: https://docs.chain.link/ccip/tutorials/canton/destination
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+**Canton as Destination** (`any2canton`) tutorials cover receiving on Canton — Ethereum Sepolia is the source in the starter kit, Canton is the destination.
+
+<Aside type="caution" title="You must manually execute on Canton">
+  Every tutorial in this section ends with **`any2canton:manual-exec`**. See [Manual Execution (Canton)](/ccip/concepts/canton/manual-execution).
+</Aside>
+
+<Aside type="note" title="Testnet only">
+  These tutorials run on **Canton testnet** and **Ethereum Sepolia** only. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites) with testnet credentials and tokens before starting.
+</Aside>
+
+Tutorials use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) on [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk).
+
+## Getting Started
+
+- [Prerequisites for Canton as Destination](/ccip/tutorials/canton/destination/prerequisites) — Clone the starter kit, configure Sepolia and Canton access, and fund TEST/ETH.
+- [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton) — Execute path in the overview.
+
+## Tutorials by Use Case
+
+| Tutorial                                                                                        | Scripts                                     | Description                                  |
+| :---------------------------------------------------------------------------------------------- | :------------------------------------------ | :------------------------------------------- |
+| [Arbitrary Messaging](/ccip/tutorials/canton/destination/arbitrary-messaging)                   | `any2canton:data` + `manual-exec`           | Execute an incoming data message on Canton   |
+| [Token Transfers](/ccip/tutorials/canton/destination/token-transfers)                           | `any2canton:token` + `manual-exec`          | Execute an incoming token transfer on Canton |
+| [Programmable Token Transfers](/ccip/tutorials/canton/destination/programmable-token-transfers) | `any2canton:data-and-token` + `manual-exec` | Execute an incoming PTT on Canton            |
+
+## Common Flow (all any2canton tutorials)
+
+1. Send from Sepolia with an `any2canton:*` script
+2. Poll message status via the CCIP API or [CCIP Explorer](/ccip/tools-resources/ccip-explorer)
+3. Run `any2canton:manual-exec` — the SDK **finds or creates** a compatible `CCIPReceiver` for message finality
+4. Fetch proofs from the indexer and disclosures from Global CCIP EDS (+ token pool operator EDS for token messages)
+5. For token messages: accept the `TransferInstruction` to receive LINK on-ledger
+
+<Aside type="tip">
+  No separate receiver deployment tutorial is needed for the default path. Pass a `receiver` hint only for custom `CCIPReceiver` configurations.
+</Aside>
+
+## Prerequisites
+
+- [Starter kit setup](/ccip/tutorials/canton/destination/prerequisites)
+- Funded Sepolia account with ETH (or LINK for fees) and TEST for token tutorials
+- Canton ledger access for manual execution
+- Token pool registered for the instrument — see [CCT guides](/ccip/tutorials/canton/cross-chain-tokens)
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Prerequisites for Canton as Destination Tutorials
+Source: https://docs.chain.link/ccip/tutorials/canton/destination/prerequisites
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+Before starting the **Canton as Destination** (`any2canton`) tutorials, ensure you have the following:
+
+<Aside type="note" title="Testnet only">
+  These tutorials use **Canton testnet** and **Ethereum Sepolia** only. The starter kit's `helperConfig.ts` and `canton-config.example.json` are pre-configured for the Canton CCIP testnet lane.
+</Aside>
+
+## Development Environment
+
+- **Node.js v20 or higher**: You can use the [nvm package](http://nvm.sh/) to install and switch between Node.js versions. Once installed, verify the node version with:
+
+  ```bash filename="Terminal"
+  node -v
+  ```
+
+  Example output:
+
+  ```text
+  $ node -v
+  v22.15.0
+  ```
+
+- **npm**: For installing and managing dependencies.
+
+- **Git**: For cloning the repository.
+
+## Starter Kit Repository
+
+1. Clone the [CCIP Canton Starter Kit](https://github.com/smartcontractkit/ccip-starter-kit-canton):
+
+   ```bash filename="Terminal"
+   git clone https://github.com/smartcontractkit/ccip-starter-kit-canton.git
+   ```
+
+2. Navigate to the directory:
+
+   ```bash filename="Terminal"
+   cd ccip-starter-kit-canton
+   ```
+
+3. Install dependencies:
+
+   ```bash filename="Terminal"
+   npm install
+   ```
+
+The starter kit uses [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) v1.10+ for sending from Ethereum Sepolia and executing on Canton.
+
+## Understanding Network Configuration
+
+Lane defaults live in [`helperConfig.ts`](https://github.com/smartcontractkit/ccip-starter-kit-canton/blob/main/helperConfig.ts):
+
+- **Canton testnet** chain selector: `9268731218649498074`
+- **Ethereum Sepolia** chain selector: `16015286601757825753`
+- **Token lane**: Canton LINK ↔ Sepolia TEST (`0xeEe6675b20fE5950eb51361b93021D076289F612`)
+
+Canton deployment fields live in `config/canton-config.json` — see the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites#understanding-canton-configuration-canton-configjson) for the full file reference. Replace **`party`** and **`transferInstructionUrl`**; other fields are pre-configured for the Canton CCIP testnet lane.
+
+## Wallets and Accounts
+
+- **Ethereum Sepolia wallet and private key**: Required to send CCIP messages from Sepolia (`any2canton` send scripts). Set up a wallet like [MetaMask](https://metamask.io/), export the private key for the account you send from, and add it to `.env` as `EVM_PRIVATE_KEY`.
+
+- **Canton party**: The destination receiver on Canton. Defaults to the `party` field in `canton-config.json`. Override with `--cantonReceiver` on send scripts or `--receiver` on `any2canton:manual-exec` when needed.
+
+<Aside type="tip" title="No separate receiver deployment">
+  The SDK **finds or creates** a compatible `CCIPReceiver` when you run `any2canton:manual-exec`. Pass a `receiver` hint only for custom `CCIPReceiver` configurations.
+</Aside>
+
+## Environment Configuration (`.env` file)
+
+Create `.env` from the example:
+
+```bash filename="Terminal"
+cp .env.example .env
+cp config/canton-config.example.json config/canton-config.json
+```
+
+Fill in the following values:
+
+| Variable                                    | Description                                                                                              |
+| :------------------------------------------ | :------------------------------------------------------------------------------------------------------- |
+| `EVM_PRIVATE_KEY`                           | Sepolia signer hex key (with or without `0x` prefix)                                                     |
+| `ETHEREUM_SEPOLIA_RPC_URL`                  | Sepolia JSON-RPC URL                                                                                     |
+| `CANTON_LEDGER_URL`                         | Canton participant JSON Ledger API URL (required for `any2canton:manual-exec`; not EDS or the validator) |
+| `CANTON_CONFIG_PATH`                        | Path to `canton-config.json`                                                                             |
+| `CANTON_AUTH_URL`                           | OIDC authorization server URL (from your validator setup)                                                |
+| `CANTON_CLIENT_ID` / `CANTON_CLIENT_SECRET` | OIDC credentials for ledger auth on Canton                                                               |
+
+In `canton-config.json`, set **`party`** to your Canton testnet party ID and **`transferInstructionUrl`** to your validator's transfer-instruction API. See [source prerequisites](/ccip/tutorials/canton/source/prerequisites#understanding-canton-configuration-canton-configjson) for field reference.
+
+Send scripts use a default **`--gasLimit` of `200000`** for destination `ccipReceive` (see [optional script flags](/ccip/tutorials/canton/source/prerequisites#optional-script-flags) in source prerequisites).
+
+**Example `.env` file:**
+
+```bash filename=".env"
+EVM_PRIVATE_KEY=0xYourSepoliaPrivateKey
+ETHEREUM_SEPOLIA_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/YOUR_API_KEY
+CANTON_LEDGER_URL=https://your-canton-ledger-api.example.com
+CANTON_CONFIG_PATH=./config/canton-config.json
+CANTON_AUTH_URL=https://auth.example.com
+CANTON_CLIENT_ID=your_client_id
+CANTON_CLIENT_SECRET=your_client_secret
+```
+
+<Aside type="caution" title="Keep your secrets safe">
+  Never commit `.env`, OIDC secrets, or private keys to version control.
+</Aside>
+
+## Testnet Tokens
+
+### ETH on Ethereum Sepolia
+
+ETH pays for Sepolia transaction fees and CCIP fees (default `--feeToken native`). Use the [Chainlink Faucet](https://faucet.chain.link) to obtain test ETH.
+
+### LINK on Ethereum Sepolia (optional)
+
+Pass `--feeToken link` on `any2canton` send scripts to pay CCIP fees in LINK instead of ETH. Use the [Chainlink Faucet](https://faucet.chain.link) for test LINK.
+
+### TEST token on Ethereum Sepolia (token transfer tutorials)
+
+Token transfer tutorials send the Sepolia **TEST** token (`BurnMintERC20WithDrip`). Mint test tokens with the starter kit faucet:
+
+```bash filename="Terminal"
+npm run faucet:evm-test
+```
+
+This calls `drip()` on the TEST token contract and credits 1 TEST to your `EVM_PRIVATE_KEY` wallet.
+
+### Canton holdings after execution
+
+TEST burned on Sepolia mints **LINK** on Canton only after you run `any2canton:manual-exec` once the message is ready. Data-only messages do not transfer tokens.
+
+Check balances before and after execution:
+
+```bash filename="Terminal"
+npm run check-balance
+```
+
+## Verify Setup
+
+Confirm Sepolia and Canton configuration:
+
+```bash filename="Terminal"
+npm run check-balance -- --chain sepolia --token test
+npm run check-balance -- --chain canton --token link
+```
+
+When setup is complete, continue to the [Canton as Destination tutorials](/ccip/tutorials/canton/destination).
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Token Transfers: Canton as Destination
+Source: https://docs.chain.link/ccip/tutorials/canton/destination/token-transfers
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+This tutorial demonstrates how to transfer tokens from Ethereum Sepolia to Canton: burn **TEST** on Sepolia and receive **LINK** on Canton after manual execution.
+
+<Aside title="Prerequisites">
+  Complete the [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites). You need:
+
+  - Sepolia **ETH** for CCIP fees (or LINK with `--feeToken link`).
+  - Sepolia **TEST** tokens — mint with `npm run faucet:evm-test`.
+  - Canton ledger access for `any2canton:manual-exec`.
+
+  These steps use **Canton testnet** and **Ethereum Sepolia** only.
+</Aside>
+
+## Introduction
+
+The prod testnet lane maps Sepolia **TEST** to Canton **LINK**. Token delivery on Canton happens only after you:
+
+1. Send the token transfer from Sepolia (`any2canton:token`).
+2. Wait for source finality and Committee Verifier proofs on the indexer.
+3. Execute on Canton (`any2canton:manual-exec`) — the SDK processes `TokenReceiveTicket` and issues a `TransferInstruction` for your party to accept.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Fund your Sepolia wallet with TEST tokens.
+- Send `1` TEST from Sepolia to your Canton party.
+- Execute on Canton and verify LINK balance.
+
+## Understanding Token Transfers (any2canton)
+
+Key points:
+
+- **Burn and mint**: TEST is burned on Sepolia; LINK is minted on Canton after execution.
+- **Manual execution required**: Unlike `canton2any` default auto-exec on Sepolia, all `any2canton` token transfers require `any2canton:manual-exec` on Canton.
+- **Token pool disclosures**: Execution fetches disclosures from Global CCIP EDS and the token pool operator EDS.
+
+See the [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton) — `TokenReceiveTicket` and token pool release steps.
+
+<Aside type="tip" title="Custom CCIPReceiver">
+  Use the optional `--receiver` flag on `any2canton:manual-exec` only when you need a specific `CCIPReceiver` contract (custom Committee Verifier or finality configuration on the receiver). The default path finds or creates a compatible receiver automatically.
+</Aside>
+
+## Running the Tutorial
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites).
+
+2. Mint TEST on Sepolia:
+
+   ```bash filename="Terminal"
+   npm run faucet:evm-test
+   ```
+
+3. Note your Canton LINK balance before the transfer:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain canton --token link
+   ```
+
+## Step 1: Send TEST from Sepolia
+
+```bash filename="Terminal"
+npm run any2canton:token -- --amount 1
+```
+
+Faster finality (32 block confirmations):
+
+```bash filename="Terminal"
+npm run any2canton:token -- --amount 1 --finality 32
+```
+
+### Expected send output
+
+```text
+🪙 Sending 1 TEST from Sepolia → Canton
+   Receiver party: yourParty::1220…
+   LINK is minted on Canton only after manual execution.
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+
+⚙️  Execute on Canton once the message is finalized on Sepolia:
+   npm run any2canton:manual-exec -- 0x<messageId>
+```
+
+## Step 2: Execute on Canton
+
+Wait for the requested finality and Committee Verifier proofs on the indexer, then:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId>
+```
+
+Pass either the **Sepolia source transaction hash** (`📜 Source transaction`) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) — `any2canton:manual-exec` accepts both.
+
+Execution typically takes 1–3 minutes on the ledger after you run the command.
+
+## Verification
+
+### Check LINK balance on Canton
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token link
+```
+
+Your LINK balance should increase after successful execution and `TransferInstruction` acceptance.
+
+### CCIP Explorer
+
+Confirm the message reached **SUCCESS** and inspect the Canton execution update in Lighthouse.
+
+### Verbose holdings (optional)
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token link --show-holdings
+```
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Arbitrary Messaging: Canton as Destination
+Source: https://docs.chain.link/ccip/tutorials/canton/destination/arbitrary-messaging
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+This tutorial demonstrates how to send arbitrary data from Ethereum Sepolia to Canton and **execute** the message on Canton using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+  Complete the [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites) before starting. You need Sepolia ETH for send fees and Canton ledger access for `any2canton:manual-exec`.
+
+  These steps use **Canton testnet** and **Ethereum Sepolia** only.
+</Aside>
+
+## Introduction
+
+When Canton is the **destination** chain, the source send happens on Ethereum Sepolia and execution happens on Canton. For data-only messages:
+
+1. You call the CCIP Router on Sepolia via `any2canton:data`.
+2. CommitteeVerifier operators validate and aggregate proofs.
+3. You run `any2canton:manual-exec` to execute on Canton — the SDK finds or creates a compatible `CCIPReceiver`.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Send a data-only message from Sepolia to your Canton party with `any2canton:data`.
+- Wait for source finality and Committee Verifier proofs on the indexer.
+- Execute the message on Canton with `any2canton:manual-exec`.
+- Track progress in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+## Understanding Arbitrary Messaging (any2canton)
+
+Key points when Canton is the destination:
+
+- **Two-step flow**: Send on Sepolia, then manually execute on Canton (all `any2canton` tutorials use manual execution on Canton).
+- **Receiver**: Defaults to the `party` in `canton-config.json`. Override with `--cantonReceiver` on send or `--receiver` on manual exec.
+- **Finality**: Default `--finality finalized` waits for Sepolia finality before execution is allowed. Pass `--finality 32` (or another block depth) for faster-than-finality.
+- **Fee payment**: CCIP fees on Sepolia default to native ETH. Pass `--feeToken link` to pay in LINK.
+
+See the [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton) in the overview.
+
+## How the Scripts Work
+
+**`scripts/any2canton/ccipSendData.ts`**:
+
+1. Resolves the Canton receiver party from `canton-config.json`.
+2. Builds and sends a data-only CCIP message via the SDK's `sendMessage` on Sepolia.
+3. Prints the CCIP Message ID and a copy-pasteable `any2canton:manual-exec` command.
+
+**`scripts/any2canton/manualExecute.ts`**:
+
+1. Looks up the message using the **Sepolia source transaction hash** from the send output.
+2. Fetches proofs from the indexer and disclosures from Global CCIP EDS.
+3. Calls `CantonChain.execute` — the SDK resolves or creates the `CCIPReceiver` and submits to the ledger.
+
+## Running the Tutorial
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites).
+2. Confirm Sepolia ETH balance:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain sepolia --token link
+   ```
+
+## Step 1: Send from Sepolia
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton"
+```
+
+Pay fee in LINK:
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton" --feeToken link
+```
+
+Request faster execution with block-depth finality (32 confirmations):
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton" --finality 32
+```
+
+Override the Canton receiver party:
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton" --cantonReceiver 'yourParty::1220…'
+```
+
+### Expected send output
+
+```text
+📧 Sending data from Sepolia → Canton: "Hello Canton"
+   Receiver party: yourParty::1220…
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+📜 Source transaction: https://sepolia.etherscan.io/tx/0x…
+
+⚙️  Execute on Canton once the message is finalized on Sepolia:
+   npm run any2canton:manual-exec -- 0x<messageId>
+```
+
+Save the **CCIP Message ID** (`🆔 CCIP Message ID`) — or the **Sepolia source transaction hash** (`📜 Source transaction`) — from the send output for the execution step. `any2canton:manual-exec` accepts either.
+
+## Step 2: Execute on Canton
+
+Wait until the message is ready — timing depends on `--finality`:
+
+- **`finalized`** (default): Wait for Sepolia finality (often 15+ minutes).
+- **Block depth** (e.g. `32`): Wait for the specified number of Sepolia confirmations.
+
+Monitor status in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer). When proofs are on the indexer, run:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId>
+```
+
+You can pass either the **Sepolia source transaction hash** or the **CCIP Message ID** (`0x…`). They share the same `0x`+64-hex shape, so the script resolves the message from whichever matches. Examples:
+
+```bash filename="Terminal"
+# By Sepolia source transaction hash
+npm run any2canton:manual-exec -- 0x5a814d64666f60d2777c5425e8d0ea5a4b1bc9a3215eaeabced8b248050a3b99
+
+# By CCIP Message ID
+npm run any2canton:manual-exec -- 0x1220e4133ede8f2daf2e665b53321da54d1bd0b8e00fb1cece20b63079c1d48d6a5b
+```
+
+### Expected execution output
+
+```text
+⚙️  Executing on Canton (OffRamp 0x…)…
+   Resolving CCIPReceiver, fetching EDS disclosures, and submitting to the ledger — often 1–3 minutes with no further output.
+✅ Canton execution transaction: https://lighthouse.testnet.cantonloop.com/transactions/…
+```
+
+<Aside type="tip" title="Debug logging">
+  Set `CCIP_DEBUG=1` in `.env` for step-by-step SDK logs during execution.
+</Aside>
+
+## Verification
+
+1. Confirm **SUCCESS** in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+2. Inspect the Canton execution transaction on [Canton Lighthouse](https://lighthouse.testnet.cantonloop.com).
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
+# Programmable Token Transfers: Canton as Destination
+Source: https://docs.chain.link/ccip/tutorials/canton/destination/programmable-token-transfers
+Last Updated: 2026-07-06
+
+<Aside type="caution">
+  Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+</Aside>
+
+This tutorial demonstrates how to send a **programmable token transfer (PTT)** from Ethereum Sepolia to Canton — TEST tokens plus arbitrary data — and execute it on Canton using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+  Complete the [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites) and review [Token Transfers (Canton as Destination)](/ccip/tutorials/canton/destination/token-transfers). You need Sepolia TEST tokens (`npm run faucet:evm-test`) and Canton ledger access.
+
+  These steps use **Canton testnet** and **Ethereum Sepolia** only.
+</Aside>
+
+## Introduction
+
+A programmable token transfer delivers both tokens and a data payload to the destination. On Canton, execution:
+
+1. Resolves or creates a `CCIPReceiver` for the message finality.
+2. Processes `TokenReceiveTicket` and mints LINK via the token pool.
+3. Delivers the attached data to your receiver logic through `ccipReceive` on Canton.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Send `1` TEST plus a UTF-8 data string from Sepolia with `any2canton:data-and-token`.
+- Execute on Canton with `any2canton:manual-exec`.
+- Verify LINK balance and message execution.
+
+## Understanding Programmable Token Transfers (any2canton)
+
+| Aspect               | Token-only                               | Programmable token transfer            |
+| :------------------- | :--------------------------------------- | :------------------------------------- |
+| **Send script**      | `any2canton:token`                       | `any2canton:data-and-token`            |
+| **Data**             | Empty                                    | `--dataString` payload                 |
+| **Canton execution** | LINK mint + accept `TransferInstruction` | LINK mint + data delivered to receiver |
+
+The execution path fetches proofs, Global CCIP EDS disclosures, and token pool operator EDS inputs — see the [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton).
+
+## Running the Tutorial
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites).
+2. Mint TEST on Sepolia:
+
+   ```bash filename="Terminal"
+   npm run faucet:evm-test
+   ```
+
+## Step 1: Send data + TEST from Sepolia
+
+```bash filename="Terminal"
+npm run any2canton:data-and-token -- --dataString "Hello" --amount 1
+```
+
+Pay CCIP fee in LINK and use block-depth finality:
+
+```bash filename="Terminal"
+npm run any2canton:data-and-token -- \
+  --dataString "Hello" \
+  --amount 1 \
+  --feeToken link \
+  --finality 32
+```
+
+### Expected send output
+
+```text
+📧🪙 Sending data + 1 TEST from Sepolia → Canton: "Hello"
+   Receiver party: yourParty::1220…
+   LINK is minted on Canton only after manual execution.
+🆔 CCIP Message ID: 0x…
+
+⚙️  Execute on Canton once Sepolia reaches 32 block confirmations for this message:
+   npm run any2canton:manual-exec -- 0x<messageId>
+```
+
+## Step 2: Execute on Canton
+
+After finality and Committee Verifier proofs are on the indexer:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId>
+```
+
+Pass either the **Sepolia source transaction hash** (`📜 Source transaction`) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) — `any2canton:manual-exec` accepts both.
+
+Optional custom receiver hint:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId> --receiver 'yourParty::1220…'
+```
+
+## Verification
+
+1. **CCIP Explorer**: Confirm SUCCESS for the transfer.
+2. **LINK balance**: `npm run check-balance -- --chain canton --token link`
+3. **Canton Lighthouse**: Inspect the execution transaction for token pool and receiver activity.
+
+<Aside type="caution" title="Educational Example Disclaimer">
+  This page includes an educational example to use a Chainlink system, product, or service and is provided to
+  demonstrate how to interact with Chainlink's systems, products, and services to integrate them into your own. This
+  template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, it has not been audited, and it may be
+  missing key checks or error handling to make the usage of the system, product or service more clear. Do not use the
+  code in this example in a production environment without completing your own audits and application of best practices.
+  Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs
+  that are generated due to errors in code.
+</Aside>
+
+---
+
 # CCIP Explorer
 Source: https://docs.chain.link/ccip/tools-resources/ccip-explorer
 Last Updated: 2025-05-19
diff --git a/src/content/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool.mdx b/src/content/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool.mdx
new file mode 100644
index 00000000000..ff2adddfdc8
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool.mdx
@@ -0,0 +1,280 @@
+---
+section: ccip
+date: Last Modified
+title: "BurnMint Token Pool Deployment (Canton)"
+metadata:
+  description: "Deploy a CCIP BurnMint token pool on Canton, register on the Token Admin Registry, and enable a cross-chain lane using the starter kit or Ledger API."
+  excerpt: "CCIP Canton BurnMint token pool, TAR registration, ApplyChainUpdates, starter kit, cct scripts"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-06"
+  difficulty: "advanced"
+  estimatedTime: "45 minutes"
+whatsnext:
+  "Explicit Disclosure API": "/ccip/concepts/canton/explicit-disclosure"
+  "Cross-chain overview": "/ccip/concepts/canton/overview"
+  "LockRelease alternative": "/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool"
+---
+
+import { Aside } from "@components"
+import { Tabs } from "@components/Tabs"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+Deploy a **BurnMint** token pool on Canton, register it on the Token Admin Registry (TAR), and enable a cross-chain lane. Use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) for pool deployment and TAR registration, or submit Ledger API commands directly.
+
+This guide assumes you already have a token instrument live on Canton with supply minted on-ledger — for example a Registry instrument from Digital Asset's [Registry utility](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/index.html), or any instrument supporting CIP-56 with the `BurnMintFactory` interface.
+
+**Scope:** On-ledger pool connection — deploy, TAR registration, and lane enablement. Does not cover [EDS setup](/ccip/concepts/canton/explicit-disclosure) or end-to-end transfer tests.
+
+<Aside type="note" title="Testnet only">
+
+Starter kit `cct:*` scripts target **Canton testnet** only.
+
+</Aside>
+
+## Prerequisites
+
+- **Instrument (token managed on Canton Ledger)** with known `InstrumentId = { admin, id }`. The admin party must be the same party that will own the token pool.
+- **Burn/mint authority** — `instrumentId.admin == poolOwner` (enforced by the BurnMint template and by the starter kit).
+- **BurnMint token pool DAR** on your participant — [`ccip-burn-mint-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-burn-mint-token-pool-1.0.0.dar) (bundles its CCIP dependencies — the only DAR you upload).
+- **CCIP contract references** from Chainlink ops: CCIP owner party, Token Admin Registry, RMNRemote, FeeQuoter.
+- **Starter kit setup** (if using `cct:*` scripts) — complete [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) and the [CCT overview](/ccip/tutorials/canton/cross-chain-tokens#starter-kit-cct-scripts).
+
+<Aside type="caution" title="Pool owner trust">
+
+CCIP fully trusts the pool owner party. Whoever owns the pool controls remote-chain configuration, rate limits, fees, and token handling. We strongly recommend pool owner and instrument admin be the same party, decentralized across multiple nodes.
+
+</Aside>
+
+## Deployment overview
+
+| Step | Action                     | Starter kit            | Manual                              |
+| :--- | :------------------------- | :--------------------- | :---------------------------------- |
+| 1    | Deploy `BurnMintTokenPool` | `cct:deploy-burn-mint` | Ledger API `CreateCommand`          |
+| 2    | Register on TAR            | `cct:set-token`        | TAR choices via Ledger API          |
+| 3    | Enable lane                | —                      | Rate limiters + `ApplyChainUpdates` |
+| 4    | Go live                    | —                      | EDS + verification                  |
+
+## Step 1 — Deploy the BurnMint Token Pool
+
+Create one [`BurnMintTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/burn-mint-token-pool/daml/CCIP/BurnMintTokenPoolV2.daml). `poolOwner` + `instanceId` uniquely identifies the pool. Signatory: `poolOwner`.
+
+<Tabs client:visible>
+  <Fragment slot="tab.1">Starter kit</Fragment>
+  <Fragment slot="tab.2">Manual</Fragment>
+  <Fragment slot="panel.1">
+
+From the starter kit root:
+
+```bash filename="Terminal"
+npm run cct:deploy-burn-mint -- \
+  --instanceId acme-eur-bm-pool \
+  --instrument 'yourParty::1220…::token-id'
+```
+
+**Flags:**
+
+| Flag           | Required | Description                                                               |
+| :------------- | :------- | :------------------------------------------------------------------------ |
+| `--instanceId` | Yes      | Unique pool instance ID for your party (e.g. `acme-eur-bm-pool`)          |
+| `--instrument` | Yes      | Canton instrument ID: `party::fingerprint::tokenId`                       |
+| `--poolOwner`  | No       | Defaults to `party` in `canton-config.json` (must equal instrument admin) |
+| `--ccipOwner`  | No       | Defaults to `ccipParty` in `canton-config.json`                           |
+| `--decimals`   | No       | Token decimals on Canton (default `10`)                                   |
+
+**Expected output:**
+
+```text
+Deploying BurnMint token pool on Canton
+   instanceId: acme-eur-bm-pool
+   instrument: yourParty::1220…::token-id
+   poolOwner:  yourParty::1220…
+Canton bearer token obtained via OIDC client credentials.
+✅ BurnMintTokenPool contract ID: 00abc…
+   Pool address: acme-eur-bm-pool@yourParty::1220…
+   Update: https://lighthouse.testnet.cantonloop.com/transactions/…
+
+Next step: register the pool on the Token Admin Registry:
+   npm run cct:set-token -- --instrument "yourParty::1220…::token-id" --poolInstanceId "acme-eur-bm-pool" --poolOwner "yourParty::1220…"
+```
+
+Save the **pool address** (`{instanceId}@{poolOwner}`) and contract ID for verification.
+
+  </Fragment>
+  <Fragment slot="panel.2">
+
+Submit a `CreateCommand` for `BurnMintTokenPool` via your participant's JSON Ledger API (`submit-and-wait-for-transaction-tree`).
+
+| Argument                  | Guidance                                                                                  |
+| :------------------------ | :---------------------------------------------------------------------------------------- |
+| `instanceId`              | Unique string for your party, e.g. `acme-eur-bm-pool`                                     |
+| `poolOwner`               | Party that owns the pool. Recommended: instrument admin.                                  |
+| `ccipOwner`               | Chainlink CCIP owner party from ops                                                       |
+| `instrumentId`            | Your underlying asset's `InstrumentId`                                                    |
+| `decimals`                | Standard value: `10`                                                                      |
+| `rateLimitAdmin`          | Optional — leave unset unless a separate party manages limits                             |
+| `remoteChainConfigs`      | Leave empty — configure via `ApplyChainUpdates` (Step 3)                                  |
+| `tokenTransferFeeConfigs` | Optional per-destination fees — set at deploy or via `ApplyTokenTransferFeeConfigUpdates` |
+| `poolReceiveContext`      | Leave empty at creation                                                                   |
+| `transferTimeout`         | `Indefinite` to disable expiry on pending outgoing transfers                              |
+| `deps`                    | `tokenAdminRegistry`, `rmnRemote`, `feeQuoter` references from ops                        |
+
+After creation, your pool address is `{instanceId}@{poolOwner}`.
+
+  </Fragment>
+</Tabs>
+
+### Transfer-fee fields
+
+When setting `tokenTransferFeeConfigs` (map keyed by destination chain selector):
+
+| Field               | Meaning                                                 |
+| :------------------ | :------------------------------------------------------ |
+| `isEnabled`         | Must be `true` to apply the config                      |
+| `feeUSDCents`       | Flat fee in USD cents (non-negative)                    |
+| `destGasOverhead`   | Gas for destination execution (> 0 when set via choice) |
+| `destBytesOverhead` | Data-availability bytes overhead (≥ 32)                 |
+| `feeBps`            | Proportional fee in basis points (< 10000)              |
+
+### CCIP hosted addresses
+
+| Field                     | Testnet                                                                                                    | Mainnet                                                                                                                |
+| :------------------------ | :--------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
+| Token Admin Registry      | `tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551` | Contact the [CCIP team](https://chain.link/ccip-contact) for the Token Admin Registry address to register a token pool |
+| RMNRemote                 | `rmn_remote-nzvtd@rmnOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `rmn_remote-mnprd@rmnOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| FeeQuoter                 | `feequoter-scxln@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `feequoter-fpxih@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| CCIP owner party          | `ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`                          | `ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                                      |
+| Global EDS                | `https://eds.testnet.ccip.chain.link`                                                                      | `https://eds.ccip.chain.link`                                                                                          |
+| Indexer                   | `https://indexer-1.testnet.ccip.chain.link`                                                                | Primary: `https://indexer-1.ccip.chain.link` · Backup: `https://indexer-2.ccip.chain.link`                             |
+| Canton chain selector     | `9268731218649498074`                                                                                      | `2308837218439511688`                                                                                                  |
+| Default CommitteeVerifier | `committeeverifier-tqkny@ccvOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`   | `committeeverifier-mnprd@ccvOwner::122096accf0a84fc7d80d5fce5ea3135317a03eb22e62e0d8cdd7548865f984f11ff`               |
+
+## Step 2 — Register on the Token Admin Registry
+
+TAR maps each instrument to a single token pool. Registration: **propose → accept → set pool**.
+
+<Tabs client:visible>
+  <Fragment slot="tab.1">Starter kit</Fragment>
+  <Fragment slot="tab.2">Manual</Fragment>
+  <Fragment slot="panel.1">
+
+```bash filename="Terminal"
+npm run cct:set-token -- \
+  --instrument 'yourParty::1220…::token-id' \
+  --poolInstanceId acme-eur-bm-pool
+```
+
+**Flags:**
+
+| Flag               | Required | Description                                                                     |
+| :----------------- | :------- | :------------------------------------------------------------------------------ |
+| `--instrument`     | Yes      | Same instrument ID used in Step 1                                               |
+| `--poolInstanceId` | Yes      | `instanceId` from Step 1                                                        |
+| `--poolOwner`      | No       | Party that owns the pool contract (defaults to `party` in `canton-config.json`) |
+| `--poolAdmin`      | No       | TAR admin party (defaults to `poolOwner`)                                       |
+| `--proposeCaller`  | No       | Party that calls `ProposeAdministrator` (defaults to instrument admin)          |
+| `--tokenConfigCid` | No       | Resume at `AcceptAdminRole` if `ProposeAdministrator` already succeeded         |
+| `--skipAccept`     | No       | Resume at `SetPool` only (skip propose and accept)                              |
+
+The script fetches TAR disclosures from Global EDS, then submits all three TAR choices in sequence.
+
+**Expected output:**
+
+```text
+Registering token pool on the Token Admin Registry (TAR)
+   instrument:     yourParty::1220…::token-id
+   poolInstanceId: acme-eur-bm-pool
+   pool address:   acme-eur-bm-pool@yourParty::1220…
+Step 1/3 — ProposeAdministrator on Token Admin Registry
+   tokenConfigCid: 00def…
+Step 2/3 — AcceptAdminRole on Token Admin Registry
+Step 3/3 — SetPool on Token Admin Registry
+✅ Token pool registered for yourParty::1220…::token-id
+   tokenConfigCid: 00ghi…
+
+Next step: enable a cross-chain lane (rate limiters + ApplyChainUpdates on the pool).
+```
+
+  </Fragment>
+  <Fragment slot="panel.2">
+
+### Fetch TAR explicit disclosure
+
+Your party is not an observer on TAR. Query the Global EDS batch endpoint:
+
+```shell
+curl --request POST \
+  --url https://eds.testnet.ccip.chain.link/ccip/v1/global/disclosure/batch \
+  --header 'content-type: application/json' \
+  --data '{
+  "addresses": [
+    "tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551"
+  ]
+}'
+```
+
+Include disclosed contracts in subsequent ledger submissions. OpenAPI: [`eds-global.yaml`](https://github.com/smartcontractkit/chainlink-canton/blob/main/openapi/src/eds/global/eds-global.yaml).
+
+### TAR choices
+
+1. **`ProposeAdministrator`** — CCIP owner or instrument admin. Pass `instrumentId`, `newAdmin`, `caller`. For new instruments, leave `tokenConfigCid` as `None`. Returns `TokenConfig` CID for next steps.
+2. **`AcceptAdminRole`** — Proposed admin exercises with `tokenConfigCid`, `instrumentId`, `caller`.
+3. **`SetPool`** — Admin links instrument to pool via `PoolRegistration` (`poolOwner`, `poolInstanceId` from Step 1).
+
+Admin role can be transferred with `TransferAdminRole` → `AcceptAdminRole`.
+
+  </Fragment>
+</Tabs>
+
+## Step 3 — Enable a lane
+
+Lane enablement is **not** automated by the starter kit. Deploy rate limiters and call `ApplyChainUpdates` on your pool via the Ledger API.
+
+### 1. Deploy three rate limiters
+
+Each lane requires [`RateLimiter`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/rate-limiter/daml/CCIP/RateLimiterV2.daml) contracts (for testing, deploy disabled with zero capacity/rate):
+
+- **Inbound (default finality)**
+- **Inbound (custom finality)**
+- **Outbound**
+
+Created by `poolOwner` with matching `poolInstanceId`, `poolOwner`, and `remoteChainSelector`.
+
+### 2. Apply the chain update
+
+Call [`ApplyChainUpdates`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/burn-mint-token-pool/daml/CCIP/BurnMintTokenPoolV2.daml) on the pool:
+
+| ChainUpdate field                            | Guidance                                                                   |
+| :------------------------------------------- | :------------------------------------------------------------------------- |
+| `remoteChainSelector`                        | Destination chain selector — see [CCIP Directory](/ccip/directory/testnet) |
+| `remotePools`                                | Remote token pool address(es)                                              |
+| `remoteTokenAddress`                         | Remote token address                                                       |
+| `inboundCCVs` / `outboundCCVs`               | Default CommitteeVerifier (testnet address above) unless custom            |
+| `finalityConfig`                             | `WaitForFinality` for default finalized source tx                          |
+| `inboundRateLimiter`                         | Inbound default limiter CID                                                |
+| `inboundCustomBlockConfirmationsRateLimiter` | Inbound custom limiter CID                                                 |
+| `outboundRateLimiter`                        | Outbound limiter CID                                                       |
+
+Once applied, the on-ledger lane is complete.
+
+## Step 4 — Go live
+
+### Verification checklist
+
+1. `InstrumentId.admin` equals pool owner.
+2. TAR maps your instrument to your pool with your party as admin.
+3. Pool exists at `{instanceId}@{poolOwner}` with matching `InstrumentId`.
+4. Lane rate limiters are in place.
+
+### Stand up EDS for your pool
+
+Users need [explicit disclosures](/ccip/concepts/canton/explicit-disclosure) for your pool to send and execute transfers. The [reference EDS Docker image](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/eds.Dockerfile) supports BurnMint out of the box.
+
+### Test transactions
+
+See [CCIP on Canton — Overview](/ccip/concepts/canton/overview) for user flows. Track messages in [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+For Registry-issued tokens, also complete [`SetBurnMintFactory`](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide) with your `AllocationFactory` contract ID.
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/cross-chain-tokens/index.mdx b/src/content/ccip/tutorials/canton/cross-chain-tokens/index.mdx
new file mode 100644
index 00000000000..aa90585bb39
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/cross-chain-tokens/index.mdx
@@ -0,0 +1,105 @@
+---
+section: ccip
+date: Last Modified
+title: "Cross-Chain Token (CCT) — Canton"
+metadata:
+  description: "Deploy and register CCIP token pools on Canton for cross-chain token transfers using the starter kit or Ledger API."
+  excerpt: "CCIP Canton CCT, token pools, Registry issuer, BurnMint, LockRelease, Token Admin Registry, starter kit"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-06"
+isIndex: true
+whatsnext:
+  "Registry Issuer Guide": "/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide"
+  "Token pool concepts": "/ccip/concepts/canton/token-pools"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+Connect a Canton instrument to CCIP by deploying a token pool, registering on the Token Admin Registry (TAR), and enabling a cross-chain lane.
+
+<Aside type="note" title="Testnet only">
+
+Starter kit `cct:*` scripts target **Canton testnet** only.
+
+</Aside>
+
+## Choose your guide
+
+| Guide                                                                                                  | When to use                                                              |
+| :----------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------- |
+| [Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide)               | Issue a new token via Digital Asset Registry and connect CCIP end to end |
+| [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)       | Existing CIP-56 instrument with burn/mint authority                      |
+| [LockRelease Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool) | Fixed-supply instrument with transfer pre-approvals                      |
+
+## Starter kit (`cct:*` scripts)
+
+The [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) automates pool deployment and TAR registration on Canton testnet. Each BurnMint and LockRelease guide includes **Starter kit** and **Manual** paths for those steps.
+
+### Setup
+
+1. Clone and install:
+
+   ```bash filename="Terminal"
+   git clone https://github.com/smartcontractkit/ccip-starter-kit-canton.git
+   cd ccip-starter-kit-canton
+   npm install
+   ```
+
+2. Configure environment — follow [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) for `.env`, `canton-config.json`, and ledger auth.
+
+3. In `config/canton-config.json`, set **`party`** (pool owner/admin) and **`transferInstructionUrl`** (your validator API) — see [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites#understanding-canton-configuration-canton-configjson).
+
+### Scripts
+
+| Script                  | Command                           | What it does                                                                                                                                                                                    |
+| :---------------------- | :-------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Deploy BurnMint pool    | `npm run cct:deploy-burn-mint`    | Creates a [`BurnMintTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/burn-mint-token-pool/daml/CCIP/BurnMintTokenPoolV2.daml) on-ledger          |
+| Deploy LockRelease pool | `npm run cct:deploy-lock-release` | Creates a [`LockReleaseTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/lock-release-token-pool/daml/CCIP/LockReleaseTokenPoolV2.daml) on-ledger |
+| Register on TAR         | `npm run cct:set-token`           | Runs `ProposeAdministrator` → `AcceptAdminRole` → `SetPool` on the Token Admin Registry                                                                                                         |
+
+### Typical flow (BurnMint)
+
+```bash filename="Terminal"
+# 1. Deploy pool
+npm run cct:deploy-burn-mint -- \
+  --instanceId acme-eur-bm-pool \
+  --instrument 'yourParty::1220…::token-id'
+
+# 2. Register on TAR (poolOwner defaults to party in canton-config.json)
+npm run cct:set-token -- \
+  --instrument 'yourParty::1220…::token-id' \
+  --poolInstanceId acme-eur-bm-pool
+
+# 3. Enable lane — manual Ledger API (see guide Step 3)
+```
+
+<Aside type="note" title="Script scope">
+
+Starter kit scripts cover **pool creation** and **TAR registration** only. You still configure **rate limiters**, **`ApplyChainUpdates`**, **LockRelease liquidity and pre-approval**, **EDS**, and **lane validation** manually — each guide documents those steps.
+
+</Aside>
+
+## On-ledger checklist (all guides)
+
+Every CCT deployment ends with the same verification path:
+
+1. Pool deployed at `{instanceId}@{poolOwner}` with the correct `InstrumentId`.
+2. TAR maps the instrument to your pool; your party is token admin.
+3. Lane enabled — three rate limiters plus `ApplyChainUpdates` on the pool.
+4. [Explicit Disclosure Service](/ccip/concepts/canton/explicit-disclosure) running for your pool operator.
+5. Test transfers — see [CCIP on Canton — Overview](/ccip/concepts/canton/overview) and [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+Cross-chain send and receive are validated by Chainlink operations once your token is registered and lanes are configured.
+
+## Prerequisites (all CCT guides)
+
+- [Starter kit setup](/ccip/tutorials/canton/source/prerequisites) for `cct:*` scripts (`.env`, `canton-config.json`, ledger auth)
+- The token pool DAR for your pool type on your participant — [`ccip-burn-mint-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-burn-mint-token-pool-1.0.0.dar) or [`ccip-lock-release-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-lock-release-token-pool-1.0.0.dar) (each bundles its CCIP dependencies — the only DAR you upload).
+- CCIP contract references from Chainlink ops (owner party, TAR, RMNRemote, FeeQuoter) — EDS and indexer URLs are pre-filled in the starter kit
+- A validator user with `can_act_as` rights for your ledger parties
+- Understanding of [token pools](/ccip/concepts/canton/token-pools) and [explicit disclosure](/ccip/concepts/canton/explicit-disclosure)
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool.mdx b/src/content/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool.mdx
new file mode 100644
index 00000000000..d90f08ea178
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool.mdx
@@ -0,0 +1,290 @@
+---
+section: ccip
+date: Last Modified
+title: "LockRelease Token Pool Deployment (Canton)"
+metadata:
+  description: "Deploy a CCIP LockRelease token pool on Canton for fixed-supply CIP-56 instruments, register on TAR, and enable a cross-chain lane."
+  excerpt: "CCIP Canton LockRelease token pool, pre-approval, TAR registration, starter kit, cct scripts"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-06"
+  difficulty: "advanced"
+  estimatedTime: "45 minutes"
+whatsnext:
+  "Explicit Disclosure API": "/ccip/concepts/canton/explicit-disclosure"
+  "BurnMint alternative": "/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool"
+  "Token pool concepts": "/ccip/concepts/canton/token-pools"
+---
+
+import { Aside } from "@components"
+import { Tabs } from "@components/Tabs"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+Deploy a **LockRelease** token pool on Canton, fund pool-owner liquidity, register on the Token Admin Registry (TAR), and enable a cross-chain lane. Use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) for pool deployment and TAR registration, or submit Ledger API commands directly.
+
+This guide assumes you have a token instrument live on Canton with supply minted on-ledger, supporting the CIP-56 `TransferFactory` interface and transfer pre-approvals.
+
+**LockRelease** is for **fixed total supply** tokens where cross-chain transfers are backed by locked liquidity — not mint/burn. On send, tokens lock to the pool owner; on receive, the pool releases from its holdings.
+
+**Scope:** Deploy pool, fund liquidity, register on TAR, enable a lane. Excludes [EDS setup](/ccip/concepts/canton/explicit-disclosure) and end-to-end transfer tests.
+
+<Aside type="note" title="Testnet only">
+
+Starter kit `cct:*` scripts target **Canton testnet** only.
+
+</Aside>
+
+## Prerequisites
+
+- **Instrument (token managed on Canton Ledger)** with known `InstrumentId = { admin, id }` supporting `TransferFactory` and pre-approvals.
+- Token liquidity held by the pool owner party for expected release volume.
+- **LockRelease token pool DAR** on your participant — [`ccip-lock-release-token-pool-1.0.0.dar`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/dars/legacy/ccip-lock-release-token-pool-1.0.0.dar) (bundles its CCIP dependencies — the only DAR you upload).
+- CCIP contract references from Chainlink ops.
+- **Starter kit setup** (if using `cct:*` scripts) — complete [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) and the [CCT overview](/ccip/tutorials/canton/cross-chain-tokens#starter-kit-cct-scripts).
+
+<Aside type="caution" title="Pool owner trust">
+
+CCIP fully trusts the pool owner. Strongly recommend pool owner equals instrument admin, decentralized across nodes.
+
+</Aside>
+
+## Deployment overview
+
+| Step | Action                           | Starter kit               | Manual                              |
+| :--- | :------------------------------- | :------------------------ | :---------------------------------- |
+| 1    | Deploy `LockReleaseTokenPool`    | `cct:deploy-lock-release` | Ledger API `CreateCommand`          |
+| 2    | Fund holdings + set pre-approval | —                         | Ledger API choices                  |
+| 3    | Register on TAR                  | `cct:set-token`           | TAR choices via Ledger API          |
+| 4    | Enable lane                      | —                         | Rate limiters + `ApplyChainUpdates` |
+| 5    | Go live                          | —                         | EDS + verification                  |
+
+## Step 1 — Deploy the LockRelease Token Pool
+
+Create one [`LockReleaseTokenPool`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/lock-release-token-pool/daml/CCIP/LockReleaseTokenPoolV2.daml). Signatory: `poolOwner`.
+
+<Tabs client:visible>
+  <Fragment slot="tab.1">Starter kit</Fragment>
+  <Fragment slot="tab.2">Manual</Fragment>
+  <Fragment slot="panel.1">
+
+```bash filename="Terminal"
+npm run cct:deploy-lock-release -- \
+  --instanceId acme-eur-lr-pool \
+  --instrument 'yourParty::1220…::token-id'
+```
+
+**Flags:**
+
+| Flag           | Required | Description                                                                   |
+| :------------- | :------- | :---------------------------------------------------------------------------- |
+| `--instanceId` | Yes      | Unique pool instance ID (e.g. `acme-eur-lr-pool`)                             |
+| `--instrument` | Yes      | Canton instrument ID: `party::fingerprint::tokenId`                           |
+| `--poolOwner`  | No       | Party that holds pool liquidity (defaults to `party` in `canton-config.json`) |
+| `--ccipOwner`  | No       | Defaults to `ccipParty` in `canton-config.json`                               |
+| `--decimals`   | No       | Token decimals on Canton (default `10`)                                       |
+
+**Expected output:**
+
+```text
+Deploying LockRelease token pool on Canton
+   instanceId: acme-eur-lr-pool
+   instrument: yourParty::1220…::token-id
+   poolOwner:  yourParty::1220…
+✅ LockReleaseTokenPool contract ID: 00abc…
+   Pool address: acme-eur-lr-pool@yourParty::1220…
+
+Next steps:
+   1. Fund the pool owner with token liquidity
+   2. Set the pool receive preapproval (AddPoolReceiveContextContractValue)
+   3. Register on the Token Admin Registry:
+      npm run cct:set-token -- --instrument "…" --poolInstanceId "acme-eur-lr-pool" --poolOwner "…"
+```
+
+  </Fragment>
+  <Fragment slot="panel.2">
+
+| Argument                  | Guidance                                           |
+| :------------------------ | :------------------------------------------------- |
+| `instanceId`              | Unique string, e.g. `acme-eur-lr-pool`             |
+| `poolOwner`               | Recommended: instrument admin                      |
+| `ccipOwner`               | Chainlink CCIP owner party                         |
+| `instrumentId`            | Underlying asset `InstrumentId`                    |
+| `decimals`                | `10`                                               |
+| `rateLimitAdmin`          | Optional                                           |
+| `remoteChainConfigs`      | Empty — configure via `ApplyChainUpdates` (Step 4) |
+| `tokenTransferFeeConfigs` | Optional per-destination fees                      |
+| `poolReceiveContext`      | Empty at creation — set preapproval in Step 2      |
+| `transferTimeout`         | `Indefinite`                                       |
+| `deps`                    | `tokenAdminRegistry`, `rmnRemote`, `feeQuoter`     |
+
+After creation, pool address: `{instanceId}@{poolOwner}`.
+
+  </Fragment>
+</Tabs>
+
+### Transfer-fee fields
+
+When setting `tokenTransferFeeConfigs` (map keyed by destination chain selector):
+
+| Field               | Meaning                                                 |
+| :------------------ | :------------------------------------------------------ |
+| `isEnabled`         | Must be `true` to apply the config                      |
+| `feeUSDCents`       | Flat fee in USD cents (non-negative)                    |
+| `destGasOverhead`   | Gas for destination execution (> 0 when set via choice) |
+| `destBytesOverhead` | Data-availability bytes overhead (≥ 32)                 |
+| `feeBps`            | Proportional fee in basis points (< 10000)              |
+
+### CCIP hosted addresses
+
+| Field                     | Testnet                                                                                                    | Mainnet                                                                                                                |
+| :------------------------ | :--------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
+| Token Admin Registry      | `tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551` | Contact the [CCIP team](https://chain.link/ccip-contact) for the Token Admin Registry address to register a token pool |
+| RMNRemote                 | `rmn_remote-nzvtd@rmnOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `rmn_remote-mnprd@rmnOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| FeeQuoter                 | `feequoter-scxln@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`          | `feequoter-fpxih@ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                      |
+| CCIP owner party          | `ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`                          | `ccipOwner::122012714685760dc1927c4cfe119ce2126c48756154e95c06f5c181da05a5519093`                                      |
+| Global EDS                | `https://eds.testnet.ccip.chain.link`                                                                      | `https://eds.ccip.chain.link`                                                                                          |
+| Indexer                   | `https://indexer-1.testnet.ccip.chain.link`                                                                | Primary: `https://indexer-1.ccip.chain.link` · Backup: `https://indexer-2.ccip.chain.link`                             |
+| Canton chain selector     | `9268731218649498074`                                                                                      | `2308837218439511688`                                                                                                  |
+| Default CommitteeVerifier | `committeeverifier-tqkny@ccvOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551`   | `committeeverifier-mnprd@ccvOwner::122096accf0a84fc7d80d5fce5ea3135317a03eb22e62e0d8cdd7548865f984f11ff`               |
+
+## Step 2 — Fund the pool and configure pre-approval
+
+LockRelease liquidity comes from the **pool owner's token holdings**. Top up those holdings to match expected outbound volume — there is no separate on-pool deposit step. When a receiver executes an inbound transfer on Canton, tokens move from the pool owner's holdings to the recipient.
+
+<Aside type="note" title="Manual step">
+
+The starter kit does not automate funding or pre-approval. Complete this step via the Ledger API before registering on TAR.
+
+</Aside>
+
+### Set pool receive preapproval
+
+Record the token's transfer preapproval in `poolReceiveContext` so inbound transfers to the pool owner succeed atomically on send:
+
+```shell
+curl --request POST \
+  --url https://<your-participant>/api/json/v2/commands/submit-and-wait-for-transaction-tree \
+  --header "authorization: Bearer $JWT" \
+  --header 'content-type: application/json' \
+  --data '{
+  "commands": [
+    {
+      "ExerciseCommand": {
+        "templateId": "#ccip-lock-release-token-pool:CCIP.LockReleaseTokenPool:LockReleaseTokenPool",
+        "contractId": "<POOL_CONTRACT_ID>",
+        "choice": "AddPoolReceiveContextContractValue",
+        "choiceArgument": {
+          "contextKey": "transfer-preapproval",
+          "referredContract": "<PREAPPROVAL_CONTRACT_ID>"
+        }
+      }
+    }
+  ],
+  "commandId": "set-pool-receive-preapproval",
+  "actAs": ["<POOL_OWNER_PARTY>"]
+}'
+```
+
+| Field              | Value                                                        |
+| :----------------- | :----------------------------------------------------------- |
+| `contextKey`       | Key the TransferFactory expects, e.g. `transfer-preapproval` |
+| `referredContract` | ContractId of the pool owner's transfer preapproval          |
+
+Related choices: `AddPoolReceiveContextNonContractValue`, `RemovePoolReceiveContextValue`, `ClearPoolReceiveContext`.
+
+## Step 3 — Register on the Token Admin Registry
+
+TAR maps each instrument to a single token pool. Registration: **propose → accept → set pool**.
+
+<Tabs client:visible>
+  <Fragment slot="tab.1">Starter kit</Fragment>
+  <Fragment slot="tab.2">Manual</Fragment>
+  <Fragment slot="panel.1">
+
+```bash filename="Terminal"
+npm run cct:set-token -- \
+  --instrument 'yourParty::1220…::token-id' \
+  --poolInstanceId acme-eur-lr-pool
+```
+
+Use the same flags as [BurnMint Step 2](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool#step-2--register-on-the-token-admin-registry). The script runs `ProposeAdministrator` → `AcceptAdminRole` → `SetPool` and prints ledger update links on success.
+
+  </Fragment>
+  <Fragment slot="panel.2">
+
+### Fetch TAR explicit disclosure
+
+```shell
+curl --request POST \
+  --url https://eds.testnet.ccip.chain.link/ccip/v1/global/disclosure/batch \
+  --header 'content-type: application/json' \
+  --data '{
+  "addresses": [
+    "tokenadminregistry-lzrnd@ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551"
+  ]
+}'
+```
+
+Include disclosed contracts in subsequent ledger submissions. OpenAPI: [`eds-global.yaml`](https://github.com/smartcontractkit/chainlink-canton/blob/main/openapi/src/eds/global/eds-global.yaml).
+
+### TAR choices
+
+1. **`ProposeAdministrator`** — CCIP owner or instrument admin. Pass `instrumentId`, `newAdmin`, `caller`. For new instruments, leave `tokenConfigCid` as `None`. Returns `TokenConfig` CID for next steps.
+2. **`AcceptAdminRole`** — Proposed admin exercises with `tokenConfigCid`, `instrumentId`, `caller`.
+3. **`SetPool`** — Admin links instrument to pool via `PoolRegistration` (`poolOwner`, `poolInstanceId` from Step 1).
+
+Admin role can be transferred with `TransferAdminRole` → `AcceptAdminRole`.
+
+  </Fragment>
+</Tabs>
+
+## Step 4 — Enable a lane
+
+Lane enablement is **not** automated by the starter kit.
+
+### 1. Deploy three rate limiters
+
+Each lane requires [`RateLimiter`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/rate-limiter/daml/CCIP/RateLimiterV2.daml) contracts (for testing, deploy disabled with zero capacity/rate):
+
+- **Inbound (default finality)**
+- **Inbound (custom finality)**
+- **Outbound**
+
+Created by `poolOwner` with matching `poolInstanceId`, `poolOwner`, and `remoteChainSelector`.
+
+### 2. Apply the chain update
+
+Call [`ApplyChainUpdates`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/pools/lock-release-token-pool/daml/CCIP/LockReleaseTokenPoolV2.daml) on the pool:
+
+| ChainUpdate field                            | Guidance                                                                   |
+| :------------------------------------------- | :------------------------------------------------------------------------- |
+| `remoteChainSelector`                        | Destination chain selector — see [CCIP Directory](/ccip/directory/testnet) |
+| `remotePools`                                | Remote token pool address(es)                                              |
+| `remoteTokenAddress`                         | Remote token address                                                       |
+| `inboundCCVs` / `outboundCCVs`               | Default CommitteeVerifier (testnet address above) unless custom            |
+| `finalityConfig`                             | `WaitForFinality` for default finalized source tx                          |
+| `inboundRateLimiter`                         | Inbound default limiter CID                                                |
+| `inboundCustomBlockConfirmationsRateLimiter` | Inbound custom limiter CID                                                 |
+| `outboundRateLimiter`                        | Outbound limiter CID                                                       |
+
+Once applied, the on-ledger lane is complete.
+
+## Step 5 — Go live
+
+### Verification checklist
+
+1. TAR maps instrument to pool with your party as admin.
+2. Pool at `{instanceId}@{poolOwner}` with matching `InstrumentId`.
+3. Pool owner holds sufficient liquidity; receive preapproval set in `poolReceiveContext`.
+4. Lane rate limiters in place.
+
+### Stand up EDS
+
+The [reference EDS](https://github.com/smartcontractkit/chainlink-canton/blob/main/eds/eds.Dockerfile) supports LockRelease, including holdings and TransferFactory context for pre-approvals.
+
+### Test transactions
+
+See [CCIP on Canton — Overview](/ccip/concepts/canton/overview) and [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide.mdx b/src/content/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide.mdx
new file mode 100644
index 00000000000..aa677a80f0c
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide.mdx
@@ -0,0 +1,401 @@
+---
+section: ccip
+date: Last Modified
+title: "Registry Issuer Guide (Canton)"
+metadata:
+  description: "Issue a token through Digital Asset Registry on Canton and connect it to Chainlink CCIP for cross-chain transfers."
+  excerpt: "Canton Registry CCIP, issuer guide, BurnMint token pool, TAR, AllocationFactory, canton-registry-kit, cct scripts, institutional tokens"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-06"
+  difficulty: "advanced"
+  estimatedTime: "2 hours"
+whatsnext:
+  "BurnMint pool reference": "/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool"
+  "Token pools": "/ccip/concepts/canton/token-pools"
+  "Explicit Disclosure API": "/ccip/concepts/canton/explicit-disclosure"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+**Audience:** Engineers who understand Canton and want to issue a token through Digital Asset's Registry utility and connect it to Chainlink CCIP.
+
+**Outcome:** A live Registry instrument on Canton, initial token supply on-ledger, a registrar-owned CCIP BurnMint token pool, and registration in the Token Admin Registry (TAR) so Chainlink can bridge the token once lane configuration is complete.
+
+## 1. Overview
+
+Two on-ledger systems connect at a single **instrument identity**:
+
+| Layer              | Purpose                                                  | Analog                               |
+| :----------------- | :------------------------------------------------------- | :----------------------------------- |
+| **DA Registry**    | Who may issue this token and how much exists on Canton   | Transfer agent + securities registry |
+| **Chainlink CCIP** | How this Canton token enters and exits cross-chain lanes | Bridge + router + token pool         |
+
+**Flow:** Provider onboards Registrar → Registrar creates instrument and mints → Registrar deploys CCIP BurnMint pool → TAR links instrument to pool → Chainlink ops validates cross-chain lanes.
+
+### Critical identity rule
+
+CCIP identifies your token with an **InstrumentId**:
+
+```
+InstrumentId = { admin: <registrar party>, id: "<your instrument string>" }
+```
+
+The `admin` field **must** be your **registrar** party. Wrong party → TAR and pool will not recognize your token.
+
+### What Chainlink ops handles
+
+This guide covers **issuer/registrar** steps only. Chainlink operations must have deployed CCIP core contracts, configured lanes, and provided contract references before you begin. Cross-chain send/receive (`CCIPSender.Send`, `CCIPReceiver.Execute`) are validated separately once your token is registered.
+
+## 2. Parties and roles
+
+| Party           | Organization              | Role in this guide                                                   |
+| :-------------- | :------------------------ | :------------------------------------------------------------------- |
+| **DA Operator** | Digital Asset             | Accepts Provider onboarding; Operator Backend for context/disclosure |
+| **Provider**    | Token program owner (you) | Onboards registrars; credential requirements                         |
+| **Registrar**   | Transfer agent / treasury | Creates instrument, mints, owns CCIP pool, TAR admin                 |
+| **Issuer**      | Mint requester (optional) | Requests mint when credentials apply                                 |
+| **Holder**      | Investor / end user       | Holds balances — no Registry service onboarding required             |
+| **CCIP owner**  | Chainlink                 | Owns TAR, OnRamp, OffRamp, shared CCIP infrastructure                |
+
+**Recommended:** three parties under your org — Provider, Registrar, Holder — plus Chainlink's CCIP owner on the participant.
+
+Registry onboarding: [DA Registry onboarding guide](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/onboarding-offboarding.html).
+
+## 3. Prerequisites
+
+### 3.1 Values from Chainlink ops
+
+| Value                               | Used for                              |
+| :---------------------------------- | :------------------------------------ |
+| CCIP owner party ID                 | TAR `ProposeAdministrator`            |
+| TokenAdminRegistry contract ID      | TAR exercises                         |
+| RMNRemote / FeeQuoter addresses     | Pool dependencies                     |
+| Remote chain selector               | Pool `RemoteChainConfig`              |
+| Remote pool / token addresses (hex) | Pool lane config                      |
+| EDS and indexer URLs                | Disclosures and proofs for CCIP lanes |
+
+### 3.2 Values from your participant operator
+
+| Value                            | Used for                                                                                      |
+| :------------------------------- | :-------------------------------------------------------------------------------------------- |
+| Ledger JSON API URL              | All ledger submissions                                                                        |
+| Validator user with `can_act_as` | Acts on behalf of Provider, Registrar, optional Issuer/Holder — do not use shared admin users |
+| DA Operator party ID             | Registry onboarding                                                                           |
+
+### 3.3 Values you choose
+
+| Value                     | Guidance                                  |
+| :------------------------ | :---------------------------------------- |
+| Instrument ID             | Short uppercase, e.g. `ACME-USD`          |
+| Pool instance ID          | e.g. `acme-usd-ccip-pool`                 |
+| Rate limiter instance IDs | Inbound default, inbound custom, outbound |
+| Initial mint amount       | e.g. `1000000.0`                          |
+
+### 3.4 Environment requirements
+
+Devnet, testnet, and mainnet are **provisioned by operators**. Issuers do **not** upload DAR packages.
+
+| Responsibility                   | Provider                  | What you get                                |
+| :------------------------------- | :------------------------ | :------------------------------------------ |
+| Registry utility DARs (≥ 0.12.5) | Participant / DA operator | Registry template code on-ledger            |
+| CCIP DAR packages                | Chainlink ops             | TAR, pools, OnRamp, OffRamp templates       |
+| Registry choice context          | DA Operator Backend       | `extraArgs.context`, `disclosedContracts`   |
+| CCIP choice context              | CCIP EDS                  | Disclosures for TAR, pool, router exercises |
+
+**DARs vs disclosures:** DARs must exist before contracts can be created (infrastructure). Disclosures are fetched at request time for contracts your party is not a stakeholder on — include them in JSON API submissions.
+
+### 3.5 Optional tooling — `canton-registry-kit`
+
+Chainlink provides a CLI automating many Registry and TAR steps on devnet. Every automated step maps to an on-ledger exercise documented below.
+
+Example `registry-kit.toml`:
+
+```toml
+network = "devnet-cv1"
+
+[ledger]
+json_api_url = "https://<your-participant>/api/json"
+grpc_ledger_api_url = "<your-participant>:443"
+admin_api_url = "<your-participant>:443"
+user_id = "your-ledger-user-id"
+synchronizer_id = "global-domain::1220..."
+
+[ledger.auth]
+type = "authorizationCode"
+auth_url = "https://your-idp/oauth2/default"
+client_id = "your-oauth-client-id"
+
+[parties]
+operator = "operator-party::1220..."
+provider = "provider-party::1220..."
+registrar = "registrar-party::1220..."
+
+[ccip]
+token_admin_registry_cid = "00..."
+ccip_party = "ccip-owner-party::1220..."
+burn_mint_pool_instance_id = "your-pool-instance-id"
+
+[operator_backend]
+base_url = "https://api.utilities.digitalasset-dev.com/api/utilities"
+```
+
+Global flags: `canton-registry-kit --config registry-kit.toml [--state registry-kit.state.json]`
+
+## 4. End-to-end workflow
+
+| Phase                   | Steps | Actor                    |
+| :---------------------- | :---- | :----------------------- |
+| A — Registry onboarding | 1–6   | Provider (+ DA Operator) |
+| B — Instrument and mint | 7–9   | Registrar                |
+| C — CCIP pool deploy    | 10–13 | Registrar (pool owner)   |
+| D — TAR registration    | 14–17 | CCIP owner + Registrar   |
+| E — Verification        | 18    | Registrar                |
+
+Hand off to Chainlink ops for lane testing after Phase E.
+
+## 5. Phase A — Registry onboarding
+
+Request/accept workflow on-ledger. UI walkthrough: [DA issuance onboarding tutorial](https://docs.digitalasset.com/utilities/mainnet/tutorials/issuance/1-onboarding.html).
+
+### Step 1 — Verify environment
+
+```shell
+canton-registry-kit onboarding check-packages
+```
+
+If packages missing, contact participant operator — do not upload DARs unless you operate the validator.
+
+### Step 2 — Request Provider service
+
+| Field     | Value                                                |
+| :-------- | :--------------------------------------------------- |
+| Template  | `ProviderServiceRequest`                             |
+| Create as | Provider                                             |
+| Fields    | `operator` = DA Operator, `provider` = your Provider |
+
+CLI: `canton-registry-kit onboarding request-provider-service`
+
+### Step 3 — Wait for Provider acceptance
+
+DA Operator exercises `ProviderServiceRequest_Accept` → creates `ProviderService`.
+
+CLI: `canton-registry-kit onboarding wait-provider-service --timeout 15m`
+
+### Step 4 — Create Provider configuration
+
+Choice: `ProviderService_CreateProviderConfiguration` (Provider). Use empty `registrarRequirements` / `holderRequirements` for simplest path.
+
+### Step 5 — Request Registrar service
+
+Template: `RegistrarServiceRequest` (Provider). Set `createAllocationFactory = true`, `createTransferRule = true`.
+
+The `AllocationFactory` implements Splice `BurnMintFactory` — CCIP uses it for burn/mint on Registry holdings.
+
+### Step 6 — Accept Registrar service
+
+Choice: `ProviderService_AcceptRegistrarServiceRequest` → creates `RegistrarService`, **`AllocationFactory`**, `TransferRule`.
+
+CLI (Steps 4–6): `canton-registry-kit onboarding onboard-registrar`
+
+**Record:** `RegistrarService`, `AllocationFactory`, `TransferRule` CIDs.
+
+Inspect: `canton-registry-kit onboarding discover-registry-factories`
+
+## 6. Phase B — Create instrument and mint
+
+Registry **0.12.5+** uses AllocationFactory two-step mint (`RequestMint` → `Accept`).
+
+### Step 7 — Create instrument
+
+Choice: `RegistrarService_CreateInstrumentConfiguration` (Registrar). `instrumentId` e.g. `ACME-USD`.
+
+Your CCIP InstrumentId: `{ admin: <registrar>, id: "ACME-USD" }`
+
+CLI: `canton-registry-kit issuer create-instrument ACME-USD`
+
+### Step 8 — Request mint
+
+Choice: `AllocationFactory_RequestMint`. Fetch Operator Backend context first:
+
+```
+POST {operator_backend}/v0/registry/mint/v0/request
+Body: { "holder": "<holder>", "instrumentId": { "admin": "<registrar>", "id": "ACME-USD" } }
+```
+
+Include `choiceContextData` and `disclosedContracts` in ledger submission.
+
+CLI: `canton-registry-kit issuer mint --amount 1000000.0 --holder <holder-party>`
+
+### Step 9 — Accept mint
+
+Choice: `MintRequest_Accept` with Operator Backend context:
+
+```
+POST {operator_backend}/v0/registry/mint/v0/request/{mintRequestCid}/choice-contexts/accept
+```
+
+CLI: `canton-registry-kit issuer accept-mint`
+
+Verify: `canton-registry-kit issuer query-supply`
+
+## 7. Phase C — Deploy CCIP token pool
+
+Deploy rate limiters first, then the BurnMint pool. For **pool creation** on Canton testnet, you can use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) (`cct:deploy-burn-mint`) or submit Ledger API commands directly — see [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool).
+
+### Steps 10–12 — Rate limiters
+
+Deploy three [`RateLimiter`](https://github.com/smartcontractkit/chainlink-canton/blob/main/contracts/ccip/rate-limiter/daml/CCIP/RateLimiterV2.daml) contracts:
+
+- Inbound, `mode = DefaultFinality`
+- Inbound, `mode = CustomFinality`
+- Outbound
+
+### Step 13 — Deploy BurnMintTokenPool
+
+| Field                          | Value                                  |
+| :----------------------------- | :------------------------------------- |
+| `instanceId`                   | e.g. `acme-usd-ccip-pool`              |
+| `poolOwner`                    | Registrar                              |
+| `ccipOwner`                    | From Chainlink ops                     |
+| `instrumentId`                 | `{ admin: registrar, id: "ACME-USD" }` |
+| `decimals`                     | `10`                                   |
+| `deps.*`                       | TAR, RMNRemote, FeeQuoter bindings     |
+| `remoteChainConfigs[selector]` | Remote pool/token addresses from ops   |
+
+Record pool address `{poolInstanceId}@{registrarParty}` and all rate limiter CIDs.
+
+**Starter kit (testnet):**
+
+```bash filename="Terminal"
+npm run cct:deploy-burn-mint -- \
+  --instanceId acme-usd-ccip-pool \
+  --instrument 'registrarParty::1220…::ACME-USD' \
+  --poolOwner 'registrarParty::1220…'
+```
+
+Full field reference and manual Ledger API path: [BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool).
+
+## 8. Phase D — Register in Token Admin Registry
+
+### Steps 14–16 — Propose, accept, set pool
+
+| Step | Choice                 | Act as     |
+| :--- | :--------------------- | :--------- |
+| 14   | `ProposeAdministrator` | CCIP owner |
+| 15   | `AcceptAdminRole`      | Registrar  |
+| 16   | `SetPool`              | Registrar  |
+
+Steps 15–16 require TAR disclosed to registrar (CCIP EDS or starter kit).
+
+**Starter kit (testnet):**
+
+```bash filename="Terminal"
+npm run cct:set-token -- \
+  --instrument 'registrarParty::1220…::ACME-USD' \
+  --poolInstanceId acme-usd-ccip-pool \
+  --poolOwner 'registrarParty::1220…' \
+  --proposeCaller 'ccipOwner::1220…'
+```
+
+**Registry kit alternative:** `canton-registry-kit operator link-token-to-pool`
+
+### Step 17 — SetBurnMintFactory (required)
+
+**Mandatory** for Registry tokens — links TAR to your `AllocationFactory` from Step 6.
+
+| Field             | Value                                      |
+| :---------------- | :----------------------------------------- |
+| Choice            | `SetBurnMintFactory` on TokenAdminRegistry |
+| Act as            | Registrar                                  |
+| `burnMintFactory` | **AllocationFactory CID** from Step 6      |
+
+Without this, cross-chain transfers fail at execution. CCIP EDS assembles Registry-specific pool context at runtime.
+
+Reference: [DA burn-mint how-to](https://docs.digitalasset.com/utilities/mainnet/how-tos/registry/burn-mint/burn-mint.html).
+
+## 9. Phase E — Verification
+
+```shell
+canton-registry-kit operator validate
+```
+
+| Check               | How                                                            |
+| :------------------ | :------------------------------------------------------------- |
+| Instrument identity | `InstrumentId.admin` = registrar; `id` matches Registry config |
+| Holdings            | Active `Holding`(s); supply matches mint                       |
+| TAR mapping         | `TokenConfig` references your pool and registrar as admin      |
+| Factory link        | `TokenConfig.burnMintFactory` = AllocationFactory CID          |
+| Pool active         | `BurnMintTokenPool` at `{poolInstanceId}@{registrarParty}`     |
+
+## 10. CLI command reference
+
+All commands: `--config registry-kit.toml [--state registry-kit.state.json]`
+
+### Onboarding
+
+| Command                                  | Description                                                  |
+| :--------------------------------------- | :----------------------------------------------------------- |
+| `onboarding check-packages`              | Verify Registry DARs (read-only)                             |
+| `onboarding request-provider-service`    | Submit ProviderServiceRequest                                |
+| `onboarding wait-provider-service`       | Poll until DA accepts                                        |
+| `onboarding onboard-registrar`           | ProviderConfiguration + RegistrarService + AllocationFactory |
+| `onboarding discover-registry-factories` | List Registry contracts for registrar                        |
+
+### Issuer
+
+| Command                                       | Description                      |
+| :-------------------------------------------- | :------------------------------- |
+| `issuer create-instrument <ID>`               | Create InstrumentConfiguration   |
+| `issuer mint --amount <N> [--holder <party>]` | RequestMint via Operator Backend |
+| `issuer accept-mint`                          | AcceptMint                       |
+| `issuer query-supply`                         | Sum Holding balances             |
+
+### Operator (CCIP linking)
+
+| Command                       | Description                                      |
+| :---------------------------- | :----------------------------------------------- |
+| `operator link-token-to-pool` | ProposeAdministrator → AcceptAdminRole → SetPool |
+| `operator validate`           | Read-only TAR and instrument checks              |
+
+### CLI gaps (Ledger API only)
+
+- Deploy RateLimiter contracts
+- Deploy BurnMintTokenPool
+- `SetBurnMintFactory`
+
+## 11. Troubleshooting
+
+| Symptom                      | Cause                             | Resolution                                                                                                                                                 |
+| :--------------------------- | :-------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mint credential error        | Missing issuer credentials        | Issue per [DA credential docs](https://docs.digitalasset.com/utilities/mainnet/overview/credential-user-guide/introduction.html) or use empty requirements |
+| Bridge fails after SetPool   | `SetBurnMintFactory` not called   | Exercise Step 17 with AllocationFactory CID                                                                                                                |
+| Pool doesn't recognize token | Wrong `InstrumentId.admin`        | Must be registrar, not Provider or CCIP owner                                                                                                              |
+| Registry choice fails        | Missing Operator Backend context  | Call Operator Backend before submission                                                                                                                    |
+| Missing utility packages     | Participant not provisioned       | Contact operator                                                                                                                                           |
+| TAR exercise fails           | TAR not disclosed                 | Use CCIP EDS or `link-token-to-pool`                                                                                                                       |
+| 403 from Ledger API          | User lacks `can_act_as` for party | Use a validator user scoped to your parties                                                                                                                |
+
+## 12. Glossary
+
+| Term                   | Definition                                               |
+| :--------------------- | :------------------------------------------------------- |
+| **InstrumentId**       | CCIP token ID: `{ admin: party, id: string }`            |
+| **Holding**            | Registry balance record for an instrument                |
+| **AllocationFactory**  | Registry factory implementing Splice `BurnMintFactory`   |
+| **TAR**                | TokenAdminRegistry — maps instrument → pool + admin      |
+| **EDS**                | Chainlink Execution Disclosure Service                   |
+| **Disclosed contract** | Contract blob in submission for non-stakeholder exercise |
+
+## 13. Further reading
+
+| Topic                      | Link                                                                                                                  |
+| :------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
+| Registry introduction      | [Registry user guide](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/introduction.html) |
+| Token Standard integration | [Token Standard](https://docs.digitalasset.com/utilities/mainnet/overview/registry-user-guide/token-standard.html)    |
+| Issuance tutorial          | [Issuance onboarding](https://docs.digitalasset.com/utilities/mainnet/tutorials/issuance/1-onboarding.html)           |
+| Utility DAR versions       | [DAR versions](https://docs.digitalasset.com/utilities/mainnet/reference/dar-versions/dar-versions.html)              |
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/destination/arbitrary-messaging.mdx b/src/content/ccip/tutorials/canton/destination/arbitrary-messaging.mdx
new file mode 100644
index 00000000000..bfc573deede
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/destination/arbitrary-messaging.mdx
@@ -0,0 +1,165 @@
+---
+section: ccip
+date: Last Modified
+title: "Arbitrary Messaging: Canton as Destination"
+isIndex: false
+metadata:
+  description: "Send a data-only CCIP message from Ethereum Sepolia and execute it on Canton using any2canton scripts."
+  image: "/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  excerpt: "Canton as Destination, any2canton, arbitrary messaging, manual execution, CCIPReceiver"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "25 minutes"
+  difficulty: "intermediate"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+This tutorial demonstrates how to send arbitrary data from Ethereum Sepolia to Canton and **execute** the message on Canton using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+
+Complete the [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites) before starting. You need Sepolia ETH for send fees and Canton ledger access for `any2canton:manual-exec`.
+
+These steps use **Canton testnet** and **Ethereum Sepolia** only.
+
+</Aside>
+
+## Introduction
+
+When Canton is the **destination** chain, the source send happens on Ethereum Sepolia and execution happens on Canton. For data-only messages:
+
+1. You call the CCIP Router on Sepolia via `any2canton:data`.
+2. CommitteeVerifier operators validate and aggregate proofs.
+3. You run `any2canton:manual-exec` to execute on Canton — the SDK finds or creates a compatible `CCIPReceiver`.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Send a data-only message from Sepolia to your Canton party with `any2canton:data`.
+- Wait for source finality and Committee Verifier proofs on the indexer.
+- Execute the message on Canton with `any2canton:manual-exec`.
+- Track progress in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+
+## Understanding Arbitrary Messaging (any2canton)
+
+Key points when Canton is the destination:
+
+- **Two-step flow**: Send on Sepolia, then manually execute on Canton (all `any2canton` tutorials use manual execution on Canton).
+- **Receiver**: Defaults to the `party` in `canton-config.json`. Override with `--cantonReceiver` on send or `--receiver` on manual exec.
+- **Finality**: Default `--finality finalized` waits for Sepolia finality before execution is allowed. Pass `--finality 32` (or another block depth) for faster-than-finality.
+- **Fee payment**: CCIP fees on Sepolia default to native ETH. Pass `--feeToken link` to pay in LINK.
+
+See the [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton) in the overview.
+
+## How the Scripts Work
+
+**`scripts/any2canton/ccipSendData.ts`**:
+
+1. Resolves the Canton receiver party from `canton-config.json`.
+2. Builds and sends a data-only CCIP message via the SDK's `sendMessage` on Sepolia.
+3. Prints the CCIP Message ID and a copy-pasteable `any2canton:manual-exec` command.
+
+**`scripts/any2canton/manualExecute.ts`**:
+
+1. Looks up the message using the **Sepolia source transaction hash** from the send output.
+2. Fetches proofs from the indexer and disclosures from Global CCIP EDS.
+3. Calls `CantonChain.execute` — the SDK resolves or creates the `CCIPReceiver` and submits to the ledger.
+
+## Running the Tutorial
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites).
+2. Confirm Sepolia ETH balance:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain sepolia --token link
+   ```
+
+## Step 1: Send from Sepolia
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton"
+```
+
+Pay fee in LINK:
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton" --feeToken link
+```
+
+Request faster execution with block-depth finality (32 confirmations):
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton" --finality 32
+```
+
+Override the Canton receiver party:
+
+```bash filename="Terminal"
+npm run any2canton:data -- --dataString "Hello Canton" --cantonReceiver 'yourParty::1220…'
+```
+
+### Expected send output
+
+```text
+📧 Sending data from Sepolia → Canton: "Hello Canton"
+   Receiver party: yourParty::1220…
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+📜 Source transaction: https://sepolia.etherscan.io/tx/0x…
+
+⚙️  Execute on Canton once the message is finalized on Sepolia:
+   npm run any2canton:manual-exec -- 0x<messageId>
+```
+
+Save the **CCIP Message ID** (`🆔 CCIP Message ID`) — or the **Sepolia source transaction hash** (`📜 Source transaction`) — from the send output for the execution step. `any2canton:manual-exec` accepts either.
+
+## Step 2: Execute on Canton
+
+Wait until the message is ready — timing depends on `--finality`:
+
+- **`finalized`** (default): Wait for Sepolia finality (often 15+ minutes).
+- **Block depth** (e.g. `32`): Wait for the specified number of Sepolia confirmations.
+
+Monitor status in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer). When proofs are on the indexer, run:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId>
+```
+
+You can pass either the **Sepolia source transaction hash** or the **CCIP Message ID** (`0x…`). They share the same `0x`+64-hex shape, so the script resolves the message from whichever matches. Examples:
+
+```bash filename="Terminal"
+# By Sepolia source transaction hash
+npm run any2canton:manual-exec -- 0x5a814d64666f60d2777c5425e8d0ea5a4b1bc9a3215eaeabced8b248050a3b99
+
+# By CCIP Message ID
+npm run any2canton:manual-exec -- 0x1220e4133ede8f2daf2e665b53321da54d1bd0b8e00fb1cece20b63079c1d48d6a5b
+```
+
+### Expected execution output
+
+```text
+⚙️  Executing on Canton (OffRamp 0x…)…
+   Resolving CCIPReceiver, fetching EDS disclosures, and submitting to the ledger — often 1–3 minutes with no further output.
+✅ Canton execution transaction: https://lighthouse.testnet.cantonloop.com/transactions/…
+```
+
+<Aside type="tip" title="Debug logging">
+
+Set `CCIP_DEBUG=1` in `.env` for step-by-step SDK logs during execution.
+
+</Aside>
+
+## Verification
+
+1. Confirm **SUCCESS** in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+2. Inspect the Canton execution transaction on [Canton Lighthouse](https://lighthouse.testnet.cantonloop.com).
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/destination/index.mdx b/src/content/ccip/tutorials/canton/destination/index.mdx
new file mode 100644
index 00000000000..496dfc06290
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/destination/index.mdx
@@ -0,0 +1,73 @@
+---
+section: ccip
+date: Last Modified
+title: "CCIP Tutorials: Canton as Destination"
+metadata:
+  description: "Send from Ethereum Sepolia and execute incoming cross-chain messages and token transfers on Canton using the CCIP Canton Starter Kit."
+  excerpt: "CCIP Canton destination, any2canton, execute on Canton, manual execution, CCIPReceiver"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-06"
+  difficulty: "intermediate"
+isIndex: true
+whatsnext:
+  "Prerequisites": "/ccip/tutorials/canton/destination/prerequisites"
+  "Token Transfers": "/ccip/tutorials/canton/destination/token-transfers"
+  "Cross-chain overview": "/ccip/concepts/canton/overview"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+**Canton as Destination** (`any2canton`) tutorials cover receiving on Canton — Ethereum Sepolia is the source in the starter kit, Canton is the destination.
+
+<Aside type="caution" title="You must manually execute on Canton">
+
+Every tutorial in this section ends with **`any2canton:manual-exec`**. See [Manual Execution (Canton)](/ccip/concepts/canton/manual-execution).
+
+</Aside>
+
+<Aside type="note" title="Testnet only">
+
+These tutorials run on **Canton testnet** and **Ethereum Sepolia** only. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites) with testnet credentials and tokens before starting.
+
+</Aside>
+
+Tutorials use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) on [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk).
+
+## Getting Started
+
+- [Prerequisites for Canton as Destination](/ccip/tutorials/canton/destination/prerequisites) — Clone the starter kit, configure Sepolia and Canton access, and fund TEST/ETH.
+- [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton) — Execute path in the overview.
+
+## Tutorials by Use Case
+
+| Tutorial                                                                                        | Scripts                                     | Description                                  |
+| :---------------------------------------------------------------------------------------------- | :------------------------------------------ | :------------------------------------------- |
+| [Arbitrary Messaging](/ccip/tutorials/canton/destination/arbitrary-messaging)                   | `any2canton:data` + `manual-exec`           | Execute an incoming data message on Canton   |
+| [Token Transfers](/ccip/tutorials/canton/destination/token-transfers)                           | `any2canton:token` + `manual-exec`          | Execute an incoming token transfer on Canton |
+| [Programmable Token Transfers](/ccip/tutorials/canton/destination/programmable-token-transfers) | `any2canton:data-and-token` + `manual-exec` | Execute an incoming PTT on Canton            |
+
+## Common Flow (all any2canton tutorials)
+
+1. Send from Sepolia with an `any2canton:*` script
+2. Poll message status via the CCIP API or [CCIP Explorer](/ccip/tools-resources/ccip-explorer)
+3. Run `any2canton:manual-exec` — the SDK **finds or creates** a compatible `CCIPReceiver` for message finality
+4. Fetch proofs from the indexer and disclosures from Global CCIP EDS (+ token pool operator EDS for token messages)
+5. For token messages: accept the `TransferInstruction` to receive LINK on-ledger
+
+<Aside type="tip">
+
+No separate receiver deployment tutorial is needed for the default path. Pass a `receiver` hint only for custom `CCIPReceiver` configurations.
+
+</Aside>
+
+## Prerequisites
+
+- [Starter kit setup](/ccip/tutorials/canton/destination/prerequisites)
+- Funded Sepolia account with ETH (or LINK for fees) and TEST for token tutorials
+- Canton ledger access for manual execution
+- Token pool registered for the instrument — see [CCT guides](/ccip/tutorials/canton/cross-chain-tokens)
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/destination/prerequisites.mdx b/src/content/ccip/tutorials/canton/destination/prerequisites.mdx
new file mode 100644
index 00000000000..f6ed890bc20
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/destination/prerequisites.mdx
@@ -0,0 +1,174 @@
+---
+section: ccip
+date: Last Modified
+title: "Prerequisites for Canton as Destination Tutorials"
+isIndex: false
+metadata:
+  description: "Complete setup guide for Canton as Destination cross-chain development. Install Node.js, configure Ethereum Sepolia and Canton ledger access, and fund testnet tokens for CCIP tutorials."
+  image: "/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  excerpt: "prerequisites, Canton, any2canton, wallets, tokens, setup"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "15 minutes"
+  difficulty: "beginner"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+Before starting the **Canton as Destination** (`any2canton`) tutorials, ensure you have the following:
+
+<Aside type="note" title="Testnet only">
+
+These tutorials use **Canton testnet** and **Ethereum Sepolia** only. The starter kit's `helperConfig.ts` and `canton-config.example.json` are pre-configured for the Canton CCIP testnet lane.
+
+</Aside>
+
+## Development Environment
+
+- **Node.js v20 or higher**: You can use the [nvm package](http://nvm.sh/) to install and switch between Node.js versions. Once installed, verify the node version with:
+
+  ```bash filename="Terminal"
+  node -v
+  ```
+
+  Example output:
+
+  ```text
+  $ node -v
+  v22.15.0
+  ```
+
+- **npm**: For installing and managing dependencies.
+- **Git**: For cloning the repository.
+
+## Starter Kit Repository
+
+1. Clone the [CCIP Canton Starter Kit](https://github.com/smartcontractkit/ccip-starter-kit-canton):
+
+   ```bash filename="Terminal"
+   git clone https://github.com/smartcontractkit/ccip-starter-kit-canton.git
+   ```
+
+1. Navigate to the directory:
+
+   ```bash filename="Terminal"
+   cd ccip-starter-kit-canton
+   ```
+
+1. Install dependencies:
+
+   ```bash filename="Terminal"
+   npm install
+   ```
+
+The starter kit uses [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) v1.10+ for sending from Ethereum Sepolia and executing on Canton.
+
+## Understanding Network Configuration
+
+Lane defaults live in [`helperConfig.ts`](https://github.com/smartcontractkit/ccip-starter-kit-canton/blob/main/helperConfig.ts):
+
+- **Canton testnet** chain selector: `9268731218649498074`
+- **Ethereum Sepolia** chain selector: `16015286601757825753`
+- **Token lane**: Canton LINK ↔ Sepolia TEST (`0xeEe6675b20fE5950eb51361b93021D076289F612`)
+
+Canton deployment fields live in `config/canton-config.json` — see the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites#understanding-canton-configuration-canton-configjson) for the full file reference. Replace **`party`** and **`transferInstructionUrl`**; other fields are pre-configured for the Canton CCIP testnet lane.
+
+## Wallets and Accounts
+
+- **Ethereum Sepolia wallet and private key**: Required to send CCIP messages from Sepolia (`any2canton` send scripts). Set up a wallet like [MetaMask](https://metamask.io/), export the private key for the account you send from, and add it to `.env` as `EVM_PRIVATE_KEY`.
+
+- **Canton party**: The destination receiver on Canton. Defaults to the `party` field in `canton-config.json`. Override with `--cantonReceiver` on send scripts or `--receiver` on `any2canton:manual-exec` when needed.
+
+<Aside type="tip" title="No separate receiver deployment">
+
+The SDK **finds or creates** a compatible `CCIPReceiver` when you run `any2canton:manual-exec`. Pass a `receiver` hint only for custom `CCIPReceiver` configurations.
+
+</Aside>
+
+## Environment Configuration (`.env` file)
+
+Create `.env` from the example:
+
+```bash filename="Terminal"
+cp .env.example .env
+cp config/canton-config.example.json config/canton-config.json
+```
+
+Fill in the following values:
+
+| Variable                                    | Description                                                                                              |
+| :------------------------------------------ | :------------------------------------------------------------------------------------------------------- |
+| `EVM_PRIVATE_KEY`                           | Sepolia signer hex key (with or without `0x` prefix)                                                     |
+| `ETHEREUM_SEPOLIA_RPC_URL`                  | Sepolia JSON-RPC URL                                                                                     |
+| `CANTON_LEDGER_URL`                         | Canton participant JSON Ledger API URL (required for `any2canton:manual-exec`; not EDS or the validator) |
+| `CANTON_CONFIG_PATH`                        | Path to `canton-config.json`                                                                             |
+| `CANTON_AUTH_URL`                           | OIDC authorization server URL (from your validator setup)                                                |
+| `CANTON_CLIENT_ID` / `CANTON_CLIENT_SECRET` | OIDC credentials for ledger auth on Canton                                                               |
+
+In `canton-config.json`, set **`party`** to your Canton testnet party ID and **`transferInstructionUrl`** to your validator's transfer-instruction API. See [source prerequisites](/ccip/tutorials/canton/source/prerequisites#understanding-canton-configuration-canton-configjson) for field reference.
+
+Send scripts use a default **`--gasLimit` of `200000`** for destination `ccipReceive` (see [optional script flags](/ccip/tutorials/canton/source/prerequisites#optional-script-flags) in source prerequisites).
+
+**Example `.env` file:**
+
+```bash filename=".env"
+EVM_PRIVATE_KEY=0xYourSepoliaPrivateKey
+ETHEREUM_SEPOLIA_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/YOUR_API_KEY
+CANTON_LEDGER_URL=https://your-canton-ledger-api.example.com
+CANTON_CONFIG_PATH=./config/canton-config.json
+CANTON_AUTH_URL=https://auth.example.com
+CANTON_CLIENT_ID=your_client_id
+CANTON_CLIENT_SECRET=your_client_secret
+```
+
+<Aside type="caution" title="Keep your secrets safe">
+
+Never commit `.env`, OIDC secrets, or private keys to version control.
+
+</Aside>
+
+## Testnet Tokens
+
+### ETH on Ethereum Sepolia
+
+ETH pays for Sepolia transaction fees and CCIP fees (default `--feeToken native`). Use the [Chainlink Faucet](https://faucet.chain.link) to obtain test ETH.
+
+### LINK on Ethereum Sepolia (optional)
+
+Pass `--feeToken link` on `any2canton` send scripts to pay CCIP fees in LINK instead of ETH. Use the [Chainlink Faucet](https://faucet.chain.link) for test LINK.
+
+### TEST token on Ethereum Sepolia (token transfer tutorials)
+
+Token transfer tutorials send the Sepolia **TEST** token (`BurnMintERC20WithDrip`). Mint test tokens with the starter kit faucet:
+
+```bash filename="Terminal"
+npm run faucet:evm-test
+```
+
+This calls `drip()` on the TEST token contract and credits 1 TEST to your `EVM_PRIVATE_KEY` wallet.
+
+### Canton holdings after execution
+
+TEST burned on Sepolia mints **LINK** on Canton only after you run `any2canton:manual-exec` once the message is ready. Data-only messages do not transfer tokens.
+
+Check balances before and after execution:
+
+```bash filename="Terminal"
+npm run check-balance
+```
+
+## Verify Setup
+
+Confirm Sepolia and Canton configuration:
+
+```bash filename="Terminal"
+npm run check-balance -- --chain sepolia --token test
+npm run check-balance -- --chain canton --token link
+```
+
+When setup is complete, continue to the [Canton as Destination tutorials](/ccip/tutorials/canton/destination).
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/destination/programmable-token-transfers.mdx b/src/content/ccip/tutorials/canton/destination/programmable-token-transfers.mdx
new file mode 100644
index 00000000000..d4307398e08
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/destination/programmable-token-transfers.mdx
@@ -0,0 +1,118 @@
+---
+section: ccip
+date: Last Modified
+title: "Programmable Token Transfers: Canton as Destination"
+isIndex: false
+metadata:
+  description: "Send TEST tokens with a data payload from Ethereum Sepolia and execute the programmable token transfer on Canton."
+  image: "/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  excerpt: "Canton as Destination, any2canton, programmable token transfer, PTT, manual execution"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "30 minutes"
+  difficulty: "intermediate"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+This tutorial demonstrates how to send a **programmable token transfer (PTT)** from Ethereum Sepolia to Canton — TEST tokens plus arbitrary data — and execute it on Canton using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+
+Complete the [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites) and review [Token Transfers (Canton as Destination)](/ccip/tutorials/canton/destination/token-transfers). You need Sepolia TEST tokens (`npm run faucet:evm-test`) and Canton ledger access.
+
+These steps use **Canton testnet** and **Ethereum Sepolia** only.
+
+</Aside>
+
+## Introduction
+
+A programmable token transfer delivers both tokens and a data payload to the destination. On Canton, execution:
+
+1. Resolves or creates a `CCIPReceiver` for the message finality.
+2. Processes `TokenReceiveTicket` and mints LINK via the token pool.
+3. Delivers the attached data to your receiver logic through `ccipReceive` on Canton.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Send `1` TEST plus a UTF-8 data string from Sepolia with `any2canton:data-and-token`.
+- Execute on Canton with `any2canton:manual-exec`.
+- Verify LINK balance and message execution.
+
+## Understanding Programmable Token Transfers (any2canton)
+
+| Aspect               | Token-only                               | Programmable token transfer            |
+| :------------------- | :--------------------------------------- | :------------------------------------- |
+| **Send script**      | `any2canton:token`                       | `any2canton:data-and-token`            |
+| **Data**             | Empty                                    | `--dataString` payload                 |
+| **Canton execution** | LINK mint + accept `TransferInstruction` | LINK mint + data delivered to receiver |
+
+The execution path fetches proofs, Global CCIP EDS disclosures, and token pool operator EDS inputs — see the [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton).
+
+## Running the Tutorial
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites).
+2. Mint TEST on Sepolia:
+
+   ```bash filename="Terminal"
+   npm run faucet:evm-test
+   ```
+
+## Step 1: Send data + TEST from Sepolia
+
+```bash filename="Terminal"
+npm run any2canton:data-and-token -- --dataString "Hello" --amount 1
+```
+
+Pay CCIP fee in LINK and use block-depth finality:
+
+```bash filename="Terminal"
+npm run any2canton:data-and-token -- \
+  --dataString "Hello" \
+  --amount 1 \
+  --feeToken link \
+  --finality 32
+```
+
+### Expected send output
+
+```text
+📧🪙 Sending data + 1 TEST from Sepolia → Canton: "Hello"
+   Receiver party: yourParty::1220…
+   LINK is minted on Canton only after manual execution.
+🆔 CCIP Message ID: 0x…
+
+⚙️  Execute on Canton once Sepolia reaches 32 block confirmations for this message:
+   npm run any2canton:manual-exec -- 0x<messageId>
+```
+
+## Step 2: Execute on Canton
+
+After finality and Committee Verifier proofs are on the indexer:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId>
+```
+
+Pass either the **Sepolia source transaction hash** (`📜 Source transaction`) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) — `any2canton:manual-exec` accepts both.
+
+Optional custom receiver hint:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId> --receiver 'yourParty::1220…'
+```
+
+## Verification
+
+1. **CCIP Explorer**: Confirm SUCCESS for the transfer.
+2. **LINK balance**: `npm run check-balance -- --chain canton --token link`
+3. **Canton Lighthouse**: Inspect the execution transaction for token pool and receiver activity.
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/destination/token-transfers.mdx b/src/content/ccip/tutorials/canton/destination/token-transfers.mdx
new file mode 100644
index 00000000000..b67a199030f
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/destination/token-transfers.mdx
@@ -0,0 +1,141 @@
+---
+section: ccip
+date: Last Modified
+title: "Token Transfers: Canton as Destination"
+isIndex: false
+metadata:
+  description: "Send TEST tokens from Ethereum Sepolia and execute the incoming token transfer on Canton using any2canton scripts."
+  image: "/images/ccip/concepts/architecture/ccip-canton-destination-chain.png"
+  excerpt: "Canton as Destination, any2canton, token transfers, manual execution, LINK mint"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "30 minutes"
+  difficulty: "intermediate"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+This tutorial demonstrates how to transfer tokens from Ethereum Sepolia to Canton: burn **TEST** on Sepolia and receive **LINK** on Canton after manual execution.
+
+<Aside title="Prerequisites">
+
+Complete the [Canton as Destination prerequisites](/ccip/tutorials/canton/destination/prerequisites). You need:
+
+- Sepolia **ETH** for CCIP fees (or LINK with `--feeToken link`).
+- Sepolia **TEST** tokens — mint with `npm run faucet:evm-test`.
+- Canton ledger access for `any2canton:manual-exec`.
+
+These steps use **Canton testnet** and **Ethereum Sepolia** only.
+
+</Aside>
+
+## Introduction
+
+The prod testnet lane maps Sepolia **TEST** to Canton **LINK**. Token delivery on Canton happens only after you:
+
+1. Send the token transfer from Sepolia (`any2canton:token`).
+2. Wait for source finality and Committee Verifier proofs on the indexer.
+3. Execute on Canton (`any2canton:manual-exec`) — the SDK processes `TokenReceiveTicket` and issues a `TransferInstruction` for your party to accept.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Fund your Sepolia wallet with TEST tokens.
+- Send `1` TEST from Sepolia to your Canton party.
+- Execute on Canton and verify LINK balance.
+
+## Understanding Token Transfers (any2canton)
+
+Key points:
+
+- **Burn and mint**: TEST is burned on Sepolia; LINK is minted on Canton after execution.
+- **Manual execution required**: Unlike `canton2any` default auto-exec on Sepolia, all `any2canton` token transfers require `any2canton:manual-exec` on Canton.
+- **Token pool disclosures**: Execution fetches disclosures from Global CCIP EDS and the token pool operator EDS.
+
+See the [Canton as Destination flow](/ccip/concepts/canton/overview#public-chain--canton) — `TokenReceiveTicket` and token pool release steps.
+
+<Aside type="tip" title="Custom CCIPReceiver">
+
+Use the optional `--receiver` flag on `any2canton:manual-exec` only when you need a specific `CCIPReceiver` contract (custom Committee Verifier or finality configuration on the receiver). The default path finds or creates a compatible receiver automatically.
+
+</Aside>
+
+## Running the Tutorial
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/destination/prerequisites).
+2. Mint TEST on Sepolia:
+
+   ```bash filename="Terminal"
+   npm run faucet:evm-test
+   ```
+
+3. Note your Canton LINK balance before the transfer:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain canton --token link
+   ```
+
+## Step 1: Send TEST from Sepolia
+
+```bash filename="Terminal"
+npm run any2canton:token -- --amount 1
+```
+
+Faster finality (32 block confirmations):
+
+```bash filename="Terminal"
+npm run any2canton:token -- --amount 1 --finality 32
+```
+
+### Expected send output
+
+```text
+🪙 Sending 1 TEST from Sepolia → Canton
+   Receiver party: yourParty::1220…
+   LINK is minted on Canton only after manual execution.
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+
+⚙️  Execute on Canton once the message is finalized on Sepolia:
+   npm run any2canton:manual-exec -- 0x<messageId>
+```
+
+## Step 2: Execute on Canton
+
+Wait for the requested finality and Committee Verifier proofs on the indexer, then:
+
+```bash filename="Terminal"
+npm run any2canton:manual-exec -- <sepoliaTxHash | messageId>
+```
+
+Pass either the **Sepolia source transaction hash** (`📜 Source transaction`) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) — `any2canton:manual-exec` accepts both.
+
+Execution typically takes 1–3 minutes on the ledger after you run the command.
+
+## Verification
+
+### Check LINK balance on Canton
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token link
+```
+
+Your LINK balance should increase after successful execution and `TransferInstruction` acceptance.
+
+### CCIP Explorer
+
+Confirm the message reached **SUCCESS** and inspect the Canton execution update in Lighthouse.
+
+### Verbose holdings (optional)
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token link --show-holdings
+```
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/source/arbitrary-messaging.mdx b/src/content/ccip/tutorials/canton/source/arbitrary-messaging.mdx
new file mode 100644
index 00000000000..281dc070133
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/source/arbitrary-messaging.mdx
@@ -0,0 +1,155 @@
+---
+section: ccip
+date: Last Modified
+title: "Arbitrary Messaging: Canton as Source"
+isIndex: false
+metadata:
+  description: "Send a data-only CCIP message from Canton to Ethereum Sepolia using the CCIP Canton Starter Kit and canton2any scripts."
+  image: "/images/ccip/concepts/architecture/ccip-canton-source-chain.png"
+  excerpt: "Canton as Source, canton2any, arbitrary messaging, CCIPSender, data transfer"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "20 minutes"
+  difficulty: "intermediate"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+This tutorial demonstrates how to send a data-only CCIP message from Canton testnet to a receiver contract on Ethereum Sepolia using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+
+Complete the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) before starting this tutorial. Your Canton party needs **Amulet** holdings to pay CCIP fees (or use `--feeToken link`).
+
+These steps use **Canton testnet** and **Ethereum Sepolia** only.
+
+</Aside>
+
+## Introduction
+
+This tutorial covers sending arbitrary data from Canton to Ethereum Sepolia without any token transfer. When you send a message using CCIP:
+
+1. The SDK fetches explicit disclosures from Global CCIP EDS and creates or reuses `CCIPSender` and `PerPartyRouter` on Canton.
+2. The message is submitted via `PerPartyRouter_CCIPSend` with CommitteeVerifier tickets.
+3. CommitteeVerifier operators validate the message and aggregate proofs to the indexer.
+4. The message is executed on Sepolia — automatically by default, or manually with `canton2any:manual-exec`.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Run `canton2any:data` to send a UTF-8 data payload from Canton to Sepolia.
+- Pay CCIP fees in Amulet (default) or LINK.
+- Track delivery in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+- Optionally execute manually on Sepolia with `canton2any:manual-exec`.
+
+## Understanding Arbitrary Messaging (canton2any)
+
+Key points for data-only sends from Canton:
+
+- **Data only**: No `tokenAmounts` — only a `data` payload is delivered to the Sepolia receiver contract's `ccipReceive` function.
+- **Fee payment**: CCIP fees are paid on Canton in **Amulet** by default. Pass `--feeToken link` to pay in CCIP LINK instead.
+- **Auto-execution**: By default, the starter kit allows automatic execution on Sepolia when an executor is configured. Pass `--no-exec` to skip auto-execution and run `canton2any:manual-exec` after Committee Verifier proofs are on the indexer.
+- **Receiver**: Defaults to the starter kit's demo receiver on Sepolia. Override with `--evmReceiver`.
+
+See the [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain) in the overview for the full on-ledger and off-ledger path.
+
+## How the Script Works
+
+The `scripts/canton2any/ccipSendData.ts` script uses `@chainlink/ccip-sdk` `CantonChain.sendMessage`:
+
+1. **Context initialization**: Loads `canton-config.json`, authenticates to the Ledger API, and connects.
+2. **Argument parsing**: Reads `--dataString`, `--feeToken`, `--evmReceiver`, `--gasLimit` (default `200000`), and `--no-exec`.
+3. **Message construction**: Builds a CCIP message with encoded data, fee token, and `extraArgs` (gas limit and optional `executorMode: 'none'`).
+4. **Ledger submit**: Submits the send via authenticated direct ledger submit — no local Canton signing key required.
+5. **Output**: Prints the CCIP Message ID, CCIP Explorer URL, and Canton Lighthouse transaction link.
+
+## Running the Arbitrary Message
+
+### Prerequisites Check
+
+Before running the script:
+
+1. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites) setup (`npm install`, `.env`, `canton-config.json`).
+2. Confirm Amulet balance for fees:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain canton --token amulet
+   ```
+
+3. Ensure `ETHEREUM_SEPOLIA_RPC_URL` and `EVM_PRIVATE_KEY` are set if you plan to run `canton2any:manual-exec`.
+
+### Execute the Script
+
+Send a data-only message from Canton to Sepolia:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia"
+```
+
+Pay the CCIP fee in LINK instead of Amulet:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia" --feeToken link
+```
+
+Skip automatic execution on Sepolia and execute manually after Committee Verifier proofs are on the indexer:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia" --no-exec
+```
+
+Override the Sepolia receiver contract:
+
+```bash filename="Terminal"
+npm run canton2any:data -- --dataString "Hello Sepolia" --evmReceiver 0xYourReceiverAddress
+```
+
+### Understanding the Output
+
+On success, you should see output similar to:
+
+```text
+📧 Sending data from Canton → Sepolia: "Hello Sepolia"
+   Executor: default (auto-execution on Sepolia when an executor is configured)
+Canton bearer token obtained via OIDC client credentials.
+🆔 CCIP Message ID: 0x1220e4133ede8f2daf2e665b53321da54d1bd0b8e00fb1cece20b63079c1d48d6a5b
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x1220…
+📜 Canton transaction: https://lighthouse.testnet.cantonloop.com/transactions/…
+```
+
+If you used `--no-exec`, the script also prints a copy-pasteable `canton2any:manual-exec` command.
+
+## Verification and Monitoring
+
+### Track on CCIP Explorer
+
+Open the CCIP Explorer URL from the script output to monitor message status from send through destination execution.
+
+### Manual execution on Sepolia
+
+If you passed `--no-exec`, wait until proofs are on the indexer (check the CCIP Explorer), then run:
+
+```bash filename="Terminal"
+npm run canton2any:manual-exec -- <cantonUpdateId | messageId>
+```
+
+Pass either the Canton **update ID** from the send output (`📜 Canton transaction` / Lighthouse link) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`). `canton2any:manual-exec` accepts both — resolving by message ID lets the SDK fetch the OffRamp and Committee Verifier proofs from the CCIP API automatically.
+
+On success:
+
+```text
+⚙️  Executing on Sepolia OffRamp 0x…
+✅ Execution transaction: https://sepolia.etherscan.io/tx/0x…
+```
+
+<Aside type="note" title="Execution timing">
+
+End-to-end delivery time depends on Canton finality and CommitteeVerifier proof aggregation. Allow several minutes before manual execution if the message is not yet ready.
+
+</Aside>
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/source/index.mdx b/src/content/ccip/tutorials/canton/source/index.mdx
new file mode 100644
index 00000000000..14e35128f28
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/source/index.mdx
@@ -0,0 +1,61 @@
+---
+section: ccip
+date: Last Modified
+title: "CCIP Tutorials: Canton as Source"
+metadata:
+  description: "Send cross-chain messages and token transfers from Canton to remote CCIP chains using the CCIP Canton Starter Kit."
+  excerpt: "CCIP Canton source, canton2any, CCIPSender, token transfers, arbitrary messaging"
+  datePublished: "2026-06-27"
+  lastModified: "2026-07-06"
+  difficulty: "intermediate"
+isIndex: true
+whatsnext:
+  "Prerequisites": "/ccip/tutorials/canton/source/prerequisites"
+  "Token Transfers": "/ccip/tutorials/canton/source/token-transfers"
+  "Cross-chain overview": "/ccip/concepts/canton/overview"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+**Canton as Source** (`canton2any`) tutorials cover sending from Canton — Canton is the source chain, a remote CCIP-supported chain (Ethereum Sepolia in the starter kit) is the destination.
+
+<Aside type="note" title="Testnet only">
+
+These tutorials run on **Canton testnet** and **Ethereum Sepolia** only. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites) with testnet credentials and tokens before starting.
+
+</Aside>
+
+Tutorials use the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) on [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk).
+
+## Getting Started
+
+- [Prerequisites for Canton as Source](/ccip/tutorials/canton/source/prerequisites) — Clone the starter kit, configure Canton ledger access, and fund Amulet/LINK.
+- [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain) — On-ledger send path in the overview.
+
+## Tutorials by Use Case
+
+| Tutorial                                                                                   | Script                      | Description                                   |
+| :----------------------------------------------------------------------------------------- | :-------------------------- | :-------------------------------------------- |
+| [Arbitrary Messaging](/ccip/tutorials/canton/source/arbitrary-messaging)                   | `canton2any:data`           | Send a data-only message from Canton          |
+| [Token Transfers](/ccip/tutorials/canton/source/token-transfers)                           | `canton2any:token`          | Bridge LINK from Canton to Sepolia            |
+| [Programmable Token Transfers](/ccip/tutorials/canton/source/programmable-token-transfers) | `canton2any:data-and-token` | Send LINK plus calldata to a Sepolia receiver |
+
+## Common Flow (all canton2any tutorials)
+
+1. Fetch explicit disclosures from Global CCIP EDS (and token pool operator EDS for token messages)
+2. Create or reuse `CCIPSender` and `PerPartyRouter` on Canton
+3. Submit via `PerPartyRouter_CCIPSend` with CommitteeVerifier tickets (and token pool tickets when applicable)
+4. Track delivery in [CCIP Explorer](/ccip/tools-resources/ccip-explorer)
+5. Destination execution on Sepolia runs automatically by default, or via `canton2any:manual-exec` with `--no-exec`
+
+## Prerequisites
+
+- [Starter kit setup](/ccip/tutorials/canton/source/prerequisites)
+- **Amulet** (default) or **LINK** on Canton for CCIP fees
+- **LINK** on Canton for token transfer and PTT tutorials
+- Token pool registered on TAR for token messages — see [CCT guides](/ccip/tutorials/canton/cross-chain-tokens)
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/source/prerequisites.mdx b/src/content/ccip/tutorials/canton/source/prerequisites.mdx
new file mode 100644
index 00000000000..1c09d2622c5
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/source/prerequisites.mdx
@@ -0,0 +1,228 @@
+---
+section: ccip
+date: Last Modified
+title: "Prerequisites for Canton as Source Tutorials"
+isIndex: false
+metadata:
+  description: "Complete setup guide for Canton as Source cross-chain development. Install Node.js, configure Canton ledger access and Ethereum Sepolia, and fund testnet tokens for CCIP tutorials."
+  image: "/images/ccip/concepts/architecture/ccip-canton-source-chain.png"
+  excerpt: "prerequisites, Canton, canton2any, wallets, tokens, setup"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "15 minutes"
+  difficulty: "beginner"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+Before starting the **Canton as Source** (`canton2any`) tutorials, ensure you have the following. New to Canton? Read [Key Concepts](/ccip/concepts/canton/key-concepts) first (parties, fees, tooling).
+
+<Aside type="note" title="Tooling">
+
+These tutorials use [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton) — tutorial scripts on top of [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) (same send/execute model as [`ccip-cli`](https://github.com/smartcontractkit/ccip-tools-ts)). For production integrations, use the SDK or CLI directly.
+
+</Aside>
+
+<Aside type="note" title="Testnet only">
+
+These tutorials use **Canton testnet** and **Ethereum Sepolia** only. The starter kit's `helperConfig.ts` and `canton-config.example.json` are pre-configured for the Canton CCIP testnet lane.
+
+</Aside>
+
+## Development Environment
+
+- **Node.js v20 or higher**: You can use the [nvm package](http://nvm.sh/) to install and switch between Node.js versions. Once installed, verify the node version with:
+
+  ```bash filename="Terminal"
+  node -v
+  ```
+
+  Example output:
+
+  ```text
+  $ node -v
+  v22.15.0
+  ```
+
+- **npm**: For installing and managing dependencies.
+- **Git**: For cloning the repository.
+
+## Starter Kit Repository
+
+1. Clone the [CCIP Canton Starter Kit](https://github.com/smartcontractkit/ccip-starter-kit-canton):
+
+   ```bash filename="Terminal"
+   git clone https://github.com/smartcontractkit/ccip-starter-kit-canton.git
+   ```
+
+1. Navigate to the directory:
+
+   ```bash filename="Terminal"
+   cd ccip-starter-kit-canton
+   ```
+
+1. Install dependencies:
+
+   ```bash filename="Terminal"
+   npm install
+   ```
+
+The starter kit uses [`@chainlink/ccip-sdk`](https://www.npmjs.com/package/@chainlink/ccip-sdk) v1.10+ for Canton and Ethereum Sepolia interactions.
+
+## Understanding Canton Configuration (`canton-config.json`)
+
+Canton deployment fields live in `config/canton-config.json`. Copy the example file and replace the **two placeholder fields**:
+
+```bash filename="Terminal"
+cp config/canton-config.example.json config/canton-config.json
+```
+
+Replace **`party`** with your Canton testnet party ID (it must match your validator user). Replace **`transferInstructionUrl`** with your validator's transfer-instruction API (Amulet fee transfers and token metadata — not EDS). Chainlink provides shared CCIP endpoints (`edsUrl`, `indexerUrl`, `ccipParty`, `ccvs`, etc.) in the starter kit; you supply your own participant Ledger API access and validator configuration.
+
+All other fields (`edsUrl`, `indexerUrl`, `ccipParty`, `ccvs`, `senderInstanceId`, etc.) are pre-configured for the Canton CCIP testnet lane in `canton-config.example.json`.
+
+**Example `canton-config.json`:**
+
+```json filename="config/canton-config.json"
+{
+  "party": "YOUR_LEDGER_PARTY::1220…",
+  "ccipParty": "ccipOwner::1220e382f4e57b0815e6be737006e381e6b7de448e06bd033ece6df498017879f551",
+  "edsUrl": "https://eds.testnet.ccip.chain.link",
+  "transferInstructionUrl": "https://validator.example.com/api/validator",
+  "indexerUrl": "https://indexer-1.testnet.ccip.chain.link",
+  "chainId": "canton:TestNet",
+  "senderInstanceId": "prod-ccipsender",
+  "ccvs": ["0xec1e288bcf8bbf034ac2d31b67f9b15a3f1f828d086c5b9d8fc2866129cd02fe"]
+}
+```
+
+Key fields:
+
+- **`party`**: Your ledger party — the sender for `canton2any` scripts and the default Canton receiver for `any2canton` scripts.
+- **`transferInstructionUrl`**: Your validator's transfer-instruction API. Depends on which validator hosts your party (not the Global CCIP EDS at `edsUrl`).
+- **`senderInstanceId`**: The `CCIPSender` instance used when sending from Canton.
+- **`ccvs`**: CommitteeVerifier contract IDs required for message validation.
+- **`edsUrl`** / **`indexerUrl`**: Global CCIP Explicit Disclosure Service and indexer endpoints for proofs and disclosures.
+
+Network selectors, router addresses, token instruments, and the default **`--gasLimit`** (`200000` for destination `ccipReceive`) are defined in [`helperConfig.ts`](https://github.com/smartcontractkit/ccip-starter-kit-canton/blob/main/helperConfig.ts).
+
+## Optional script flags
+
+Send scripts (`canton2any:*` and `any2canton:*`) share these common flags:
+
+| Flag                                 | Default      | Description                                                                                                                              |
+| :----------------------------------- | :----------- | :--------------------------------------------------------------------------------------------------------------------------------------- |
+| `--gasLimit`                         | `200000`     | Gas limit for `ccipReceive` on the destination chain (Sepolia for `canton2any`, Canton for `any2canton`)                                 |
+| `--feeToken`                         | `native`     | CCIP fee token on the source chain (`native`: Amulet on Canton, ETH on Sepolia; or `link`)                                               |
+| `--evmReceiver` / `--cantonReceiver` | See config   | Override the default receiver on the destination chain                                                                                   |
+| `--no-exec`                          | auto-exec on | `canton2any` only — skip automatic execution on Sepolia; run `canton2any:manual-exec` after Committee Verifier proofs are on the indexer |
+| `--finality`                         | `finalized`  | `any2canton` only — requested source finality (`finalized` or block depth, e.g. `32`)                                                    |
+
+## Canton Ledger Access
+
+Canton sends and executes use **OIDC bearer-token authentication** and direct ledger submit (same as `ccip-cli` without `--wallet`). No local signing key is required for participant-hosted parties.
+
+Canton uses standard [OpenID Connect (OIDC)](https://openid.net/connect/). You can authenticate with any compatible identity provider (Okta, Keycloak, Microsoft Azure, Auth0, and others) or a local user on development nodes — see the [Canton validator documentation](https://docs.canton.network/) for setup. Local or development nodes do not require an external identity provider.
+
+The starter kit resolves a bearer token from `.env` before each run:
+
+1. `CANTON_JWT` in `.env` (explicit override)
+2. OIDC client credentials (`CANTON_AUTH_URL`, `CANTON_CLIENT_ID`, `CANTON_CLIENT_SECRET`)
+3. `jwt` field in `canton-config.json` (fallback only)
+
+<Aside type="tip" title="What Chainlink provides">
+
+Chainlink provides shared CCIP infrastructure for Canton lanes — **EDS**, **indexer**, and on-ledger contract references. These are pre-filled in `canton-config.example.json`. Contact Chainlink ops for contract references (owner party, TAR, RMNRemote, FeeQuoter). You supply your own participant Ledger API access, validator user, and `transferInstructionUrl`.
+
+</Aside>
+
+## Wallets and Accounts
+
+- **Canton party**: Your on-ledger party ID in `canton-config.json`. Scripts submit commands on behalf of this party via `submit-and-wait-for-transaction`.
+
+- **Ethereum Sepolia account** (optional for source sends): Required only if you run `canton2any:manual-exec` on Sepolia or want to verify token delivery on the destination chain. Set `EVM_PRIVATE_KEY` and `ETHEREUM_SEPOLIA_RPC_URL` in `.env`. For data-only sends with default auto-execution, you only need the **receiver contract address** on Sepolia (the starter kit provides a default).
+
+## Environment Configuration (`.env` file)
+
+Create `.env` from the example and replace every placeholder:
+
+```bash filename="Terminal"
+cp .env.example .env
+```
+
+| Variable                   | Description                                                           |
+| :------------------------- | :-------------------------------------------------------------------- |
+| `EVM_PRIVATE_KEY`          | Sepolia signer private key (hex, with or without `0x`)                |
+| `ETHEREUM_SEPOLIA_RPC_URL` | Your Sepolia JSON-RPC URL                                             |
+| `CANTON_LEDGER_URL`        | Canton participant **JSON Ledger API** URL (not EDS or the validator) |
+| `CANTON_CONFIG_PATH`       | Path to `canton-config.json` (default: `./config/canton-config.json`) |
+| `CANTON_AUTH_URL`          | OIDC authorization server URL (from your validator setup)             |
+| `CANTON_CLIENT_ID`         | OIDC client ID for your validator user                                |
+| `CANTON_CLIENT_SECRET`     | OIDC client secret — scripts fetch a fresh bearer token on each run   |
+
+**Example `.env` file:**
+
+```bash filename=".env"
+EVM_PRIVATE_KEY=0xYourSepoliaPrivateKey
+ETHEREUM_SEPOLIA_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/YOUR_API_KEY
+CANTON_LEDGER_URL=https://your-canton-ledger-api.example.com
+CANTON_CONFIG_PATH=./config/canton-config.json
+CANTON_AUTH_URL=https://auth.example.com
+CANTON_CLIENT_ID=your_client_id
+CANTON_CLIENT_SECRET=your_client_secret
+```
+
+<Aside type="caution" title="Keep your secrets safe">
+
+Never commit `.env`, OIDC secrets, or private keys to version control.
+
+</Aside>
+
+## Testnet Tokens
+
+### Amulet (default CCIP fee token on Canton)
+
+`canton2any` scripts pay CCIP fees in **Amulet** by default. Fund your Canton party with Amulet holdings before sending.
+
+Check balances:
+
+```bash filename="Terminal"
+npm run check-balance
+```
+
+Or check Amulet only:
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token amulet
+```
+
+### LINK on Canton (token transfer tutorials)
+
+Token transfer and programmable token transfer tutorials send **LINK** from Canton to Sepolia. Your party needs LINK (`link-token`) holdings on Canton.
+
+```bash filename="Terminal"
+npm run check-balance -- --chain canton --token link
+```
+
+Pass `--feeToken link` on send scripts to pay CCIP fees in LINK instead of Amulet.
+
+### Sepolia ETH (optional)
+
+If you run `canton2any:manual-exec` yourself, your Sepolia account needs test ETH for gas. Use the [Chainlink Faucet](https://faucet.chain.link) to obtain test ETH.
+
+## Verify Setup
+
+From the starter kit root, confirm Canton connectivity and balances:
+
+```bash filename="Terminal"
+npm run check-balance
+```
+
+You should see LINK and Amulet balances for your Canton party. If you configured `EVM_PRIVATE_KEY`, Sepolia LINK and TEST balances are shown as well.
+
+When setup is complete, continue to the [Canton as Source tutorials](/ccip/tutorials/canton/source).
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/source/programmable-token-transfers.mdx b/src/content/ccip/tutorials/canton/source/programmable-token-transfers.mdx
new file mode 100644
index 00000000000..f301712834f
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/source/programmable-token-transfers.mdx
@@ -0,0 +1,123 @@
+---
+section: ccip
+date: Last Modified
+title: "Programmable Token Transfers: Canton as Source"
+isIndex: false
+metadata:
+  description: "Send LINK tokens with an attached data payload from Canton to Ethereum Sepolia using canton2any:data-and-token."
+  image: "/images/ccip/concepts/architecture/ccip-canton-source-chain.png"
+  excerpt: "Canton as Source, canton2any, programmable token transfer, PTT, CCIPSender"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "25 minutes"
+  difficulty: "intermediate"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+This tutorial demonstrates how to send a **programmable token transfer (PTT)** — tokens plus arbitrary data — from Canton testnet to Ethereum Sepolia using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+
+Complete the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites) and the [Token Transfers (Canton as Source)](/ccip/tutorials/canton/source/token-transfers) tutorial concepts. You need LINK and Amulet (or LINK fee token) on your Canton party.
+
+These steps use **Canton testnet** and **Ethereum Sepolia** only.
+
+</Aside>
+
+## Introduction
+
+A programmable token transfer combines a token transfer with a data payload delivered to the destination receiver contract. On Sepolia, the receiver's `ccipReceive` function receives both the tokens and the calldata.
+
+This tutorial uses the `canton2any:data-and-token` script to send LINK plus a UTF-8 string in a single CCIP message.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Run `canton2any:data-and-token` with `--dataString` and `--amount`.
+- Pay CCIP fees in Amulet or LINK.
+- Track delivery in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+- Verify token delivery and optional manual execution on Sepolia.
+
+## Understanding Programmable Token Transfers (canton2any)
+
+| Aspect          | Token-only         | Programmable token transfer                         |
+| :-------------- | :----------------- | :-------------------------------------------------- |
+| **Data**        | Empty              | UTF-8 string (or `0x:` prefixed ABI-encoded string) |
+| **Tokens**      | LINK only          | LINK + data in one message                          |
+| **Destination** | Tokens to receiver | Tokens + `ccipReceive` calldata on Sepolia          |
+
+The send path on Canton combines token pool lock/burn (`TokenPoolTicket`) with CommitteeVerifier tickets in a single `PerPartyRouter_CCIPSend`, as described in the [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain).
+
+## How the Script Works
+
+`scripts/canton2any/ccipSendDataAndToken.ts` builds a message with both `data` (from `encodeMessageData`) and `tokenAmounts` (Canton LINK instrument), then submits via `CantonChain.sendMessage` with the same fee and execution options as the other `canton2any` scripts.
+
+## Running the Programmable Token Transfer
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites).
+2. Confirm LINK and fee-token balances:
+
+   ```bash filename="Terminal"
+   npm run check-balance
+   ```
+
+### Execute the Script
+
+Send `0.001` LINK with a data payload:
+
+```bash filename="Terminal"
+npm run canton2any:data-and-token -- --dataString "Hello" --amount 0.001
+```
+
+Pay fee in LINK and skip auto-execution:
+
+```bash filename="Terminal"
+npm run canton2any:data-and-token -- --dataString "Hello" --amount 0.001 --feeToken link --no-exec
+```
+
+Custom Sepolia receiver and a higher gas limit (default is `200000`):
+
+```bash filename="Terminal"
+npm run canton2any:data-and-token -- \
+  --dataString "Hello" \
+  --amount 0.001 \
+  --evmReceiver 0xYourReceiverAddress \
+  --gasLimit 300000
+```
+
+### Understanding the Output
+
+```text
+📧🪙 Sending data + 0.001 LINK from Canton → Sepolia: "Hello"
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+```
+
+## Verification and Monitoring
+
+### CCIP Explorer
+
+Monitor message status and destination execution state in the CCIP Explorer.
+
+### Manual execution on Sepolia
+
+After `--no-exec` sends, run manual execution once Committee Verifier proofs are on the indexer:
+
+```bash filename="Terminal"
+npm run canton2any:manual-exec -- <cantonUpdateId | messageId>
+```
+
+Pass either the Canton **update ID** (`📜 Canton transaction` / Lighthouse link) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) from the send output — `canton2any:manual-exec` accepts both.
+
+### Verify on Sepolia
+
+Check TEST token balance and inspect the receiver contract's events on [Sepolia Etherscan](https://sepolia.etherscan.io/) to confirm both token delivery and data processing.
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/content/ccip/tutorials/canton/source/token-transfers.mdx b/src/content/ccip/tutorials/canton/source/token-transfers.mdx
new file mode 100644
index 00000000000..04950ca21e1
--- /dev/null
+++ b/src/content/ccip/tutorials/canton/source/token-transfers.mdx
@@ -0,0 +1,150 @@
+---
+section: ccip
+date: Last Modified
+title: "Token Transfers: Canton as Source"
+isIndex: false
+metadata:
+  description: "Transfer LINK tokens from Canton to Ethereum Sepolia using the CCIP Canton Starter Kit canton2any:token script."
+  image: "/images/ccip/concepts/architecture/ccip-canton-source-chain.png"
+  excerpt: "Canton as Source, canton2any, token transfers, LINK, CCIPSender"
+  datePublished: "2026-07-06"
+  lastModified: "2026-07-06"
+  estimatedTime: "25 minutes"
+  difficulty: "intermediate"
+---
+
+import { Aside } from "@components"
+import CcipCommon from "@features/ccip/CcipCommon.astro"
+
+<CcipCommon callout="cantonAddressesBanner" />
+
+This tutorial demonstrates how to transfer **LINK** tokens from Canton testnet to Ethereum Sepolia using the [`ccip-starter-kit-canton`](https://github.com/smartcontractkit/ccip-starter-kit-canton).
+
+<Aside title="Prerequisites">
+
+Complete the [Canton as Source prerequisites](/ccip/tutorials/canton/source/prerequisites). For token transfers you also need:
+
+- **LINK** holdings on your Canton party (the token being sent).
+- **Amulet** (or LINK with `--feeToken link`) for CCIP fees.
+- A registered token pool on the Token Admin Registry — the prod testnet **LINK ↔ TEST** lane is pre-configured. For custom instruments, see [Cross-Chain Token guides](/ccip/tutorials/canton/cross-chain-tokens).
+
+These steps use **Canton testnet** and **Ethereum Sepolia** only.
+
+</Aside>
+
+## Introduction
+
+This tutorial covers a token-only transfer from Canton to Ethereum Sepolia without an attached data payload. When you transfer tokens using CCIP:
+
+1. Tokens are burned or locked in the token pool on Canton.
+2. Equivalent tokens are minted or released on Sepolia after destination execution.
+3. CCIP fees are collected on Canton in Amulet (default) or LINK.
+
+The prod testnet lane maps Canton **LINK** to Sepolia **TEST**.
+
+## What You Will Build
+
+In this tutorial, you will:
+
+- Run `canton2any:token` to send LINK from Canton to Sepolia.
+- Pay CCIP fees in Amulet or LINK.
+- Monitor the transfer in the [CCIP Explorer](/ccip/tools-resources/ccip-explorer).
+- Verify TEST token balance on Sepolia after execution.
+
+## Understanding Token Transfers (canton2any)
+
+Key points for token-only transfers from Canton:
+
+- **Burn and mint**: LINK is burned on Canton; TEST is minted on Sepolia for the configured lane.
+- **Fee payment**: CCIP fees are paid on Canton. Default fee token is **Amulet**; pass `--feeToken link` to pay in LINK.
+- **No data payload**: Token-only transfers omit the `data` field.
+- **Token pool**: The SDK fetches disclosures from the token pool operator EDS and obtains a `TokenPoolTicket` during send.
+
+See the [Canton as Source flow](/ccip/concepts/canton/overview#canton--public-chain) in the overview.
+
+## How the Script Works
+
+The `scripts/canton2any/ccipSendToken.ts` script:
+
+1. Loads Canton config, authenticates to the ledger, and connects.
+2. Parses `--amount` (human-readable LINK, e.g. `0.001`), `--feeToken`, `--evmReceiver`, and `--no-exec`.
+3. Builds a message with `tokenAmounts` for the Canton LINK instrument and submits via `CantonChain.sendMessage`.
+4. Prints the CCIP Message ID, explorer links, and optional manual-exec hint.
+
+## Running the Token Transfer
+
+### Prerequisites Check
+
+1. Complete [prerequisites](/ccip/tutorials/canton/source/prerequisites).
+2. Verify LINK and Amulet balances:
+
+   ```bash filename="Terminal"
+   npm run check-balance -- --chain canton --token link
+   npm run check-balance -- --chain canton --token amulet
+   ```
+
+3. Set `EVM_PRIVATE_KEY` if you will verify Sepolia balances or run manual execution.
+
+### Execute the Script
+
+Send `0.001` LINK from Canton to Sepolia (default receiver):
+
+```bash filename="Terminal"
+npm run canton2any:token -- --amount 0.001
+```
+
+Pay CCIP fee in LINK:
+
+```bash filename="Terminal"
+npm run canton2any:token -- --amount 0.001 --feeToken link
+```
+
+Skip auto-execution on Sepolia:
+
+```bash filename="Terminal"
+npm run canton2any:token -- --amount 0.001 --no-exec
+```
+
+### Understanding the Output
+
+```text
+🪙 Sending 0.001 LINK from Canton → Sepolia
+   Executor: default (auto-execution on Sepolia when an executor is configured)
+🆔 CCIP Message ID: 0x…
+🔗 CCIP Explorer: https://ccip.chain.link/#/side-drawer/msg/0x…
+📜 Canton transaction: https://lighthouse.testnet.cantonloop.com/transactions/…
+```
+
+## Verification and Monitoring
+
+### CCIP Explorer
+
+Track the full message lifecycle using the CCIP Explorer URL from the output.
+
+### Manual execution on Sepolia
+
+If you used `--no-exec`:
+
+```bash filename="Terminal"
+npm run canton2any:manual-exec -- <cantonUpdateId | messageId>
+```
+
+Pass either the Canton **update ID** (`📜 Canton transaction` / Lighthouse link) or the **CCIP Message ID** (`🆔 CCIP Message ID`, `0x…`) from the send output — `canton2any:manual-exec` accepts both.
+
+### Verify TEST balance on Sepolia
+
+After successful execution, check the Sepolia wallet that received TEST:
+
+```bash filename="Terminal"
+npm run check-balance -- --chain sepolia --token test
+```
+
+Or inspect the receiver address on [Sepolia Etherscan](https://sepolia.etherscan.io/).
+
+<Aside type="note" title="Decimals">
+
+Canton LINK uses **10** decimal places in the starter kit configuration (`helperConfig.ts`), not the 18 decimals used on Sepolia ERC-20 tokens.
+
+</Aside>
+
+<CcipCommon callout="educationalDisclaimer" />
diff --git a/src/features/ccip/CantonAddressesBanner.mdx b/src/features/ccip/CantonAddressesBanner.mdx
new file mode 100644
index 00000000000..86da3971c46
--- /dev/null
+++ b/src/features/ccip/CantonAddressesBanner.mdx
@@ -0,0 +1,7 @@
+import { Aside } from "@components"
+
+<Aside type="caution">
+
+Addresses shown may change due to upgrades since Canton contracts are immutable. Confirm party IDs and contract addresses with [Chainlink CCIP](https://chain.link/ccip-contact).
+
+</Aside>
diff --git a/src/features/ccip/CcipCommon.astro b/src/features/ccip/CcipCommon.astro
index b3f3a1fff40..ff4dc70d18c 100644
--- a/src/features/ccip/CcipCommon.astro
+++ b/src/features/ccip/CcipCommon.astro
@@ -24,6 +24,7 @@ import EvmToSvmBasicPrerequisitesComponent from "./EvmToSvmBasicPrerequisites.md
 import CalloutCCTSVMComponent from "./CalloutCCTSVM.mdx"
 import SvmCrossChainTokenPrerequisitesComponent from "./SvmCrossChainTokenPrerequisites.mdx"
 import SvmCrossChainTokenProductionPrerequisitesComponent from "./SvmCrossChainTokenProductionPrerequisites.mdx"
+import CantonAddressesBannerComponent from "./CantonAddressesBanner.mdx"
 
 export type Props = {
   callout?:
@@ -53,6 +54,7 @@ export type Props = {
     | "calloutCCTSVM"
     | "svmCrossChainTokenPrerequisites"
     | "svmCrossChainTokenProductionPrerequisites"
+    | "cantonAddressesBanner"
 }
 const { callout } = Astro.props as Props
 ---
@@ -83,3 +85,4 @@ const { callout } = Astro.props as Props
 {callout === "calloutCCTSVM" && <CalloutCCTSVMComponent />}
 {callout === "svmCrossChainTokenPrerequisites" && <SvmCrossChainTokenPrerequisitesComponent />}
 {callout === "svmCrossChainTokenProductionPrerequisites" && <SvmCrossChainTokenProductionPrerequisitesComponent />}
+{callout === "cantonAddressesBanner" && <CantonAddressesBannerComponent />}
diff --git a/src/features/utils/index.ts b/src/features/utils/index.ts
index c044e273d3f..82a81fc58cf 100644
--- a/src/features/utils/index.ts
+++ b/src/features/utils/index.ts
@@ -90,6 +90,51 @@ export const getExplorerAddressUrl =
     return queryString ? `${url}?${queryString}` : url
   }
 
+/** Canton contract IDs are hashes — only party IDs are explorable in Lighthouse. */
+export const getCantonPartyIdFromAddress = (address?: string): string | undefined => {
+  if (!address) return undefined
+
+  const atIndex = address.indexOf("@")
+  if (atIndex !== -1) {
+    const partyId = address.slice(atIndex + 1)
+    return partyId || undefined
+  }
+
+  // Values like ccipOwner::1220... are already party IDs.
+  if (address.includes("::")) {
+    return address
+  }
+
+  return undefined
+}
+
+export const getCantonPartyExplorerUrl = (explorer: ExplorerInfo, partyId?: string): string | undefined => {
+  if (!partyId) return undefined
+  return `${explorer.baseUrl}/party/${encodeURIComponent(partyId)}`
+}
+
+export const getCantonAddressExplorerUrl = (explorer: ExplorerInfo, address?: string): string | undefined => {
+  const partyId = getCantonPartyIdFromAddress(address)
+  return getCantonPartyExplorerUrl(explorer, partyId)
+}
+
+/** Canton token addresses that should be copy-only (no Lighthouse link). */
+export const isCantonNativeFeeToken = (chain: string, tokenId: string): boolean => {
+  if (!chain.startsWith("canton-")) return false
+  if (tokenId === "LINK") return true
+  return (chain === "canton-mainnet" && tokenId === "CC") || (chain === "canton-testnet" && tokenId === "Amulet")
+}
+
+export const getContractExplorerUrl =
+  (explorer: ExplorerInfo, chainType: ChainType = "evm") =>
+  (contractAddress?: string): string | undefined => {
+    if (!contractAddress) return undefined
+    if (chainType === "canton") {
+      return getCantonAddressExplorerUrl(explorer, contractAddress)
+    }
+    return getExplorerAddressUrl(explorer, chainType)(contractAddress)
+  }
+
 export const getExplorerTransactionUrl = (explorer: ExplorerInfo) => (transactionSignature: string) => {
   const url = `${explorer.baseUrl}/tx/${transactionSignature}`
   if (!explorer.queryParameters) return url
@@ -595,6 +640,10 @@ export const directoryToSupportedChain = (chainInRdd: string): SupportedChain =>
       return "TON_TESTNET"
     case "ton-mainnet":
       return "TON_MAINNET"
+    case "canton-testnet":
+      return "CANTON_TESTNET"
+    case "canton-mainnet":
+      return "CANTON_MAINNET"
     case "creditcoin-mainnet":
       return "CREDITCOIN_MAINNET"
     default:
@@ -960,6 +1009,10 @@ export const supportedChainToChainInRdd = (supportedChain: SupportedChain): stri
       return "ton-testnet"
     case "TON_MAINNET":
       return "ton-mainnet"
+    case "CANTON_TESTNET":
+      return "canton-testnet"
+    case "CANTON_MAINNET":
+      return "canton-mainnet"
     case "CREDITCOIN_MAINNET":
       return "creditcoin-mainnet"
     default:
diff --git a/src/lib/ccip/services/chain-data.ts b/src/lib/ccip/services/chain-data.ts
index 2e92dba94b9..01925def1e7 100644
--- a/src/lib/ccip/services/chain-data.ts
+++ b/src/lib/ccip/services/chain-data.ts
@@ -407,15 +407,86 @@ class AptosChainStrategy extends BaseChainStrategy {
   }
 }
 
+// Canton Chain Strategy
+class CantonChainStrategy extends BaseChainStrategy {
+  validateChainData(
+    chainId: number | string | undefined,
+    networkId: string,
+    chainConfig: ChainsConfig[string],
+    selectorEntry?: { selector: string; name: string },
+    supportedChain?: SupportedChain
+  ): {
+    isValid: boolean
+    missingFields: string[]
+    validatedData?: ChainDetails
+  } {
+    const baseValidation = this.validateBaseFields(chainId, networkId, chainConfig, selectorEntry, supportedChain)
+
+    if (!baseValidation.isValid || !baseValidation.baseData) {
+      return {
+        isValid: false,
+        missingFields: baseValidation.missingFields,
+      }
+    }
+
+    const cantonRequiredFields = {
+      committeeVerifier: !chainConfig.committeeVerifier?.address,
+      feeQuoterModule: !chainConfig.feeQuoterModule?.address,
+    }
+
+    const missingFields: string[] = []
+
+    Object.entries(cantonRequiredFields).forEach(([field, isMissing]) => {
+      if (isMissing) missingFields.push(field)
+    })
+
+    if (missingFields.length > 0) {
+      logger.warn({
+        message: "Missing Canton-specific fields in chain configuration",
+        requestId: this.requestId,
+        networkId,
+        missingFields,
+      })
+
+      return {
+        isValid: false,
+        missingFields,
+      }
+    }
+
+    const { baseData } = baseValidation
+    const tokenAdminRegistry = chainConfig.tokenAdminRegistry?.address || undefined
+    const validatedData: ChainDetails = {
+      chainId: baseData.chainId!,
+      displayName: baseData.displayName!,
+      selector: baseData.selector!,
+      internalId: baseData.internalId!,
+      feeTokens: baseData.feeTokens!,
+      router: baseData.router!,
+      rmn: baseData.rmn!,
+      chainType: baseData.chainType!,
+      chainFamily: baseData.chainFamily!,
+      supported: true,
+      ...(tokenAdminRegistry ? { tokenAdminRegistry } : {}),
+    }
+
+    return {
+      isValid: true,
+      missingFields: [],
+      validatedData,
+    }
+  }
+}
+
 class ChainStrategyFactory {
   private static readonly strategies = new Map<ChainType, new (requestId: string) => IChainProcessingStrategy>([
     ["evm", EvmChainStrategy],
     ["solana", SolanaChainStrategy],
     ["aptos", AptosChainStrategy],
     ["sui", AptosChainStrategy], // Sui uses Move VM like Aptos
+    ["canton", CantonChainStrategy],
     // New chain types use EVM strategy as fallback until specific strategies are implemented
     ["tron", EvmChainStrategy],
-    ["canton", EvmChainStrategy],
     ["ton", EvmChainStrategy],
     ["stellar", EvmChainStrategy],
     ["starknet", EvmChainStrategy],
diff --git a/src/stores/chainType.ts b/src/stores/chainType.ts
index c6379945dd0..3ff598198eb 100644
--- a/src/stores/chainType.ts
+++ b/src/stores/chainType.ts
@@ -72,6 +72,7 @@ function detectChainFromPath(pathname: string): ChainType | null {
   if (/\/(svm|solana)(\/|$)/i.test(pathname)) return "solana"
   if (/\/aptos(\/|$)/i.test(pathname)) return "aptos"
   if (/\/ton(\/|$)/i.test(pathname)) return "ton"
+  if (/\/canton(\/|$)/i.test(pathname)) return "canton"
   return null
 }
 
diff --git a/src/styles/index.css b/src/styles/index.css
index f93d20c0c69..ed51c817aea 100644
--- a/src/styles/index.css
+++ b/src/styles/index.css
@@ -52,8 +52,8 @@ body {
 :where(a:hover) {
   color: var(--color-text-link-hover);
 }
-:where(a:focus) {
-  color: var(--color-text-link-clicked);
+:where(a:focus-visible) {
+  color: var(--color-text-link-active);
 }
 
 /*
@@ -74,7 +74,7 @@ a:hover code:not(pre code):not([class*="language-"]) {
 }
 
 a:focus-visible code:not(pre code):not([class*="language-"]) {
-  color: var(--color-text-link-clicked) !important;
+  color: var(--color-text-link-active) !important;
 }
 
 a:focus {