Data sources and freshness
rangebound builds its numbers from on-chain data first. Market data from outside the chain is used only for what the chain can't provide: listed option prices and the underlying stock's own trading.
Sources
| Data | Source | How often |
|---|---|---|
| Pool price, liquidity in range, fee counters, dynamic-fee state | The pool accounts on Solana | Every 30 seconds |
| Vault balances (TVL) | The pool's token accounts on Solana | Every 10 minutes |
| Liquidity at each tick | Raydium's pool data, checked against the on-chain liquidity at the current price; for Orca, built from the positions in the pool | Every 10 minutes on Raydium, with each position scan on Orca |
| Open positions, ranges, owners, uncollected fees | A scan of every position account in each pool | Hourly |
| Each position's history | The position's own transactions on Solana | When a position is new or has changed |
| Swaps missed during an outage | The pool's transaction history on Solana | Every 10 minutes, for the last 24 hours |
| 24-hour token price change | Jupiter | Every 5 minutes |
| Realised volatility of the underlying | Public market data for the listed stock or ETF | Every 5 minutes |
| Implied volatility and option chains | Public listed-option data for the underlying | Every 30 minutes in US market hours |
| Meme tokens | Launchpad and AMM pools on Solana, and Jupiter token data | See Memes |
| Tracked tokens | A fixed list of issuer mints, checked against issuer lists and on-chain authorities | Updated when issuers list new tokens |
Why fees come from counters, not from swap-by-swap indexing
Each pool keeps running totals of the protocol's share of fees. Because that share is a fixed fraction of every swap fee, the change in the totals between two readings gives the exact fees paid in between, with no swap missed. Volume follows by dividing fees by the fee rate.
This was checked against fully decoded swap histories: volume from counters matched decoded swaps to within a few percent on almost every pool. See Fees, volume and APR.
After an outage
If data collection stops, for example during a restart, the gap in the last 24 hours is rebuilt from the pool's transaction history, one reading per minute. The rebuilt hours match swap-by-swap data to within about 1% on volume. 24-hour figures therefore don't need a day to recover after a restart.
When data is stale
If the latest data is more than 5 minutes old, the app shows a banner saying so. Pages keep working on the last good data and refresh on their own when new data arrives.
Tokens and lookalikes
Only tokens minted by the real issuers are tracked. A token with the same name but a different mint address is listed under Lookalike mints excluded on the Assets page and left out of every figure.