Wallet History API / planned API

A wallet history you can trace back.

Build around what a wallet did—and the evidence behind it. We are developing a wallet history API that keeps source transactions, technical movements and coverage together.

Read the technical preview Early-access plans

In development · no public production endpoint

CONTRACT DIRECTIONILLUSTRATIVE

{
  "address": "illustrative-wallet",
  "range": {
    "fromBlock": "1",
    "toBlock": "3"
  },
  "historyComplete": false,
  "amountAtomic": "1000000000000000000"
}

This example explains a design principle. It is not a live API response or a stable production schema.

01 / Why this matters

What does a complete history actually mean?

An empty response cannot tell you whether a wallet was inactive or a data source missed a block. Indexbase is being designed to report the range it examined and the data kinds it could verify. A complete result for three blocks is still only a three-block history.

Source evidence and interpretation should travel together. A downstream product must be able to distinguish observed data, a supported interpretation and an unresolved question.

The intended contract

Address participation

Find transaction senders, recipients and participants identified in supported event formats. Unknown event topics are retained, not guessed into wallet activity.

Exact movement amounts

Keep native and token movements in atomic integer strings. Missing token symbols or decimals remain unknown instead of being substituted with invented metadata.

Repeatable imports

Stable technical identities and resumable checkpoints support re-reading a bounded range without multiplying the same movements.

USE CASES / Built for technical teams

A better basis for your product.

Portfolio tools

Explain the source of a movement before presenting it as portfolio activity.

Reconciliation

Compare known addresses and time ranges while keeping gaps visible.

Research

Work with an address index that can be checked against the original transaction.

API in development

What is available today?

The local Ethereum M1 prototype can query addresses across signed synthetic test blocks. It does not establish complete real-world wallet histories. Incoming movements outside recognised event formats and historical trace availability remain separate coverage questions.

Read the implementation status

QUESTIONS / Wallet History API

Before you build.

Can I request a full wallet history today?

No. There is no public production endpoint yet. Current validation uses bounded synthetic datasets.

Will a successful import mean the history is complete?

No. Consumers must inspect the requested range, missing intervals and per-data-kind coverage, independently of the job status.

Does this calculate taxes?

No. Technical movements are separate from economic classification and the tax rules of any consuming application.

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