Pool State & Indexing Guide
What data to index and how to keep simulations accurate
Overview
To simulate swaps or monitor execution availability, integrators must index a minimal set of on-chain state from Bolt Outposts.
This page describes:
Which pool variables matter
How often state should be refreshed
How to reason about inventory availability
Core State to Index
Typical state includes:
Available inventory per asset
Pool thresholds and minimum balances
Fee parameters
Oracle reference identifiers
Exact field names and schemas are chain-specific.
Indexing Strategy
Poll or subscribe to Outpost state updates
Refresh state frequently enough to avoid stale quotes
Treat inventory availability as the primary execution constraint
Execution Availability
Unlike AMMs:
Pool depth does not affect price
Inventory availability determines fill success
Quotes should be rejected if inventory is insufficient
This makes Bolt particularly suitable for deterministic routing.
Last updated