address comment

Author: akaladarshi

docs/e2e_api_testing_guide.md

@@ -127,13 +127,6 @@ with wallet cap validation.
 2. Wait 65s → `3rd attempt WALLET CAPPED` (429, >1h retry time)
 3. Test equivalent address (`t410`) → 429 (same wallet)
 
-**CalibnetUSDFC ID wallet (fresh wallet, 0 transactions):**
-
-1. Wait 65s → `1st SUCCESS` (200)
-2. Wait 65s → `2nd SUCCESS` (200, reaches cap)
-3. Wait 65s → `3rd attempt WALLET CAPPED` (429, >1h retry time)
-4. Test equivalent address (`t0`) → 429 (same wallet)
-
 ### 5. Common Helper Functions
 
 **`makeClaimRequest(faucetInfo, address)`**: A centralized API call that handles

e2e/test_claim_token_api_config.js

@@ -297,8 +297,11 @@ export const TEST_SCENARIOS = {
       walletCapErrorResponse: true,
     },
 
+    // TODO(forest-explorer): https://github.com/ChainSafe/forest-explorer/issues/335
+    //                       Token sent to the t0 and it's eth mapping address 0x
+    //                       are not accessible. Hence commenting out the following
+    //                       test cases.
     // === CalibnetUSDFC ID Wallet (fresh wallet, 0 transactions) ===
-    // Commented out because we are not sure how to get the token back from the ID address
     // {
     //   name: 'CalibnetUSDFC (ID) - 1st SUCCESS (fresh wallet)',
     //   faucet_info: FaucetTypes.CalibnetUSDFC,