XRP Valuation Series  ·  The Living Framework
Field Note · April 29, 2026
The Living Framework  ·  No. 8

The network finds
the liquidity. Until it can't.

XRPL's pathfinding and dynamic liquidity assembly change the picture at smaller ticket sizes. A serious practitioner pushed on whether the static depth assumption overstates the requirement. He's right — up to a point. This note finds that point.

Origin of this note

"You're anchoring to 'liquidity must exist at execution' for large tickets. That's fair. But XRPL isn't a single pool. It's fragmented paths, routing, and conditional liquidity showing up just in time. If liquidity can be sourced dynamically across paths, your required static depth assumption might be overstated. The question isn't just how big the pool is. It's how efficiently the network can find and assemble liquidity at execution." — @mrcauliman, April 29, 2026

That is the right question. And it deserves a precise answer rather than a defensive one. The short version: the static depth assumption is overstated at smaller ticket sizes — the series should acknowledge that directly. At larger ticket sizes, specifically the irreducible ticket floor documented in Field Note No. 6, the dynamic assembly argument encounters a ceiling that the series can now define precisely.

This note draws that line. Not to defend the model from the challenge — but because locating the line is more useful than either asserting the static assumption universally or conceding it entirely.

What dynamic liquidity assembly actually does

XRPL's pathfinding engine does not route transactions to a single order book. It identifies the cheapest available execution path across the network's entire liquidity landscape — DEX order books, AMM pools, auto-bridged pairs, and LP inventory positions — simultaneously. A transaction that would move the market by 47bp against a single thin order book may be executable at 8bp when the engine finds and aggregates depth across twelve fragmented pools that individually couldn't absorb it.

This is a genuine capability and the series has not credited it fully. The static depth model — which prices required market cap against a single-pool execution assumption — overstates the capital requirement at ticket sizes where fragmented pool aggregation is effective. The concession is real. The question is where it stops being real.

Dynamic assembly doesn't eliminate the aggregate capital requirement. It distributes the market impact across more of the available liquidity. The question is how much liquidity is available to distribute across — and whether that scales with ticket size.

Where dynamic assembly helps — and where it hits a ceiling

The efficiency gain from dynamic path assembly is a function of two variables: the total depth available across all paths, and the degree to which that depth is fragmented rather than concentrated. When depth is fragmented across many small pools, pathfinding provides significant improvement over single-pool execution. When depth is concentrated — because the total available liquidity is small relative to transaction size — there are no efficient paths to find. The engine routes optimally across what exists. It cannot route to liquidity that does not exist.

This produces a three-regime picture across the framework's scenario tiers that the series has not mapped explicitly until now.

Scenario tier Ticket size range Regime What dynamic assembly does
Near-term corridor $1M – $50M Dynamic assembly wins Fragmented XRPL pools, JIT LP inventory, and pathfinding provide meaningful improvement over single-pool execution. Static depth assumption overstates the requirement at this tier. Current peak ODL tickets are estimated below $1M, placing today's network at the boundary of the dynamic assembly regime — the settlement terminal shows a live ceiling of ~$875K at current spot volume and volatility. The framework's $16–$180 near-term range may already be conservative as a result.
Transition zone $50M – $500M Mixed — empirically unresolved Dynamic assembly provides partial improvement but total available depth becomes increasingly binding. No confirmed on-ledger execution data exists in this range. This is where the framework's assumptions are least empirically anchored — the series acknowledges this gap directly.
Irreducible ticket floor $500M – $500B Static depth is the binding constraint At these sizes, the sum of impacts across all available paths approaches the single-path impact. There is no fragmentation efficiency gain when transaction size exceeds total available depth across all pools combined. BIS Project Mariana establishes linear scaling in this regime — more liquidity required, not less, than the square-root law implies.

