Integrations / explicit availability
Source acquisition, the Indexbase engine and customer integrations have different responsibilities. Their current status stays visible.
AWS Public Blockchain Data is the priority for historical BSC acquisition; Google BigQuery is the priority for historical Ethereum acquisition. Both integrations are planned and require separate validation. No AWS or BigQuery production integration has been completed. Access rights, source contents, costs and coverage need separate acceptance.
Sources and consumers
Planned priority for historical BNB Smart Chain acquisition. Dataset evaluation and a bounded adapter are still pending. Transaction datasets alone do not prove archive-state balances or full trace coverage.
Planned priority for historical Ethereum acquisition. Queries, export evidence, source revisions and usage budgets must be validated. A production adapter and complete wallet coverage are not available.
Our own raw engine, blockchain indexers and bounded wallet indexes provide the development foundation. Synthetic indexing is tested; real historical ingestion and durable production backfills remain release work.
First API customer. Signed synthetic requests, Historical Balance results and read-only comparisons have been tested, including a two-host run. Public customer activation and real transaction imports are not released.
Later integration through versioned APIs and project-scoped access. No public onboarding, availability commitment or commercial coverage claim is offered today.
BOUNDARIES / Before integration
Every source needs a declared range, supported data kinds, rights and budget. A normalised response cannot hide missing raw evidence. API customers retain responsibility for their own bookkeeping and decisions.
Read the technical previewBuilt with a long view
Explore the direction. Early access is not open yet.