Know the contract.
Know its limits.

01 / CURRENT STATUS

Local validation. No public Mainnet service.

The Ethereum M1 raw indexer and an authenticated local API integration have been implemented and tested with signed synthetic fixtures. The public API is not available. A real Ethereum node pilot has not been completed.

02 / DATA MODEL

Three layers, different responsibilities.

Raw evidence

Original RPC response bytes, their digest, retrieval time and source reference are preserved. A raw-byte digest identifies the archived response; it is not interchangeable with an Ethereum block hash.

Technical movements

Supported native and token movements retain chain, transaction and event references. Unknown events remain accessible. Re-reading data must preserve technical identities.

Economic interpretation

Future decoders will add meanings such as swaps, deposits or borrowing within declared deployment and version boundaries. These interpretations must not silently replace original movements or create duplicate economic attribution. Tax treatment remains a separate responsibility of the consuming product.

03 / COMPLETENESS

A completed job is not a complete wallet history.

Coverage is tracked separately for blocks, transactions, receipts, logs and traces. Read the requested range, missing intervals and finality context before deciding whether a dataset suits a use case.

{
  "chain": "ethereum-m1-fixture",
  "synthetic": true,
  "range": {
    "fromBlock": "1",
    "toBlock": "3"
  },
  "historyComplete": false,
  "finality": "not_applicable_synthetic",
  "dataKinds": {
    "receipts": {
      "status": "complete"
    },
    "traces": {
      "status": "partial"
    }
  }
}

Illustrative subset of the local coverage contract. A complete receipt range can coexist with incomplete traces.

An empty wallet result is not evidence of a lifetime without activity. Reorganisations, unavailable receipts and finality conflicts must be handled explicitly. Current validation is not a claim of full EVM or consensus re-execution.

04 / PRECISION

Atomic amounts. No guessed metadata.

Amounts are decimal integer strings in atomic units. They must not be parsed as floating-point numbers. For example, "1000000000000000000" remains a string through transport and storage.

A token quantity is not a USD valuation. Token identity starts with its chain and contract; unknown symbols or decimals remain unknown. Matching a Transfer log format does not by itself verify every property of a token contract.

05 / ACCESS

Technical preview, not public endpoint documentation.

The existing local integration uses versioned REST paths and tenant-scoped jobs, raw references and wallet queries. That local contract is evidence for development, not a published commercial API or an invitation to connect to a production host.

No public registration, billing or API-key issuance is enabled. There is no public API base URL, production authentication guide or availability commitment yet. Future access terms, rate limits and supported capabilities will be documented before access is offered.

06 / WHAT COMES NEXT

Prove a bounded range. Then expand.

1. Local foundationImplemented: synthetic Ethereum indexing, coverage and API isolation tests.
2. Own-node pilotPlanned: a limited set of real Ethereum blocks, independently checked and measured.
3. Historical coveragePlanned: explicit backfill ranges, retention and durable address search.
4. Decoder families and more chainsPlanned: economic interpretation and chain-specific validation for further networks.

These are implementation directions, not promised release dates.