Markets and status
Three tokens are monitored. None is open for series yet. Here is what that means and what has to change.
The markets
| Market | Reference price | Market price |
|---|---|---|
| JitoSOL | Jito stake pool state | Raydium JitoSOL/WSOL concentrated pools |
| mSOL | Marinade state | Raydium mSOL/WSOL concentrated pools |
| hSOL | Sanctum stake pool state | Raydium hSOL/WSOL concentrated pools |
Each market is pinned by mint address and issuer state, not by symbol. All three have nine decimals. Price collection is mainnet only, whatever cluster a program is deployed to.
Status words
| Status | Meaning |
|---|---|
| UNAVAILABLE | No fresh qualified interval and no usable current price. Nothing is shown in its place. |
| STALE | No fresh qualified interval; the last current price is older than ten minutes. |
| MONITOR ONLY | A fresh current price exists but no five-minute window has passed the policy. Cannot open a series. |
| SETTLEMENT ELIGIBLE | A fresh qualified interval exists. Reporters and the series policy hash are still required on chain. |
Why nothing is listed
A market opens for series only when its price can be measured the way the contract promises. A census of Raydium pools on 2026-09-20 found candidate pairs for JitoSOL and mSOL, and a single viable pool for hSOL:
| Market | Pools indexed | With active liquidity | Result |
|---|---|---|---|
| JitoSOL | 16 | 4 | Candidate pair; secondary pool is shallow |
| mSOL | 13 | 4 | Candidate pair; secondary pool is shallow |
| hSOL | 4 | 1 | One viable pool; the policy requires two |
A five-minute replay the same day showed the sampling path works: four of five candidate pools produced a full window with gaps under 30 seconds, and one JitoSOL pool was rejected for two 31-second gaps. A working feed is still not an approved market.
What has to happen first
- Two approved pools per marketSustained coverage across epochs and stressed periods, with the cost of moving each pool's five-minute average measured against the series' maximum exposure.
- Independent reportersThree operators with their own keys, infrastructure and RPC access, and a published policy file whose hash goes into every series.
- A reviewed, deployed programIndependent review of the program and the price pipeline, a real program id, and disclosed upgrade-authority custody.
- Disclosed missing-data ruleMeasured outage frequency and an explicit decision that the zero-accrual skip is acceptable to BREAK buyers.
Until then the site and app show real monitoring data and nothing else. The full engineering record is in the repository's docs; the API exposes the same status flags to anyone building on it.