Protocol-owned liquidity: how to set it up
Fund it, manage it, keep it non-custodial.
Protocol-owned liquidity (POL) is set up by allocating treasury assets to an LP position that the protocol itself controls, ideally through a non-custodial vault where a strategy operator such as Amplifi manages ranges but only the protocol can withdraw. The core decisions are how much to allocate, which assets fund each side, who operates the position, and what the strategy is allowed to do. Done properly, POL is permanent depth that earns fees for the treasury instead of paying emissions to renters.
Decide the allocation
Size POL against target in-range depth, not against a percentage of treasury. Model the drawdown you want to defend under expected sell flow, then size to that. The right number is whatever makes the pool credibly deep at the reference spread; anything less is symbolic.
Fund the sides
POL can be paired (native + stable/WETH) or single-sided (native token only, using a single-sided vault that converts as buyers hit it). Paired POL provides symmetric depth immediately but requires the treasury to source the quote asset. Single-sided POL avoids selling anything at deployment and lets organic flow accumulate the quote asset over time. Most treasuries mix both.
Choose the operator and the guardrails
The vault sits on the protocol's Safe. The operator (Amplifi or an in-house LP team) holds strategy authority through a separate multisig with a scoped role: it can move ranges, rebalance, and collect fees, but it cannot withdraw funds. Write the guardrails into the multisig role: allowed pools, allowed range widths, max inventory tilt, pause conditions.
Report and govern
POL performance is fully onchain: current inventory, fees accrued, rebalances, and net APY reported in deposit-token terms. Governance controls when to expand, contract, or wind down the position. The treasury retains withdrawal rights at all times.
To scope a POL mandate, contact contact@amplifiliquidity.com.