Read every dashboard number according to its source and unit, then cross-check timestamp, market scope, and calculation before comparing panels.
Map each view to its purpose
A dashboard is a set of lenses, not one unified truth. The home market indicators view screens CoinGecko assets with price, market capitalization, reported volume, returns, daily range, and rule-based labels. The DeepBook dashboard focuses on on-chain central-limit-order-book information for supported pools, including SUI/USDC. The charts page provides indicator context, and the signals page surfaces event-style prompts.
Because these views answer different questions, similar words can have different calculations. Browser pressure is a heuristic derived from market momentum, range, and volume conditions. DeepBook imbalance compares visible resting bid and ask notional. Server alerts monitor their own conditions and cooldowns. Do not assume the UI pressure number and a server alert are interchangeable.
Audit units before interpretation
The DeepBook order book returns price and quantity levels. The server sums price × quantity across visible bids and separately across visible asks, producing quote-value notionals. Those values describe displayed liquidity at retrieval time. Although internal response names may suggest longs and shorts, bids are not open long positions and asks are not open short positions. Resting orders can disappear before execution.
The dashboard field labeled spot TVL is populated from reported SUI/USDC 24-hour quote volume in the current implementation. Volume is flow over a period; total value locked is a stock measured at a point in time. This field is not actual TVL. Check labels, units, and documentation before comparing it with a protocol's formally reported TVL.
- Price × quantity gives order notional, not position exposure.
- Quote volume measures trading activity, not capital locked.
- A bid/ask ratio is specific to the sampled book and moment.
Account for freshness and fallback behavior
External APIs can be delayed, rate-limited, or temporarily unavailable. CoinGecko market responses are cached for five minutes; the market page also treats fetched data as fresh for 30 seconds. DeepBook requests can reuse a last-known-good snapshot without a maximum age, or return default fallback values if no snapshot exists. A stable screen is not proof of a live reading. If a source timestamp or live status cannot be established, treat the value as unverified and check another appropriate source before making a time-sensitive inference.
Server alerts are intentionally event-oriented and may use cooldowns to avoid repeated messages. The absence of a new alert is not evidence that market conditions are neutral. Conversely, an alert records a condition, not a trade instruction. Use the dashboard to formulate a question, then verify it on the relevant market and define risk.
Illustrative DeepBook depth read
Assume a simplified book with only the aggregate rows below. The numbers are hypothetical and omit fees, deeper levels, and cancellation risk.
- Visible bids
- 10,000 SUI × $1.20 = $12,000 notional
- Visible asks
- 8,000 SUI × $1.25 = $10,000 notional
- Bid/ask ratio
- $12,000 / $10,000 = 1.20
- 24h quote volume
- $500,000 activity; not $500,000 TVL
The sampled book is modestly bid-heavy, but it does not show $12,000 of longs or predict an upward trade. Price distance, order changes, and actual executions still matter.
Common interpretation traps
- Reporting DeepBook bid and ask notionals as long and short positions.
- Calling the 24-hour quote-volume proxy actual TVL.
- Comparing cached snapshots as though every panel shares the same timestamp and market.
Frequently asked questions
Why can the dashboard disagree with another exchange?+
Venues have different participants, pairs, liquidity, and update timing. DeepBook data describes its own pools; CoinGecko aggregates according to its methodology.
Does more bid notional mean price will rise?+
No. Visible depth can be distant, canceled, or consumed. It is liquidity context rather than a deterministic direction signal.
Are dashboard alerts the same as home pressure labels?+
No. They are separate mechanisms with different inputs and purposes. Avoid inferring undocumented threshold equivalence.