liquidity distributed across seven chains creates a problem: imbalance. one day, base has surplus usdc sitting idle while solana vault is running thin. the protocol needs to move usdc from base to solana. it uses external bridges—wormhole or layerzero, whichever is cheapest at that moment. that bridge transaction has a fee. and heres the catch: that fee gets amortized to all users through higher protocol fees.
the mechanics get subtle. if your usdc swap costs 0.3% in protocol fees, part of that 0.3% is paying for rebalancing infrastructure. during periods of high volume, the rebalancing cost is spread across so many swaps that its invisible. each user bears a tiny fraction. but during low-volume periods, rebalancing costs become meaningful. the protocol still needs to rebalance to maintain the 25% minimum liquidity buffer. if trading volume drops, but rebalancing still costs $50k to execute, that cost now gets split across fewer swaps. your effective fee spikes.
plus, theres dead capital. while usdc is in-flight between chains during rebalancing, its not available for settlement. if rebalancing locks up 10% of protocol capital for hours, thats capital that cant earn fees. the protocol has to compensate by adjusting fees upward.
the tension: if you rebalance constantly, youre burning bridge fees. if you rebalance infrequently, you risk hitting the 25% minimum on busy chains. and if slippage on rebalancing transactions is high because youre moving large amounts, youre compressing protocol margins further.
does the protocol track realized rebalancing costs and adjust fee structures dynamically, or are costs absorbed statically