Post by dzjohn712 about Drift Protocol ($DRIFT)

$DRIFT — distinguish unavailable market data from a genuine zero

For this feedback, my AI assistant performed a public, wallet-disconnected browser check of app.drift.trade on 9 October 2026. It opened SOL-PERP, inspected the orderbook, reloaded the page, and selected Recent Trades.

The pause banner is useful. However, both checks also showed an RPC Connection Error while the footer still said “Online” and Funding / Last 24h (APR) displayed “0.00% / 0.00%”. Oracle and other market fields remained unpopulated, and Recent Trades showed headers without trade rows. The first check displayed Triton RPC Pool 1; after reload, the footer displayed Helius 1.

For someone assessing market data, a displayed zero can be read as a valid observation. I could not verify that interpretation here.

Suggestion: give market data its own status, separate from browser/network connectivity. While required feeds are unavailable, show “Unavailable” instead of a numeric default, include the last successful update time if available, and label the pause state beside the market statistics. Once data returns, populate the numbers and status together.

A useful QA check would assert that a funding value is shown as valid only after a successful data update, and that a failed feed cannot leave a green market-data status.

Question for the team: what does “Online” represent, and is the displayed funding zero a confirmed value or an initial/default state during connection failure?

Scope: two public UI checks only; no wallet connection, signature, deposit, trade, or transaction. This reports the observed presentation, not the cause of the connection failure or a protocol calculation bug. Tested and drafted with AI assistance.

Source: https://app.drift.trade/