Bitcoin Research Snapshot Difference Explorer

Field-level comparison of parameters, results, data versions and methodology across two immutable snapshots

What is the Bitcoin Research Snapshot Difference Explorer?

The difference explorer flattens two immutable research payloads into field paths and marks added, removed and changed parameters or results.

How do I use the Bitcoin Research Snapshot Difference Explorer?

Compare data version, methodology, capital and costs before performance fields so input changes are not mistaken for strategy improvement.

What should I watch out for?

Large arrays create many element-level differences; use the CSV for full audit because the page shows only the first 500 filtered rows.

How the Bitcoin Research Snapshot Difference Explorer works

Load two immutable research snapshots, flatten their payloads into field paths and flag every field that was added, removed or changed. Use it to see exactly which parameters, data or results differ between two backtests or studies.

What you enter

  • Left snapshot: bir_ ID or link
  • Right snapshot: a different bir_ ID or link
  • Optional field-path filter, such as settings or summary

What it shows

  • Header per snapshot: title, ID, data version and methodology version
  • Counts of total, changed, added and removed fields
  • Table of path, status, left and right values (first 500 filtered rows)
  • Full diff CSV (path, status, left, right, left_type, right_type) and a link to the verifier

How to use it

  1. Paste the two IDs or links.
  2. Click Compare snapshots.
  3. Check both versions in the headers first.
  4. Filter by settings, then summary, and export the CSV for a full audit.

Formula

Each payload is flattened to leaf paths such as settings.feeBps or cells[3].finalValue (keys sorted, up to 50,000 leaves). Added = only on the right; removed = only on the left; changed = on both sides with a different value or type. Identical paths are omitted.

Worked example

Left has settings.buyPercentile 25 and summary.finalValue 52,000; right has 20 and 49,500; feeBps is 10 in both. The table lists 2 changed rows and omits feeBps. The difference, 49,500 − 52,000 = −2,500, is yours to compute.

How to read the result

  • Different data or methodology versions may explain result changes on their own.
  • Read summary changes only when capital, contributions and costs in settings match.
  • Many added or removed array rows usually mean series of different lengths.

Limits and cautions

  • Only 500 filtered rows display; the CSV has everything.
  • A numeric difference is not automatically an improvement.
  • Payloads over 50,000 leaves are truncated and flagged with a $truncated row.

Common questions

Why so many rows?

Every array element is its own path; filter by settings or summary.

Can I compare a snapshot with itself?

No, two different valid IDs are required.

Does comparing change anything?

No. It only reads two immutable public records.

🌡 Latest BTC cycle reading: 40/100 · Neutral Zone (as of 2026-11-05). BTC Cycle Thermometer: Bitcoin top or bottom?

Free to use with no signup. Read Bitcoin valuation, cycle, backtests and alerts, and calculate fees, slippage, funding and post-rebate cost before trading.