Summary: Maverick is best cataloged not as just another concentrated-liquidity DEX, but as a protocol that moves liquidity positioning itself into the AMM’s native mechanism. Its core idea is the Dynamic Distribution AMM: LPs choose static or movement modes (Right, Left, Both, Static), and the smart contract automatically shifts bins as price moves instead of outsourcing active management to off-protocol vault managers. That makes Maverick a useful comparison class for Uniswap v3-style range liquidity, Bunni- or Arrakis-style manager layers, and other systems where the real control surface is not the swap curve alone but who gets to decide when and how liquidity stays near price.
What it does:
Lets LPs provide concentrated liquidity across customizable price bins with configurable widths and fee tiers
Supports four native liquidity modes: Right, Left, Both, and Static
Automates liquidity movement inside the AMM smart contract so LPs in movement modes do not pay gas to reposition bins
Enables directional LPing, where an LP can intentionally follow price in one direction rather than merely betting on sideways markets
Allows custom liquidity distributions within a single position rather than forcing LPs to mint many separate positions to express more complex shapes
Routes trader flow across available pools to the pool offering best execution at a given moment
Key claims:
The docs homepage calls Maverick the first Dynamic Distribution AMM, emphasizing native automation of concentrated-liquidity movement rather than manual rebalancing by LPs or third-party managers
The docs explain that LP positions are built from bins, with movement rules based on price behavior and a TWAP-driven mechanism for when liquidity should shift
Mode Right and Mode Left are explicitly framed as directional tools for LPs who want to follow price in only one direction, which is analytically different from ordinary passive range liquidity
Mode Both keeps liquidity close to price in both directions, but the docs also surface a protocol-specific Permanent Loss risk, which matters because the efficiency gain comes from a distinct loss surface rather than from free improvement over Uniswap-style range LPing
The docs warn that movement-mode security depends on sufficient static liquidity and arbitrage depth to resist unwanted TWAP manipulation, which makes pool composition and bootstrapping policy a real control surface
The original protocol writeup argues Maverick can absorb strategies that elsewhere would be implemented by meta-protocols, meaning the protocol internalizes a layer of active-liquidity management that other ecosystems often leave to vault managers
The public GitHub org and v2 interfaces/examples repos support the view that Maverick is not just a UI concept but an actively exposed smart-contract and routing surface
Whitepaper: The canonical public technical paper is the official Maverick Directional AMM v1.0 PDF, saved locally at ../whitepapers/maverick-directional-amm-v1.0.pdf. See also ../whitepapers/maverick-protocol-primary-sources-2026-05-09.md.