indexbase.

Independent infrastructure. Transparent evidence.

On-chain data.
With the evidence
attached.

Blockchain data infrastructure for teams that need to know what happened—and how much of the story they can verify.

Explore the APIs Read the docs

Ethereum-first. Under development. No public API access yet.

ETHEREUM / M1LOCAL PROTOTYPE
01

Original transaction

retained
02

Receipt & event logs

linked
03

Address participation

indexed
HISTORY COVERAGEbounded
historyComplete: false

A verified range is not a lifetime history.

Illustrative view · synthetic data only

One foundation.
A multi-chain direction.

EthereumLocal M1 prototype
BNB Smart ChainPlanned
SolanaPlanned
BitcoinPlanned

01 / The data layer

Different questions.
One traceable foundation.

Four API directions, built around a shared principle: useful data should keep its evidence and its limitations.

01

Wallet History API

Address-level activity with provenance and explicit historical boundaries.

02

DeFi Data API

Reusable decoder families, versioned interpretations and visible unknowns.

03

Blockchain Data API

Raw blocks, transactions, receipts and logs with a clear chain of evidence.

04

Ethereum Wallet API

An Ethereum-first view of native transfers, token events and trace evidence.

Designed for a source you can inspect

From raw evidence
to usable context.

Original data, technical movements and economic interpretation have different jobs. We keep them separate.

  1. 01 / SOURCE

    Capture

    Own-node data acquisition is the target. The prototype currently uses local synthetic fixtures.

  2. 02 / VERIFY

    Preserve

    Keep original bytes, hashes and provenance. Check block and receipt relationships.

  3. 03 / UNDERSTAND

    Interpret

    Normalise technical movement. Add economic meaning only within a tested decoder scope.

  4. 04 / DELIVER

    Make limits visible

    Carry coverage, missing ranges and unknowns into the intended API contract.

02 / A deliberate standard

Confidence starts
with honest boundaries.

[01]

Coverage is part of the data.

A successful response does not automatically mean a complete history. Blocks, receipts, logs and traces need their own coverage evidence.

[02]

Unknowns stay in the picture.

An event we cannot interpret remains a technical record. No silent deletion and no invented token metadata.

[03]

Amounts keep their precision.

Token and native amounts use atomic integer strings. Economic valuation and tax treatment belong to separate layers.

API in development

A working local foundation.
A measured path to production.

The Ethereum M1 raw indexer and its synthetic API integration are locally tested. A self-operated node pilot, broader historical coverage and reusable DeFi decoders are next in the roadmap.

See the current scope

Built with a long view

Help shape the next
layer of blockchain data.

Explore the direction. Early access is not open yet.

Early-access plans