smartcontractkit · ejacquier · May 11, 2026 · May 11, 2026 · May 12, 2026 · May 12, 2026
@@ -717,6 +717,11 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           url: "cre/reference/gelato-migration",
           highlightAsCurrent: ["cre/reference/gelato-migration-ts", "cre/reference/gelato-migration-go"],
         },
+        {
+          title: "Migrate from Chainlink Functions",
+          url: "cre/reference/clf-migration",
+          highlightAsCurrent: ["cre/reference/clf-migration-ts", "cre/reference/clf-migration-go"],
+        },
       ],
     },
   ],

@@ -13,11 +13,8 @@ whatsnext:
 
 import { Aside, CopyText, CodeSample, ClickToZoom } from "@components"
 import { Tabs } from "@components/Tabs"
-import ChainlinkFunctions from "@features/chainlink-functions/common/ChainlinkFunctions.astro"
 import { YouTube } from "@astro-community/astro-embed-youtube"
 
-<ChainlinkFunctions callout="cre" />
-
 Learn how to make requests to the Chainlink Functions Decentralized Oracle Network (DON) and make any computation or API calls offchain. Chainlink Functions is available on several blockchains (see the [supported networks page](/chainlink-functions/supported-networks)), but this guide uses Sepolia to simplify access to testnet funds. Complete the following tasks to get started with Chainlink Functions:
 
 - Set up your web3 wallet and fund it with testnet tokens.

@@ -12,9 +12,6 @@ whatsnext:
 ---
 
 import { Aside } from "@components"
-import ChainlinkFunctions from "@features/chainlink-functions/common/ChainlinkFunctions.astro"
-
-<ChainlinkFunctions callout="cre" />
 
 Chainlink Functions provides your smart contracts access to trust-minimized compute infrastructure, allowing you to fetch data from APIs and perform custom computation. Your smart contract sends source code in a request to a [Decentralized Oracle Network (DON)](/chainlink-functions/resources/concepts), and each node in the DON executes the code in a serverless environment. The DON then aggregates all the independent return values from each execution and sends the final result back to your smart contract.
 

@@ -397,8 +397,6 @@ const myArr = new Uint8Array(ARRAY_LENGTH)
 # Getting Started
 Source: https://docs.chain.link/chainlink-functions/getting-started
 
-<ChainlinkFunctions callout="cre" />
-
 Learn how to make requests to the Chainlink Functions Decentralized Oracle Network (DON) and make any computation or API calls offchain. Chainlink Functions is available on several blockchains (see the [supported networks page](/chainlink-functions/supported-networks)), but this guide uses Sepolia to simplify access to testnet funds. Complete the following tasks to get started with Chainlink Functions:
 
 - Set up your web3 wallet and fund it with testnet tokens.
@@ -876,8 +874,6 @@ Now that you understand the structure of the API. Let's delve into the JavaScrip
 # Chainlink Functions
 Source: https://docs.chain.link/chainlink-functions
 
-<ChainlinkFunctions callout="cre" />
-
 Chainlink Functions provides your smart contracts access to trust-minimized compute infrastructure, allowing you to fetch data from APIs and perform custom computation. Your smart contract sends source code in a request to a [Decentralized Oracle Network (DON)](/chainlink-functions/resources/concepts), and each node in the DON executes the code in a serverless environment. The DON then aggregates all the independent return values from each execution and sends the final result back to your smart contract.
 
 Chainlink Functions eliminates the need for you to manage your own Chainlink node and provides decentralized offchain computation and consensus, ensuring that a minority of the network cannot manipulate the response sent back to your smart contract.
