Introducing Limit Break AMM (LBAMM) A programmable AMM protocol that lets tokens and developers define exactly how trading works: fees, access, pricing, and liquidity. Built for onchain games, RWAs, and rule-enforcing assets. Not just a DEX—an execution engine.

This thread covers the highlights of Limit Break AMM. For the full deep dive into architecture, use cases, and more - read our blog: 🔗

Want practical design ideas? Check out the AMM Cookbook which is packed with examples you can adapt for your own markets: 📚

Tokens have evolved: enforcing access, charging fees, adapting over time. But AMMs haven’t kept up. LBAMM closes that gap with programmable logic at the token, pool, and position level.

Markets today run on DEXs that assume every token behaves the same. But tokens with rules can’t rely on legacy AMMs that do not understand them. They need infrastructure that enforces logic natively, not middleware bolted on top.

LBAMM is: – Modular – Context-aware – Fully extensible – Built from scratch for Apptokens – Permissionless across chains Hooks are first-class. Logic is enforced. Infrastructure is composable.

Token hooks enforce behavior across all pools: – Restrict access (NFT, KYC, game progress) – Apply dynamic fees – Block unauthorized transfers – Respond to context (caller, route, method)

Example: A token charges: – 1% for new wallets – 0.1% for active DAO voters – 0% for Gold NFT holders – Reverts trades from Sybil-flagged bots All enforced onchain.

Pool hooks define logic like: – Oracle or bonding curve pricing – Dynamic LP fees – Volume-based or address-based incentives – Custom whitelist access Each pool becomes its own programmable market.

Example: A game token pool charges: – 0.1% fee under $10 – 0.4% from $10 to $1K – 1.0% above $1K Encouraging in-game swaps while taxing large extractive flow.

Position hooks give fine-grained control: – Lock liquidity – Vest over time – Restrict LP access – Attach gameplay or protocol logic to LP behavior Liquidity becomes dynamic and role-aware.

Example: Only Wizard-class players at level 30+ can LP into a $MANA/ETH pool. They earn in-game rewards, leaderboard points, and crafting boosts as swaps route through their liquidity.

Execution is modular and consistent: – Direct swaps – Off-chain signed orders – Onchain orderbook-style limit orders – Routed affiliate flows – Flashloans

Each LBAMM pool is created with a specified pool type contract that defines its pricing, liquidity, and fee mechanics. Developers can introduce new pool types over time, expanding what kinds of markets the system can support.

Three pool types will be available at launch: – Dynamic Price, Concentrated Liquidity – Fixed Price, Asymmetric Liquidity – Single Provider, Hook-Controlled Pools (hook-defined pricing) All interoperate and share a common execution flow.

Signed orders: Users post off-chain intents with slippage and conditions. Searchers or peers fill them via LBAMM. Hooks still enforce token rules and fees.

Example: Sell 1,000 $TOKEN for 1 ETH. A solver fills via LBAMM pools and earns the spread. Meanwhile, the token hook applies a 1% tax, routed to its treasury.

Onchain orderbooks are native. Limit orders are posted onchain at fixed prices. Fillable by users or routing agents. Each fill runs through token, pool, and hook logic. CLOB, without offchain infra.

Example: Post: Sell 1,000 $TOKEN at 1.00 USDC. Swaps route into the order at that price. Each partial fill enforces token-level fees and access logic.

LBAMM deploys to the same address on every EVM chain. No permission. No custom integration. No need to ask or wait. Stable infra. Portable logic.

Why not Uniswap? Uniswap wasn’t built for tokens with rules. It assumes: – LP tokens move freely – Token logic is optional – Hooks see partial context LBAMM is different: – Hooks are global – Context is preserved – Rules are enforced By design.

LBAMM is for builders: – Games – RWAs – Permissioned DeFi – Affiliate routing Audit competition opens soon. Cookbook is live.

Liquidity doesn’t need to be passive. It can enforce. Adapt. Reward. Restrict. It can be lifecycle-aware. With LBAMM, liquidity is programmable. /end