CHAIN HEAD · EPOCH {{ headEpochFmt }} VERIFIED IN THIS TAB

sha256 chain root · recomputed, not reported · every receipt since genesis chains to this value{{ readingsCommit }}

REF_SPOT · REFERENCE READING

{{ spotBig }} {{ deltaFmt }} last 32 min

ref_spot ref_ewma_fast ref_ewma_slow

WAD strings are the data; this chart is display. Withheld epochs render as gaps, never zeros.

HEARTBEAT · WALL-CLOCK TRUTH

UNBROKEN FOR{{ unbroken }}

NEWEST RECEIPT{{ lastPub }}

NEXT EPOCH{{ nextIn }}

EXPORT | CHECK{{ exportStr }}

LIVE VERIFICATION NEVER STOPS

epoch{{ l.epochFmt }}receipt OKlink OK

ANCHOR CHAIN · EACH EPOCH BOUND TO AN ETHEREUM BLOCK ALL {{ tickAnchors }} ANCHORS →

MATURING next anchor block read at depth
no wallet, no gas

ETHEREUM TIP

BLOCK{{ a.age }} ago

{{ a.block }} epochs {{ a.range }}

{{ a.rootPfx }}…PROVEN

Rewriting this history now means rewriting Ethereum. The only forgeable history is a future one; the accrued past is the moat.

LATEST RECEIPTS · VERIFIED ON ARRIVAL FULL TIMELINE →

EPOCHUTCREF_SPOTROOTSTATUS

{{ r.epochFmt }} {{ r.time }} {{ r.spotFmt }} {{ r.rootPfx }}… {{ r.stText }}

Open any receipt to climb its proof ladder: integrity → continuity → recomputation → anchor → full replay.

READINGS · RECOMPUTED SERIES ALL →

1e18 WAD · content-addressed program

Each series is re-derived in this tab by the reference implementation, state threaded from genesis. Nothing here is quoted from anyone.

DAILY SEGMENTS · A DAY IS IMMUTABLE ONCE COMPLETE

UTC DAYEPOCHSRECORDSSEGMENT SHA256LOADEDX-RAY

{{ d.date }}{{ d.range }}{{ d.records }}{{ d.sha }}…{{ d.loaded }}{{ d.bytes }}

a day is immutable once complete; today's partial re-shards each export and its predecessor is pruned (the manifest chain records every state).

{{ rf.id }}latest {{ rf.latest }} · WAD strings are the data, this chart is display

withheld epochs render as gaps, never zeros.

{{ receiptsTotal }}RECEIPTS RECORDED

{{ tickAnchors }}ANCHORS BOUND

{{ tickAnchorsMined }}ETH-BOUND

{{ genesisDate }}UNBROKEN SINCE

{{ receiptsTotal }}REPLAYED IN THIS TAB

{{ tickSegments }}DAILY SEGMENTS

Deliberately absent

visitor counts, country maps, "verified by N people," mirror totals without signed attestations. This site has no analytics and therefore cannot know those numbers; every figure above is derivable from public artifacts, and several impressive-sounding statistics are absent rather than invented. Mirror and verifier attestations render here when the standing ledger publishes them; until then this section stays quiet on purpose.

ANCHORSEVIDENCE

EPOCHROOTCALENDARSETH BLOCKPROOF

{{ ar.epoch }}{{ ar.root }}…{{ ar.cal }}{{ ar.btc }}{{ ar.proof }}

ETHEREUM BLOCK BINDINGSEVIDENCE

ETHEREUM BLOCKBINDS ROOT OF EPOCHTIMESTAMP (UTC)ROOT

{{ br.block }}{{ br.epoch }} {{ br.gen }}{{ br.ts }}{{ br.root }}…

block-header confirmation is the CLI path (anchor-verify); any explorer link would be informative only, and none is required.

NIGHTLY FULL REPLAYPUBLISHER ATTESTATION, INFORMATIVE

the operator's machine re-derives the entire history every night; a red line here is the system catching itself. Independent proof is the same command on your machine: node verify.mjs config.json

RUN (UTC)VERDICTRECORDSHEAD EPOCHROOTTOOK

{{ rr.run }}OK{{ rr.records }}{{ rr.head }}{{ rr.root }}…{{ rr.took }}

VERIFICATION LEDGEREVIDENCE

one dated line per audit run on the recorder host; the frontier only ever moves forward:

