update deprecation/migration notices (#1125)

Author: eric-stacks

content/docs/en/apis/ordinals-api/index.mdx

@@ -11,7 +11,7 @@ The Ordinals API provides comprehensive inscription data for Bitcoin ordinals th
 
 :::callout
 ### Deprecation Notice
-The Ordinals API will be deprecated on March 1st, 2026. Refer to the [migration guide](/apis/ordinals-api/migration) to migrate your application to using Xverse's Ordinals API instead.
+The Ordinals API will be deprecated on March 9th, 2026. Refer to the [migration guide](/apis/ordinals-api/migration) to migrate your application to using Xverse's Ordinals API instead.
 :::
 
 ## Key features

content/docs/en/apis/ordinals-api/migration.mdx

@@ -6,14 +6,9 @@ llm: true
 
 As part of the deprecation of Hiro’s L1 APIs for Ordinals, Runes, BRC-20, Ordhooks, and Runehooks, we’re recommending developers move to using the L1 APIs from Xverse, who have built a robust set of tooling for Bitcoin metaprotocols. We’ve put together this guide for developers on how to migrate your applications to using their APIs.
 
-:::callout
-### Using Xverse's L1 APIs
-NOTE: The Xverse L1 APIs are in private beta, but we’ve worked with them to create an expedited approval path for those coming from Hiro APIs, so just [fill out this form](https://form.typeform.com/to/HkwDUt9P?typeform-source=docs.xverse.app) and they will get back to you quickly.
-:::
-
 ## Timeline
-- Announcement date: Feburary 7th, 2026
-- Deprecation effective: March 1st, 2026
+- Announcement date: Feburary 6th, 2026
+- Deprecation effective: March 9th, 2026
 
 ## What you'll learn
 

content/docs/en/apis/runes-api/index.mdx

@@ -11,7 +11,7 @@ The Runes API provides comprehensive data for Bitcoin Runes through a high-perfo
 
 :::callout
 ### Deprecation Notice
-The Runes API will be deprecated on March 1st, 2026. Refer to the [migration guide](/apis/runes-api/migration) to migrate your application to using Xverse's Runes API instead.
+The Runes API will be deprecated on March 9th, 2026. Refer to the [migration guide](/apis/runes-api/migration) to migrate your application to using Xverse's Runes API instead.
 :::
 
 ## Key features

content/docs/en/apis/runes-api/migration.mdx

@@ -6,14 +6,9 @@ llm: true
 
 As part of the deprecation of Hiro’s L1 APIs for Ordinals, Runes, BRC-20, Ordhooks, and Runehooks, we’re recommending developers move to using the L1 APIs from Xverse, who have built a robust set of tooling for Bitcoin metaprotocols. We’ve put together this guide for developers on how to migrate your applications to using their APIs.
 
-:::callout
-### Using Xverse's L1 APIs
-NOTE: The Xverse L1 APIs are in private beta, but we’ve worked with them to create an expedited approval path for those coming from Hiro APIs, so just [fill out this form](https://form.typeform.com/to/HkwDUt9P?typeform-source=docs.xverse.app) and they will get back to you quickly.
-:::
-
 ## Timeline
-- Announcement date: Feburary 7th, 2026
-- Deprecation effective: March 1st, 2026
+- Announcement date: Feburary 6th, 2026
+- Deprecation effective: March 9th, 2026
 
 ## What you'll learn
 

content/docs/en/tools/bitcoin-indexer/index.mdx

@@ -11,7 +11,7 @@ The Bitcoin Indexer connects to your Bitcoin node, processes blocks in real-time
 
 :::callout
 ### Deprecation Notice
-Ongoing maintainence and updates to the Bitcoin Indexer will stop on March 1st, 2026. The [Bitcoin Indexer repo](https://github.com/hirosystems/bitcoin-indexer) will continue to be open-sourced.
+Ongoing maintainence and updates to the Bitcoin Indexer will stop on March 9th, 2026. The [Bitcoin Indexer repo](https://github.com/hirosystems/bitcoin-indexer) will continue to be open-sourced.
 :::
 
 ## Key features

content/docs/en/tools/chainhooks/(overview)/migration.mdx

@@ -4,8 +4,8 @@ description: Guide for migrating legacy chainhooks to v2
 ---
 
 :::callout
-### Managing v1 chainhooks
-Legacy v1 chainhooks remain read-only in the Platform UI, but you manage them through the [Platform API](/apis/platform-api/reference/chainhooks/list).
+### Deprecation of Chainhooks v1
+Legacy v1 chainhooks will be deprecated on March 9th, 2026.
 :::
 
 ## What you'll learn
@@ -228,12 +228,10 @@ For more details, check out the [Filters](/tools/chainhooks/reference/filters) r
 
 Chainhooks v2 does not have the ability to specify a **start block** in a hook’s configuration for past block scans.
 
-However, you can use the [Replay Block API endpoint](https://docs.hiro.so/en/tools/chainhooks/evaluate) to request any block replay you need at any time. Once requested, you will receive that block’s information through the same webhook payload endpoint you use for real-time updates within a couple seconds.
+However, you can use the [Replay Block API endpoint](/tools/chainhooks/evaluate) to request any block replay you need at any time. Once requested, you will receive that block’s information through the same webhook payload endpoint you use for real-time updates within a couple seconds.
 
 This method ensures you have complete control over which blocks you need to replay whenever you need to.
 
-See [Replay a block](/tools/chainhooks/(chainhook-sdk)/evaluate) for more information.
-
 ## Next steps
 
 :::next-steps

content/docs/en/tools/chainhooks/index.mdx

@@ -3,15 +3,8 @@ title: Chainhooks
 sidebarTitle: Overview
 description: Chainhooks is a webhook service for the Stacks blockchain that lets you register event streams and define precise filters to capture on-chain data as it happens.
 llm: false
-isBeta: true
 ---
 
-:::callout
-type: warn
-### Chainhooks 2.0 (Beta)
-Chainhooks is currently in beta. If you encounter issues or have feedback, please reach out to [beta@hiro.so](mailto:beta@hiro.so).
-:::
-
 ## Overview
 
 Chainhooks makes it easy to subscribe to blockchain activity on Stacks by registering event streams, filtering for exactly the data you care about, and sending it straight to your app in real time.