udpate announcements page

docs/learn/announcements.md

@@ -6,34 +6,56 @@ title: "Announcements and Developments"
 
 This page tracks recent and upcoming changes to the Bittensor protocol and other major events in the Bittensor ecosystem.
 
+**December, 2025**
+
 ## Upcoming TAO halving
 
 The first TAO halving event is approaching, which will reduce block rewards by 50%—0.5 TAO per block. This change means less liquidity will be injected each block into the subnet pools. For more information, see the [TAO halving documentation](../concepts/halving.md).
 
 You can track the halving schedule and countdown on the [tao.app explorer](https://tao.app/halving), which provides real-time block data and the estimated time remaining until the reward reduction occurs.
 
-## Root claim
+## Proxies
 
 **Status**: Implemented
 
-- **What**: Root claim replaces the automatic selling of root-alpha dividends and allows users to either accumulate their alpha dividends or enable autosell to sell them off immediately.
+- **What**: Proxies allow one wallet to perform Bittensor operations on behalf of another, adding a security layer for valuable wallets.
 - **Key Features**:
-  - Taking no action means your root alpha is automatically swapped to TAO and added to your root stake.
-  - Auto-claims happen automatically and randomly—roughly once every two days per account. Your `Keep`/`Swap` setting will apply.
-  - To keep your alpha, call the `set_root_claim_type(Keep)` extrinsic.
-  - Manually claim accumulated alpha on specific subnets by calling the `claim_root()` extrinsic and providing the list of subnets.
+  - Keep high-value coldkeys in cold storage while using proxies for daily operations.
+  - Constrain proxy permissions using `ProxyType` (e.g., staking-only, transfer-only).
+  - Add time-lock delays with public announcements for high-risk actions.
+
+For detailed information, see: [Proxies Overview](../keys/proxies/index.md).
+
+## MEV Shield
+
+**Status**: Implemented
+
+MEV Shield encrypts transactions to protect them from maximal extractable value (MEV) attacks.
+
+For detailed information, see: [MEV Shield](../sdk/mev-protection.md).
 
 ## Bittensor SDK v10
 
-**Status**: Releases
+**Status**: Released
 
-- **What**: A new major version of the Bittensor SDK is in development and will introduce breaking changes.
-- **Key Features**:
-  - Comprehensive error handling for all extrinsics and related calls.
-  - New standardized extrinsic response class with success status, error objects, receipts, and transaction fees in TAO and alpha.
-  - Amount handling standardized to balance type only for consistent calculations.
+A new major version of the Bittensor SDK has arrived!
 
-For detailed information, see: [Bittensor SDK v10 Migration guide](../sdk/migration-guide).
+See: [Bittensor SDK v10 Migration guide](../sdk/migration-guide).
+
+---
+
+**October, 2025**
+
+## Root claim
+
+**Status**: Implemented
+
+- **What**: Root claim replaces the automatic selling of root-alpha dividends and allows users to either accumulate their alpha dividends or enable autosell to sell them off immediately.
+- **Key Features**:
+  - Taking no action means your root alpha is kept as Alpha tokens (the new default is `Keep`).
+  - Auto-claims happen automatically and randomly—roughly once every two days per account. Your `Keep`/`Swap` setting will apply.
+  - To swap your alpha to TAO, call the `set_root_claim_type(Swap)` extrinsic.
+  - Manually claim accumulated alpha on specific subnets by calling the `claim_root()` extrinsic and providing the list of subnets.
 
 ## Subnet UID trimming
 

docs/sdk/migration-guide.md

@@ -1,18 +1,18 @@
 ---
-title: "Bittensor SDK v10.0 Migration Guide"
+title: "Bittensor SDK v10 Migration Guide"
 ---
 
 import { SdkVersion } from "./_sdk-version.mdx";
 
-# Bittensor SDK v10.0 Migration Guide
+# Bittensor SDK v10 Migration Guide
 
-This page documents breaking changes and new features for the Bittensor Python SDK `v10.0`. This is a major release with significant refactoring, standardization, and new functionality.
+This page documents breaking changes and new features for the Bittensor Python SDK `v10`. This is a major release with significant refactoring, standardization, and new functionality.
 
 See [Bittensor Python SDK Reference Docs](./bt-api-ref)
 
 ## Executive Summary
 
-Bittensor SDK v10.0 is a **major breaking release** with significant improvements to consistency, type safety, and functionality. Key changes include:
+Bittensor SDK v10 is a **major breaking release** with significant improvements to consistency, type safety, and functionality. Key changes include:
 
 **Breaking Changes:**