Low Liquidity Markets

Because AggreLend selects among multiple venues per token, there are times when the top-quoted market has limited capacity or fast-changing utilization and therefore cannot sustain its headline rate once filled at size; to keep realized outcomes steady, the router evaluates liquidity health before any optimization and may choose to place only a portion of a large balance into the top venue, prefer the second-best venue when it is materially more stable, or split allocations across the top candidates so each leg sits inside a healthy capacity band, which reduces immediate rate decay and preserves the usefulness of the on-screen APY as a predictor of what the position will actually earn.

This stability bias is intentional: rather than chase brief spikes that fall as soon as deposits arrive, the router waits for improvements to persist across a short confirmation window and checks for basic signs of rate reliability so the position avoids back-and-forth thrash; users do not need to take action for this to work, since the routing logic handles these checks and executes the atomic withdraw-then-deposit sequence only when it expects a better result than staying put.

When conditions change, the interface updates and the router evaluates again on its next cycle, which keeps allocations aligned with what is achievable in practice rather than what is theoretically quoted at zero utilization.