Merge branch 'main' of github.com:hyperlane-xyz/hyperlane-monorepo into xeno/usdc-fpwr-bsc+katana-extension

Author: xeno097

.changeset/cuddly-meals-retire.md

@@ -0,0 +1,5 @@
+---
+'@hyperlane-xyz/rebalancer': patch
+---
+
+Mixed-decimal inventory follow-ups were fixed by failing fast on missing bridged supply, tightening bridge plan coverage, and formatting monitored inventory balances with token-aware decimals.

.changeset/late-wolves-repeat.md

@@ -398,6 +398,117 @@ hyperlane warp check \
 
 **NOTE**: Warp check may show provider errors for newly added chains - this is expected.
 
+### Step 8b: Test transferRemote on Fork
+
+After verifying configuration with `warp check`, test that an actual token transfer works on the forked chains. This catches issues that config checks miss: broken `transferRemote` calldata, token accounting bugs (lock/mint/burn/unlock), and message dispatch failures.
+
+#### 8b.1 Pick an Origin → Destination Pair
+
+Choose one origin → destination pair from the warp route. Prefer a pair where both chains have transactions (i.e., both were modified), so you're testing the freshly configured path.
+
+#### 8b.2 Bypass ISM on Destination (Required for Self-Relay)
+
+Forked mainnet chains have real multisig ISMs that require validator signatures. Since there are no validators on anvil forks, you must set a permissive ISM on the destination so self-relay can deliver the message.
+
+```bash
+# 1. Get the mailbox address for the destination chain from the forked registry
+DEST_MAILBOX=$(cast call <warp-router-address> "mailbox()(address)" --rpc-url http://localhost:<DEST-PORT>)
+
+# 2. Get the mailbox owner
+MAILBOX_OWNER=$(cast call $DEST_MAILBOX "owner()(address)" --rpc-url http://localhost:<DEST-PORT>)
+
+# 3. Get the current default ISM (to restore later if needed)
+OLD_ISM=$(cast call $DEST_MAILBOX "defaultIsm()(address)" --rpc-url http://localhost:<DEST-PORT>)
+
+# 4. Deploy Hyperlane's TestIsm.
+# TestIsm returns Types.NULL from moduleType() and true from verify(bytes,bytes),
+# so `hyperlane warp send --relay` uses null metadata instead of trying to derive
+# multisig/routing metadata on the fork.
+TEST_DEPLOYER_KEY="0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80"
+# Ensure Foundry dependencies are materialized in fresh worktrees/checkouts.
+pnpm -C solidity deps:soldeer
+TEST_ISM_ADDRESS=$(forge create \
+  --root solidity \
+  --broadcast \
+  --rpc-url http://localhost:<DEST-PORT> \
+  --private-key $TEST_DEPLOYER_KEY \
+  contracts/test/TestIsm.sol:TestIsm \
+  | awk '/Deployed to:/ {print $3}')
+
+# Confirm the fork bypass ISM has the expected Hyperlane behavior:
+# moduleType() == 6 (Types.NULL) and verify(...) == true.
+cast call $TEST_ISM_ADDRESS "moduleType()(uint8)" --rpc-url http://localhost:<DEST-PORT>
+cast call $TEST_ISM_ADDRESS "verify(bytes,bytes)(bool)" 0x 0x --rpc-url http://localhost:<DEST-PORT>
+
+# 5. Impersonate mailbox owner and set the permissive ISM
+cast rpc anvil_impersonateAccount $MAILBOX_OWNER --rpc-url http://localhost:<DEST-PORT>
+BALANCE="0x56BC75E2D63100000"
+cast rpc anvil_setBalance $MAILBOX_OWNER $BALANCE --rpc-url http://localhost:<DEST-PORT>
+cast send $DEST_MAILBOX "setDefaultIsm(address)" $TEST_ISM_ADDRESS --from $MAILBOX_OWNER --rpc-url http://localhost:<DEST-PORT> --unlocked
+cast rpc anvil_stopImpersonatingAccount $MAILBOX_OWNER --rpc-url http://localhost:<DEST-PORT>
+```
+
+**NOTE**: If the warp router has a custom ISM set (not using the mailbox default), you'll need to impersonate the router owner and call `setInterchainSecurityModule(address)` on the router instead.
+
+#### 8b.3 Fund the Test Sender
+
+```bash
+# Generate a test private key (or use a well-known anvil key)
+TEST_KEY="0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80"
+TEST_SENDER="0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266"  # Anvil account 0
+
+# Fund with native gas on origin
+cast rpc anvil_setBalance $TEST_SENDER "0x56BC75E2D63100000" --rpc-url http://localhost:<ORIGIN-PORT>
+
+# For collateral/ERC20 routes: mint or transfer tokens to the test sender
+# Option A: If the token has a mint function (e.g., test tokens)
+# cast send <token-address> "mint(address,uint256)" $TEST_SENDER 1000000000000000000 ...
+
+# Option B: Impersonate a whale holder and transfer
+# Find a top holder from the fork state, impersonate, and transfer
+# cast rpc anvil_impersonateAccount <whale> --rpc-url http://localhost:<ORIGIN-PORT>
+# cast send <token-address> "transfer(address,uint256)" $TEST_SENDER <amount> --from <whale> --rpc-url http://localhost:<ORIGIN-PORT> --unlocked
+
+# Option C: For native token routes, setBalance is sufficient (already done above)
+
+# Also fund on destination for self-relay gas
+cast rpc anvil_setBalance $TEST_SENDER "0x56BC75E2D63100000" --rpc-url http://localhost:<DEST-PORT>
+```
+
+#### 8b.4 Run the Transfer
+
+```bash
+HYP_KEY=$TEST_KEY \
+hyperlane warp send \
+  --registry <YOUR-ACTUAL-forked-registry-url-from-step-4> \
+  --warp-route-id <warp-route-id> \
+  --origin <origin-chain> \
+  --destination <destination-chain> \
+  --amount 1 \
+  --relay \
+  --skip-validation \
+  --yes
+```
+
+**Key flags:**
+
+- `--relay` — Self-relay the message (no real relayer on forks)
+- `--skip-validation` — Skip balance/collateral checks that may fail on forks
+- `--amount 1` — Use smallest practical amount (1 wei or 1 unit)
+
+#### 8b.5 Verify Result
+
+- **Success**: The CLI should log `Transfer was self-relayed!` and show the message ID
+- **Failure**: Check the error output. Common issues:
+  - `Ownable: caller is not the owner` on ISM bypass → wrong mailbox owner or router has custom ISM
+  - `insufficient funds` → test sender not funded with tokens (for collateral routes)
+  - `message already delivered` → ISM bypass not working, retry with router-level ISM override
+  - Timeout waiting for delivery → self-relay failed, check ISM was properly set
+
+**Capture output** to `/tmp/warp-transfer-test.log` for the final report.
+
+**NOTE**: This step is optional but strongly recommended. If it fails due to ISM complexity (e.g., routing ISMs, aggregation ISMs), document the failure and move on — the config check in Step 8 still validates the deployment.
+
 ### Step 9: Interpret Results
 
 Analyze the warp check output carefully:
@@ -516,6 +627,14 @@ Create a comprehensive markdown report with the following sections:
 
 [List of chains not modified and their expected violations]
 
+## Transfer Test Results
+
+- **Origin → Destination**: <chain-a> → <chain-b>
+- **Amount**: <amount>
+- **Result**: ✅ Success / ❌ Failed (reason)
+- **Message ID**: <id> (if successful)
+- **ISM Bypass**: Yes (TestIsm deployed at <address> set on destination mailbox)
+
 ## Decoded Transactions (Heimdall Output)
 
 ```json