The universal AMM primitive: one abstraction over every curve
How BlazePhoenix V2 routes across constant-product, stable and concentrated-liquidity pools through a single mathematical interface instead of per-DEX handlers. Pre-audit design.
Known formally as The Universal AMM Primitive in the BlazePhoenix whitepaper.
BlazePhoenix Engineering · updated 2026-08-05 · 7 min · written from the deployed bytecode
By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.
BlazePhoenix V2 is pre-deployment and under audit; this describes the intended abstraction. Most aggregators carry a separate code path per DEX family, which is where bugs and blind spots breed. V2 defines one universal AMM primitive: a common interface of get-output and capacity that each curve family — constant product, Solidly-style stable, concentrated liquidity — implements against the same contract.
Why one interface is safer
When every pool answers the same two questions in the same units, the router reasons about routes without knowing which venue it is on. Adding a venue means implementing the primitive, not touching the router, so the surface that can go wrong does not grow with integrations. It is the taxonomy of AMM math reduced to a single, testable contract boundary.
Do not trust this page — reproduce it
Every claim above is checkable against the chain. Start here:
Compare a stable-pool quote from the primitive to the pool own getAmountOut on chain; the universal path should match the venue within a tight toleranceCite this article
Licensed CC BY 4.0 — quote, translate and reuse freely, including commercially, with attribution and a link. Copy a ready-made citation:
BlazePhoenix (2026). The universal AMM primitive: one abstraction over every curve. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/universal-amm-primitive@misc{blazephoenix_universal_amm_primitive,
title = {The universal AMM primitive: one abstraction over every curve},
author = {BlazePhoenix},
year = {2026},
url = {https://blazephoenix.xyz/learn/universal-amm-primitive},
note = {Accessed: reproduce the claim with the command above}
}Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.
Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF). Standards cited: HTTPS://ARXIV.ORG/ABS/2204.05238 · HTTPS://ARXIV.ORG/ABS/2510.05428
Share this article · join the discussion