This describes a pre-release version of LBAMM. Interfaces and behavior may change.
Verify the exact repository commit before building production integrations.
Audience & Roles
This documentation serves multiple audiences with different goals and integration depths. Each section is designed to stand independently while sharing a common set of concepts and terminology.
This page helps you identify which parts of the documentation are most relevant to you.
Token Issuers
Who you are
You are deploying a new token or extending the behavior of an existing ERC-20 using LBAMM. You care about where and how your token can be used, and you want those constraints to hold consistently across liquidity venues.
What you’ll care about
- How token-level hooks work and when they are invoked
- How pools, positions, and routes interact with token behavior
- What guarantees LBAMM provides around execution context and enforcement
- How much control you retain, and for how long
Recommended reading
Common misconception: LBAMM is only for Apptokens. In reality, LBAMM works with any ERC-20 token. Apptokens are simply ERC-20s that are designed to fully leverage LBAMM’s execution guarantees and hook system.
Common misconception: Using LBAMM means permanent issuer control. Control is defined by deployment choices. Hooks can be immutable, delegated, time-limited, or scoped. LBAMM enforces rules—it does not dictate who owns them or forever.
DEX Integrators & Aggregators
Who you are
You are building a DEX, router, wallet, or aggregator that wants to access LBAMM liquidity or execute trades through LBAMM pools.
You care about predictable execution semantics, composable interfaces, and avoiding edge-case failures when interacting with tokens that implement hook-based or policy-driven behavior.
What you’ll care about
- How execution context is constructed and propagated
- What assumptions you can and cannot make about token behavior or hook side effects
- How different pool types expose liquidity
- How hooks affect swap, mint, burn, and transfer flows
Recommended reading
Hook Authors
Who you are
You are implementing custom logic that runs during LBAMM execution. You may be writing:
- Token hooks
- Pool hooks
- Position-level constraints
You care about correctness, call ordering, invariants, and minimizing unintended interactions.
What you’ll care about
- Exact hook interfaces and call signatures
- When hooks run relative to core AMM logic
- What execution context data is available
- Which invariants the protocol guarantees vs. which you must enforce
Recommended reading