The transition zone — $50M to $500M — is where the series is most honest about what it doesn't know. No confirmed XRPL execution data exists in this range at institutional slippage tolerance. The framework's assumptions in this zone are calibrated from BIS pilot data, LP spread math from Field Note No. 1, and the AMM scaling findings from Field Note No. 7. They are informed estimates, not empirically anchored observations. The series names this gap explicitly and watches for the data that would close it.

Why the ceiling exists

The intuition behind the ceiling is straightforward. Dynamic liquidity assembly improves execution by finding depth the single-pool model doesn't see. But the total depth available across all paths is bounded by the total XRP capital deployed in the network's liquidity infrastructure — LP inventory, AMM pool deposits, order book resting orders. That total is a direct function of XRP's market cap and the economic incentives to deploy capital into settlement infrastructure.

At small ticket sizes, a transaction represents a small fraction of total available depth. Pathfinding is effective because there is more depth than the transaction needs, distributed across many pools. At large ticket sizes, the transaction approaches — or exceeds — a meaningful fraction of total available depth across all paths simultaneously. At that point, the engine is not finding hidden liquidity. It is routing optimally across everything that exists, and everything that exists is not enough.

The ceiling — when dynamic assembly stops helping
Let V = required daily volume across all paths    Q = transaction size    σ = volatility    τ = slippage tolerance
Ceiling derivation from Part I square-root law (Impact = σ × √(Q/V), set Impact = τ):
Dynamic assembly effective when:  Q << V × (τ / σ)²
Static depth becomes binding when:  Q approaches V × (τ / σ)²
At current state (σ = 5%, τ = 10bp, V = live 24h spot volume ~$2.19B per terminal):
Ceiling Q = $2.19B × (0.001 / 0.05)² = $2.19B × 0.0004 = ~$875K
At institutional scenario (σ = 3%, τ = 10bp, V = $1.8T/day at $180T mcap × 1% turnover):
Ceiling Q = $1.8T × (0.001 / 0.03)² = $1.8T × 0.0011 = ~$2B
Note on V inputs: the current ceiling uses live 24h CoinGecko spot volume (~$2.19B) — the same source as the terminal — which reflects actual observed market depth. XRP is currently trading at ~2.7% daily vol/mcap, above the model's 1% central estimate, producing a higher live ceiling than a pure model calculation would imply. The institutional scenario uses V = market cap × 1% turnover (the Part I central estimate) because no live data exists at that scale. The ceiling scales from ~$875K today to ~$2B at institutional — a 2,300× increase driven by market cap growth. Today's ODL peak tickets (<$1M) sit at the boundary of the current ceiling, confirming the network is approaching the limit of the dynamic assembly regime at current depth.

This is the framework's most important response to the dynamic assembly challenge: the ceiling is not fixed. It scales with market cap. A deeper, more liquid network has a higher ceiling — which means dynamic assembly remains effective at progressively larger ticket sizes as the system matures. But the ceiling always exists, and at the irreducible ticket floor — $500M to $500B — the required market cap to push the ceiling above the transaction size is the institutional and sovereign scenario range the series has always described. Dynamic assembly doesn't eliminate the required price. It changes where the static depth assumption begins to bite.

What the series concedes and what it holds

The concession is real and should be stated plainly. The static depth model overstates the capital requirement at the near-term corridor tier. XRPL's pathfinding, AMM pools, and JIT LP inventory provide genuine execution efficiency that the single-pool model does not capture. The near-term scenario prices in the series — $16 at the lowest tier — may be conservative. A more sophisticated execution model might show that dynamic assembly keeps slippage within tolerance at lower prices than the static assumption implies for the sub-$50M ticket range.

The framework's core claim holds at the irreducible ticket floor. For the $500M–$500B transaction categories documented in Field Note No. 6, dynamic assembly encounters the ceiling described above. The aggregate market impact across all available paths approaches the single-path impact when transaction size is a meaningful fraction of total system depth. At those sizes, the framework's required price is not an overstatement of a single-pool execution. It is a statement about total system depth — how much XRP capital must exist in aggregate, across all paths and pools, to absorb the transaction within tolerance. That claim survives dynamic assembly entirely.

