This describes a pre-release version of LBAMM. Interfaces and behavior may change.
Verify the exact repository commit before building production integrations.
Integration Guides
This section walks through integrating with LBAMM in the order a real application encounters it.
It is written primarily for:
- Frontend and DEX UI developers
- Token issuers deploying their own markets
- Teams building production-facing swap interfaces or routing layers
These guides assume you understand core concepts such as:
- Pools
- Liquidity
- Swaps
- Hooks
- Fee surfaces
If you need deeper protocol semantics, refer to:
- Protocol Fundamentals
- Hooks
- Pools
- Fees & Economics
This section focuses on how to use the system correctly in production.
The Integration Lifecycle
Interacting with LBAMM follows a natural progression:
-
Create a Pool
Define a market between two tokens and configure pool type and fee behavior. -
Add Liquidity
Supply capital to the pool so swaps can execute. -
Execute Swaps
Perform single-hop or multi-hop swaps with explicit execution-level fee configuration. -
Route Across Pools
Construct multi-hop routes and reason about per-hop and execution-level fee behavior. -
Use Transfer Handlers & Signed Orders
Integrate advanced settlement patterns (permit-based flows, CLOB-style flows, etc.). -
Read Execution Context
Surface contextual data to hooks, indexers, analytics, and UI components. -
Avoid Common Integration Mistakes
Prevent subtle execution, fee, and routing errors.
Each guide builds on the previous one.
If you are building a production swap interface, you should follow them in order.
What These Guides Emphasize
These guides prioritize:
- Deterministic behavior
- Correct fee wiring
- Safe parameter bounds
- Execution ordering clarity
- Production-grade assumptions
They do not:
- Recommend fee values
- Prescribe economic strategy
- Provide UI/UX design guidance
- Replace formal protocol reference documentation
Production Assumptions
Examples in this section assume:
- Tokens are already deployed.
- The LBAMM contracts are deployed.
- You are interacting with production contracts.
- You are not relying on local-only test scaffolding.
We will not cover token deployment, faucet flows, or test token minting.
How to Use This Section
If you are:
A DEX UI developer
Start with:
→ Create a Pool (if your interface allows pool creation)
→ Add Liquidity
→ Execute Swaps
A token issuer launching a market
Start with:
→ Create a Pool
→ Attach Hooks (if applicable)
→ Add Liquidity
Building a routing layer
Focus on:
→ Execute Swaps
→ Route Across Pools
→ Transfer Handlers
Design Philosophy
LBAMM is explicit:
- Fees are explicit.
- Routing is explicit.
- Hooks are explicit.
- Execution context is explicit.
Your integration must respect that explicitness.
These guides show how to wire everything correctly without accidentally introducing hidden assumptions.