Pool profiles
Compare the four immutable Abyss pool profiles and choose the appropriate fee and observation model.
A pool profile fixes two independent decisions at creation:
- Whether fees follow the input asset or one designated quote asset.
- Whether the pool records only canonical observations or canonical plus truncated observations.
| Interface name | Contract profile | Fee denomination | Observation histories |
|---|---|---|---|
| Standard | STANDARD | Input token | Canonical |
| Beacon | STANDARD_ORACLE | Input token | Canonical and truncated |
| Stream | QUOTE | Designated quote token | Canonical |
| Lighthouse | QUOTE_ORACLE | Designated quote token | Canonical and truncated |
Standard
Standard preserves the familiar concentrated-liquidity fee model. A trade pays its fee in the input asset. Buying the base token with the quote token accrues quote-token fees. Selling the base token accrues base-token fees.
Use Standard when conventional two-asset fee inventory is desired and no truncated observation stream is required.
Beacon
Beacon combines Standard fee accounting with the auxiliary truncated observation ring. Fees can accrue in either asset, exactly as in Standard. The pool additionally commits a quote-normalized tick history subject to its immutable per-block movement cap.
Use Beacon when conventional fee accounting and a bounded-movement data stream are both required.
Stream
Stream directs swap and permitted flash fees into one designated quote token. This creates a consistent fee inventory for liquidity providers across both trade directions. The spot curve, ticks, ranges, and canonical observations remain concentrated-liquidity behavior.
Use Stream when providers want fee claims denominated only in a selected quote asset and do not need the truncated observation ring.
Lighthouse
Lighthouse combines Stream fee accounting with the truncated observation ring. It is the quote-fee, oracle-enabled profile. The name describes a market that produces a consistent quote-token fee stream and a bounded-movement reference stream.
A Lighthouse pool is not safer merely because it has an oracle. The oracle does not guarantee truthful price, deep liquidity, economic value, USD conversion, or suitability as collateral.
Immutable choices
The profile, fee tier, quote orientation, and oracle configuration are part of the pool key. They cannot be changed after creation. Creating another pool with different settings creates a separate market and separates liquidity.
Permissionless lifecycle
Anyone may create a structurally valid pool, initialize it once, add or remove liquidity, collect, or trade. The factory does not maintain token, creator, trader, router, quote-token, or liquidity-provider allowlists. Pool creation does not call token contracts, so a successfully created pool does not establish that either token behaves correctly.