Overview
How DALP turns EVM events into queryable platform state, where indexed reads can lag on-chain finality, and which monitoring pages operators use during indexing incidents.
DALP data availability is the read-side architecture that turns supported EVM events into queryable platform state. It explains what the platform can show after an on-chain action. It also explains why dashboards and API reads can lag a mined transaction.
This overview is an explanation for buyers, architects, operators, and reviewers. It connects the Chain Indexer, PostgreSQL read models, blockchain monitoring, and observability pages. Use it to decide where to look when on-chain execution and DALP screens appear out of sync.
How the pieces fit together
SMART Protocol contracts remain the source of on-chain execution truth. DALP does not replace EVM finality with an internal database record. Instead, the Chain Indexer observes supported contract events, decodes them with known ABIs, and writes read models that DALP APIs, dashboards, reports, and review screens can query.
Those read models make platform state usable and searchable from the application layer. The consistency model is practical: a transaction can be final on-chain before every DALP read surface has caught up.
What this section covers
| Topic | What it explains | Read it when |
|---|---|---|
| Chain Indexer | How DALP reads EVM logs, processes checkpoints, handles finality and reorgs, and builds read models. | You need the mental model for event indexing or indexed-state freshness. |
| Read-model consistency model | Why an explorer can show a transaction before DALP screens update. | A support or review question depends on whether the indexer has processed the transaction block. |
| Blockchain monitoring | Which operational checks show chain RPC health, block lag, handler errors, backfill state, and reindex progress. | An operator needs to distinguish normal lag from an indexing incident. |
| Observability | How deployment metrics, logs, and traces explain service behaviour around the indexer and related components. | You need infrastructure evidence for why a read surface is stale or recovering. |
| Database | How DALP stores application state and read-side data. | You need the storage-layer context behind indexed read models. |
Reader paths
Buyers usually start with DALP overview for the business capabilities. This section shows how on-chain activity becomes dashboard state, API reads, reports, and operating evidence. Move next to Observability when diligence depends on telemetry for stale or recovering read surfaces.
Architects usually start with Chain Indexer, then move to Contract Runtime to understand how contract calls and event decoding relate.
Operators usually start with Blockchain monitoring when a dashboard or API result looks stale. That page gives the live checks. The Chain Indexer page explains why those checks matter.
Security and audit reviewers usually start with the consistency model. That split separates on-chain execution evidence from indexed application state, custody records, legal records, and off-chain reserve evidence.
What indexed state does not prove
Indexed state shows that DALP has processed supported on-chain events into its read model up to the relevant checkpoint. It does not prove an external reserve balance. It does not replace custody-provider evidence, guarantee an RPC provider's availability, or index arbitrary external contracts by default.
Use this section for platform read visibility and operational freshness. Use custody, reserve, legal, or external-provider evidence pages for records that do not come from DALP's supported EVM event stream.
Next pages
- DALP overview for the buyer-level capability view before architecture detail.
- Chain Indexer for the full indexing explanation.
- Blockchain monitoring for operator checks during lag, downtime, reorg recovery, or reindexing.
- Observability for deployment telemetry that helps explain indexing behaviour.
Supported networks
Reference for DALP network configuration across built-in viem chains, custom EVM-compatible networks, RPC transport settings, finality controls, and monitoring behaviour for test and production environments.
Chain Indexer
The Chain Indexer reads EVM logs, decodes DALP events, and writes queryable read models. It explains how checkpoints, finality, reorg handling, and reindexing affect the state shown by APIs and dashboards.