Only what the chain can support.
Kitchen’s server indexes 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 12-block 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.
There is no Delta data feed in the Kitchen workspace. Dollar prices, historic charts and returns are not manufactured. The current deployment uses the network’s rate-limited public RPC; dedicated archive infrastructure is needed for reliable operation at scale. A configured KITCHEN_RPC_URL can replace the server transport without changing any signing addresses.