Skip to content
Keel
Ledger
64,490,308
Methodology
1.0.8-draft
Age
17s

What depth stands behind this price?

AQUA against USDC · GBNZIL…67AQUA

How much can this asset safely back?

The ceiling is the lower of two independent limits. Which one binds is the part a lender acts on, so both are shown.
  1. Low
  2. Medium — this asset
  3. High
  4. Critical

Mediumpartial confidence

A band marked partial is a floor. At least one high-severity check could not be evaluated, so the real band can only be worse than the one shown, never better.

6,420.60 USDC (shortened; full value 6420.6039029501798570929135125 USDC)

Limited by manipulation cost

Liquidation term
10,841.32 USDC (shortened; full value 10841.327135732386172958215707634548524368114882205319 USDC)

Sell-side depth at the liquidation delta, times the haircut.

Manipulation termbinds
6,420.60 USDC (shortened; full value 6420.6039029501798570929135125 USDC)

Order-book-only manipulation cost at the critical delta, times the safety margin.

These bands come from thresholds that were chosen, not calibrated

The thresholds were chosen based on the magnitude of the Blend incident of February 2026 and on conservative judgement, not calibrated against a set of incidents. Every flag is reported separately so that consumers can apply their own thresholds.

Every threshold, as the engine serves it

Where this number comes from
Source
GET /asset/{assetId}/depth → maxSafeCollateral, maxSafeCollateralLiquidation, maxSafeCollateralManipulation
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

What this computation could not do

  • maxReachablePrice and costToMaxReachablePrice are null because an active pool is present: under a constant product curve the price tends to infinity as the base reserve tends to zero, so every target is reachable and a highest price has no meaning

Served by the engine with this response and shown as written.

Where does the price come from?

Two venues can disagree. Both readings are shown, not only the one that won.
Mid price
0.00034034 USDC (shortened; full value 0.00034034402505575 USDC)

Source: order book mid

Spread
0.9731 % (shortened; full value 0.97311826994979170399803291 %)

Undefined unless the price came from a two-sided book

Pool spot price
0.00034165 USDC (shortened; full value 0.0003416507752024 USDC)

Reported whenever an active pool exists, whichever source won

Divergence between the two
0.3824 % (shortened; full value 0.38248124737192765194787526 %)

Null means there is no pool to diverge from, not that the sources agree

Where this number comes from
Source
GET /asset/{assetId}/depth → midPrice, priceSource, spreadPct, poolSpotPrice, priceDivergencePct
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

What volume can it absorb before the price moves?

Three rungs at 2, 5 and 10 per cent, in each direction. The buy side matters for oracle manipulation and the sell side for liquidation.
  • SDEX
  • AMM
  • Sell side, composition not reported

2% from mid

Buy side
17,010.43 USDC (shortened; full value 17010.4367667779240061806891806364 USDC)
Sell side
4,052.04 USDC (shortened; full value 4052.04979991979788326465551996474315857964369329013 USDC)

5% from mid

Buy side
24,086.71 USDC (shortened; full value 24086.715490073934887869919398086 USDC)
Sell side
18,196.48 USDC (shortened; full value 18196.48403394142331527455554308233692347416529974602 USDC)

10% from mid

Buy side
25,753.75 USDC (shortened; full value 25753.7569521547692810283753025438 USDC)
Sell side
21,682.65 USDC (shortened; full value 21682.654271464772345916431415269097048736229764410638 USDC)

Bars share one scale. The venue split decomposes the buy side; the sell side is drawn as an outline because its composition is not reported.

Where this number comes from
Source
GET /asset/{assetId}/depth → depth[]
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

What would it cost to move the price?

Read cost together with reachability: a figure on an unreachable rung says how far the book goes, not what the move costs.
Cost to move the price by each delta, through all venues and through the order book alone, with whether the target is reachable at all.
MoveTarget priceCost, all venuesCost, order book only
0.5%0.000510 USDC (shortened; full value 0.000510516037583625 USDC)29,857.10 USDC (shortened; full value 29857.1000349368077112922834025331 USDC)25,682.41 USDC (shortened; full value 25682.41561180071942837165405 USDC)
1%0.000680 USDC (shortened; full value 0.0006806880501115 USDC)34,218.94 USDC (shortened; full value 34218.9414392686709603634443984777 USDC)26,494.54 USDC (shortened; full value 26494.54298240078788837165405 USDC)
10%0.003743 USDC (shortened; full value 0.00374378427561325 USDC)248,202.81 USDC (shortened; full value 248202.8112428936466469354432586989 USDC)204,836.55 USDC (shortened; full value 204836.5566096040626018060151 USDC)
100%0.034374 USDC (shortened; full value 0.03437474653063075 USDC)926,115.60 USDC (shortened; full value 926115.6059475185416908655194542392 USDC)756,601.25 USDC (shortened; full value 756601.2534792282909118060151 USDC)

Reachability on the all-venues ladder is unconditionally true whenever an active pool exists, because a constant product curve has no upper price bound. The order-book-only column is the one that answers whether a target is attainable, and it is the one Keel itself uses.

How far the book actually goes

Furthest price the book reaches
not computed

Null by structure, not by failure: an active pool means every target is reachable and a highest price has no meaning

Cost to walk it that far
not computed

Null for the same reason as the price above

Against genuine volume

Not reported for this asset. Without it there is no comparison between the cost of an attack and the genuine trading it would have to hide inside.

Where this number comes from
Source
GET /asset/{assetId}/depth → manipulationCostCombined[], manipulationCostOrderbookOnly[], oracleResistance
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

Which checks fired, and which could not run?

An unevaluated check is not a check that came back clear. The two never share a treatment.

Triggered(1)

  • THIN_DEPTH_5PCT

Could not be evaluated(6)

  • MANIPULATION_RATIO_LOW
  • NO_GENUINE_TRADE_30D
  • HOLDER_CONCENTRATION_EXTREME
  • NO_GENUINE_TRADE_7D
  • HOLDER_CONCENTRATION_HIGH
  • WASH_TRADE_SUSPECTED
Where this number comes from
Source
GET /asset/{assetId}/depth → flags[], unevaluatedFlags[], bandConfidence
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

Who holds it, and is it genuinely traded?

Concentration and wash trading bound how much of the depth above is real.
Largest holder
not computed
Top ten holders
not computed
Concentration index
not computed

Herfindahl–Hirschman, over the holder distribution

Volume excluded as not genuine
not computed

Of 30 day volume. A high share indicates suspected wash trading

Volume to supply, 30 day
not computed
Last genuine trade
not computed

No genuine trade was found in the window

Where this number comes from
Source
GET /asset/{assetId}/depth → holderTop1Pct, holderTop10Pct, holderHhi, volumeToSupply, lastGenuineTrade, tradesExcludedPct
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

How has this moved over time?

A single reading cannot separate a thin asset from one that just got thin. This is a stored series, not the historical replay that health reports as unavailable — those are different endpoints.

No readings were stored in this range from this source

The engine accepted the request and returned nothing for Hubble. The series is as old as the deployment, and the reconstruction sources are not populated in production, so a window can reach back further than anything that was recorded. It is not empty because the figures were zero.

Where this number comes from
Source
GET /asset/{assetId}/history → points[], gaps[], dataSource
What it is
Awaiting methodology copy.
What it does not account for
Awaiting methodology copy.

What was this computed from?

Ledger
64,490,308

Closed at 2026-09-18T13:15:18Z

Computed at
2026-09-18T13:15:35.022854Z
Data source
horizon
Methodology
1.0.8-draft

The version that produced these figures, not the one this page was built against