Tokenized Stock Liquidity: Price, Pool TVL, and Executable Depth

How to separate indicative token prices, pool liquidity, and size-stated execution estimates when evaluating tokenized equities.

Reviewed 2026-07-10 · 6 minute read · Informational only

Price, pool capital, and executable depth are three different numbers

A displayed token price is an observation, not a fill. Pool TVL describes capital associated with a venue or pool, while an execution quote estimates the output available through a route for a specific input size. None can safely stand in for the others.

RWA Screener preserves these layers because thin tokenized-equity markets can look healthy at a headline price while deteriorating quickly as trade size increases.

Executable liquidity must always state size and time

A useful route estimate records input notional, expected output, price impact, venue or aggregator, and timestamp. Comparing routes at $1,000 and $25,000 can expose a slippage cliff that a single mid-price cannot show.

Quotes remain estimates. Pool state, order books, fees, and competing transactions can change between observation and execution, so the interface must not describe a quote as guaranteed liquidity.

  • Compare the same wrapper, direction, notional, and timestamp.
  • Keep aggregator routes distinct from the underlying pools or order books they traverse.
  • Flag stale or unavailable routes rather than carrying forward an old executable value.

Off-hours premiums need a timestamped reference

Tokenized equities may trade when the underlying US market is closed. During those periods, a premium should be described relative to the last valid reference price, not as a live premium to an underlying market that is not currently producing a price.

The reference source, market status, timestamp, and staleness belong next to the comparison. This keeps weekend price discovery separate from a claim about where the underlying equity would trade if its market were open.

How RWA Screener presents the evidence

Asset pages show normalized wrapper value, public pool observations, and size-stated execution routes as separate evidence. The methodology page documents the calculation boundaries, while each value retains its source and observation time where available.

The product is read-only. It does not route orders, guarantee execution, or infer that visible liquidity will remain available during market stress.

Primary sources

  1. xStocks: How xStocks work
  2. Jupiter: Developer documentation
  3. RWA Screener: Liquidity methodology