Skip to content
Transparency

Daily measurement roots

Every UTC day we hash 5 classes of measurement into one SHA-256 Merkle root and anchor it in Bitcoin. With the same source rows you can recompute it, so "agent X was grade B on 2026-05-19" can be checked, not just asserted. Algorithm

Published roots · last 30 days

Date Merkle root Agents Snaps Probes Revenue rows Bitcoin anchor
2026-11-20 8ccccf087c324ef5f6b7b878… 9,145 983 17,730 21,556 Pending · awaiting Bitcoin .ots proof
2026-11-19 ddd17f8beaf2073de13c45ee… 8,964 852 18,743 21,197 Anchored in Bitcoin block 976658 2026-11-20 .ots proof
2026-11-18 fe4cec8e7f8735c48d625ac6… 9,136 1,247 16,632 20,802 Anchored in Bitcoin block 976507 2026-11-19 .ots proof
2026-11-17 be9cc5f9fe996e2991f7f2ca… 6,841 524 4,841 20,290 Anchored in Bitcoin block 976350 2026-11-18 .ots proof
2026-11-16 a737a9abc4524c04033e2180… 7,073 497 5,577 20,025 Anchored in Bitcoin block 976202 2026-11-17 .ots proof
2026-11-15 5ca5d418dc4ac6a0d7a783ac… 6,862 556 4,979 19,861 Anchored in Bitcoin block 976042 2026-11-16 .ots proof
2026-11-14 1d0babdd09702073fdecacd3… 6,905 450 4,888 19,650 Anchored in Bitcoin block 975873 2026-11-15 .ots proof
2026-11-13 dda2efc0d11e9eca2e479b46… 6,926 677 4,757 19,465 Anchored in Bitcoin block 975734 2026-11-14 .ots proof
2026-11-12 e5f23e93c3c0c96c18008983… 6,647 579 4,914 19,283 Anchored in Bitcoin block 975619 2026-11-13 .ots proof
2026-11-11 dd35f9a57b4aaaf324244b80… 6,940 475 4,937 19,176 Anchored in Bitcoin block 975504 2026-11-12 .ots proof
2026-11-10 de0b639612160c10bc29c54b… 7,725 631 6,679 19,031 Anchored in Bitcoin block 975362 2026-11-11 .ots proof
2026-11-09 5bb6a2130a0d7e7965cabf5e… 7,250 479 5,569 18,882 Anchored in Bitcoin block 975235 2026-11-10 .ots proof
2026-11-08 bd49ad39f597f3ae634b3cb8… 4,623 462 5,492 18,735 Anchored in Bitcoin block 975121 2026-11-09 .ots proof
2026-11-07 8b7fc28b236fd978877e0755… 7,163 460 5,218 18,648 Anchored in Bitcoin block 975020 2026-11-08 .ots proof
2026-11-06 966e205a46205510bd9ba40b… 7,190 482 5,082 18,565 Anchored in Bitcoin block 974880 2026-11-07 .ots proof
2026-11-05 5c75c16a332314d97b61a64a… 8,787 732 16,414 18,491 Anchored in Bitcoin block 974743 2026-11-06 .ots proof
2026-11-04 d1bac308d17371ecc4e3b854… 8,834 851 17,241 18,407 Anchored in Bitcoin block 974606 2026-11-05 .ots proof
2026-11-03 d091760cdec361eae6428f1f… 8,779 867 23,475 18,250 Anchored in Bitcoin block 974460 2026-11-04 .ots proof
2026-11-02 38adcc116d7a7cf068fb9fa9… 7,982 1,329 17,169 17,974 Anchored in Bitcoin block 974324 2026-11-03 .ots proof
2026-11-01 02df84f55b51895bd35734d7… 8,257 648 16,732 17,661 Anchored in Bitcoin block 974200 2026-11-02 .ots proof
2026-10-31 0ce393285aed0077cc68f0e6… 8,336 821 22,547 17,539 Anchored in Bitcoin block 974045 2026-11-01 .ots proof
2026-10-30 5cc6cbce67d22fb05d2ba7dd… 8,511 913 22,809 17,357 Anchored in Bitcoin block 973898 2026-10-31 .ots proof
2026-10-29 a8a64d59e7d1b69d3d18f910… 5,621 1,173 23,478 16,671 Anchored in Bitcoin block 973759 2026-10-30 .ots proof
2026-10-28 8f4ed3ec09ac5dfadb46c882… 8,147 877 21,462 16,207 Anchored in Bitcoin block 973617 2026-10-29 .ots proof
2026-10-27 1f1ea7af0bf869f95a5218fa… 7,995 795 23,605 16,021 Anchored in Bitcoin block 973476 2026-10-28 .ots proof
2026-10-26 4954c43f5bcc932edbe13250… 7,696 743 18,921 15,729 Anchored in Bitcoin block 973320 2026-10-27 .ots proof
2026-10-25 85e0f1e12dd4e7e9a439c8a0… 7,997 568 18,271 15,364 Anchored in Bitcoin block 973152 2026-10-26 .ots proof
2026-10-24 eecbd2e496106244065e64ca… 7,910 864 16,080 15,017 Anchored in Bitcoin block 972999 2026-10-25 .ots proof
2026-10-23 536fc65d6e6223d8ac9b93ad… 7,651 744 13,979 14,186 Anchored in Bitcoin block 972852 2026-10-24 .ots proof
2026-10-22 8d88a2a6a945bece4eca53d6… 7,933 755 13,152 14,088 Anchored in Bitcoin block 972678 2026-10-23 .ots proof

