update

Author: aelmanaa

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

@@ -424,3 +424,37 @@ 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
+
+##### Address Lookup Table Requirements
+
+The `pool_lookuptable` must contain exactly these accounts in the specified order for proper CCIP token pool operations:
+
+| Index | Account                     | Derivation                                                   | Description                                                                                                                             |
+| ----- | --------------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
+| 0     | **Lookup Table Address**    | N/A                                                          | The Address Lookup Table itself                                                                                                         |
+| 1     | **Token Admin Registry**    | `["token_admin_registry", mint]` under Router program        | Registry PDA for this token                                                                                                             |
+| 2     | **Pool Program**            | N/A                                                          | The token pool program ID (e.g., BurnMint or LockRelease Token Pool program)                                                            |
+| 3     | **Pool Config**             | `["ccip_tokenpool_config", mint]` under pool program         | Token-specific pool configuration and settings                                                                                          |
+| 4     | **Pool Token Account**      | ATA of (pool_signer, mint, token_program)                    | Associated Token Account holding pool's tokens                                                                                          |
+| 5     | **Pool Signer**             | `["ccip_tokenpool_signer", mint]` under pool program         | PDA with authority for token operations                                                                                                 |
+| 6     | **Token Program**           | N/A                                                          | SPL Token program (`TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA`) or Token-2022 program (`TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb`) |
+| 7     | **Token Mint**              | N/A                                                          | The SPL token mint address                                                                                                              |
+| 8     | **Fee Token Config**        | `["fee_billing_token_config", mint]` under Fee Quoter        | Fee token billing configuration PDA                                                                                                     |
+| 9     | **CCIP Router Pool Signer** | `["external_token_pools_signer", pool_program]` under Router | Router's signer PDA for the pool                                                                                                        |
+
+**Notes:**
+
+- The ALT contains exactly 10 accounts as shown above
+- Custom token pools may require additional accounts beyond these core 10
+- All PDA derivations must use the correct program IDs
+- Pool Token Account must be the proper Associated Token Account for the Pool Signer
+- Writable permissions are specified via the `writable_indexes` parameter
+
+**Creating the ALT:**
+
+1. Create a new Address Lookup Table
+1. Add accounts in the exact order specified above
+1. Ensure all PDA derivations are correct for your specific token and pool program
+1. Call `set_pool` with the ALT address and appropriate `writable_indexes`
+
+For PDA derivation examples and account validation details, see the [Token Pool documentation](/ccip/concepts/cross-chain-token/svm/token-pools).

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

@@ -86,7 +86,7 @@ The CCIP Router program is central to cross-chain token management. It has two f
 1. **Token Administration**
 
    - **TokenAdminRegistry (one [PDA](https://solana.com/docs/core/pda) per mint):** Stores the designated CCIP [token administrator](/ccip/concepts/cross-chain-token/overview#token-administrator) public key for a specific token mint (distinct from the SPL token's own mint authority) and references the token's pool [address lookup table](https://docs.solana.com/developing/lookup-tables) (ALT). The PDA is derived using seeds `[seed::TOKEN_ADMIN_REGISTRY, mint.key().as_ref()]`. This registry is created during token registration (see [Token section](#token)) and governs all subsequent CCIP operations for that token.
-   - **Token Pool Address Lookup Table:** A Solana [address lookup table](https://docs.solana.com/developing/lookup-tables) that precisely defines the set of account addresses (including pool configuration [PDAs](https://solana.com/docs/core/pda), pool signer PDAs, and other required accounts) that are authorized for cross-chain operations with this token. The ALT contains a minimum of 9 required accounts in a specific order.
+   - **Token Pool Address Lookup Table:** A Solana [address lookup table](https://docs.solana.com/developing/lookup-tables) that precisely defines the set of account addresses (including pool configuration [PDAs](https://solana.com/docs/core/pda), pool signer PDAs, and other required accounts) that are authorized for cross-chain operations with this token. For the complete list of required accounts and their exact order, see the [`set_pool` ALT requirements](/ccip/api-reference/svm/v1.6.0/router#address-lookup-table-requirements).
    - **Administrator Methods:** The token administrator can register or update cross-chain support for their mint through a sequence of instructions:
 
      1. [`owner_propose_administrator`](/ccip/api-reference/svm/v1.6.0/router#owner_propose_administrator): Initiated by the mint authority to designate a token administrator.

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

@@ -190,8 +190,8 @@ See [Mint Authority Management](/ccip/concepts/cross-chain-token/svm/token-pools
 ### Step 5: Create Address Lookup Table (ALT)
 
 - Create an ALT containing all required accounts for your pool operations
-- Must include minimum 9 required accounts in specific order
-- See [Pool Configuration requirements](/ccip/concepts/cross-chain-token/svm/registration-administration#token-pool-configuration-pool-side) for account list
+- Must include required accounts in specific order as detailed in the [`set_pool` API reference](/ccip/api-reference/svm/v1.6.0/router#address-lookup-table-requirements)
+- See the complete [ALT requirements table](/ccip/api-reference/svm/v1.6.0/router#address-lookup-table-requirements) for exact account order and derivations
 
 ### Step 6: Link Pool to Token Registry
 

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

@@ -153,7 +153,7 @@ On SVM-based blockchains (e.g., Solana), the [`set_pool`](/ccip/api-reference/sv
    - Resets the old permission bits, then enables the specified "writable indexes."
    - This ensures the new token pool has the correct set of PDAs with the correct writable permissions.
 1. **Validate or Delist:**
-   - If the new `pool_lookuptable` is not the zero address, the Router checks that this lookup table has at least the minimal set of addresses required for cross-chain transfers. This includes the token mint, pool program, token program, pool configuration PDA, and any other mandatory accounts specified by the pool implementation. If valid, the token becomes enabled for cross-chain transfers.
+   - If the new `pool_lookuptable` is not the zero address, the Router checks that this lookup table has at least the minimal set of addresses required for cross-chain transfers. For the complete list of required accounts and their exact order, see the [`set_pool` ALT requirements](/ccip/api-reference/svm/v1.6.0/router#address-lookup-table-requirements). If valid, the token becomes enabled for cross-chain transfers.
    - If the `pool_lookuptable` is the zero address, the token is effectively delisted from CCIP, meaning no new cross-chain transfers can occur.
 
 The sequence diagram below explains how the [`set_pool`](/ccip/api-reference/svm/v1.6.0/router#set_pool) instruction updates the `TokenAdminRegistry` PDA and either enables or delists the token for cross-chain transfers.

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

@@ -54,7 +54,7 @@ Your token's requirements depend on which token pool type you'll deploy, determi
 **Token Requirements:**
 
 - Must support `mint_to` and `burn` instructions
-- **Mint authority** must be transferable (directly to pool signer PDA or via SPL Token Multisig). See [BurnMint Pool mint authority configuration](/ccip/concepts/cross-chain-token/svm/token-pools#option-2-multisig-configuration-recommended-for-production) for detailed multisig requirements
+- **Mint authority** must be transferable (directly to pool signer PDA or via SPL Token Multisig). See [BurnMint Pool mint authority configuration](/ccip/concepts/cross-chain-token/svm/token-pools#mint-authority-management) for detailed multisig requirements
 
 #### LockRelease Pool