Skip to content
Keel
Ledger
64,490,137
Methodology
1.0.8-draft
Age
5s

What depth stands behind this price?

USDZ against USDC · GAKTLP…5U6XPR

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
  3. High
  4. Critical — this asset

Criticalpartial 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.

1,133.44 USDC (shortened; full value 1133.446541978002864355313255 USDC)

Limited by manipulation cost

Liquidation term
2,514.76 USDC (shortened; full value 2514.764930734339018206568226542814819097275291624936 USDC)

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

Manipulation termbinds
1,133.44 USDC (shortened; full value 1133.446541978002864355313255 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
1.00000280 USDC (shortened; full value 1.00000280491621955 USDC)

Source: order book mid

Spread
0.2195 % (shortened; full value 0.21952030779149815501858539 %)

Undefined unless the price came from a two-sided book

Pool spot price
1.00117016 USDC (shortened; full value 1.0011701616247994 USDC)

Reported whenever an active pool exists, whichever source won

Divergence between the two
0.1165 % (shortened; full value 0.11659923091249008018070042 %)

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
3,703.53 USDC (shortened; full value 3703.5353164746421260149104237761 USDC)
Sell side
4,286.18 USDC (shortened; full value 4286.1814467464970613279126471910536979934797581888 USDC)

5% from mid

Buy side
4,970.73 USDC (shortened; full value 4970.7375954419454222540600834503 USDC)
Sell side
4,561.24 USDC (shortened; full value 4561.248583815887588717708357693309465655063197581954 USDC)

10% from mid

Buy side
5,407.72 USDC (shortened; full value 5407.728917889468982269648386829 USDC)
Sell side
5,029.52 USDC (shortened; full value 5029.529861468678036413136453085629638194550583249872 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%1.500004 USDC (shortened; full value 1.500004207374329325 USDC)8,596.05 USDC (shortened; full value 8596.0528686719911826344588775401 USDC)4,533.78 USDC (shortened; full value 4533.78616791201145742125302 USDC)
1%2.000005 USDC (shortened; full value 2.0000056098324391 USDC)12,029.61 USDC (shortened; full value 12029.6166966972969807852167456979 USDC)4,533.78 USDC (shortened; full value 4533.78616791201145742125302 USDC)
10%11.000030 USDC (shortened; full value 11.00003085407841505 USDC)46,505.23 USDC (shortened; full value 46505.2355685606030222845088473441 USDC)4,533.78 USDC (shortened; full value 4533.78616791201145742125302 USDC)
100%101.000283 USDC (shortened; full value 101.00028329653817455 USDC)168,525.64 USDC (shortened; full value 168525.6410391107382000950468029925 USDC)4,533.78 USDC (shortened; full value 4533.78616791201145742125302 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(2)

  • MANIPULATION_CHEAP
  • 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,137

Closed at 2026-09-18T13:01:03Z

Computed at
2026-09-18T13:01:08.795098Z
Data source
horizon
Methodology
1.0.8-draft

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