Ethereum Wallet API / planned API

Ethereum activity.
Without the guesswork.

From a transaction hash to the movements it produced. Our Ethereum-first approach combines raw receipts, supported event decoding and a bounded address index.

Read the technical preview Early-access plans

In development · no public production endpoint

CONTRACT DIRECTIONILLUSTRATIVE

{
  "chain": "ethereum-m1-fixture",
  "valueAtomic": "1000000000000000000",
  "historyComplete": false,
  "synthetic": true
}

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

04 / Why this matters

Receipts tell a different story from intent.

A submitted value is not always a successful transfer. The local Ethereum indexer checks transaction and receipt relationships, retains failed transactions and only normalises successful movements under the supported rules. This distinction matters before any downstream accounting decision.

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

Native ETH movement

Preserve exact atomic values and execution evidence. Failed transactions remain visible without inventing successful value transfers.

ERC-20 event interpretation

Recognise supported Transfer event shapes and retain the contract address. Matching a log format is not a certification of the token contract or its metadata.

Internal movement evidence

Internal ETH movements require actual call traces and supported verification. A trace gap is reported as a gap, not treated as zero internal activity.

USE CASES / Built for technical teams

A better basis for your product.

Wallet builders

Show address-relevant technical activity with a link back to its source.

Treasury tooling

Reconcile native and token movements across a precisely specified range.

Developer research

Inspect transaction, event and raw references together.

API in development

What is available today?

Ethereum M1 and its local API integration are tested with signed synthetic transactions, not a public Mainnet feed. The next planned step is a limited, separately approved test against a self-operated Ethereum node.

Read the implementation status

QUESTIONS / Ethereum Wallet API

Before you build.

Is Ethereum Mainnet access available?

Not yet. Public endpoint access and a production Mainnet coverage commitment have not been released.

Do you infer decimals or token symbols?

No. The raw movement contract can preserve a contract address and atomic amount while metadata remains unknown.

Can I use the preview for production accounting?

No. The current synthetic preview is for understanding the technical direction. Production data, compatibility and accounting behaviour require separate validation.

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

Ethereum activity.Without the guesswork.