Usage
Every kind of participant, and how each one interacts with the protocol.
These pages cover six participant roles in the current implementation. The protocol is pre-release; the leverage extension remains a separate proposal. Each role links to the relevant concepts.
Current implementation
| role | what they do | instrument |
|---|---|---|
| Swapper | buys or sells against the curve | instant fill: name what you pay, or on a C-pool what you receive |
| Resting order | buys or sells passively, earning fees while waiting | a capped LP position — no separate mechanism |
| Liquidity provider | provides liquidity on a C-pool, with their own floor and cap | fungible ERC-6909 position classes |
| Basket holder | holds assets as one productive, auto-rebalanced share | F-pool shares, base-to-base routing |
| Token creator | launches a token onto a structural price floor | a pad: an F-pool under the pad policy, |
| Developer | integrates programmatically | the TypeScript SDK |
Deferred to the leverage extension
| role | what they do |
|---|---|
| leveraged producer | borrows against a position to lever exposure |
| liquidator | keeps leveraged producers solvent; liquidation is a tick, not a search |
| supplier | lends quote (and base) to leveraged producers |
These are specified but not shipped. v1 is the AMM primitive only — a deliberate scope decision, with the core built so each extension can be added against an immutable base.
Start here
Getting started — token and position permissions, a first swap and a first position.
Choosing an operation
A trader selects a market, an amount and an execution bound. An uncapped C-pool LP chooses size and floor; a capped position adds an upper boundary. An F-pool depositor joins shared terms and chooses a deposit size. Each operation also needs token limits, a recipient and a deadline.