Verify it yourself

  • Latest root: /api/transparency/daily-root.json
  • Any date: /api/transparency/<date>.json (YYYY-MM-DD)
  • Recompute: pull the source rows from /api/feed/all.jsonl.gz, run the algorithm, compare.
  • Check an anchor: download a day's .ots proof above, then pip install opentimestamps-client and run ots verify -d <merkle_root> agenstry-root-YYYY-MM-DD.ots with that day's full 64-character root. It checks against a Bitcoin node, so you rely on neither us nor the calendars. Complete a pending proof first with ots upgrade.

Algorithm

This is the specification. The repository is private. Today's version is 3; every date is replayed under the version it was built with, reported by /api/transparency/<date>.json.

The six steps
  1. For each UTC day, collect rows from 5 append-only sources: agent_day_states (an immutable end-of-day capture of each agent's graded columns; v1 and v2 dates read the live agents table instead), agent_card_snapshots (every card change), probe_runs (every probe), agent_revenue_snapshots (every per-window revenue settlement), agent_passports (every passport issued that day).
  2. Hash each row into a 32-byte leaf: SHA-256 over a NUL-separated, domain-prefixed serialisation of its key columns. The prefix (agent\0…, snapshot\0…, …) prevents cross-table collision.
  3. Compute a Merkle root per sub-tree using the RFC-6962 odd-leaf-carry variant (no duplication, which avoids the second-preimage attack on classic Merkle).
  4. Prefix each sub-root with its label and a colon, sha256(label + ":" + sub_root_hex), then Merkle-fold those 5 hashes in the fixed order agents → snaps → probes → revenue → passports for the top-level root. The order is append-only: a new tree kind goes on the end under a new version number.
  5. Persist the root, row counts, computed_at and root_version in transparency_roots. The row is never updated; a mismatch on recompute is a flag, not a silent fix.
  6. Anchor the root's 32 bytes (not a hash of its hex) in Bitcoin with OpenTimestamps, via several public calendars, so even an attacker with write access to our database cannot rewrite a published day. A day reads pending until its proof carries a Bitcoin block attestation, and anchored in Bitcoin block N only after that attestation is checked against the block header. A timestamp proves the root existed no later than that block. Roots computed before anchoring began were stamped later, so their block date is the day we stamped them.