Rubicon

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

Rubicon’s measured liquidity perimeter now spans Optimism, Ethereum, Arbitrum and Base and aggregates three investable market-making systems: Classic order-book reserves and legacy Optimism Bath vaults, Aquila v2 constant-product pools and v3 concentrated-liquidity pools. DefiLlama measured $219,575 on 2026-08-16. Each measured claim holds inventory so others can trade, leaving the supplier exposed to fills or reserve rebalancing. The version-1 AMM-LP dossier remains exact, but the former Base-only/order-book-only description was stale.

Kill criteria: the events that revoke this verdict
• Ships a separately accounted product whose client return does not depend on market-making inventory, adverse fills or pool reserve rebalancing
• For any exact market or pool, approved assets, contracts, authorities, bounds, incident history and a proposed-size stressed inventory exit are independently verified

The research file

Mechanism and aggregate-class applicability

Rubicon Classic is an Oasis-style onchain order book; Optimism BathTokens pool assets and place maker liquidity. The current measured aggregate also includes Aquila v2, a constant-product AMM fork, and v3 concentrated-liquidity factories. Although execution curves differ, the investable balance in each system is inventory offered to traders and can exit in a different asset mix or after adverse fills. AMM-LP is therefore the closest existing fundamental class for the surveyed liquidity claims.

Corrected contracts and chain perimeter

The current adapter lists Classic markets on Optimism, Arbitrum and Base, seven legacy Bath pools only on Optimism, Aquila factories on Ethereum, Optimism, Arbitrum and Base, and v3 factories on the same four chains. The API attributed $219,575 across all four on 2026-08-16, led by Optimism and Base. This supersedes the stale Base-only four-pool description.

Control, lifecycle and exit applicability

Classic makers depend on order cancellation or counter-orders and custody in the market or Bath vault; Aquila and v3 LPs depend on pool reserves, price ranges, factory and pool code and chain settlement. The current Gladius intents system is a separate non-custodial trading path and is not counted as client TVL here. Proposed-size exit must therefore be proven separately for each exact Classic, Bath, v2 or v3 position rather than inferred from aggregate protocol TVL.

Comparison and measurable reopening test

Rubicon Classic changes execution from an AMM curve to explicit offers, but it does not remove adverse-selection or inventory-conversion risk for passive makers. Aquila and v3 map directly to constant-product and concentrated-liquidity alternatives. Reopen only for a separately accounted non-market-making product, or after an exact pool or maker mandate demonstrates approved assets, immutable bounds, complete authorities and a proposed-size stressed exit without unacceptable inventory conversion.

Sources

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

• Rubicon Docs — current protocol overview · primary · accessed 2026-08-16
  Supports: protocol identity, onchain exchange, product navigation, current lifecycle
• Rubicon — v1 Classic protocol repository · primary · accessed 2026-08-16
  Supports: RubiconMarket, order book, BathTokens, maker inventory, Classic contracts
• Rubicon — v2 protocol repository · primary · accessed 2026-08-16
  Supports: Aquila contracts, v2 liquidity, factory controls, protocol code
• Rubicon — Gladius protocol repository · primary · accessed 2026-08-16
  Supports: current intents product, non-custodial settlement, separate product scope, lifecycle
• DefiLlama adapter — Rubicon aggregate accounting · secondary · accessed 2026-08-16
  Supports: Classic markets, Bath pools, Aquila v2, CLMM v3, four-chain perimeter
• DefiLlama — Rubicon survey record · secondary · accessed 2026-08-16
  Supports: $219,575 TVL, Optimism, Ethereum, Arbitrum, Base

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.