Canonical Market Definition

Each PURITY launch defines exactly one canonical market, created at deployment: a constant-product AMM pair between the token and the base asset. The Treasury's constructor creates this pair itself, and the pair address is immutable from that moment; there is no mechanism to re-point a launch at a different venue.

In the current implementation the base asset is ETH (held internally as WETH), targeting EVM-compatible chains. The design generalises: the standard is chain-agnostic, and a deployment selects its chain and base asset at deployment time.

The canonical pool is the sole source of every market signal the Treasury consumes:

• price — computed directly from the pool's reserves,
• reserves — read directly from the pair,
• buying-pressure signals — measured as changes in the pool's base-asset reserve over time.

The constraints follow from that exclusivity. Treasury logic ignores all other pools and venues. No external price oracles are used, no time-weighted averages, no cross-pool aggregation, no off-chain data feeds. Every swap the Treasury executes references canonical pool reserves only.

This deliberately trades sophistication for robustness. Anchoring all behaviour to a single explicit market eliminates ambiguity about which price the system is responding to, removes the oracle-manipulation surface entirely, and keeps every input to the engine auditable from one contract. Arbitrage will connect external venues in practice, but the Treasury's behaviour is anchored to one source of truth that anyone can read.

The Treasury owns 100% of the initial LP in the canonical pool. Third parties may add liquidity afterward, which dilutes the Treasury's proportional LP ownership over time; the market-making logic operates on its own position and does not depend on holding 100% of LP at all times.