Joe V2.2
Joe V2.2 is LFJ’s Liquidity Book exchange, which lets liquidity providers place capital in discrete price bins on Avalanche and Monad. Binned liquidity is concentrated liquidity: when price moves out of a provider’s range, the position converts into the weaker asset and the loss is realised on exit. That is impermanent loss, and it cannot be explained to a mass-affluent client in two sentences or defended when it bites. We reject the AMM liquidity-provision category as a whole, protocol quality aside. Joe V2.2 held $9.1M across 19 pools at the August 14, 2026 survey.
- Ships a product line without impermanent-loss exposure that merits its own review
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Applicability to the surveyed record
LFJ identifies Liquidity Book v2.2 as a concentrated-liquidity AMM. Liquidity is distributed across discrete constant-sum price bins; bins away from the active price hold only one side of the pair, and LPs choose their distribution. That inventory conversion establishes the shared AMM-LP class despite the design differing from constant-product pools.
Current observation and perimeter
The DefiLlama API read on 2026-08-15 classified Joe V2.2 as a DEX and reported approximately $3.43M: $3.35M on Avalanche, $42,100 on Monad and $37,900 on Arbitrum. Arbitrum is added to the observed perimeter; size is contextual because the shared v1 AMM-LP exclusion applies at any scale.
Control and exit applicability
LP outcomes depend on token pair, chosen bins, bin step, active-price movement and fixed plus volatility-responsive fees. As swaps cross bins, inventory converts toward one asset and only crossed bins earn fees; withdrawal realizes the position’s current asset composition rather than restoring the original pair quantities.
Why the class rule decides
The shared v1 AMM-LP dossier controls because Liquidity Book fee income still requires two-sided inventory conversion against market moves. Reopen only for an economically separate LFJ product without AMM inventory exposure, then review its cash flows, contracts and control, asset and chain dependencies, audits and incidents, executable liquidity, stressed exit, and named non-AMM alternatives.
Class rule
The amm lp class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- LFJ — current protocol documentation · primary · accessed 2026-08-15
Supports: Liquidity Book DEX identity, discrete liquidity bins, LP distributions, Avalanche and Monad deployment, fee capture - LFJ — bin-liquidity mechanics · primary · accessed 2026-08-15
Supports: constant-sum bin, active price, one-sided out-of-range bins, reserve composition - DefiLlama — Joe V2.2 survey record · secondary · accessed 2026-08-15
Supports: current TVL, Avalanche, Arbitrum, Monad, DEX category, survey perimeter
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Avalanche | Approved with limits | Governed, no freeze | no party can freeze or seize C-Chain funds, but one vendor writes the only production client and Messari measured over a third of stake hosted on AWS. |
| Arbitrum One | Approved with limits | Mixed control | a single sequencer orders >99% of transactions and admin keys can upgrade bridge contracts on a ~7-day timelock. |
| Monad | Approved with limits | Governed, no freeze | the L1 has a public validator path, but its short production record, single initial client lineage, and Foundation-directed delegation keep stake and operations concentrated. |