@@ -1223,12 +1219,6 @@ Source: https://docs.chain.link/chainlink-functions/resources
 # Secrets Management
 Source: https://docs.chain.link/chainlink-functions/resources/secrets
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 Chainlink Functions enables users to fetch data from HTTP(s) APIs and perform custom computation. To enable access to APIs that require authentication credentials, Chainlink Functions allows users to provide encrypted secret values, which can be used when the DON executes a Functions request. These values can only be decrypted via a multi-party decryption process called threshold decryption. This means that every node can only decrypt the secrets with participation from other DON nodes.
 
 These encrypted secret values can either be uploaded to the DON or hosted at a remote URL. Then, a reference to the encrypted secrets can be used when making a Functions request.
@@ -1372,23 +1362,11 @@ You can read the [Examine the code section](/chainlink-functions/tutorials/simpl
 
 **Note**: You can also import and use the Chainlink Functions Toolkit NPM package as a scripting dependency inside [Remix IDE scripts](https://remix-ide.readthedocs.io/en/latest/running_js_scripts.html) in your browser.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues. Please be aware that Chainlink
-  Functions does not control how your secrets or environment variables are used or accessed within Remix or when
-  executing scripts within Remix, and the safekeeping of secrets and environment variables is your responsibility.
-</Aside>
-
 ---
 
 # Managing CL Functions Subscriptions
 Source: https://docs.chain.link/chainlink-functions/resources/subscriptions
 
-<Aside type="note" title="Mainnet Beta">
-  Chainlink Functions is available on mainnet only as a BETA preview to ensure that this new platform is robust and secure for developers. While in BETA, developers must follow best practices and not use the BETA for any mission-critical application or secure any value. Chainlink Functions is likely to evolve and improve. Breaking changes might occur while the service is in BETA. Monitor these docs to stay updated on feature improvements along with interface and contract changes.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You are responsible for independently reviewing any code and API dependencies that you submit in a request. Community-created code examples might not be audited, so you must independently review this code before you use it.
 
@@ -1516,12 +1494,6 @@ Developers who implement Chainlink Functions in their code and applications are
 
 ### Secrets
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 - **Self-hosted secrets**: Developers are responsible for securing self-hosted secrets, monitoring unauthorized access, auditing permissions, and ensuring that secrets are available for retrieval by Chainlink Functions when executing code.
 - **Secrets best practices**: For all types of secrets used with Chainlink Functions, developers must follow common best practices for managing secrets for applications. Developers are responsible for selecting, setting expiration time, monitoring, and rotating secrets to ensure the security of their applications and Chainlink Functions code.
 
@@ -2512,12 +2484,6 @@ To build a decentralized asset price, send a request to the DON to fetch the pri
 - [CoinGecko](https://www.coingecko.com/en/api/documentation)
 - [CoinPaprika](https://api.coinpaprika.com/)
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with
@@ -3144,12 +3110,6 @@ Read the [Using Secrets in Requests](/chainlink-functions/tutorials/api-use-secr
 2. Encrypt the gist URL.
 3. Include the encrypted gist URL in your Chainlink Functions request.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with
@@ -3333,12 +3293,6 @@ Read the [Using User-hosted (gist) Secrets in Requests](/chainlink-functions/tut
 4. Encrypt the S3 HTTPs URL .
 5. Include the encrypted URL in your Chainlink Functions request.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with
@@ -3569,12 +3523,6 @@ This tutorial shows you how to send a request to a Decentralized Oracle Network
 
 The encrypted secrets are never stored onchain. This tutorial uses the threshold encryption feature. The encrypted secrets are stored with the DON. Read the [Secrets Management page](/chainlink-functions/resources/secrets) to learn more.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with
@@ -3809,12 +3757,6 @@ Read the [Automate your Functions (Time-based Automation)](/chainlink-functions/
 
 After you deploy and set up your contract, Chainlink Automation triggers your function on every block.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with
@@ -4092,12 +4034,6 @@ Read the [API multiple calls](/chainlink-functions/tutorials/api-multiple-calls)
 
   After you deploy and set up your contract, Chainlink Automation triggers your function according to a time schedule.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with
@@ -4450,12 +4386,6 @@ Read the [Call Multiple Data Sources](/chainlink-functions/tutorials/api-multipl
 
 - Instead of sending the request data (source code, encrypted secrets reference, and arguments) in the request, you will first encode it offchain and then send the encoded request. Encoding the request offchain from your front end or a server rather than onchain from your smart contract. This helps save gas.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with

@@ -6,12 +6,6 @@ title: "Secrets Management"
 
 import { Aside } from "@components"
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 Chainlink Functions enables users to fetch data from HTTP(s) APIs and perform custom computation. To enable access to APIs that require authentication credentials, Chainlink Functions allows users to provide encrypted secret values, which can be used when the DON executes a Functions request. These values can only be decrypted via a multi-party decryption process called threshold decryption. This means that every node can only decrypt the secrets with participation from other DON nodes.
 
 These encrypted secret values can either be uploaded to the DON or hosted at a remote URL. Then, a reference to the encrypted secrets can be used when making a Functions request.

@@ -78,11 +78,3 @@ Follow the [Simple Computation](/chainlink-functions/tutorials/simple-computatio
 You can read the [Examine the code section](/chainlink-functions/tutorials/simple-computation#javascript-example) for a detailed description of the code example.
 
 **Note**: You can also import and use the Chainlink Functions Toolkit NPM package as a scripting dependency inside [Remix IDE scripts](https://remix-ide.readthedocs.io/en/latest/running_js_scripts.html) in your browser.
-
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues. Please be aware that Chainlink
-  Functions does not control how your secrets or environment variables are used or accessed within Remix or when
-  executing scripts within Remix, and the safekeeping of secrets and environment variables is your responsibility.
-</Aside>
@@ -6,11 +6,6 @@ title: "Managing CL Functions Subscriptions"
 
 import { Aside, ClickToZoom } from "@components"
 
-<Aside type="note" title="Mainnet Beta">
-Chainlink Functions is available on mainnet only as a BETA preview to ensure that this new platform is robust and secure for developers. While in BETA, developers must follow best practices and not use the BETA for any mission-critical application or secure any value. Chainlink Functions is likely to evolve and improve. Breaking changes might occur while the service is in BETA. Monitor these docs to stay updated on feature improvements along with interface and contract changes.
-
-</Aside>
-
 <Aside type="note">
 Chainlink Functions is a self-service solution. You are responsible for independently reviewing any code and API dependencies that you submit in a request. Community-created code examples might not be audited, so you must independently review this code before you use it.
 

@@ -33,12 +33,6 @@ Developers who implement Chainlink Functions in their code and applications are
 
 ### Secrets
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 - **Self-hosted secrets**: Developers are responsible for securing self-hosted secrets, monitoring unauthorized access, auditing permissions, and ensuring that secrets are available for retrieval by Chainlink Functions when executing code.
 - **Secrets best practices**: For all types of secrets used with Chainlink Functions, developers must follow common best practices for managing secrets for applications. Developers are responsible for selecting, setting expiration time, monitoring, and rotating secrets to ensure the security of their applications and Chainlink Functions code.
 

@@ -16,12 +16,6 @@ To build a decentralized asset price, send a request to the DON to fetch the pri
 - [CoinGecko](https://www.coingecko.com/en/api/documentation)
 - [CoinPaprika](https://api.coinpaprika.com/)
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with

@@ -17,12 +17,6 @@ Read the [Using Secrets in Requests](/chainlink-functions/tutorials/api-use-secr
 1. Encrypt the gist URL.
 1. Include the encrypted gist URL in your Chainlink Functions request.
 
-<Aside type="caution">
-  Chainlink Functions is still in BETA. The use of secrets in your requests is an experimental feature that may not
-  operate as expected and is subject to change. Use of this feature is at your own risk and may result in unexpected
-  errors, possible revealing of the secret as new versions are released, or other issues.
-</Aside>
-
 <Aside type="note">
   Chainlink Functions is a self-service solution. You must ensure that the data sources or APIs specified in requests
   are of sufficient quality and have the proper availability for your use case. You are responsible for complying with