Liquidity Router

Ordo is Latin for order: a fixed sequence that does not vary. Every fee the protocol collects walks the same one — collected, priced against a time-averaged rate, converted, added to depth. The Liquidity Router is that sequence, written into a contract so nobody has to remember to run it.

What it does

A project collects fees from its own pool. Instead of those fees leaving the system, the router converts them into liquidity and adds them back to the pool. Depth goes up and stays up. Nobody has to remember to do it.

When it fires

Two triggers. Cadence routing fires on a fixed schedule. Milestone routing fires when the token crosses a market-cap level you set in advance. Milestones fire once each and in order, so a token that whipsaws across a level does not drain the buffer.

What guards it

Every conversion is priced against a time-averaged price rather than spot, so a router transaction cannot be sandwiched into a bad fill by whoever is watching the mempool. If the spot price sits outside the guard band, the route does not execute.

Who can move the money

Nobody. The funds stay inside the router contract for their whole life. A keeper can call the trigger and nothing else — it has no withdrawal path, no upgrade path, and no ability to change the destination pool.

Why it compounds

Deeper liquidity means less price impact per trade. Less price impact means larger orders fill without slippage. Larger orders mean more fee volume. More fee volume means more to route back in. That loop is the whole product.