From ae9190971520e48715f68f4ec9d548ebcbd8878a Mon Sep 17 00:00:00 2001
From: Emmanuel Jacquier <emmanuel.jacquier@gmail.com>
Date: Mon, 26 Oct 2026 12:04:01 -0400
Subject: [PATCH 1/6] Updated vrf deprecation notice

---
 public/cre/llms.txt                        |  3 +++
 src/content/vrf/index.mdx                  |  9 ++++++---
 src/content/vrf/llms-full.txt              |  9 ++++++---
 src/features/vrf/v1/common/deprecation.mdx | 10 +++++++---
 src/features/vrf/v2/common/deprecation.mdx | 11 ++++++++---
 5 files changed, 30 insertions(+), 12 deletions(-)

diff --git a/public/cre/llms.txt b/public/cre/llms.txt
index ed645e90707..ec986073384 100644
--- a/public/cre/llms.txt
+++ b/public/cre/llms.txt
@@ -31,6 +31,7 @@ Use `go/llms-full.txt` or `ts/llms-full.txt` only when broad CRE context is requ
 - [Triggers](https://docs.chain.link/cre/capabilities/triggers.md)
 - [HTTP](https://docs.chain.link/cre/capabilities/http.md)
 - [EVM Read and Write](https://docs.chain.link/cre/capabilities/evm-read-write.md)
+- [Solana Read and Write](https://docs.chain.link/cre/capabilities/solana-read-write.md)
 - [Confidential HTTP (Go)](https://docs.chain.link/cre/capabilities/confidential-http-go.md)
 - [Confidential HTTP (TypeScript)](https://docs.chain.link/cre/capabilities/confidential-http-ts.md)
 
@@ -41,6 +42,8 @@ Use `go/llms-full.txt` or `ts/llms-full.txt` only when broad CRE context is requ
 - [Using Confidential HTTP Client](https://docs.chain.link/cre/guides/workflow/using-confidential-http-client.md)
 - [Using EVM Client (Go)](https://docs.chain.link/cre/guides/workflow/using-evm-client/overview-go.md)
 - [Using EVM Client (TypeScript)](https://docs.chain.link/cre/guides/workflow/using-evm-client/overview-ts.md)
+- [Using Solana Client (Go)](https://docs.chain.link/cre/guides/workflow/using-solana-client/overview-go.md)
+- [Using Solana Client (TypeScript)](https://docs.chain.link/cre/guides/workflow/using-solana-client/overview-ts.md)
 - [Secrets](https://docs.chain.link/cre/guides/workflow/secrets.md)
 - [Using Randomness](https://docs.chain.link/cre/guides/workflow/using-randomness.md)
 
diff --git a/src/content/vrf/index.mdx b/src/content/vrf/index.mdx
index 5571cf79ff5..6849895a9b6 100644
--- a/src/content/vrf/index.mdx
+++ b/src/content/vrf/index.mdx
@@ -19,9 +19,12 @@ import { Aside } from "@components"
 
 \*In the unlikely event that an adversary compromises VRF's randomness-generating secret key and obtains the ability to construct blocks on the target chain, they could strongly bias the result.
 
-<Aside type="note" title="Migrate to V2.5">
-  Follow the [migration guide](/vrf/v2-5/migration-from-v2) to learn how VRF has changed in V2.5 and to get example
-  code.
+<Aside type="danger" title="VRF v1 and v2 shut down in November 2026">
+  VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+  48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+  November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+  application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions,
+  [contact us](https://chain.link/contact) or reach out to your Chainlink representative.
 </Aside>
 
 Use Chainlink VRF to build reliable smart contracts for any applications that rely on unpredictable outcomes:
diff --git a/src/content/vrf/llms-full.txt b/src/content/vrf/llms-full.txt
index 03a6028cfe2..3990ff3e4ca 100644
--- a/src/content/vrf/llms-full.txt
+++ b/src/content/vrf/llms-full.txt
@@ -9,10 +9,13 @@ Source: https://docs.chain.link/vrf
 
 \*In the unlikely event that an adversary compromises VRF's randomness-generating secret key and obtains the ability to construct blocks on the target chain, they could strongly bias the result.
 
-> **NOTE: Migrate to V2.5**
+> **DANGER: VRF v1 and v2 shut down in November 2026**
 >
-> Follow the [migration guide](/vrf/v2-5/migration-from-v2) to learn how VRF has changed in V2.5 and to get example
-> code.
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions,
+> [contact us](https://chain.link/contact) or reach out to your Chainlink representative.
 
 Use Chainlink VRF to build reliable smart contracts for any applications that rely on unpredictable outcomes:
 
diff --git a/src/features/vrf/v1/common/deprecation.mdx b/src/features/vrf/v1/common/deprecation.mdx
index 59b0bd91d84..f7c7510e8ae 100644
--- a/src/features/vrf/v1/common/deprecation.mdx
+++ b/src/features/vrf/v1/common/deprecation.mdx
@@ -1,8 +1,12 @@
 import { Aside } from "@components"
 
-<Aside type="caution" title="Chainlink VRF v1 is deprecated">
-  Security fixes for VRF v1 are not guaranteed. VRF v2.5 replaced both VRF v1 and VRF v2 on November 29, 2024. [Migrate
-  your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v1).
+<Aside type="danger" title="Chainlink VRF v1 shuts down on November 18, 2026">
+  VRF v1 was deprecated on November 29, 2024 and will be permanently shut down on November 18, 2026. After this date,
+  VRF v1 will no longer fulfill randomness requests. [Migrate your application to Chainlink VRF
+  v2.5](/vrf/v2-5/migration-from-v1) before November 18, 2026 to avoid service disruption.
+
+If you have questions about this shutdown or need help with your migration, [contact us](https://chain.link/contact)
+or reach out to your Chainlink representative.
 
 _Continued use of VRF v1 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures._
 
diff --git a/src/features/vrf/v2/common/deprecation.mdx b/src/features/vrf/v2/common/deprecation.mdx
index d1f15c3f775..6be57c4f4b9 100644
--- a/src/features/vrf/v2/common/deprecation.mdx
+++ b/src/features/vrf/v2/common/deprecation.mdx
@@ -1,12 +1,17 @@
 import { Aside } from "@components"
 
-<Aside type="caution" title="Chainlink VRF v2 is deprecated">
-  Security fixes for VRF v2 are not guaranteed. VRF v2.5 replaced both VRF v1 and VRF v2 on November 29, 2024. [Migrate
-  your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2).
+<Aside type="danger" title="Chainlink VRF v2 shuts down on November 30, 2026">
+  VRF v2 was deprecated on November 29, 2024 and will be permanently shut down on November 30, 2026. A 48-hour
+  brownout is scheduled for October 28-30, 2026, during which VRF v2 will not fulfill randomness requests. After the
+  shutdown date, VRF v2 will no longer fulfill randomness requests. [Migrate your application to Chainlink VRF
+  v2.5](/vrf/v2-5/migration-from-v2) before November 30, 2026 to avoid service disruption.
 
 The migration guide includes VRF v2.5 code examples for both subscription and direct funding and explains the
 differences between VRF v2.5 and VRF v2.
 
+If you have questions about this shutdown or need help with your migration, [contact us](https://chain.link/contact)
+or reach out to your Chainlink representative.
+
 _Continued use of VRF v2 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures._
 
 </Aside>

From 8feb2dca5fb3a38abcdab09a5348888a69977571 Mon Sep 17 00:00:00 2001
From: Emmanuel Jacquier <emmanuel.jacquier@gmail.com>
Date: Mon, 26 Oct 2026 12:11:52 -0400
Subject: [PATCH 2/6] Updated vrf noticed

---
 src/content/vrf/index.mdx                  | 2 +-
 src/content/vrf/llms-full.txt              | 2 +-
 src/features/vrf/v1/common/deprecation.mdx | 4 ++--
 src/features/vrf/v2/common/deprecation.mdx | 4 ++--
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/src/content/vrf/index.mdx b/src/content/vrf/index.mdx
index 6849895a9b6..fe9efb912e6 100644
--- a/src/content/vrf/index.mdx
+++ b/src/content/vrf/index.mdx
@@ -24,7 +24,7 @@ import { Aside } from "@components"
   48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
   November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
   application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions,
-  [contact us](https://chain.link/contact) or reach out to your Chainlink representative.
+  reach out to your Chainlink representative.
 </Aside>
 
 Use Chainlink VRF to build reliable smart contracts for any applications that rely on unpredictable outcomes:
diff --git a/src/content/vrf/llms-full.txt b/src/content/vrf/llms-full.txt
index 3990ff3e4ca..cfc4f710409 100644
--- a/src/content/vrf/llms-full.txt
+++ b/src/content/vrf/llms-full.txt
@@ -15,7 +15,7 @@ Source: https://docs.chain.link/vrf
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
 > November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
 > application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions,
-> [contact us](https://chain.link/contact) or reach out to your Chainlink representative.
+> reach out to your Chainlink representative.
 
 Use Chainlink VRF to build reliable smart contracts for any applications that rely on unpredictable outcomes:
 
diff --git a/src/features/vrf/v1/common/deprecation.mdx b/src/features/vrf/v1/common/deprecation.mdx
index f7c7510e8ae..f3068299ef2 100644
--- a/src/features/vrf/v1/common/deprecation.mdx
+++ b/src/features/vrf/v1/common/deprecation.mdx
@@ -5,8 +5,8 @@ import { Aside } from "@components"
   VRF v1 will no longer fulfill randomness requests. [Migrate your application to Chainlink VRF
   v2.5](/vrf/v2-5/migration-from-v1) before November 18, 2026 to avoid service disruption.
 
-If you have questions about this shutdown or need help with your migration, [contact us](https://chain.link/contact)
-or reach out to your Chainlink representative.
+If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+representative.
 
 _Continued use of VRF v1 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures._
 
diff --git a/src/features/vrf/v2/common/deprecation.mdx b/src/features/vrf/v2/common/deprecation.mdx
index 6be57c4f4b9..26f8bfcbe72 100644
--- a/src/features/vrf/v2/common/deprecation.mdx
+++ b/src/features/vrf/v2/common/deprecation.mdx
@@ -9,8 +9,8 @@ import { Aside } from "@components"
 The migration guide includes VRF v2.5 code examples for both subscription and direct funding and explains the
 differences between VRF v2.5 and VRF v2.
 
-If you have questions about this shutdown or need help with your migration, [contact us](https://chain.link/contact)
-or reach out to your Chainlink representative.
+If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+representative.
 
 _Continued use of VRF v2 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures._
 

From 873f79ef3e77cfaacf4829a94500e23e6b42347e Mon Sep 17 00:00:00 2001
From: Emmanuel Jacquier <emmanuel.jacquier@gmail.com>
Date: Mon, 26 Oct 2026 13:19:18 -0400
Subject: [PATCH 3/6] Updated vrf notice to be in all vrf pages

---
 src/content/vrf/index.mdx                     |  12 +-
 src/content/vrf/llms-full.txt                 | 130 ++++++++++++++++--
 .../vrf/v2-5/arbitrum-cost-estimation.mdx     |   3 +
 src/content/vrf/v2-5/best-practices.mdx       |   3 +
 src/content/vrf/v2-5/billing.mdx              |   3 +
 .../direct-funding/get-a-random-number.mdx    |   3 +
 src/content/vrf/v2-5/getting-started.mdx      |   3 +
 src/content/vrf/v2-5/migration-from-v1.mdx    |   9 +-
 src/content/vrf/v2-5/migration-from-v2.mdx    |   9 +-
 .../vrf/v2-5/overview/direct-funding.mdx      |   3 +
 .../vrf/v2-5/overview/subscription.mdx        |   3 +
 src/content/vrf/v2-5/security.mdx             |   4 +
 .../vrf/v2-5/subscription/create-manage.mdx   |   3 +
 .../v2-5/subscription/get-a-random-number.mdx |   3 +
 .../vrf/v2-5/subscription/test-locally.mdx    |   3 +
 src/content/vrf/v2-5/supported-networks.mdx   |   3 +
 src/features/vrf/VrfDeprecation.astro         |   4 +-
 src/features/vrf/v2-5/v1-v2-shutdown.mdx      |   9 ++
 18 files changed, 184 insertions(+), 26 deletions(-)
 create mode 100644 src/features/vrf/v2-5/v1-v2-shutdown.mdx

diff --git a/src/content/vrf/index.mdx b/src/content/vrf/index.mdx
index fe9efb912e6..28a3a778953 100644
--- a/src/content/vrf/index.mdx
+++ b/src/content/vrf/index.mdx
@@ -11,7 +11,9 @@ metadata:
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
-import { Aside } from "@components"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
+
+<VrfDeprecation version="v2-5" />
 
 <Vrf2_5Common callout="security" />
 
@@ -19,14 +21,6 @@ import { Aside } from "@components"
 
 \*In the unlikely event that an adversary compromises VRF's randomness-generating secret key and obtains the ability to construct blocks on the target chain, they could strongly bias the result.
 
-<Aside type="danger" title="VRF v1 and v2 shut down in November 2026">
-  VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
-  48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-  November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-  application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions,
-  reach out to your Chainlink representative.
-</Aside>
-
 Use Chainlink VRF to build reliable smart contracts for any applications that rely on unpredictable outcomes:
 
 - Building blockchain games and NFTs.
diff --git a/src/content/vrf/llms-full.txt b/src/content/vrf/llms-full.txt
index cfc4f710409..05c082b8d1f 100644
--- a/src/content/vrf/llms-full.txt
+++ b/src/content/vrf/llms-full.txt
@@ -1,6 +1,14 @@
 # Chainlink VRF
 Source: https://docs.chain.link/vrf
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 > **TIP: Security Considerations**
 >
 > Be sure to review your contracts with the [security considerations](/vrf/v2-5/security) in mind.
@@ -9,14 +17,6 @@ Source: https://docs.chain.link/vrf
 
 \*In the unlikely event that an adversary compromises VRF's randomness-generating secret key and obtains the ability to construct blocks on the target chain, they could strongly bias the result.
 
-> **DANGER: VRF v1 and v2 shut down in November 2026**
->
-> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
-> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions,
-> reach out to your Chainlink representative.
-
 Use Chainlink VRF to build reliable smart contracts for any applications that rely on unpredictable outcomes:
 
 - Building blockchain games and NFTs.
@@ -66,6 +66,14 @@ To learn when VRF v2.5 becomes available on more networks, follow us on [Twitter
 # Getting Started with Chainlink VRF V2.5
 Source: https://docs.chain.link/vrf/v2-5/getting-started
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 > **NOTE: Requirements**
 >
 > This guide assumes that you have basic knowledge about writing and deploying smart contracts. If you are new to smart
@@ -433,9 +441,14 @@ To read more about generating random numbers in Solidity, read our blog posts:
 # Migrating from VRF v2
 Source: https://docs.chain.link/vrf/v2-5/migration-from-v2
 
-> **CAUTION: Chainlink VRF v2 is deprecated**
+> **DANGER: Chainlink VRF v2 shuts down on November 30, 2026**
+>
+> VRF v2 was deprecated on November 29, 2024 and will be permanently shut down on November 30, 2026. A 48-hour
+> brownout is scheduled for October 28-30, 2026, during which VRF v2 will not fulfill randomness requests. Complete
+> this guide to migrate your application to Chainlink VRF v2.5 before November 30, 2026 to avoid service disruption.
 >
-> Security fixes for VRF v2 are not guaranteed. Complete this guide to migrate your application to Chainlink VRF v2.5.
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 >
 > *Continued use of VRF v2 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures.*
 
@@ -907,9 +920,14 @@ ConfirmedOwner
 # Migrating from VRF v1
 Source: https://docs.chain.link/vrf/v2-5/migration-from-v1
 
-> **CAUTION: Chainlink VRF v1 is deprecated**
+> **DANGER: Chainlink VRF v1 shuts down on November 18, 2026**
+>
+> VRF v1 was deprecated on November 29, 2024 and will be permanently shut down on November 18, 2026. After this date,
+> VRF v1 will no longer fulfill randomness requests. Complete this guide to migrate your application to Chainlink VRF
+> v2.5 before November 18, 2026 to avoid service disruption.
 >
-> Security fixes for VRF v1 are not guaranteed. Complete this guide to migrate your application to Chainlink VRF v2.5.
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 >
 > *Continued use of VRF v1 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures.*
 
@@ -1168,6 +1186,14 @@ Open the full example `DirectFundingConsumer` contract:
 # Supported Networks
 Source: https://docs.chain.link/vrf/v2-5/supported-networks
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 Chainlink VRF allows you to integrate provably fair and verifiably random data in your smart contract. For implementation details, read [Introduction to Chainlink VRF](/vrf).
 
 VRF v2.5 coordinators for subscription funding are available on several networks. To use Chainlink VRF on certain networks, you may need to conduct token transfers. You can transfer tokens by using [Chainlink CCIP](/ccip/evm/tutorials/application-developers/transfer-tokens-from-contract), [Transporter](https://www.transporter.io/) or third-party applications such as [XSwap](https://xswap.link/).
@@ -1878,6 +1904,14 @@ Chainlink's PegSwap service**](https://pegswap.chain.link/)
 # VRF Security Considerations
 Source: https://docs.chain.link/vrf/v2-5/security
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 Gaining access to high quality randomness onchain requires a solution like Chainlink's VRF, but it also requires you to understand some of the ways that miners or validators can potentially manipulate randomness generation. Here are some of the top security considerations you should review in your project.
 
 ## Use `requestId` to match randomness requests with their fulfillment in order
@@ -1935,6 +1969,14 @@ Fulfillments require sufficient subscription balance at processing time. If the
 # VRF Best Practices
 Source: https://docs.chain.link/vrf/v2-5/best-practices
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 > **TIP: Security Considerations**
 >
 > Be sure to review your contracts with the [security considerations](/vrf/v2-5/security) in mind.
@@ -2157,6 +2199,14 @@ contract VRFv2MultiplePaths is VRFConsumerBaseV2Plus {
 # VRF Billing
 Source: https://docs.chain.link/vrf/v2-5/billing
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 This guide explains how to estimate VRF 2.5 costs for both the subscription and direct funding methods.
 
 ## Understanding transaction costs
@@ -2469,6 +2519,14 @@ This example request would cost 0.01266474 ETH.
 # Subscription Method
 Source: https://docs.chain.link/vrf/v2-5/overview/subscription
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 > **TIP: Security Considerations**
 >
 > Be sure to review your contracts with the [security considerations](/vrf/v2-5/security) in mind.
@@ -2633,6 +2691,14 @@ You can see the configuration for each network on the [Supported networks](/vrf/
 # Direct Funding Method
 Source: https://docs.chain.link/vrf/v2-5/overview/direct-funding
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 This guide explains how to generate random numbers using the *direct funding* method. This method doesn't require a subscription and is optimal for one-off requests for randomness. This method also works best for applications where your end-users must pay the fees for VRF because the cost of the request is determined at request time.
 
 > **NOTE: Migrate to V2.5**
@@ -2707,6 +2773,14 @@ You can see the configuration for each network on the [Supported networks](/vrf/
 # VRF Cost Estimation on Arbitrum
 Source: https://docs.chain.link/vrf/v2-5/arbitrum-cost-estimation
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 The total transaction costs for using Arbitrum involve both L2 gas costs and L1 costs. Arbitrum transactions are [posted in batches to L1 Ethereum](https://developer.arbitrum.io/inside-arbitrum-nitro/#how-the-sequencer-publishes-the-sequence), which incurs an L1 cost. For an individual transaction, the total cost includes part of the L1 cost incurred to post the batch that included the transaction.
 
 To learn how to estimate gas costs for Arbitrum, refer to the [Arbitrum gas estimation tutorial](https://developer.arbitrum.io/devs-how-tos/how-to-estimate-gas) and the full [Arbitrum gas estimation script](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/gas-estimation) using their SDK. There is also a [**version of Arbitrum's gas estimation script extended to include VRF calculations**](#arbitrum-and-vrf-gas-estimation-code).
@@ -2856,6 +2930,14 @@ const VRFDirectFundingGasEstimate = P.mul(VRFDirectFundingGasTotal)
 # Create and manage VRF V2.5 subscriptions
 Source: https://docs.chain.link/vrf/v2-5/subscription/create-manage
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 > **TIP: Security Considerations**
 >
 > Be sure to review your contracts with the [security considerations](/vrf/v2-5/security) in mind.
@@ -2944,6 +3026,14 @@ If you prefer to create, fund and manage your subscriptions programmatically, yo
 # Get a Random Number
 Source: https://docs.chain.link/vrf/v2-5/subscription/get-a-random-number
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 This guide explains how to get random values using a simple contract to request and receive random values from Chainlink VRF v2.5. The guide uses the Subscription Manager to create and manage your subscription. Alternatively, you can also [create and manage subscriptions programmatically](/vrf/v2-5/subscription/create-manage#create-a-subscription-programmatically). To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
 
 > **NOTE: VRF Subscription Manager limitations**
@@ -3215,6 +3305,14 @@ After you are done with this contract and the subscription, you can retrieve the
 # Local testing using a mock subscription contract
 Source: https://docs.chain.link/vrf/v2-5/subscription/test-locally
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 This guide explains how to test Chainlink VRF v2.5 on a [Remix IDE](https://remix-ide.readthedocs.io/en/latest/run.html#environment) sandbox blockchain environment. **Note**: You can reuse the same logic on another development environment, such as Hardhat or Foundry. For example, read the Hardhat Starter Kit [RandomNumberConsumer unit tests](https://github.com/smartcontractkit/hardhat-starter-kit/blob/main/test/unit/RandomNumberConsumer.spec.js).
 
 > **CAUTION: Test on public testnets thoroughly**
@@ -3477,6 +3575,14 @@ This guide demonstrated how to test a VRF v2.5 consumer contract on your local b
 # Get a Random Number
 Source: https://docs.chain.link/vrf/v2-5/direct-funding/get-a-random-number
 
+> **DANGER: VRF v1 and v2 shut down in November 2026**
+>
+> VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+> 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+
 This guide explains how to get random values using a simple contract to request and receive random values from Chainlink VRF v2.5 without managing a subscription. To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
 
 ## Requirements
diff --git a/src/content/vrf/v2-5/arbitrum-cost-estimation.mdx b/src/content/vrf/v2-5/arbitrum-cost-estimation.mdx
index d4bf8a04327..ec19dec9620 100644
--- a/src/content/vrf/v2-5/arbitrum-cost-estimation.mdx
+++ b/src/content/vrf/v2-5/arbitrum-cost-estimation.mdx
@@ -8,8 +8,11 @@ metadata:
 isMdx: true
 ---
 
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { Tabs, TabsContent } from "@components/Tabs"
 
+<VrfDeprecation version="v2-5" />
+
 The total transaction costs for using Arbitrum involve both L2 gas costs and L1 costs. Arbitrum transactions are [posted in batches to L1 Ethereum](https://developer.arbitrum.io/inside-arbitrum-nitro/#how-the-sequencer-publishes-the-sequence), which incurs an L1 cost. For an individual transaction, the total cost includes part of the L1 cost incurred to post the batch that included the transaction.
 
 To learn how to estimate gas costs for Arbitrum, refer to the [Arbitrum gas estimation tutorial](https://developer.arbitrum.io/devs-how-tos/how-to-estimate-gas) and the full [Arbitrum gas estimation script](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/gas-estimation) using their SDK. There is also a [**version of Arbitrum's gas estimation script extended to include VRF calculations**](#arbitrum-and-vrf-gas-estimation-code).
diff --git a/src/content/vrf/v2-5/best-practices.mdx b/src/content/vrf/v2-5/best-practices.mdx
index 68a6f277b25..4a564768135 100644
--- a/src/content/vrf/v2-5/best-practices.mdx
+++ b/src/content/vrf/v2-5/best-practices.mdx
@@ -8,8 +8,11 @@ metadata:
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { CodeSample } from "@components"
 
+<VrfDeprecation version="v2-5" />
+
 <Vrf2_5Common callout="security" />
 
 These are example best practices for using Chainlink VRF. To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
diff --git a/src/content/vrf/v2-5/billing.mdx b/src/content/vrf/v2-5/billing.mdx
index f5af8dccbdf..cebb09c3ea2 100644
--- a/src/content/vrf/v2-5/billing.mdx
+++ b/src/content/vrf/v2-5/billing.mdx
@@ -8,9 +8,12 @@ metadata:
 isMdx: true
 ---
 
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { CodeSample } from "@components"
 import { TabsContent } from "@components/Tabs"
 
+<VrfDeprecation version="v2-5" />
+
 This guide explains how to estimate VRF 2.5 costs for both the subscription and direct funding methods.
 
 ## Understanding transaction costs
diff --git a/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx b/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx
index e2d104ed172..715fce77c4c 100644
--- a/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx
+++ b/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx
@@ -14,9 +14,12 @@ metadata:
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { Aside, CodeSample } from "@components"
 import { TabsContent } from "@components/Tabs"
 
+<VrfDeprecation version="v2-5" />
+
 This guide explains how to get random values using a simple contract to request and receive random values from Chainlink VRF v2.5 without managing a subscription. To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
 
 ## Requirements
diff --git a/src/content/vrf/v2-5/getting-started.mdx b/src/content/vrf/v2-5/getting-started.mdx
index 4bd87aca8f2..d2d8842e280 100644
--- a/src/content/vrf/v2-5/getting-started.mdx
+++ b/src/content/vrf/v2-5/getting-started.mdx
@@ -15,8 +15,11 @@ metadata:
   image: "/files/2a242f1-link.png"
 ---
 
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { Aside, CodeSample, ClickToZoom } from "@components"
 
+<VrfDeprecation version="v2-5" />
+
 <Aside type="note" title="Requirements">
   This guide assumes that you have basic knowledge about writing and deploying smart contracts. If you are new to smart
   contract development, learn how to [Deploy Your First Smart Contract](/quickstarts/deploy-your-first-contract) before
diff --git a/src/content/vrf/v2-5/migration-from-v1.mdx b/src/content/vrf/v2-5/migration-from-v1.mdx
index 4d3d43d822e..eafe8cd6934 100644
--- a/src/content/vrf/v2-5/migration-from-v1.mdx
+++ b/src/content/vrf/v2-5/migration-from-v1.mdx
@@ -8,8 +8,13 @@ import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
 import { Aside, CodeSample } from "@components"
 import { Tabs, TabsContent } from "@components/Tabs"
 
-<Aside type="caution" title="Chainlink VRF v1 is deprecated">
-  Security fixes for VRF v1 are not guaranteed. Complete this guide to migrate your application to Chainlink VRF v2.5.
+<Aside type="danger" title="Chainlink VRF v1 shuts down on November 18, 2026">
+  VRF v1 was deprecated on November 29, 2024 and will be permanently shut down on November 18, 2026. After this date,
+  VRF v1 will no longer fulfill randomness requests. Complete this guide to migrate your application to Chainlink VRF
+  v2.5 before November 18, 2026 to avoid service disruption.
+
+If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+representative.
 
 _Continued use of VRF v1 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures._
 
diff --git a/src/content/vrf/v2-5/migration-from-v2.mdx b/src/content/vrf/v2-5/migration-from-v2.mdx
index f154c9ce77e..8f9dd92d840 100644
--- a/src/content/vrf/v2-5/migration-from-v2.mdx
+++ b/src/content/vrf/v2-5/migration-from-v2.mdx
@@ -8,8 +8,13 @@ import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
 import { Aside, CodeSample } from "@components"
 import { Tabs, TabsContent } from "@components/Tabs"
 
-<Aside type="caution" title="Chainlink VRF v2 is deprecated">
-  Security fixes for VRF v2 are not guaranteed. Complete this guide to migrate your application to Chainlink VRF v2.5.
+<Aside type="danger" title="Chainlink VRF v2 shuts down on November 30, 2026">
+  VRF v2 was deprecated on November 29, 2024 and will be permanently shut down on November 30, 2026. A 48-hour
+  brownout is scheduled for October 28-30, 2026, during which VRF v2 will not fulfill randomness requests. Complete
+  this guide to migrate your application to Chainlink VRF v2.5 before November 30, 2026 to avoid service disruption.
+
+If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+representative.
 
 _Continued use of VRF v2 is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures._
 
diff --git a/src/content/vrf/v2-5/overview/direct-funding.mdx b/src/content/vrf/v2-5/overview/direct-funding.mdx
index 75e04dec222..dbe367dd8eb 100644
--- a/src/content/vrf/v2-5/overview/direct-funding.mdx
+++ b/src/content/vrf/v2-5/overview/direct-funding.mdx
@@ -13,8 +13,11 @@ metadata:
 ---
 
 import VrfCommon from "@features/vrf/v2/common/VrfCommon.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { Aside, ClickToZoom } from "@components"
 
+<VrfDeprecation version="v2-5" />
+
 This guide explains how to generate random numbers using the _direct funding_ method. This method doesn't require a subscription and is optimal for one-off requests for randomness. This method also works best for applications where your end-users must pay the fees for VRF because the cost of the request is determined at request time.
 
 <Aside type="note" title="Migrate to V2.5">
diff --git a/src/content/vrf/v2-5/overview/subscription.mdx b/src/content/vrf/v2-5/overview/subscription.mdx
index 08d5354bb10..eea4fc69de9 100644
--- a/src/content/vrf/v2-5/overview/subscription.mdx
+++ b/src/content/vrf/v2-5/overview/subscription.mdx
@@ -8,10 +8,13 @@ metadata:
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { Aside, ClickToZoom } from "@components"
 import { TabsContent } from "@components/Tabs"
 import { YouTube } from "@astro-community/astro-embed-youtube"
 
+<VrfDeprecation version="v2-5" />
+
 <Vrf2_5Common callout="security" />
 
 This section explains how to generate random numbers using the subscription method.
diff --git a/src/content/vrf/v2-5/security.mdx b/src/content/vrf/v2-5/security.mdx
index 76d58e143af..0d90cd38b34 100644
--- a/src/content/vrf/v2-5/security.mdx
+++ b/src/content/vrf/v2-5/security.mdx
@@ -4,6 +4,10 @@ date: Last Modified
 title: "VRF Security Considerations"
 ---
 
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
+
+<VrfDeprecation version="v2-5" />
+
 Gaining access to high quality randomness onchain requires a solution like Chainlink's VRF, but it also requires you to understand some of the ways that miners or validators can potentially manipulate randomness generation. Here are some of the top security considerations you should review in your project.
 
 ## Use `requestId` to match randomness requests with their fulfillment in order
diff --git a/src/content/vrf/v2-5/subscription/create-manage.mdx b/src/content/vrf/v2-5/subscription/create-manage.mdx
index 50c163cc43c..f9502f055d6 100644
--- a/src/content/vrf/v2-5/subscription/create-manage.mdx
+++ b/src/content/vrf/v2-5/subscription/create-manage.mdx
@@ -5,9 +5,12 @@ title: "Create and manage VRF V2.5 subscriptions"
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { CodeSample } from "@components"
 import { Tabs, TabsContent } from "@components/Tabs"
 
+<VrfDeprecation version="v2-5" />
+
 <Vrf2_5Common callout="security" />
 
 ## Using the VRF Subscription Manager
diff --git a/src/content/vrf/v2-5/subscription/get-a-random-number.mdx b/src/content/vrf/v2-5/subscription/get-a-random-number.mdx
index d082f88bd30..c254de483d5 100644
--- a/src/content/vrf/v2-5/subscription/get-a-random-number.mdx
+++ b/src/content/vrf/v2-5/subscription/get-a-random-number.mdx
@@ -14,8 +14,11 @@ metadata:
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import { Aside, CodeSample } from "@components"
 
+<VrfDeprecation version="v2-5" />
+
 This guide explains how to get random values using a simple contract to request and receive random values from Chainlink VRF v2.5. The guide uses the Subscription Manager to create and manage your subscription. Alternatively, you can also [create and manage subscriptions programmatically](/vrf/v2-5/subscription/create-manage#create-a-subscription-programmatically). To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
 
 <Vrf2_5Common callout="uicallout" />
diff --git a/src/content/vrf/v2-5/subscription/test-locally.mdx b/src/content/vrf/v2-5/subscription/test-locally.mdx
index 0c4e14b6343..5a6fdaeb4ba 100644
--- a/src/content/vrf/v2-5/subscription/test-locally.mdx
+++ b/src/content/vrf/v2-5/subscription/test-locally.mdx
@@ -6,12 +6,15 @@ metadata:
 ---
 
 import VrfCommon from "@features/vrf/v2/common/VrfCommon.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import ContentCommon from "@features/common/ContentCommon.astro"
 import { Aside, ClickToZoom, CodeSample, CopyText, Icon } from "@components"
 import { linkEth } from "@features/data"
 import { LatestPrice } from "@features/feeds"
 import button from "@chainlink/design-system/button.module.css"
 
+<VrfDeprecation version="v2-5" />
+
 This guide explains how to test Chainlink VRF v2.5 on a [Remix IDE](https://remix-ide.readthedocs.io/en/latest/run.html#environment) sandbox blockchain environment. **Note**: You can reuse the same logic on another development environment, such as Hardhat or Foundry. For example, read the Hardhat Starter Kit [RandomNumberConsumer unit tests](https://github.com/smartcontractkit/hardhat-starter-kit/blob/main/test/unit/RandomNumberConsumer.spec.js).
 
 <Aside type="caution" title="Test on public testnets thoroughly">
diff --git a/src/content/vrf/v2-5/supported-networks.mdx b/src/content/vrf/v2-5/supported-networks.mdx
index 033eb91a6ec..bbff9db6016 100644
--- a/src/content/vrf/v2-5/supported-networks.mdx
+++ b/src/content/vrf/v2-5/supported-networks.mdx
@@ -9,11 +9,14 @@ metadata:
 ---
 
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
+import VrfDeprecation from "@features/vrf/VrfDeprecation.astro"
 import ResourcesCallout from "@features/resources/callouts/ResourcesCallout.astro"
 import { Address, Aside, CopyText } from "@components"
 import { TabsContent } from "@components/Tabs"
 import CcipCommon from "@features/ccip/CcipCommon.astro"
 
+<VrfDeprecation version="v2-5" />
+
 Chainlink VRF allows you to integrate provably fair and verifiably random data in your smart contract. For implementation details, read [Introduction to Chainlink VRF](/vrf).
 
 VRF v2.5 coordinators for subscription funding are available on several networks. To use Chainlink VRF on certain networks, you may need to conduct token transfers. You can transfer tokens by using [Chainlink CCIP](/ccip/evm/tutorials/application-developers/transfer-tokens-from-contract), [Transporter](https://www.transporter.io/) or third-party applications such as [XSwap](https://xswap.link/).
diff --git a/src/features/vrf/VrfDeprecation.astro b/src/features/vrf/VrfDeprecation.astro
index 5fd577f1b4e..6ac7c433e65 100644
--- a/src/features/vrf/VrfDeprecation.astro
+++ b/src/features/vrf/VrfDeprecation.astro
@@ -1,9 +1,10 @@
 ---
 import V1Deprecation from "./v1/common/deprecation.mdx"
 import V2Deprecation from "./v2/common/deprecation.mdx"
+import V2_5Deprecation from "./v2-5/v1-v2-shutdown.mdx"
 
 export type Props = {
-  version: "v1" | "v2"
+  version: "v1" | "v2" | "v2-5"
 }
 
 const { version } = Astro.props as Props
@@ -11,3 +12,4 @@ const { version } = Astro.props as Props
 
 {version === "v1" && <V1Deprecation />}
 {version === "v2" && <V2Deprecation />}
+{version === "v2-5" && <V2_5Deprecation />}
diff --git a/src/features/vrf/v2-5/v1-v2-shutdown.mdx b/src/features/vrf/v2-5/v1-v2-shutdown.mdx
new file mode 100644
index 00000000000..6b2e92e8ee1
--- /dev/null
+++ b/src/features/vrf/v2-5/v1-v2-shutdown.mdx
@@ -0,0 +1,9 @@
+import { Aside } from "@components"
+
+<Aside type="danger" title="VRF v1 and v2 shut down in November 2026">
+  VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+  48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+  November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
+  application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
+  about this shutdown or need help with your migration, reach out to your Chainlink representative.
+</Aside>

From e1486955d63d3dedd76694d78e64972a08b8f69f Mon Sep 17 00:00:00 2001
From: Emmanuel Jacquier <emmanuel.jacquier@gmail.com>
Date: Mon, 26 Oct 2026 13:34:18 -0400
Subject: [PATCH 4/6] updated tests

---
 .../__tests__/buildMarkdownArtifact.test.ts   | 31 ++++++++++++++++---
 1 file changed, 26 insertions(+), 5 deletions(-)

diff --git a/src/lib/markdown/__tests__/buildMarkdownArtifact.test.ts b/src/lib/markdown/__tests__/buildMarkdownArtifact.test.ts
index 58169e93845..8421132b121 100644
--- a/src/lib/markdown/__tests__/buildMarkdownArtifact.test.ts
+++ b/src/lib/markdown/__tests__/buildMarkdownArtifact.test.ts
@@ -36,6 +36,11 @@ function expectedLegalNotice(version: string): string {
   return `Continued use of VRF ${version} is at your own risk. Use of the Chainlink Network is subject to the [Chainlink Foundation Terms of Service](https://chain.link/terms), which provides important information and disclosures.`
 }
 
+const shutdownDates: Record<string, string> = {
+  v1: "November 18, 2026",
+  v2: "November 30, 2026",
+}
+
 describe("buildMarkdownArtifact", () => {
   it.each([
     ["v1", "vrf/v1/api-reference"],
@@ -71,13 +76,20 @@ describe("buildMarkdownArtifact", () => {
       .trim()
 
     expect(transformed.transformMode).toBe("normal")
-    expect(markdown.split(`**CAUTION: Chainlink VRF ${version} is deprecated**`).length - 1).toBe(1)
-    expect(markdown.split(`Security fixes for VRF ${version} are not guaranteed.`).length - 1).toBe(1)
+    expect(
+      markdown.split(`**DANGER: Chainlink VRF ${version} shuts down on ${shutdownDates[version]}**`).length - 1
+    ).toBe(1)
+    expect(
+      markdown.split(
+        `VRF ${version} was deprecated on November 29, 2024 and will be permanently shut down on ${shutdownDates[version]}.`
+      ).length - 1
+    ).toBe(1)
     expect(markdown).toContain(`](/vrf/v2-5/migration-from-${version})`)
     expect(markdown).not.toContain("replaces and enhances VRF v1")
     expect(normalized.split(expectedLegalNotice(version)).length - 1).toBe(1)
 
     if (version === "v2") {
+      expect(normalized).toContain("A 48-hour brownout is scheduled for October 28-30, 2026")
       expect(normalized).toContain(
         "The migration guide includes VRF v2.5 code examples for both subscription and direct funding and explains the differences between VRF v2.5 and VRF v2."
       )
@@ -95,9 +107,18 @@ describe("buildMarkdownArtifact", () => {
       .trim()
 
     expect(artifact?.transformMode).toBe("normal")
-    expect(markdown).toContain(`Chainlink VRF ${version} is deprecated`)
-    expect(markdown.match(new RegExp(`Security fixes for VRF ${version} are not guaranteed\\.`, "g"))).toHaveLength(1)
-    expect(markdown).toContain("Complete this guide to migrate your application to Chainlink VRF v2.5.")
+    expect(markdown).toContain(`Chainlink VRF ${version} shuts down on ${shutdownDates[version]}`)
+    expect(
+      markdown.match(
+        new RegExp(
+          `VRF ${version} was deprecated on November 29, 2024 and will be permanently shut down on ${shutdownDates[version]}\\.`,
+          "g"
+        )
+      )
+    ).toHaveLength(1)
+    expect(normalized).toContain(
+      `Complete this guide to migrate your application to Chainlink VRF v2.5 before ${shutdownDates[version]} to avoid service disruption.`
+    )
     expect(normalized.split(expectedLegalNotice(version)).length - 1).toBe(1)
   })
 

From 19a812b4c75c82e9192065c6c80292f7ff433c34 Mon Sep 17 00:00:00 2001
From: Emmanuel Jacquier <emmanuel.jacquier@gmail.com>
Date: Mon, 26 Oct 2026 14:11:18 -0400
Subject: [PATCH 5/6] updated llm.txt

---
 src/content/data-streams/llms-full.txt | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/content/data-streams/llms-full.txt b/src/content/data-streams/llms-full.txt
index b9896dbafe3..1f6f50aa3c6 100644
--- a/src/content/data-streams/llms-full.txt
+++ b/src/content/data-streams/llms-full.txt
@@ -5848,6 +5848,8 @@ The Settlement Verifier is a community tool on [data.chain.link](https://data.ch
 
 It was designed and shipped for prediction markets, which can link to it so their users can independently check the price a market settled on.
 
+![The Settlement Verifier modal showing a BTC / USDT mid price, bid and ask prices, and the Valid From and Observed At timestamps](/images/data-streams/settlement-verifier/settlement-verifier.png)
+
 ## Who it's for
 
 - **Traders and community members** who want to confirm the price used to settle a market without reading raw report data or writing code.
@@ -5859,10 +5861,10 @@ It was designed and shipped for prediction markets, which can link to it so thei
 
 The Settlement Verifier answers a different question for a different audience: *"What price did Chainlink report at this boundary?"* It gives non-technical users a way to look up and read the report that settled a market. Builders who need cryptographic guarantees in their own contracts should still verify reports onchain.
 
-<Aside type="note" title="Informational tool">
-  The Settlement Verifier displays the data from a report. It does not perform signature verification in your browser,
-  and it does not decide how any market resolves. Each market defines its own resolution rules.
-</Aside>
+> **NOTE: Informational tool**
+>
+> The Settlement Verifier displays the data from a report. It does not perform signature verification in your browser,
+> and it does not decide how any market resolves. Each market defines its own resolution rules.
 
 ## Supported streams
 

From 0bccf0cc776c0bbcb5b644cbbc5155185c8d0ae9 Mon Sep 17 00:00:00 2001
From: Priyank Gupta <priyank.gupta@smartcontract.com>
Date: Tue, 27 Oct 2026 21:13:19 +0530
Subject: [PATCH 6/6] docs(vrf): split v1/v2 shutdown banner into paragraphs

---
 src/content/vrf/llms-full.txt            | 117 +++++++++++++++--------
 src/features/vrf/v2-5/v1-v2-shutdown.mdx |  14 ++-
 2 files changed, 87 insertions(+), 44 deletions(-)

diff --git a/src/content/vrf/llms-full.txt b/src/content/vrf/llms-full.txt
index 05c082b8d1f..b1f3dbfd5ae 100644
--- a/src/content/vrf/llms-full.txt
+++ b/src/content/vrf/llms-full.txt
@@ -5,9 +5,12 @@ Source: https://docs.chain.link/vrf
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 > **TIP: Security Considerations**
 >
@@ -70,9 +73,12 @@ Source: https://docs.chain.link/vrf/v2-5/getting-started
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 > **NOTE: Requirements**
 >
@@ -1190,9 +1196,12 @@ Source: https://docs.chain.link/vrf/v2-5/supported-networks
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 Chainlink VRF allows you to integrate provably fair and verifiably random data in your smart contract. For implementation details, read [Introduction to Chainlink VRF](/vrf).
 
@@ -1908,9 +1917,12 @@ Source: https://docs.chain.link/vrf/v2-5/security
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 Gaining access to high quality randomness onchain requires a solution like Chainlink's VRF, but it also requires you to understand some of the ways that miners or validators can potentially manipulate randomness generation. Here are some of the top security considerations you should review in your project.
 
@@ -1973,9 +1985,12 @@ Source: https://docs.chain.link/vrf/v2-5/best-practices
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 > **TIP: Security Considerations**
 >
@@ -2203,9 +2218,12 @@ Source: https://docs.chain.link/vrf/v2-5/billing
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 This guide explains how to estimate VRF 2.5 costs for both the subscription and direct funding methods.
 
@@ -2523,9 +2541,12 @@ Source: https://docs.chain.link/vrf/v2-5/overview/subscription
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 > **TIP: Security Considerations**
 >
@@ -2695,9 +2716,12 @@ Source: https://docs.chain.link/vrf/v2-5/overview/direct-funding
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 This guide explains how to generate random numbers using the *direct funding* method. This method doesn't require a subscription and is optimal for one-off requests for randomness. This method also works best for applications where your end-users must pay the fees for VRF because the cost of the request is determined at request time.
 
@@ -2777,9 +2801,12 @@ Source: https://docs.chain.link/vrf/v2-5/arbitrum-cost-estimation
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 The total transaction costs for using Arbitrum involve both L2 gas costs and L1 costs. Arbitrum transactions are [posted in batches to L1 Ethereum](https://developer.arbitrum.io/inside-arbitrum-nitro/#how-the-sequencer-publishes-the-sequence), which incurs an L1 cost. For an individual transaction, the total cost includes part of the L1 cost incurred to post the batch that included the transaction.
 
@@ -2934,9 +2961,12 @@ Source: https://docs.chain.link/vrf/v2-5/subscription/create-manage
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 > **TIP: Security Considerations**
 >
@@ -3030,9 +3060,12 @@ Source: https://docs.chain.link/vrf/v2-5/subscription/get-a-random-number
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 This guide explains how to get random values using a simple contract to request and receive random values from Chainlink VRF v2.5. The guide uses the Subscription Manager to create and manage your subscription. Alternatively, you can also [create and manage subscriptions programmatically](/vrf/v2-5/subscription/create-manage#create-a-subscription-programmatically). To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
 
@@ -3309,9 +3342,12 @@ Source: https://docs.chain.link/vrf/v2-5/subscription/test-locally
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 This guide explains how to test Chainlink VRF v2.5 on a [Remix IDE](https://remix-ide.readthedocs.io/en/latest/run.html#environment) sandbox blockchain environment. **Note**: You can reuse the same logic on another development environment, such as Hardhat or Foundry. For example, read the Hardhat Starter Kit [RandomNumberConsumer unit tests](https://github.com/smartcontractkit/hardhat-starter-kit/blob/main/test/unit/RandomNumberConsumer.spec.js).
 
@@ -3579,9 +3615,12 @@ Source: https://docs.chain.link/vrf/v2-5/direct-funding/get-a-random-number
 >
 > VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
 > 48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-> application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-> about this shutdown or need help with your migration, reach out to your Chainlink representative.
+> November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+>
+> [Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+>
+> If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+> representative.
 
 This guide explains how to get random values using a simple contract to request and receive random values from Chainlink VRF v2.5 without managing a subscription. To explore more applications of VRF, refer to our [blog](https://blog.chain.link/).
 
diff --git a/src/features/vrf/v2-5/v1-v2-shutdown.mdx b/src/features/vrf/v2-5/v1-v2-shutdown.mdx
index 6b2e92e8ee1..7f5a6314167 100644
--- a/src/features/vrf/v2-5/v1-v2-shutdown.mdx
+++ b/src/features/vrf/v2-5/v1-v2-shutdown.mdx
@@ -1,9 +1,13 @@
 import { Aside } from "@components"
 
 <Aside type="danger" title="VRF v1 and v2 shut down in November 2026">
-  VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
-  48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
-  November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests. [Migrate your
-  application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption. If you have questions
-  about this shutdown or need help with your migration, reach out to your Chainlink representative.
+VRF v1 and v2 were deprecated on November 29, 2024 and will be permanently shut down in November 2026. VRF v2 has a
+48-hour brownout scheduled for October 28-30, 2026. VRF v1 shuts down on November 18, 2026 and VRF v2 shuts down on
+November 30, 2026. After these dates, VRF v1 and v2 will no longer fulfill randomness requests.
+
+[Migrate your application to Chainlink VRF v2.5](/vrf/v2-5/migration-from-v2) to avoid service disruption.
+
+If you have questions about this shutdown or need help with your migration, reach out to your Chainlink
+representative.
+
 </Aside>