Trustless · Permanent

Anchor History

Every day, the platform commits its analyses, builds a Merkle root over them, and pins it to IPFS. This is the permanent record — nothing can be backdated, edited, or quietly dropped without breaking the root.

Verify it yourself

  1. Open the day's IPFS publication (immutable — fetch from any gateway).
  2. For each record, leaf = sha256(0x00 ‖ canonicalJSON); nodes = sha256(0x01 ‖ left ‖ right), duplicate-last on odd levels.
  3. Fold the leaves into a root and compare it to the published root below. They must match.
2026-07-022 recordsFirestore only
root 66b7a48965bbbcd4e7e316e4
2026-07-012 recordsFirestore only
root d6a91dc8813eea08e5245ec1
2026-06-302 recordsFirestore only
root c75bfb5db16663aade606171
2026-06-282 recordsFirestore only
root b6749a1122d6f9505639ae08
2026-06-272 recordsFirestore only
root ee6ed0f9c71ec090bc842e72
2026-06-262 recordsFirestore only
root b3e63f5238858aa38e28b744
2026-06-252 recordsFirestore only
root f16219dc2da3023efa6a0b43

Anchoring proves integrity and ordering of the record — that what is published today existed today and has not changed. It does not, by itself, assert the analyses are correct; correctness is settled separately when reality scores each call. See the Prediction Ledger and Reality Gap.

ⓘ Educational research tool · We do NOT accept funds, manage money, or offer investment returns · Not affiliated with Noosphere Ventures · Open-source · CC-BY-4.0