A blockchain index, built into the platform

We built a full blockchain index into the platform. The chain now reads like a database: live state, complete history, every event decoded and ready to query.

An EVM node answers one question well: what is true right now. It holds the current state of every account and contract, but it has no memory. Ask who held a security token on 31 March, or show every fee collected since an instrument launched, and a node gives you nothing. Those questions require a separate layer that reads each block as it finalises, decodes the events inside, and stores the result in a form you can actually query.

Building that layer is non-trivial work. You author mappings for each contract. You keep the indexer in step with the chain across upgrades. You handle chain reorganisations (the short branch replacements that happen on every proof-of-work and many proof-of-stake networks) so a correction at the tip of the chain does not silently corrupt your history. Then you reconcile the result against your own records, because an index that drifts is worse than none at all.

In DALP 3.0 that system is the platform. The Ledger Index finds your contracts on-chain on its own, decodes each event as it arrives, and keeps the full history in a form you query directly.

How it stays current

It runs live and historical at the same time. One pass follows each chain head as blocks finalise and backfills complete history behind it, across each network you operate on. Decoding happens on the way in, so what lands in the database is typed business data: not hex-encoded raw logs to parse later, not a raw event schema you reverse-engineer at query time.

Why it matters

For a bank, an asset manager, or a fund administrator, the question is never just "what does the ledger say today?" Quarterly audits want balances at a specific date. Tax filings require a transfer-by-transfer record for each holder. Compliance checks ask whether a given address was on the investor register at the time of a particular transfer. None of those questions have answers without an indexed read model.

Without one, institutions typically choose between three paths: run a third-party indexing service in parallel and reconcile its output against the chain; replay blocks manually at query time; or tell an auditor the data is not available. None is acceptable on a regulated book.

Correctness is the point

An index that can be wrong is worse than no index at all. A wrong number returned with confidence (a balance that excludes a transfer that happened after a reorg, or a fee total that double-counts a corrected block) becomes a finding when an auditor compares it to the chain.

So the guarantee comes first. The Ledger Index stores a hash for every entry in the reorg-detection window. When a chain reorganisation occurs, it walks backwards from the last processed block, comparing stored hashes against canonical hashes from the node. It identifies the fork point, reverses every mutation from that range in exact reverse order, then replays forward from there. The same query against the same block number always returns the same answer. That is what makes a historical balance audit evidence rather than a dashboard reading.

The same determinism guarantee applies across upgrades. When the index changes shape, a new version rebuilds the entire dataset in the background and swaps in atomically.

Fast enough to stand up cold

Speed is held to the same standard as correctness: every optimisation must return byte-for-byte identical results to the naive path. In 3.0, the Ledger Index groups contiguous contracts into shared block scans, batching addresses together so one RPC call covers many contracts in one range. It learns and remembers the block where each network's first relevant event appears, so backfills skip dead ranges instead of scanning them. Finalised history is cached so a restart does not re-fetch what is already known. A fresh environment, or one recovering after an upgrade, becomes queryable in minutes.

A new deployment needs no manual tuning. Safe rollback depths ship pre-configured for Ethereum, Polygon, Arbitrum, and generic L2s, so the Ledger Index knows how far back to look on each chain out of the box. The block range tunes itself to the RPC endpoint it is given.

New in 3.0: indexed for the questions a book gets asked

We widened what the Ledger Index captures well beyond current balances. What is now tracked is the financial detail a servicer, an auditor, or a regulator actually asks for. Each is queryable at any past block.

Read historical balances → · Browse the token-feature APIs →