{{ p.id }}v1.0.0 · CONTENT-ADDRESSED

{{ p.json }}

the file bytes are exactly the hashed preimage; verification is byte equality, and the dependency walk (program to reading to parameters) grows with the catalog.

WHAT THIS CHAIN IS FOR

The record this instrument replays is the pre-launch history of a blockchain whose subject is measurement. The protocol below is written and tested. It is not deployed, and no token exists yet. Nothing is for sale.

INDX-Q · THE WORK INSTRUMENT

One INDX-Q is one service quantum, a standardized amount of verified network service. Every price the network charges is quoted in quanta and settles at par, so what a quantum buys is set by the definition. The mechanism reads the token's market price nowhere. No collateral, no custody, no rebase.

INDX-G · THE GOVERNANCE INSTRUMENT

Earned as a fixed drizzle alongside work emission. Locking it gives voting weight and casting a vote burns some of it, so governing is a recurring commitment. An actor whose standing clears the worker threshold burns at half rate.

FOUR ROUTES FROM WORK TO POWER

VERIFY

Recompute sampled reading-epochs under commit-reveal. The public are the recomputers.

MIRROR

Serve segments, packages, and anchor proofs, proven by content hash against the pinned archive.

CHALLENGE

Catch a real divergence through the bonded lane. One machine, one caught fault, large standing.

AUTHOR

Contribute reading packages, adapters, and conformance work.

Units come into existence one way: work-metered minting into the key that performed the receipted service. No presale, no allocation, no faucet, no treasury, no premine. The one genesis mint is a stated founder reserve to a stated address.

TWO HOUSES, TWO VETOES

The consortium house is recognition-gated, one member one vote, and capital buys no seat in it. Running a conformant implementation qualifies, and sustained verification service is itself a recognition path, so the public holds agenda power. The INDX-G house weights votes by the square root of locked INDX-G per identity, aggregated under one nullifier before the root is taken: splitting a position across k keys would otherwise multiply weight by the square root of k and restore plain capital voting.

Either house vetoes at a 34% basis. The stake veto runs on locked INDX-G, the standing veto on earned capital-free standing, so the working public can block a capital-driven action from genesis. A passed veto is terminal.

OUTSIDE EVERY GOVERNANCE TRACK

The unit definition freezes at activation: the index formula, its components and weights and windows, the recalibration rule, the minting ratio, the emission cap, and the split formula. Repairing a demonstrated defect requires a published failing vector, two-thirds in both houses, both vetoes live, and a constitutional timelock, and it never touches a settled period or a balance. Governance may never declare a reading canonical or correct, and no key anywhere reaches emission, the split, or the definition.

every 60th link of {{ receiptsTotal }}; a break would render red here, and the replay says: UNBROKEN

EPOCHPREVROOT → ROOTLINK

{{ ro.epoch }}{{ ro.link }}OK

no match in the loaded prefix

FIELDA → BDELTA

TIME MACHINEMANIFEST CHAIN

Walks prevManifestHash backwards (served mode) and renders the head as it was: no future exists in that view. Complete past days resolve exactly; a then-current partial segment may have been pruned and says so.

PRESS RELEASESEVERY CLAIM IS A MERKLE LEAF

RELEASECLAIMSROOTANCHOREDCREATED (UTC)OPENFILE

{{ pr.title }}{{ pr.claims }}{{ pr.root }}…YES{{ pr.created }}OPEN →↓ FILE

a claim is either evidence-backed or it is not published; there is no confidence field anywhere in this system.

Things we cannot fake

Ethereum timestampseach root cites a settled block by hash, so a record cannot predate the block it names; the calendar leg proves the other directionproof

Historical rootseach chains to the last; one changed byte anywhere breaks every root after itproof

Receipt hashesrecomputed in your tab from the logged bodiesproof

Program identitycontent-addressed; the file bytes are the hashed preimageproof

The outputsre-derived by the reference implementation running in this pageproof

What could be faked without anchoring, and why it cannot be now

A publisher can fabricate an internally consistent history at any time; that is level 1 and 2's honest residual. What it cannot do is fabricate one that existed in the past: the Ethereum anchors pin each root to a block time, so the only forgeable history is a future one, and the accrued past is the moat. The observation caveat remains and is stated rather than hidden: a timestamp proves when, recomputation proves what follows from the logged inputs, and re-observation (archive access) closes the last gap.