Field note

Prop-AMM Liquidity for Low-Volatility Assets

A field note on designing proprietary AMM liquidity for low-volatility assets, with emphasis on inventory, oracle, redemption, and depeg failure modes.

Matariki Research4 min readPublished 10 July 2026
LiquidityMarket StructureTokenized AssetsStablecoinsSolana

Executive summary

A proprietary AMM for low-volatility assets should not be judged only by the elegance of its invariant. Stable and near-stable assets need liquidity that respects redemption mechanics, issuer operations, oracle freshness, inventory limits, and stress behavior. The curve can make ordinary trades efficient, but it cannot guarantee par, absorb unlimited toxic flow, or replace a redemption process.

Problem or question

The design question is how to provide reliable secondary liquidity for an asset expected to trade near a reference value. That reference may be a stablecoin dollar, a fund net asset value, a redemption price, or an issuer quote. If the system quotes too tightly without inventory controls, it can become a subsidized exit for informed traders. If it quotes too conservatively, it fails to provide useful liquidity.

System or market context

StableSwap showed that AMM curves can be tuned for assets expected to trade close together, reducing slippage near equilibrium while preserving protection as balances diverge. General CFMM research formalizes the broader trade-off between reserves, prices, and invariants. Tokenized assets add another layer: redemption windows, offchain settlement, issuer controls, and cross-chain movement can matter more than pure onchain depth.

Design or analytical framework

A practical design starts with five questions. What is the reference price and who controls it? How quickly can redemption convert inventory back to the reference asset? What inventory imbalance is acceptable? Which oracle or issuer signal can be trusted under stress? What happens when the reference breaks? The AMM should encode conservative behavior around these questions. The invariant, fee curve, pause policy, and treasury rules should all point at the same operating model.

Trade-offs and failure modes

Low slippage is valuable until it attracts one-way flow during stress. Oracle lag can make the pool buy an impaired asset at a stale price. Redemption gates can trap inventory that the curve assumed was liquid. A proprietary design can add controls and circuit breakers, but those controls reduce permissionless composability. The strongest designs are honest about this: they optimize for a governed liquidity function, not for being the most open venue in all conditions.

Practical implications

Engineering teams should test inventory paths, not only swap math. Simulate redemption delay, oracle staleness, one-sided order flow, and pool imbalance. Risk teams should own caps and escalation thresholds. Product teams should avoid promising instant exits unless the underlying redemption and inventory process supports it. For institutional assets, a slightly less open design can be more credible if it makes stress behavior explicit.

Verification note

For testing, the most important scenarios are rarely the calm ones. Simulate stale reference prices, delayed redemptions, one-sided exits, oracle disagreement, inventory exhaustion, and market closures. The result should inform caps, spreads, pause logic, and operator procedures. A low-volatility pool can look efficient in ordinary flow and still fail when the asset becomes hard to redeem. The design should make that stress behavior explicit to users and operators. If the pool depends on offchain inventory movement, that dependency should be monitored with the same seriousness as onchain reserves.

Review discipline

Liquidity designs should be reviewed when market conditions and operating processes change. Redemption windows, oracle sources, treasury inventory, fee policy, route availability, and user composition all affect whether the AMM remains fit for purpose. A periodic review should replay stress scenarios using current assumptions, not the launch model. The key signal is not whether normal trades clear smoothly, but whether the pool still behaves explainably when reference value, inventory, or redemption confidence comes under pressure.

Conclusion

Prop-AMM liquidity for low-volatility assets sits between market design and operations. The pricing curve matters, but inventory, redemption, oracle quality, and governance matter more when the asset is under pressure. The right objective is not the tightest normal-time quote. It is a liquidity mechanism whose behavior remains explainable when par is tested.

References

  1. StableSwap whitepaperCurve.
  2. StableSwap overviewCurve.
  3. Constant Function Market MakersStanford University.
  4. Automated Market Makers in Cryptoeconomic SystemsarXiv.
  5. Cross-Chain Transfer ProtocolCircle.

Related

Related work