420Indexer.

420Indexer is intended to normalize chain activity into queryable application data for explorers, wallets, analytics and ecosystem services.

indexed data

The public contract will document blocks, transactions, logs, addresses, contracts, token activity and application-specific projections exposed through the indexer.

reorg handling

Consumers should treat indexed data as derived from canonical chain state. Reorganizations must be reflected deterministically, and applications should avoid assuming that an observed event is final before the network's finality policy has been satisfied.

pagination & freshness

Queries should use stable cursors or explicit ordering where provided. Freshness, lag and backfill behavior will be documented so clients can distinguish delayed indexing from missing state.