Scopes

Reference · integrity

Externally-timestamped record

Each UTC day, Scopes computes a single cryptographic fingerprint (a Merkle root) over everything appended to the record that day: price snapshots, flagged divergences, reads, model reads, resolutions and corrections. The root is anchored to the Bitcoin blockchain via OpenTimestamps and mirrored to a public GitHub repository. That lets anyone prove a given day’s record existed on that date and has not been altered since, without trusting Scopes.

Method: canonicalization v1 (RFC 6962 Merkle). The exact rules are published in the scopes-integrity repository, which also carries every day’s digest line and its .ots proof.

On anchor timing

Anchoring began on Sep 28, 2026. Days before that were fingerprinted from the existing append-only record and anchored retroactively: their proofs establish existence as of the anchor date, not the record date. From Sep 28, 2026 forward, every day is anchored before the next day begins.

75 days anchored retroactively, 50 same day.

Coverage commitment

The daily root proves the record was not altered. It does not, on its own, prove nothing was quietly dropped. So Scopes also pre-registers what it commits to capture: a canonical, hashed list of every active contract, with its desk and declared cadence. That manifest hash is published ahead of time and bound into the day’s anchored root, so a third party can check that Scopes captured what it said it would, and catch anything committed but silently absent.

Active commitment

In effect since Nov 17, 2026 · method coverage-v1

185 contracts committed

Rates 93Crypto 88Polls 4

manifest 77bdba6af74539ffa3617f049d3c5bd79de3e0f3988108ab0eb8baba52db0496

The full set, in canonical form, is public at /api/coverage-manifests and mirrored to scopes-integrity/manifests. Recompute its sha256 over the canonical form and it equals the hash above.

Reconciliation · 2026-11-16 (UTC)

33 committed contracts were silently absent (committed, no captures, no disclosed gap).

0

Captured

130

Partial, disclosed

11

Fully gapped, disclosed

33

Committed but absent

174 committed · 683 disclosed gap slots on the day.

Silently absent

  • polymarket:0x165a276e862f99ba89b1b5293c95dd8e2cd79b5e0385c1d5e7dd6caf8b980c14 (Crypto)
  • polymarket:0x184cff1575a55bd94ff9acce20b1ee63bb0618c001c6569a0c7bbd5d0612c9ab (Crypto)
  • polymarket:0x1a67429cf86cfdb2fe578da6a36308b72a4737683714e8238a17d05a4c422fa7 (Crypto)
  • polymarket:0x1af9ed30bfec634f080721569c2e97b1434df736ae4599ee7ddf3f62030995d3 (Crypto)
  • polymarket:0x1be7983dfcf7c484577f3b959002feb4d7098e0eda88d205ed8051cdd9b2cb8d (Crypto)
  • polymarket:0x1ec37dfb38075787c68d26a42e03edcf38fb4ece8c9ffa56eb70216f0b1eedb8 (Crypto)
  • polymarket:0x2120bb08e9c9c569090e271614fb0b91c4bb1ed7bc56eb65f1fbadb2b0e04d16 (Crypto)
  • polymarket:0x2747e42d4c4219c3d5c616748c81195dbc9d1e7abb1a99f325fdab8554549b78 (Crypto)
  • polymarket:0x35aa69cee4984f156203a326f3f67d0ea182c64ade88a3d295e67d82d59b37eb (Crypto)
  • polymarket:0x3bd3398782556a1d4ebe5c4ab854a7b292123b8f95ebd272f4ac2027f3f2d42d (Crypto)
  • polymarket:0x426782885a27e4911065979ae3eef02c1d583cea9e45e9c5c5777ae849f30172 (Crypto)
  • polymarket:0x477aa1cb83f3dba987d49c443b516136e3f1a7947ff00217fb49406daa541624 (Crypto)
  • polymarket:0x4ece589e690335d9e4d0a11535ec58773ffcd857357d04c1554d30d37deadca8 (Crypto)
  • polymarket:0x5101f51f5b1d1e2e72153928313081d21da890e6e96575f913945431fe6be8c1 (Crypto)
  • polymarket:0x55a5a17a7c60634d5d46ad3f1189b44fb96fe97f22e0d99053d65bf4787a0c50 (Crypto)
  • polymarket:0x5666adf59e1316dcc8babc1be3de6390e70f798dba4e42debb16274e869264e6 (Crypto)
  • polymarket:0x5918821679cf9660564969a211d043bd40b286808651ea7089da5a97a5242e2d (Crypto)
  • polymarket:0x5acbe71ed2d3c2eae1da4ee30184d9d93d996f7e760b337bbba998b657049820 (Crypto)
  • polymarket:0x815003516d740312e22a4b05fbd573f4a58ff63ef3a472d4540baa7c8e3bd3dd (Crypto)
  • polymarket:0x83f4ea757ee5de433d838b9bf98676edf2805aba3fd548dc15f9c09e2800ccc0 (Crypto)
  • + 13 more

Check any day in the browser: /api/coverage-reconcile?date=YYYY-MM-DD.

The daily digests

125 days recorded, 123 Bitcoin-confirmed. Newest first. Showing 101 to 125 (page 3 of 3).

Date (UTC)Merkle rootRowsTimestampAnchorProof
2026-08-08ad90770cae0c6202d733…125Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-07f74aa756e0149a1a28a7…56Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-06ffff1735ff2af814231e…60Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-055ec1b0fe70652c5f0e0e…72Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-042b8cf4ec3f981987eab6…68Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-032b461d58f848b7c4262b…54Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-02067b9a5d48493e5d73a9…62Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-08-010b86814c82b319f95b63…66Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-314801af3ebb0396b23045…72Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-308031721c92dcbaaa2510…58Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-2980ab1f869e49e4393ffb…68Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-28ec77b5a2266a01ae2e1d…62Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-2753c4d60e6d1442f3df6d…58Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-26d1394f9d93c11af89822…68Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-25ca5a31188c021060a0a7…60Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-24c9b5b996abf63dda2b9b…51Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-23b6524e2be93a5d4690a4…56Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-22bb94f92ed30a12131926…64Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-218581739f4019988b5804…62Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-2065456ff7842bc3c2e5cd…62Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-19d9866fb0c7baa0be743d…64Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-1827ddbd51a9c0e9bb0d53…89Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-174d37fd061c8bd249cd35…50Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-1681f61dcbc116120b6d75…34Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots
2026-07-15fd10324391b4d76de3ff…26Bitcoin-confirmed
Retroactively anchoredAnchored Sep 29, 2026. Proves existence by that date, not the record date.
.ots

The Anchor column marks provenance. “Retroactively anchored” days were fingerprinted from the existing append-only record and timestamped later, so the proof establishes existence as of the anchor date shown, not the record date. “Anchored same day” days were timestamped within the nightly cycle.

How to verify

Four proofs, each runnable on your own machine without using our application or trusting us: recompute a day’s Merkle root (v1, RFC 6962) and match it; re-fold a single row’s inclusion proof; verify the Bitcoin timestamp with ots verify; and check completeness by recomputing the coverage manifest (coverage-v1) and reconciling it against captures.

The full walkthrough, with copy-pasteable commands and real current values, is on a dedicated page.

Verify the record yourself →