The root 6529 publishes reproduces from the data it serves.
Every day at 01:30 UTC this repository fetches every TDH entry from
api.6529.io, rebuilds the Merkle tree from scratch, and compares the
root it arrives at against the one the API publishes for the same block. One hash
decides. The result of every run is recorded below, pass or fail.
- Block
- —
- Identities in tree
- —
- Entries served
- —
- Consecutive passes
- —
—
The two conditions of conformance
Live check —
The root api.6529.io publishes is recomputed from the entries the
same API serves. A failure means the provider and its own data disagree — or
that the calculation upstream changed.
Golden vectors —
Eight offline cases — seven synthetic tree shapes and one frozen mainnet snapshot at block 25663469 — pinned to known roots. A failure here means this implementation broke itself, not that upstream moved.
Every run recorded
| Date (UTC) | Block | In tree | Root | Live | Vectors |
|---|---|---|---|---|---|
| loading… | |||||
What this does not claim
This checks a provider against itself: that the commitment it publishes describes the numbers it serves. It does not independently verify that 6529's TDH values are correct, because that requires computing TDH from chain data — which this project has specified in full but has not yet implemented.
Until it does, the honest statement is the narrow one: the root is internally consistent, reproducible by a third party, and has been every day recorded here. The specification is what makes the wider claim checkable by anyone, in any language.