From 381a1dc0b0cf4f2e19ad605627fa99c899dc0af5 Mon Sep 17 00:00:00 2001 From: Karim <98668332+khadni@users.noreply.github.com> Date: Thu, 22 Jan 2026 08:04:01 -0500 Subject: [PATCH 1/4] add support for zksync --- public/changelog.json | 8 ++++ .../supported-networks-go.mdx | 42 ++++++++-------- .../supported-networks-ts.mdx | 46 ++++++++++-------- src/content/cre/llms-full-go.txt | 48 +++++++++++-------- src/content/cre/llms-full-ts.txt | 48 +++++++++++-------- src/content/cre/release-notes.mdx | 6 +++ 6 files changed, 120 insertions(+), 78 deletions(-) diff --git a/public/changelog.json b/public/changelog.json index bb66882b6b9..23d20d5cbc8 100644 --- a/public/changelog.json +++ b/public/changelog.json @@ -358,6 +358,14 @@ } }, "data": [ + { + "category": "integration", + "date": "2026-01-21", + "description": "CRE now supports ZKSync Era mainnet and testnet for workflow simulation and production deployment. See the [Supported Networks](https://docs.chain.link/cre/guides/workflow/using-evm-client/supported-networks) page for chain names and forwarder addresses.", + "relatedNetworks": ["zksync"], + "title": "CRE Expands to ZKSync Era", + "topic": "CRE" + }, { "category": "release", "date": "2026-01-21", diff --git a/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx b/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx index f63bada249b..c2734132607 100644 --- a/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx @@ -7,7 +7,7 @@ pageId: "evm-supported-networks" metadata: description: "Learn which EVM networks are supported for read and write operations in CRE workflows." datePublished: "2025-11-04" - lastModified: "2025-11-20" + lastModified: "2026-01-22" --- import { Aside, CopyText } from "@components" @@ -54,18 +54,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Ethereum Mainnet | | | | OP Mainnet | | | | Polygon | | | +| ZKSync Era | | | ### Simulation Testnets -| Network | Chain Name | Mock Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | -| Arbitrum Sepolia | | | -| Avalanche Fuji | | | -| Base Sepolia | | | -| BNB Chain Testnet | | | -| Ethereum Sepolia | | | -| OP Sepolia | | | -| Polygon Amoy | | | +| Network | Chain Name | Mock Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | +| Arbitrum Sepolia | | | +| Avalanche Fuji | | | +| Base Sepolia | | | +| BNB Chain Testnet | | | +| Ethereum Sepolia | | | +| OP Sepolia | | | +| Polygon Amoy | | | +| ZKSync Era Sepolia | | | ## Production Forwarders @@ -82,15 +84,17 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Ethereum Mainnet | | | | OP Mainnet | | | | Polygon | | | +| ZKSync Era | | | ### Testnets -| Network | Chain Name | Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | -| Arbitrum Sepolia | | | -| Avalanche Fuji | | | -| Base Sepolia | | | -| BNB Chain Testnet | | | -| Ethereum Sepolia | | | -| OP Sepolia | | | -| Polygon Amoy | | | +| Network | Chain Name | Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | +| Arbitrum Sepolia | | | +| Avalanche Fuji | | | +| Base Sepolia | | | +| BNB Chain Testnet | | | +| Ethereum Sepolia | | | +| OP Sepolia | | | +| Polygon Amoy | | | +| ZKSync Era Sepolia | | | diff --git a/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx b/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx index a2949f98d40..148f6dc54a8 100644 --- a/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx @@ -7,7 +7,7 @@ pageId: "evm-supported-networks" metadata: description: "Learn which EVM networks are supported for read and write operations in CRE workflows." datePublished: "2025-11-04" - lastModified: "2025-11-20" + lastModified: "2026-01-22" --- import { Aside, CopyText } from "@components" @@ -19,8 +19,8 @@ This page lists the EVM-compatible networks supported by CRE workflows, along wi This reference provides three key pieces of information for each network: 1. **Network Name**: The human-readable network identifier (click to view the forwarder contract on the block explorer) -2. **Chain Name**: The value to use in your [`project.yaml`](/cre/reference/project-configuration-ts#31-global-configuration-projectyaml) configuration and [EVM Client code](/cre/reference/sdk/evm-client-ts#chain-selectors) -3. **Forwarder Address**: The contract address for optional consumer contract validation (click to copy) +1. **Chain Name**: The value to use in your [`project.yaml`](/cre/reference/project-configuration-ts#31-global-configuration-projectyaml) configuration and [EVM Client code](/cre/reference/sdk/evm-client-ts#chain-selectors) +1. **Forwarder Address**: The contract address for optional consumer contract validation (click to copy) ## Understanding Forwarder Addresses @@ -54,18 +54,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Ethereum Mainnet | | | | OP Mainnet | | | | Polygon | | | +| ZKSync Era | | | ### Simulation Testnets -| Network | Chain Name | Mock Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | -| Arbitrum Sepolia | | | -| Avalanche Fuji | | | -| Base Sepolia | | | -| BSC Testnet | | | -| Ethereum Sepolia | | | -| OP Sepolia | | | -| Polygon Amoy | | | +| Network | Chain Name | Mock Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | +| Arbitrum Sepolia | | | +| Avalanche Fuji | | | +| Base Sepolia | | | +| BSC Testnet | | | +| Ethereum Sepolia | | | +| OP Sepolia | | | +| Polygon Amoy | | | +| ZKSync Era Sepolia | | | ## Production Forwarders @@ -82,15 +84,17 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Ethereum Mainnet | | | | OP Mainnet | | | | Polygon | | | +| ZKSync Era | | | ### Testnets -| Network | Chain Name | Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | -| Arbitrum Sepolia | | | -| Avalanche Fuji | | | -| Base Sepolia | | | -| BSC Testnet | | | -| Ethereum Sepolia | | | -| OP Sepolia | | | -| Polygon Amoy | | | +| Network | Chain Name | Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | +| Arbitrum Sepolia | | | +| Avalanche Fuji | | | +| Base Sepolia | | | +| BSC Testnet | | | +| Ethereum Sepolia | | | +| OP Sepolia | | | +| Polygon Amoy | | | +| ZKSync Era Sepolia | | | diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index 925d4dc06ff..06c75361cf7 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -446,6 +446,12 @@ Last Updated: 2026-01-21 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## ZKSync Era Support - January 21, 2026 + +CRE now supports **ZKSync Era mainnet and testnet** for workflow simulation and production deployment. You can now build and test workflows that interact with ZKSync Era chains. + +See the [Supported Networks](/cre/guides/workflow/using-evm-client/supported-networks) page for chain names and forwarder addresses. + ## CLI v1.0.6 - January 21, 2026 **CRE CLI version 1.0.6 is now available.** @@ -10962,7 +10968,7 @@ This approach gives you IDE autocompletion, compile-time type checking, and elim # Supported Networks Source: https://docs.chain.link/cre/guides/workflow/using-evm-client/supported-networks-go -Last Updated: 2025-11-20 +Last Updated: 2026-01-22 This page lists the EVM-compatible networks supported by CRE workflows, along with their chain names (for configuration) and forwarder contract addresses (for consumer contract validation). @@ -11006,18 +11012,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Ethereum Mainnet | ethereum-mainnet | 0xa3d1ad4ac559a6575a114998affb2fb2ec97a7d9 | | OP Mainnet | ethereum-mainnet-optimism-1 | 0x9119a1501550ed94a3f2794038ed9258337afa18 | | Polygon | polygon-mainnet | 0xf458d621885e29a5003ea9bbba5280d54e19b1ce | +| ZKSync Era | ethereum-mainnet-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | ### Simulation Testnets -| Network | Chain Name | Mock Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | -| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0xd41263567ddfead91504199b8c6c87371e83ca5d | -| Avalanche Fuji | avalanche-testnet-fuji | 0x2e7371a5d032489e4f60216d8d898a4c10805963 | -| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0x82300bd7c3958625581cc2f77bc6464dcecdf3e5 | -| BNB Chain Testnet | binance_smart_chain-testnet | 0xa238e42cb8782808dbb2f37e19859244ec4779b0 | -| Ethereum Sepolia | ethereum-testnet-sepolia | 0x15fC6ae953E024d975e77382eEeC56A9101f9F88 | -| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0xa2888380dff3704a8ab6d1cd1a8f69c15fea5ee3 | -| Polygon Amoy | polygon-testnet-amoy | 0x3675a5eb2286a3f87e8278fc66edf458a2e3bb74 | +| Network | Chain Name | Mock Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | +| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0xd41263567ddfead91504199b8c6c87371e83ca5d | +| Avalanche Fuji | avalanche-testnet-fuji | 0x2e7371a5d032489e4f60216d8d898a4c10805963 | +| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0x82300bd7c3958625581cc2f77bc6464dcecdf3e5 | +| BNB Chain Testnet | binance_smart_chain-testnet | 0xa238e42cb8782808dbb2f37e19859244ec4779b0 | +| Ethereum Sepolia | ethereum-testnet-sepolia | 0x15fC6ae953E024d975e77382eEeC56A9101f9F88 | +| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0xa2888380dff3704a8ab6d1cd1a8f69c15fea5ee3 | +| Polygon Amoy | polygon-testnet-amoy | 0x3675a5eb2286a3f87e8278fc66edf458a2e3bb74 | +| ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | ## Production Forwarders @@ -11034,18 +11042,20 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Ethereum Mainnet | ethereum-mainnet | 0x0b93082D9b3C7C97fAcd250082899BAcf3af3885 | | OP Mainnet | ethereum-mainnet-optimism-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | Polygon | polygon-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| ZKSync Era | ethereum-mainnet-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | ### Testnets -| Network | Chain Name | Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | -| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Avalanche Fuji | avalanche-testnet-fuji | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | -| BNB Chain Testnet | binance_smart_chain-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Ethereum Sepolia | ethereum-testnet-sepolia | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | -| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Polygon Amoy | polygon-testnet-amoy | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Network | Chain Name | Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | +| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Avalanche Fuji | avalanche-testnet-fuji | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | +| BNB Chain Testnet | binance_smart_chain-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Ethereum Sepolia | ethereum-testnet-sepolia | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | +| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Polygon Amoy | polygon-testnet-amoy | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | --- diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index 36ae4a3a743..989f9e2cf7b 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -446,6 +446,12 @@ Last Updated: 2026-01-21 This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## ZKSync Era Support - January 21, 2026 + +CRE now supports **ZKSync Era mainnet and testnet** for workflow simulation and production deployment. You can now build and test workflows that interact with ZKSync Era chains. + +See the [Supported Networks](/cre/guides/workflow/using-evm-client/supported-networks) page for chain names and forwarder addresses. + ## CLI v1.0.6 - January 21, 2026 **CRE CLI version 1.0.6 is now available.** @@ -9725,7 +9731,7 @@ This approach gives you the flexibility of direct ABI handling with the type saf # Supported Networks Source: https://docs.chain.link/cre/guides/workflow/using-evm-client/supported-networks-ts -Last Updated: 2025-11-20 +Last Updated: 2026-01-22 This page lists the EVM-compatible networks supported by CRE workflows, along with their chain names (for configuration) and forwarder contract addresses (for consumer contract validation). @@ -9769,18 +9775,20 @@ These `MockKeystoneForwarder` addresses are used when running `cre workflow simu | Ethereum Mainnet | ethereum-mainnet | 0xa3d1ad4ac559a6575a114998affb2fb2ec97a7d9 | | OP Mainnet | ethereum-mainnet-optimism-1 | 0x9119a1501550ed94a3f2794038ed9258337afa18 | | Polygon | polygon-mainnet | 0xf458d621885e29a5003ea9bbba5280d54e19b1ce | +| ZKSync Era | ethereum-mainnet-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | ### Simulation Testnets -| Network | Chain Name | Mock Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | -| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0xd41263567ddfead91504199b8c6c87371e83ca5d | -| Avalanche Fuji | avalanche-testnet-fuji | 0x2e7371a5d032489e4f60216d8d898a4c10805963 | -| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0x82300bd7c3958625581cc2f77bc6464dcecdf3e5 | -| BSC Testnet | binance_smart_chain-testnet | 0xa238e42cb8782808dbb2f37e19859244ec4779b0 | -| Ethereum Sepolia | ethereum-testnet-sepolia | 0x15fC6ae953E024d975e77382eEeC56A9101f9F88 | -| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0xa2888380dff3704a8ab6d1cd1a8f69c15fea5ee3 | -| Polygon Amoy | polygon-testnet-amoy | 0x3675a5eb2286a3f87e8278fc66edf458a2e3bb74 | +| Network | Chain Name | Mock Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | +| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0xd41263567ddfead91504199b8c6c87371e83ca5d | +| Avalanche Fuji | avalanche-testnet-fuji | 0x2e7371a5d032489e4f60216d8d898a4c10805963 | +| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0x82300bd7c3958625581cc2f77bc6464dcecdf3e5 | +| BSC Testnet | binance_smart_chain-testnet | 0xa238e42cb8782808dbb2f37e19859244ec4779b0 | +| Ethereum Sepolia | ethereum-testnet-sepolia | 0x15fC6ae953E024d975e77382eEeC56A9101f9F88 | +| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0xa2888380dff3704a8ab6d1cd1a8f69c15fea5ee3 | +| Polygon Amoy | polygon-testnet-amoy | 0x3675a5eb2286a3f87e8278fc66edf458a2e3bb74 | +| ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x6E9EE680ef59ef64Aa8C7371279c27E496b5eDc1 | ## Production Forwarders @@ -9797,18 +9805,20 @@ These `KeystoneForwarder` addresses are used by deployed workflows. Use these ad | Ethereum Mainnet | ethereum-mainnet | 0x0b93082D9b3C7C97fAcd250082899BAcf3af3885 | | OP Mainnet | ethereum-mainnet-optimism-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | | Polygon | polygon-mainnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| ZKSync Era | ethereum-mainnet-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | ### Testnets -| Network | Chain Name | Forwarder Address | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | -| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Avalanche Fuji | avalanche-testnet-fuji | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | -| BSC Testnet | binance_smart_chain-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Ethereum Sepolia | ethereum-testnet-sepolia | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | -| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | -| Polygon Amoy | polygon-testnet-amoy | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Network | Chain Name | Forwarder Address | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ | +| Arbitrum Sepolia | ethereum-testnet-sepolia-arbitrum-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Avalanche Fuji | avalanche-testnet-fuji | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Base Sepolia | ethereum-testnet-sepolia-base-1 | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | +| BSC Testnet | binance_smart_chain-testnet | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Ethereum Sepolia | ethereum-testnet-sepolia | 0xF8344CFd5c43616a4366C34E3EEE75af79a74482 | +| OP Sepolia | ethereum-testnet-sepolia-optimism-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| Polygon Amoy | polygon-testnet-amoy | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | +| ZKSync Era Sepolia | ethereum-testnet-sepolia-zksync-1 | 0x76c9cf548b4179F8901cda1f8623568b58215E62 | --- diff --git a/src/content/cre/release-notes.mdx b/src/content/cre/release-notes.mdx index a0d9a343423..9d28cc9069e 100644 --- a/src/content/cre/release-notes.mdx +++ b/src/content/cre/release-notes.mdx @@ -12,6 +12,12 @@ import { Aside } from "@components" This page provides detailed release notes for CRE. It includes information on new features, significant changes, and known limitations. +## ZKSync Era Support - January 21, 2026 + +CRE now supports **ZKSync Era mainnet and testnet** for workflow simulation and production deployment. You can now build and test workflows that interact with ZKSync Era chains. + +See the [Supported Networks](/cre/guides/workflow/using-evm-client/supported-networks) page for chain names and forwarder addresses. + ## CLI v1.0.6 - January 21, 2026 **CRE CLI version 1.0.6 is now available.** From 5caa80979fd013d7ebcfa03cebef23cdc8a5c8a6 Mon Sep 17 00:00:00 2001 From: Karim <98668332+khadni@users.noreply.github.com> Date: Thu, 22 Jan 2026 08:08:54 -0500 Subject: [PATCH 2/4] nit caution note update --- src/content/cre/llms-full-go.txt | 21 ++++++++++++------- src/content/cre/llms-full-ts.txt | 21 ++++++++++++------- src/content/cre/organization/linking-keys.mdx | 21 ++++++++++++------- 3 files changed, 42 insertions(+), 21 deletions(-) diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index a29f178176e..5c53f93b861 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -6750,6 +6750,11 @@ The CLI will submit an onchain transaction to remove the address from the Workfl If you need to unlink a key but no longer have access to the original private key (for example, the key owner left your organization), you can still complete the unlinking process using a different wallet. + + + ### How it works When you run `cre account unlink-key --unsigned` while logged into your CRE organization, the CLI generates: @@ -6814,7 +6819,14 @@ When you run `cre account unlink-key --unsigned` while logged into your CRE orga Unlinked successfully ``` -3. **Submit the transaction** using any wallet that supports sending transactions with custom data. Here's an example using MetaMask: +3. **Submit the transaction** using any wallet that supports sending transactions with custom data. + + + + + Here's an example using MetaMask: 1. In MetaMask, go to **Settings → Advanced** and enable **"Show hex data"** 2. Click **Send** and enter the contract address as the recipient 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5 @@ -6822,12 +6834,7 @@ When you run `cre account unlink-key --unsigned` while logged into your CRE orga 4. Paste the transaction data in the **Hex data** field (add `0x` prefix) 5. Review and confirm the transaction -The unlink operation completes once the transaction is confirmed onchain. All workflows registered under that address will be permanently deleted. - - - + The unlink operation completes once the transaction is confirmed onchain. All workflows registered under that address will be permanently deleted. ## Non-interactive mode diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index 32d47191b59..00afc184873 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -5673,6 +5673,11 @@ The CLI will submit an onchain transaction to remove the address from the Workfl If you need to unlink a key but no longer have access to the original private key (for example, the key owner left your organization), you can still complete the unlinking process using a different wallet. + + + ### How it works When you run `cre account unlink-key --unsigned` while logged into your CRE organization, the CLI generates: @@ -5737,7 +5742,14 @@ When you run `cre account unlink-key --unsigned` while logged into your CRE orga Unlinked successfully ``` -3. **Submit the transaction** using any wallet that supports sending transactions with custom data. Here's an example using MetaMask: +3. **Submit the transaction** using any wallet that supports sending transactions with custom data. + + + + + Here's an example using MetaMask: 1. In MetaMask, go to **Settings → Advanced** and enable **"Show hex data"** 2. Click **Send** and enter the contract address as the recipient 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5 @@ -5745,12 +5757,7 @@ When you run `cre account unlink-key --unsigned` while logged into your CRE orga 4. Paste the transaction data in the **Hex data** field (add `0x` prefix) 5. Review and confirm the transaction -The unlink operation completes once the transaction is confirmed onchain. All workflows registered under that address will be permanently deleted. - - - + The unlink operation completes once the transaction is confirmed onchain. All workflows registered under that address will be permanently deleted. ## Non-interactive mode diff --git a/src/content/cre/organization/linking-keys.mdx b/src/content/cre/organization/linking-keys.mdx index b8032013bb8..cf1bd48b878 100644 --- a/src/content/cre/organization/linking-keys.mdx +++ b/src/content/cre/organization/linking-keys.mdx @@ -225,6 +225,11 @@ The CLI will submit an onchain transaction to remove the address from the Workfl If you need to unlink a key but no longer have access to the original private key (for example, the key owner left your organization), you can still complete the unlinking process using a different wallet. +{/* prettier-ignore */} + + ### How it works When you run `cre account unlink-key --unsigned` while logged into your CRE organization, the CLI generates: @@ -289,19 +294,21 @@ When you run `cre account unlink-key --unsigned` while logged into your CRE orga Unlinked successfully ``` -1. **Submit the transaction** using any wallet that supports sending transactions with custom data. Here's an example using MetaMask: +1. **Submit the transaction** using any wallet that supports sending transactions with custom data. + + {/* prettier-ignore */} + + + Here's an example using MetaMask: 1. In MetaMask, go to **Settings → Advanced** and enable **"Show hex data"** 1. Click **Send** and enter the contract address as the recipient 1. Set the amount to **0 ETH** 1. Paste the transaction data in the **Hex data** field (add `0x` prefix) 1. Review and confirm the transaction -The unlink operation completes once the transaction is confirmed onchain. All workflows registered under that address will be permanently deleted. - -{/* prettier-ignore */} - + The unlink operation completes once the transaction is confirmed onchain. All workflows registered under that address will be permanently deleted. ## Non-interactive mode From 2c29b72dbf58cd901adec048c33c5000eadb66e4 Mon Sep 17 00:00:00 2001 From: Karim <98668332+khadni@users.noreply.github.com> Date: Thu, 22 Jan 2026 08:24:15 -0500 Subject: [PATCH 3/4] nit --- .../guides/workflow/using-evm-client/supported-networks-ts.mdx | 2 +- src/content/cre/llms-full-ts.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx b/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx index 148f6dc54a8..b42eb8231cb 100644 --- a/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx @@ -20,7 +20,7 @@ This reference provides three key pieces of information for each network: 1. **Network Name**: The human-readable network identifier (click to view the forwarder contract on the block explorer) 1. **Chain Name**: The value to use in your [`project.yaml`](/cre/reference/project-configuration-ts#31-global-configuration-projectyaml) configuration and [EVM Client code](/cre/reference/sdk/evm-client-ts#chain-selectors) -1. **Forwarder Address**: The contract address for optional consumer contract validation (click to copy) +1. **Forwarder Address**: The contract address for optional consumer contract validation ## Understanding Forwarder Addresses diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index 00afc184873..7620888c562 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -9831,7 +9831,7 @@ This reference provides three key pieces of information for each network: 1. **Network Name**: The human-readable network identifier (click to view the forwarder contract on the block explorer) 2. **Chain Name**: The value to use in your [`project.yaml`](/cre/reference/project-configuration-ts#31-global-configuration-projectyaml) configuration and [EVM Client code](/cre/reference/sdk/evm-client-ts#chain-selectors) -3. **Forwarder Address**: The contract address for optional consumer contract validation (click to copy) +3. **Forwarder Address**: The contract address for optional consumer contract validation ## Understanding Forwarder Addresses From 0cb8b704583ab299d0a772eaf0c7fd601af614c8 Mon Sep 17 00:00:00 2001 From: Karim <98668332+khadni@users.noreply.github.com> Date: Thu, 22 Jan 2026 13:53:18 -0500 Subject: [PATCH 4/4] forwarder clarification to reflect ReceiverTemplate reqs --- .../workflow/using-evm-client/supported-networks-go.mdx | 6 ++++-- .../workflow/using-evm-client/supported-networks-ts.mdx | 6 ++++-- src/content/cre/llms-full-go.txt | 6 ++++-- src/content/cre/llms-full-ts.txt | 6 ++++-- 4 files changed, 16 insertions(+), 8 deletions(-) diff --git a/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx b/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx index c2734132607..9ce397038c1 100644 --- a/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/supported-networks-go.mdx @@ -24,9 +24,11 @@ This reference provides three key pieces of information for each network: ## Understanding Forwarder Addresses -Forwarder addresses are relevant **only if you want to add security validation to your consumer contracts**. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-go). +Forwarder addresses identify the trusted Chainlink Forwarder contract that delivers verified workflow reports to your consumer contract. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-go). -**Optional security layer**: You can configure your consumer contract's `onReport()` function to accept calls only from the trusted forwarder address. See [Configuring Permissions](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#34-configuring-permissions) for implementation details. +**Using the [ReceiverTemplate](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#3-using-receivertemplate) (recommended)**: If you use the [`ReceiverTemplate`](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#receivertemplate), the forwarder address is **required** in the constructor. This ensures your contract only accepts reports from the trusted Chainlink Forwarder. + +**Custom implementations**: If you implement the `IReceiver` interface directly without using `ReceiverTemplate`, you control your own security checks. See [Building Consumer Contracts](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts) for details. ### Simulation vs Production Addresses diff --git a/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx b/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx index b42eb8231cb..1f674220aa8 100644 --- a/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx +++ b/src/content/cre/guides/workflow/using-evm-client/supported-networks-ts.mdx @@ -24,9 +24,11 @@ This reference provides three key pieces of information for each network: ## Understanding Forwarder Addresses -Forwarder addresses are relevant **only if you want to add security validation to your consumer contracts**. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-ts). +Forwarder addresses identify the trusted Chainlink Forwarder contract that delivers verified workflow reports to your consumer contract. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-ts). -**Optional security layer**: You can configure your consumer contract's `onReport()` function to accept calls only from the trusted forwarder address. See [Configuring Permissions](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#34-configuring-permissions) for implementation details. +**Using the [ReceiverTemplate](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#3-using-receivertemplate) (recommended)**: If you use the [`ReceiverTemplate`](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#receivertemplate), the forwarder address is **required** in the constructor. This ensures your contract only accepts reports from the trusted Chainlink Forwarder. + +**Custom implementations**: If you implement the `IReceiver` interface directly without using `ReceiverTemplate`, you control your own security checks. See [Building Consumer Contracts](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts) for details. ### Simulation vs Production Addresses diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index 5c53f93b861..6ae2a56ef00 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -11072,9 +11072,11 @@ This reference provides three key pieces of information for each network: ## Understanding Forwarder Addresses -Forwarder addresses are relevant **only if you want to add security validation to your consumer contracts**. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-go). +Forwarder addresses identify the trusted Chainlink Forwarder contract that delivers verified workflow reports to your consumer contract. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-go). -**Optional security layer**: You can configure your consumer contract's `onReport()` function to accept calls only from the trusted forwarder address. See [Configuring Permissions](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#34-configuring-permissions) for implementation details. +**Using the [ReceiverTemplate](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#3-using-receivertemplate) (recommended)**: If you use the [`ReceiverTemplate`](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#receivertemplate), the forwarder address is **required** in the constructor. This ensures your contract only accepts reports from the trusted Chainlink Forwarder. + +**Custom implementations**: If you implement the `IReceiver` interface directly without using `ReceiverTemplate`, you control your own security checks. See [Building Consumer Contracts](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts) for details. ### Simulation vs Production Addresses diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index 7620888c562..7f9e9eaf994 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -9835,9 +9835,11 @@ This reference provides three key pieces of information for each network: ## Understanding Forwarder Addresses -Forwarder addresses are relevant **only if you want to add security validation to your consumer contracts**. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-ts). +Forwarder addresses identify the trusted Chainlink Forwarder contract that delivers verified workflow reports to your consumer contract. Your workflow code does not interact with forwarders directly—the EVM capability handles report delivery automatically. Learn more: [Onchain Write Overview](/cre/guides/workflow/using-evm-client/onchain-write/overview-ts). -**Optional security layer**: You can configure your consumer contract's `onReport()` function to accept calls only from the trusted forwarder address. See [Configuring Permissions](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#34-configuring-permissions) for implementation details. +**Using the [ReceiverTemplate](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#3-using-receivertemplate) (recommended)**: If you use the [`ReceiverTemplate`](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#receivertemplate), the forwarder address is **required** in the constructor. This ensures your contract only accepts reports from the trusted Chainlink Forwarder. + +**Custom implementations**: If you implement the `IReceiver` interface directly without using `ReceiverTemplate`, you control your own security checks. See [Building Consumer Contracts](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts) for details. ### Simulation vs Production Addresses