remove non available functionalities

Author: aelmanaa

src/content/ccip/api-reference/svm/v1.6.0/base-token-pool.mdx

@@ -53,7 +53,7 @@ pub struct BaseConfig {
     // Ownership and administration
     pub owner: Pubkey,              // Current pool owner
     pub proposed_owner: Pubkey,     // Proposed new owner (for ownership transfer)
-    pub rate_limit_admin: Pubkey,   // Rate limit administrator
+    pub rate_limit_admin: Pubkey,   // Rate limit administrator (currently unused - rate limits managed by pool owner)
 
     // CCIP integration
     pub router_onramp_authority: Pubkey, // Router's onramp authority PDA

src/content/ccip/api-reference/svm/v1.6.0/burn-mint-token-pool.mdx

@@ -440,11 +440,11 @@ fn set_chain_rate_limit(
 | -------------- | ---------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------ |
 | `state`        | `Account<State>`       | No        | Pool state PDA. <br/>**Derivation**: `["ccip_tokenpool_config", mint]` under this program.                               |
 | `chain_config` | `Account<ChainConfig>` | Yes       | Chain config PDA. <br/>**Derivation**: `["ccip_tokenpool_chainconfig", remote_chain_selector, mint]` under this program. |
-| `authority`    | `Signer<'info>`        | Yes       | Must be pool owner or rate limit admin.                                                                                  |
+| `authority`    | `Signer<'info>`        | Yes       | Must be the pool owner.                                                                                                  |
 
 ##### Authorization
 
-- **Caller**: Must be the pool owner OR the rate limit admin
+- **Caller**: Must be the pool owner
 
 #### `delete_chain_config`
 

src/content/ccip/api-reference/svm/v1.6.0/events.mdx

@@ -97,23 +97,6 @@ pub struct PoolSet {
 | `previous_pool_lookup_table` | `Pubkey` | The previous Address Lookup Table (zero if first time)  |
 | `new_pool_lookup_table`      | `Pubkey` | The new Address Lookup Table (zero to delist from CCIP) |
 
-##### `PoolEdited`
-
-Emitted when pool auto-derivation support is modified via `set_pool_supports_auto_derivation`.
-
-```rust
-#[event]
-pub struct PoolEdited {
-    pub token: Pubkey,
-    pub supports_auto_derivation: bool,
-}
-```
-
-| Field                      | Type     | Description                               |
-| -------------------------- | -------- | ----------------------------------------- |
-| `token`                    | `Pubkey` | The SPL token mint address                |
-| `supports_auto_derivation` | `bool`   | Whether the pool supports auto-derivation |
-
 ### BurnMint Token Pool
 
 The BurnMint Token Pool program emits events related to pool configuration, token operations, and mint authority management.

src/content/ccip/api-reference/svm/v1.6.0/lock-release-token-pool.mdx

@@ -402,9 +402,9 @@ pub fn set_chain_rate_limit(
 
 - `state`: Pool State PDA
 - `chain_config`: Chain Config PDA (mutable)
-- `authority`: Pool owner or rate limit admin (signer)
+- `authority`: Pool owner (signer)
 
-**Authorization:** Pool owner OR rate limit admin
+**Authorization:** Pool owner only
 
 ##### `delete_chain_config`
 

src/content/ccip/api-reference/svm/v1.6.0/router.mdx

@@ -424,39 +424,3 @@ fn set_pool(
 
 - **Enable Token**: Set `pool_lookuptable` to a valid Address Lookup Table with required pool accounts
 - **Disable Token**: Set `pool_lookuptable` to zero address (`Pubkey::default()`) to delist from CCIP
-
-#### `set_pool_supports_auto_derivation`
-
-Configures whether a token pool supports automatic account derivation for cross-chain transfers.
-
-```rust
-fn set_pool_supports_auto_derivation(
-    ctx: Context<EditPoolTokenAdminRegistry>,
-    mint: Pubkey,
-    supports_auto_derivation: bool,
-) -> Result<()>;
-```
-
-##### Parameters
-
-| Name                                    | Type                  | Description                                           |
-| --------------------------------------- | --------------------- | ----------------------------------------------------- |
-| <nobr>`mint`</nobr>                     | <nobr>`Pubkey`</nobr> | The SPL token mint to configure.                      |
-| <nobr>`supports_auto_derivation`</nobr> | <nobr>`bool`</nobr>   | Whether the pool supports dynamic account derivation. |
-
-##### Context (Accounts)
-
-| Field                  | Type                                       | Writable? | Description                                                                                                               |
-| ---------------------- | ------------------------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------- |
-| `config`               | <nobr>`Account<Config>`</nobr>             | No        | Router config PDA. <br/>**Derivation**: `["config"]` under the `ccip_router` program.                                     |
-| `token_admin_registry` | <nobr>`Account<TokenAdminRegistry>`</nobr> | Yes       | Existing token admin registry PDA. <br/>**Derivation**: `["token_admin_registry", mint]` under the `ccip_router` program. |
-| `authority`            | <nobr>`Signer<'info>`</nobr>               | Yes       | Must be the current administrator of the token admin registry.                                                            |
-
-##### Authorization
-
-- **Caller**: Must be the current `administrator` listed in the TokenAdminRegistry PDA
-
-##### Auto-Derivation Impact
-
-- **Enabled (`true`)**: The Router validates only static accounts in the Address Lookup Table, allowing the pool to handle additional dynamically-derived accounts
-- **Disabled (`false`)**: The Router validates all accounts against the static Address Lookup Table, expecting a complete and fixed account set

src/content/ccip/concepts/cross-chain-token/svm/architecture.mdx

@@ -95,12 +95,11 @@ The CCIP Router program is central to cross-chain token management. It has two f
 
      For detailed step-by-step procedures, sequence diagrams, and complete registration workflows, see [Registration & Administration](/ccip/concepts/cross-chain-token/svm/registration-administration).
 
-   - **Pool configuration:** The TokenAdminRegistry maps each mint to exactly one token pool configuration through the ALT. This ensures that during cross-chain transfers, only the authorized token pool implementation can interact with the token. The registry also includes a `supports_auto_derivation` flag for enhanced account derivation capabilities.
+   - **Pool configuration:** The TokenAdminRegistry maps each mint to exactly one token pool configuration through the ALT. This ensures that during cross-chain transfers, only the authorized token pool implementation can interact with the token.
    - **Security Architecture:** The one-to-one mapping between tokens and pools provides critical security guarantees:
      - **Single Authorized Pool:** Each token mint can only have one authorized pool configuration, preventing unauthorized token handling
      - **Atomic Pool Updates:** Changing pool configurations requires updating the entire ALT reference, ensuring consistent state
      - **Access Control:** Only the registry administrator can modify pool assignments, maintaining strict governance
-   - **Enhanced Account Derivation:** When `supports_auto_derivation` is enabled, token pools can dynamically derive additional accounts during cross-chain operations. This allows pools to handle complex transfer scenarios with varying account requirements while maintaining security through the registry's controlled environment.
 
 1. **Lock or Burn Flow (when sending tokens cross-chain)**
 

src/content/ccip/concepts/cross-chain-token/svm/registration-administration.mdx

@@ -28,7 +28,6 @@ Understanding who can call which Router instructions is critical for secure toke
 | [`accept_admin_role_token_admin_registry`](/ccip/api-reference/svm/v1.6.0/router#accept_admin_role_token_admin_registry)     |       ❌       |            ❌            |         ❌          |         ✅          |
 | [`transfer_admin_role_token_admin_registry`](/ccip/api-reference/svm/v1.6.0/router#transfer_admin_role_token_admin_registry) |       ❌       |            ❌            |         ✅          |         ❌          |
 | [`set_pool`](/ccip/api-reference/svm/v1.6.0/router#set_pool)                                                                 |       ❌       |            ❌            |         ✅          |         ❌          |
-| [`set_pool_supports_auto_derivation`](/ccip/api-reference/svm/v1.6.0/router#set_pool_supports_auto_derivation)               |       ❌       |            ❌            |         ✅          |         ❌          |
 
 **Notes:**
 
@@ -165,25 +164,6 @@ The sequence diagram below explains how the [`set_pool`](/ccip/api-reference/svm
   style="display: block; margin: 2rem auto; max-height: 60vh; width: auto;"
 />
 
-### Configuring Pool Auto-Derivation
-
-The [`set_pool_supports_auto_derivation`](/ccip/api-reference/svm/v1.6.0/router#set_pool_supports_auto_derivation) instruction allows a token administrator to configure whether their token pool supports automatic account derivation for cross-chain transfers. This setting affects how the CCIP Router validates and handles account lists during token transfer operations.
-
-**Auto-Derivation Capability:** When enabled (`supports_auto_derivation = true`), the token pool can dynamically derive additional accounts and lookup tables required for cross-chain operations by implementing `derive_accounts_lock_or_burn` and `derive_accounts_release_or_mint` functions. This provides flexibility for pools that need message-dependent or dynamically calculated account sets.
-
-**Account Validation Impact:**
-
-- **Auto-derivation enabled**: The Router validates only the static accounts present in the Address Lookup Table, allowing the pool to handle validation of additional dynamically-derived accounts.
-- **Auto-derivation disabled**: The Router validates all accounts against the static Address Lookup Table, expecting a complete and fixed account set.
-
-**Administrative Control:** Only the current token administrator can modify this setting, ensuring that pool configuration changes are properly authorized. The function updates the `supports_auto_derivation` flag in the `TokenAdminRegistry` PDA and emits a `PoolEdited` event for transparency.
-
-<ClickToZoom
-  src="/images/ccip/cct/cct-svm-diagrams/solana_set_pool_supports_auto_derivation.svg"
-  alt="Cross-Chain Token Standard - Configure Pool Auto-Derivation"
-  style="display: block; margin: 2rem auto; max-height: 60vh; width: auto;"
-/>
-
 ## Token Pool Configuration (Pool Side)
 
 Once you have registered your token and set the token pool via the Router, you need to configure the specific pool parameters. These operations are performed directly on the Token Pool programs, not the Router.
@@ -253,7 +233,7 @@ Configure transfer limits and access controls for your token pool:
 
     - **Instruction:** [`set_chain_rate_limit`](/ccip/api-reference/svm/v1.6.0/burn-mint-token-pool#set_chain_rate_limit)
     - **Use Case:** Apply or modify the remote blockchain's inbound/outbound rate-limit configuration. This uses a token bucket algorithm in which you can configure the capacity (maximum tokens) and rate (tokens per second refill rate) for both inbound and outbound transfers.
-    - **Authorization:** Pool Owner OR Rate Limit Admin
+    - **Authorization:** Pool Owner only
     - Read the [API reference](/ccip/api-reference/svm/v1.6.0/burn-mint-token-pool#set_chain_rate_limit) to learn more.
 
 1.  **Optional Allowlist**