> For the complete documentation index, see [llms.txt](https://wallet-basics-guide.gitbook.io/wallet-basics-guide-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wallet-basics-guide.gitbook.io/wallet-basics-guide-docs/asymmetric-bridge-flows-and-treasury-liquidity.md).

# Asymmetric bridge flows and treasury liquidity

If your treasury sends more value out of one chain than it receives back, a bridge can become slower or costlier even when your wallet holds enough funds. The constraint is often inventory at the destination: bridge operators need assets there to pay recipients, and one-way demand gradually drains that pool.

### How does one-way demand strand bridge liquidity?

A liquidity bridge pays the recipient from tokens already held on the destination chain, then replenishes its position from the sender’s transaction or through a later rebalance. If payouts mostly travel from Chain A to Chain B, the Chain B pool loses tokens while assets build up on Chain A. Those balances cannot automatically cancel each other because they sit on separate blockchains.

For a business, the practical effect is that a route can still appear available while its destination inventory is becoming scarce. The provider may raise its quote, limit the amount, wait for replenishment, or stop offering that route until liquidity returns. Ethereum.org describes liquidity networks as one bridge design; Chainalysis also explains that bridge mechanisms differ, so check whether a quoted route uses prefunded liquidity, token locking and minting, or another method.

For example, suppose a company pays contractors 80,000 USDC each week from Chain A to Chain B, but receives only 20,000 USDC back. The remaining 60,000 USDC of net outflow has to be covered by liquidity providers or a separate rebalance. Before setting a recurring payout, compare a [Mayan bridge swap](https://www.tumblr.com/nobletwistorchestra/831001481811574784/what-does-it-move) with the other available routes for that exact token pair and direction; record the destination amount received, expected time, and total fee.

### What does rebalancing cost the treasury?

Rebalancing means moving assets back toward where the bridge needs them, or arranging an offsetting flow from another customer. It consumes capital and can add a second transaction’s fees, network costs, slippage, and settlement time. Providers may include those costs in the quote, so the displayed bridge fee alone may not reveal the full price of a persistently one-way route.

The important edge case is a route that works for small test transfers but cannot handle payroll day. A provider might have enough inventory for several modest payouts, then hit a per-transaction or pool limit when the batch arrives. The same treasury can also see a different quote after a volatile market move, because the provider’s cost and available inventory have changed.

### How should a treasury plan recurring transfers?

Plan around the route’s net direction and the recipient’s required arrival time. In my view, the deciding measure is the all-in cost and reliability for your actual batch size, not a bridge’s general fee claim.

1. **Measure the imbalance.** For each chain pair and token, total expected outflows and inflows over a normal week or month. Use the net amount to estimate how much destination inventory your schedule will consume.
2. **Quote the real batch.** Request a quote for the amount, token, source, and destination you will use. Note minimums, maximums, expected completion time, destination output, and any price impact.
3. **Test a small transfer.** Send a low-value payment through the intended route and confirm the recipient can use the delivered asset. A successful test confirms execution, but it does not prove capacity for a larger batch.
4. **Set a fallback and buffer.** Keep enough destination-chain funds for urgent payouts, and define a second route or funding method for when the normal quote exceeds your cost threshold or misses the deadline.
5. **Review after each cycle.** Compare quoted and actual arrival amounts, delays, and failures. If net outflow keeps draining the same destination, adjust transfer timing, source funds locally, or negotiate a replenishment arrangement.

I would pilot the route against one full payout cycle and keep the fallback funded until actual batch performance is predictable. Treat a Mayan bridge quote as one point-in-time price, then reassess it when direction, size, or timing changes.