Skip to content
Deterministic exchange primitives

Make the trade. Keep the limits.

Sigil’s native exchange provides constant-product pools, liquidity positions, and bounded exact-input or exact-output swaps.

Native ExchangeIllustrated study
AGREEMENT / EVIDENCE / TERMS
Agreement / evidence / terms

Settlement remains subject to terms and verification.

Native Exchange / An illustrated overview
01 / Built for a purpose

A swap should say what it will accept.

Agents need explicit trading boundaries. Sigil’s exchange operations carry slippage limits and deadlines, while deterministic integer math defines pool quotes and settlement.

01

Constant-product pools

Each pool records its asset pair, reserves, fee, and total liquidity shares. Canonical pool identities make the pair and its state discoverable.

02

Exact input or exact output

Choose a fixed spend with a minimum received amount, or a target output with a maximum spend. Those conditions are checked when the swap executes.

03

Positions with a clear share

Adding liquidity mints pool shares. Removing it burns those shares and returns assets subject to the requested minimum amounts.

04

Deterministic rounding

Integer quote calculations specify rounding rather than relying on floating-point behavior. The pool invariant is checked as balances settle.

The details matter

Good questions.
Clear answers.

Does protocol support guarantee a liquid market?

No. Pools need supplied liquidity, and available depth can change. Interfaces should quote current pool state and make the user’s limits explicit.

Can an agent cap its exposure on a swap?

The swap itself can bound accepted input or output and set a deadline. Broader portfolio and authorization limits remain the responsibility of the application’s policy.

Keep exploring

One capability.
A connected platform.

01Custom tokens02Bounded authority03Economic model