Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.

- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor

docs/07-ccip/CROSS_NETWORK_FUNDING_BOOTSTRAP_STRATEGY.md

@@ -27,13 +27,13 @@ This is confirmed by live execution:
 | Mainnet | Relay-backed direct | Mainnet relay bridge must hold enough WETH | Direct `138 -> Mainnet` when relay inventory is funded |
 | BSC | Relay-backed direct | BSC relay bridge only covers tiny sends right now | Small direct `138 -> BSC`, or bootstrap mainnet through BSC |
 | Avalanche | Relay-backed direct | Avalanche relay bridge only covers tiny sends right now | Tiny direct sends only, or top up inventory first |
-| Gnosis | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Gnosis` |
-| Cronos | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Cronos` |
-| Celo | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Celo` |
-| Polygon | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Polygon` |
-| Arbitrum | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Arbitrum` |
-| Optimism | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Optimism` |
-| Base | Via mainnet hub | Bootstrap mainnet first | `138 -> Mainnet`, then `Mainnet -> Base` |
+| Gnosis | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Gnosis` after Mainnet bridge/router fix |
+| Cronos | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Cronos` after Mainnet bridge/router fix |
+| Celo | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Celo` after Mainnet bridge/router fix |
+| Polygon | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Polygon` after Mainnet bridge/router fix |
+| Arbitrum | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Arbitrum` after Mainnet bridge/router fix |
+| Optimism | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Optimism` after Mainnet bridge/router fix |
+| Base | Mainnet hub currently blocked | Bootstrap mainnet first and repair Mainnet fan-out | `138 -> Mainnet`, then `Mainnet -> Base` after Mainnet bridge/router fix |
 | WEMIX | Deploy-first | Bridge not deployed and no gas seed | Deploy and seed first |
 
 ## Best strategy now
@@ -45,7 +45,7 @@ This is the best practical topology.
 Why:
 
 - `138 -> Mainnet` is a real relay-backed route when the relay bridge has WETH
-- mainnet already has enabled fan-out mappings for Gnosis, Cronos, Celo, Polygon, Arbitrum, Optimism, and Base
+- mainnet still has enabled fan-out mappings for Gnosis, Cronos, Celo, Polygon, Arbitrum, Optimism, and Base
 - the successful recovery proved that topping up mainnet relay inventory and replaying is operationally viable
 
 ### 2. Use BSC as the bootstrap and recovery helper
@@ -73,12 +73,25 @@ Avalanche is structurally similar to BSC but currently weaker because:
 - deployer has native gas
 - relay inventory is present but still below the `0.01` WETH working threshold
 
-### 4. Treat the native-mapped chains as mainnet destinations
+### 4. Treat the native-mapped chains as blocked mainnet destinations until the source path is repaired
 
 Gnosis, Cronos, Celo, Polygon, Arbitrum, Optimism, and Base are still valuable, but their practical role is:
 
 - `Mainnet -> target` destinations after mainnet bootstrap
 - not proven direct Chain 138 first hops
+- currently blocked even as Mainnet fan-out targets on the active WETH9 source bridge path
+
+Live corrections from 2026-04-04:
+
+- a direct `138 -> Arbitrum` WETH send emitted a valid `MessageSent` event on the Chain 138 router
+- the active relay service still skipped that message because it was running the Mainnet destination profile
+- destination processing on Arbitrum remained untouched (`processedTransfers == false`)
+- a follow-on `Mainnet -> Arbitrum` send from `MAINNET_CCIP_WETH9_BRIDGE=0xc9901ce2Ddb6490FAA183645147a87496d8b20B6` also failed on-chain in tx `0x97df657f0e31341ca852666766e553650531bbcc86621246d041985d7261bb07`
+- debug tracing shows the revert occurs inside the Mainnet CCIP router `0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D` before any bridge event is emitted, so this is not a wallet-balance issue
+- the failed Mainnet send left deployer balances intact apart from gas; WETH and LINK were not stranded
+- read-only quote preflights now also revert for the current Mainnet WETH9 bridge across the tracked public-chain selectors: `BSC`, `Avalanche`, `Gnosis`, `Cronos`, `Celo`, `Polygon`, `Arbitrum`, `Optimism`, and `Base`
+
+Treat that as confirmation of the current rule: these chains are meaningful destinations after Mainnet bootstrap, not safe first hops from Chain 138 unless a dedicated relay profile and router path are added first. More importantly, the current Mainnet WETH9 public fan-out path should be treated as blocked at the source bridge/router layer until it is repaired or replaced.
 
 ## What to keep funded
 
@@ -121,7 +134,7 @@ cd /home/intlc/projects/proxmox/smom-dbis-138
 1. Audit the current route and inventory state.
 2. If mainnet relay inventory is sufficient, use direct `138 -> Mainnet`.
 3. If mainnet relay inventory is insufficient, use `138 -> BSC` plus the proven external BSC -> Mainnet bridge pattern to refill mainnet.
-4. Once mainnet is funded, fan out `Mainnet -> target` for Gnosis, Cronos, Celo, Polygon, Arbitrum, Optimism, and Base.
+4. Keep `Mainnet -> target` fan-out blocked until the current Mainnet WETH9 source bridge quote/send path is repaired.
 5. Seed Avalanche relay inventory only if Avalanche needs to become an active first hop too.
 
 ## Bottom line
@@ -129,6 +142,6 @@ cd /home/intlc/projects/proxmox/smom-dbis-138
 The practical route graph is now:
 
 - first hop from Chain 138 through the relay-backed lanes
-- keep mainnet funded and use it as the hub
+- keep mainnet funded and use it as the hub once the Mainnet WETH9 public fan-out path is repaired
 - use BSC as the proven bootstrap and recovery helper
 - treat the native-mapped public-chain bridges as mainnet destinations unless a dedicated relay is added for them