Only what the chain can support.
After deployment, Cook’s server will index its own factory and staker events from the deployment block. It keeps a persistent public checkpoint and checks its block hash before resuming. Recent blocks are excluded by a confirmation window; a mismatched checkpoint is rebuilt.
Pool token balances, current ticks, active liquidity, LP NFT counts and remaining incentive budgets come from onchain reads. Failed pool reads produce an explicit warning, not a fabricated zero balance. A recent cached snapshot may be served for up to five minutes when the RPC fails and is labeled stale.
Cook reads its own BNB deployment and does not yet provide external price feeds. Dollar prices, historical charts and returns are not manufactured. BNB market data will be shown only when the source and timestamp are available. A dedicated RPC/indexer may be needed for reliable operation at scale.