Skip to documentationIndexer & data integrity
Event discovery, reorgs, finalized observations and the line between a read and a proof.
On this page
Discover relationships from canonical events
The indexer registers governance/settings, factories, approved hooks and routing/reward contracts. It discovers tokens, pools, vaults and routes from events, preserving their original hook/version association. Launched and migration Opened events contribute to the same market directory with a distinct kind.
It records swaps and tax parts, recentering, floor operations, collections, yield changes, governance actions, route outcomes, reward commitments, payments and credits. Internal floor-price lifecycle moves are not user trades and must not inflate trading volume.
Observation and finality
| Concept | Interpretation |
|---|---|
| Chain head | Latest observed chain state. |
| Indexed block | Highest processed block represented by the indexer’s state. |
| Indexer lag | Distance between chain observation and indexed progress. |
| Finalized block | Chain finality boundary used to mark confirmed records. |
| API observation | Block at which direct state fields were read. |
HTTP 200 is availability evidence, not proof of zero lag or correct accounting. A UI can show indexed history and fresh direct state from different blocks; preserve those observation labels instead of implying all fields share an independent finality guarantee.
Reorg and authority reconciliation
Event replay and restarts must reconstruct the same canonical state after a reorganization. Derived accounting is checked against lens and contract reads. Safe replacement invalidates the replaced role’s unexecuted migration approvals through its recorded role epoch; openings approved by unchanged Safe roles stay intact.
Metadata failures leave unavailable optional legacy fields empty. They should not erase an otherwise valid market or stall unrelated indexer progress. Data-provider token discovery remains a discovery aid; balances and source identity are checked independently.
History used for rewards
Reward reconstruction needs the complete relevant holder interval, including preexisting holders for migrated tokens. Market-owned backing look-through uses version-specific events and reconciled boundary state. Archive reads provide source state that cannot be inferred from a partial event range.