The ceiling scales with market cap. Dynamic assembly remains effective at progressively larger tickets as the system matures. But the ceiling always exists — and at the irreducible ticket floor, the price required to push the ceiling above the transaction size is the institutional scenario the series has always described.

What to watch

Signal 01  ·  The transition zone
Any confirmed multi-path execution on XRPL at $100M+ ticket size with cumulative slippage documented below 10bp. This is the single most important data point for resolving the transition zone. It would be the first empirical evidence that dynamic assembly is effective above the current ODL corridor range. It does not need to be in the $500M range to matter — a confirmed $100M+ execution with documented slippage would narrow the uncertainty meaningfully. The series has named this signal in Field Note No. 6 and watches for it actively.
Signal 02  ·  AMM pool depth on XRPL
Total value locked in XRPL AMM pools relative to ODL corridor volume. If AMM TVL grows faster than corridor volume, the ceiling for dynamic assembly is rising relative to current ticket sizes — the network is becoming more efficient before it needs to be. If corridor volume grows faster than AMM TVL, the transition zone is compressing and static depth becomes the binding constraint sooner than the model implies.
Signal 03  ·  Prisma production data
Any disclosed execution data from Prisma's multi-path routing in production ODL. Prisma is the specific technology that would push the near-term corridor ceiling upward. Execution quality data — average slippage, path count, pool utilization — would allow the series to calibrate the transition zone boundary empirically rather than inferring it from BIS pilot data and theoretical models. This is the data point that would most directly anchor the framework's variables to real on-ledger behavior over time.
Framework status

The settlement thesis is unchanged. This note adds a three-regime map of where dynamic liquidity assembly is effective, where it is empirically unresolved, and where static depth is the binding constraint. The near-term scenario's static depth assumption is acknowledged as conservative — dynamic assembly provides genuine improvement at sub-$50M ticket sizes. The institutional and sovereign scenarios are unchanged — at the irreducible ticket floor, aggregate market impact across all paths approaches single-path impact, and the required price is a statement about total system depth, not single-pool execution. The transition zone ($50M–$500M) remains the framework's least empirically anchored region and the series watches for the data that would resolve it. The ceiling — the ticket size at which dynamic assembly stops helping — scales with market cap, which is precisely the framework's core claim about why price must rise with adoption.

Cross-references: Field Note No. 1 (JIT sourcing and LP inventory mechanics) · Field Note No. 6 (irreducible ticket at the obligation level) · Field Note No. 7 (AMM linear scaling at large transaction sizes).

On the ceiling calculation. The ceiling formula Q = V × (τ/σ)² is derived by inverting the square-root impact law (Impact = σ × √(Q/V), solving for Q when Impact = τ). The current ceiling uses live 24h CoinGecko spot volume (~$2.19B) as V — the same source as the settlement terminal — producing a ceiling of ~$875K at σ=5%, τ=10bp. The institutional scenario uses V = $180T × 1% turnover = $1.8T/day (the Part I central estimate), producing a ceiling of ~$2B at σ=3%, τ=10bp. The two V inputs differ because live spot volume is available for the current state and not for the institutional scenario, which has no real-world data equivalent. XRP currently trades at ~2.7% daily vol/mcap — above the model's 1% central estimate — meaning the live ceiling is higher than a pure model calculation would imply. All figures are illustrative thresholds, not precise boundaries.

On the transition zone. The $50M–$500M range is an informed estimate based on current XRPL AMM pool depths, LP inventory data from public XRPL metrics, and the BIS Project Mariana findings on multi-path AMM execution. No confirmed institutional-scale execution data exists on XRPL in this range. The boundary is approximate and the series updates it as evidence becomes available.

Attribution. The dynamic liquidity assembly challenge that prompted this note was raised by @mrcauliman on April 29, 2026. The series credits serious technical challenges that advance the framework's precision. This modeling is still in its infancy. Objections and falsifiers are welcomed. Adjustments will be made accordingly. This is not financial advice. Do your own research.