Joe V2.1

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Joe V2.1 is LFJ’s Liquidity Book AMM, now surveyed across Avalanche, Arbitrum, BSC and Ethereum. LPs distribute paired assets among fixed-price bins and earn fixed plus volatility-sensitive swap fees. Zero slippage within the active bin benefits traders; it does not protect LP inventory as price moves across bins. The version-1 amm-lp dossier therefore controls regardless of the approximately $3.05M TVL observed on 2026-08-15.

Kill criteria: the events that revoke this verdict
• Ships a product line without impermanent-loss exposure that merits its own review

The research file

Mechanism applicability

Liquidity Book is a concentrated-liquidity AMM that replaces ticks with discrete bins. LPs pair token X and token Y, choose a distribution across price bins and receive fungible LBToken balances. Swaps consume inventory from the active and adjacent bins, while fixed and variable fees accrue to participating LP positions. This is direct two-asset market making and exactly fits the shared amm-lp dossier.

Current observation and perimeter

The DefiLlama protocol API read on 2026-08-15 classified Joe V2.1 as a DEX and reported approximately $3.05M across Avalanche, Arbitrum, BSC and Ethereum, correcting the stale Avalanche-only registry perimeter. LFJ keeps version-specific routers because v2.1 pairs are not backward-compatible with the newer v2.2 router for liquidity removal. The record is live legacy infrastructure, not a generic reference to all LFJ versions.

Control, loss and exit applicability

LPs choose bins, shapes and withdrawal timing, but trades determine the assets remaining in each bin. LFJ warns that no distribution prevents impermanent loss and that concentrated shapes can require frequent rebalancing; v2.1 fees remain in position reserves until withdrawal. Exit requires the v2.1-compatible router and returns the current bin inventory, so router improvements, surge fees and incentives cannot restore relative inventory sold into price movement.

Why the class rule decides

Liquidity Book changes the curve and fee response, not the client’s role as market maker. Dynamic fees may compensate volatility and zero-slippage bins improve execution for traders, while LPs still face out-of-range and weaker-asset concentration. The shared version-1 amm-lp dossier therefore decides. Reopen only for a separate LFJ product whose client return does not require paired or synthetic liquidity provision.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• LFJ — current Liquidity Book documentation · primary · accessed 2026-08-15
  Supports: Liquidity Book, current lifecycle, liquidity documentation
• LFJ — liquidity shapes and impermanent-loss warning · primary · accessed 2026-08-15
  Supports: bin ranges, liquidity shapes, impermanent loss, active management, fee eligibility
• LFJ Developer Docs — bin inventory and LP tokens · primary · accessed 2026-08-15
  Supports: token X, token Y, bin composition, LBToken, paired reserves
• LFJ Developer Docs — v2.1 fee accounting · primary · accessed 2026-08-15
  Supports: fixed fee, variable fee, v2.1 reserves, withdrawal, volatility
• LFJ Developer Docs — version-specific liquidity removal · primary · accessed 2026-08-15
  Supports: add liquidity, remove liquidity, v2.1 router, bin distribution, version compatibility
• DefiLlama — Joe V2.1 survey record · secondary · accessed 2026-08-15
  Supports: current TVL, current chains, Dexs category, survey observation

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.