Just spotted something interesting about HyperEVM's USDC implementation—turns out it doesn't route through the standard Arbitrum bridge like most people assume. To be clear, this isn't calling out any data platform for getting it wrong. It's an easy miss, honestly. Even folks deeply familiar with the ecosystem only caught this detail recently.

The fix itself is straightforward once you know what's happening under the hood. HyperEVM has its own pathway for USDC transfers, which explains why the numbers might look off if you're tracking through traditional Arb bridge metrics. Worth noting for anyone building dashboards or analyzing cross-chain liquidity flows.