Show the method.
Keep the limits visible.
One immutable block
The first successful capture pins Blast chain 81457, block number, hash and UTC timestamp from the official RPC's finalized tag. Later runs check that same block; they do not silently advance it. Another block requires a separately versioned dataset.
Logs and state, independently cross-checked
Reconstruct standard ERC-20 Transfer logs from the verified creation block through the pin. Integer atoms account for mint, burn and transfer events; zero-address and zero-balance entries are excluded. Sorted event identity deduplicates exact repeats and rejects conflicts. Checkpointed bounded block ranges are compared with their split ranges to detect gaps and inconsistent/truncated responses; provider errors never become empty results.
Reconstructed supply must equal historical totalSupply. Every positive balance is checked against archive balanceOf, and selected historical blocks are replayed. Deployment receipts, archive bytecode and independently indexed runtime must agree. A separate historical indexer checks the block hash and representative exact-block balances, including an early zero-state control.
Escrow is underlying custody, not extra supply
The historical escrow uses address-based locks rather than NFT positions. Deposit and withdrawal events enumerate lock controllers; all nonzero underlying locked(address) amounts are checked against archive state, while closed positions are replayed with deterministic zero-state samples; totals are reconciled with escrow supply and the escrow's THRUST balance. Expired but unwithdrawn amounts remain distinguished from unexpired locks. Contract controllers may represent many people: those beneficial owners remain unknown unless separately proved.
Classification and coverage
Historical eth_getCode distinguishes deployed runtime code from no runtime code at the block. “No runtime code” is EOA-like, not proof of a private key, a human or permanent account type. Custody, exchange, treasury and bridge labels require additional evidence; absent that evidence addresses remain unknown. Direct holdings outside the escrow can still be held in other custody contracts and are not guaranteed freely transferable liquidity.
Assurance limits
RPC/indexer reconciliation is not a cryptographic state proof, a safety audit or a guarantee that providers operate independent upstream infrastructure. A consistent malicious provider could hide facts. Range comparisons and balance checks improve error detection without eliminating provider trust. No current explorer holder pagination is used to reconstruct historical ownership.
Reproduce
Use the versioned manifest, source evidence, raw compressed logs, range ledger and SHA256SUMS. The repository provides a Python standard-library pipeline and an offline replay verifier. Reruns with a new cache requery the pinned archive block; existing artifacts are never overwritten with changed bytes. No paid API, wallet, signature or blockchain write is needed.
Dust means a strictly positive balance below 1 THRUST. Concentration is calculated over token units held by addresses, including custody/escrow contracts—not unique people or an allocation recommendation.