Exact quantities
Native and token amounts use decimal integer strings. Missing values remain null; unknown is never silently changed to zero.
Historical Balance API / synthetic sandbox
Historical wallet balances belong to a precise UTC cutoff and a supported asset scope. Our developed sandbox contract keeps quantities, block context, source evidence and unknowns together.
In development · no public production endpoint
{
"cutoffUtc": "2025-12-31T22:59:59.000Z",
"amountAtomic": "1000000000000000000",
"quality": "unverified",
"historyComplete": false,
"assetUniverseComplete": false
}This example explains a design principle. It is not a live API response or a stable production schema.
05 / Why this matters
A historical balance must be bound to the selected block and a connected successor across the cutoff. Dataset transactions alone are not an archive-state proof. Missing state, metadata or independent evidence must remain visible.
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 and token amounts use decimal integer strings. Missing values remain null; unknown is never silently changed to zero.
The developed API contract uses tenant- and project-bound jobs, leases, fences and SHA-256 result binding. These properties were tested with synthetic data.
Unverified, partial and unavailable results retain their limitations. Processing completion is not a completeness or tax-approval guarantee.
USE CASES / Built for technical teams
Compare independently evidenced balances at a declared UTC instant.
Keep known asset quantities separate from missing metadata and unsupported state.
Expose a difference for review without automatically changing bookkeeping.
H6 and H6.1 synthetic Historical Balance jobs and CTR read-only comparisons have passed local and two-host tests. Real archive-state acquisition, production coverage and public access remain unapproved. AWS BSC and BigQuery Ethereum acquisition are planned; additional historical-state evidence may still be required.
Read the implementation statusQUESTIONS / Historical Balance API
No public Mainnet endpoint has been released. The available development evidence is synthetic.
No. Read quality, requested asset scope, missing values and coverage flags separately.
No. The tested CTR comparison is read-only and does not automatically write transactions or reports.
Built with a long view
Explore the direction. Early access is not open yet.