X1 Dashboard data methodology
How browser RPC, live slots, one-minute lightweight reads and ten-minute full reads feed X1 Dashboard.
Documentation reviewed
This is a documentation review date, not the timestamp of live data.
Browser-only chain reads
The browser uses X1's configured public HTTP RPC and WebSocket endpoint. There is no Dashboard Collector or historical database behind this X1 site. Individual failed components remain unavailable rather than being fabricated as zero.
Validator labels come from the same-origin validator-names.json shipped with the App. They are not an additional live data provider.
HTTP: https://rpc.mainnet.x1.xyz; WebSocket: wss://rpc.mainnet.x1.xyz
Two refresh schedules
On entry and every ten minutes, full reads obtain Supply, Inflation, governor parameters, vote accounts and the other full snapshot components. A separate one-minute update refreshes performance samples and pool pricing. Live slot notifications have their own cadence.
Last read can advance after that lightweight update without rereading Supply, Inflation or Stake. Confirm a full refresh from those RPC responses, not from Last read alone. Same-epoch inflation and stake can remain numerically unchanged after a successful full read.
Snapshots and freshness
Snapshot components are requested asynchronously; they are not guaranteed to name one identical slot or commitment point. RPC response times and defaults matter. Live slots and a slower full panel can legitimately show different ages.
The page does not backfill a permanent X1 time series. Its chart samples and forecasts must not be described as a complete archived chain history. No chain reads run when these explanation pages load.
Source limitations
Public RPC availability, rounding, sampling, naming metadata and changing pool liquidity can affect the display. A reachable page is not proof that every upstream metric is fresh.
Protocol-year inflation and calendar-year estimates are deliberately distinct. Projections assume current parameters and slot pace continue; they are not official deadlines or validator-specific reward promises.