← Back to BUD Signal BUD Signal · Proof
Publicly verifiable · Sealed to Bitcoin

Don't trust our backtest. Verify it against Bitcoin.

We replayed the exact production signal engine across three years of Bitcoin history — October 2023 to July 2026. The resulting data and supporting files were then sealed into Bitcoin, creating a public record that cannot be quietly rewritten after the fact.

Explore the verified results How verification works
Historical replay · 6,040 four-hour candles · 288 simulated windows
Informational only — not financial advice.
Historical replay Simulated · Not live performance
84%
of windows reached at least +0.5% in the signal's direction at their best point
67%
reached +1% or more
46%
reached +2% or more
+2.5%
average best move
+1.8%
typical best move
Both tails, sealed: ~1 in 8 windows ran +5% or more · ~1 in 9 drew down 5%+ before resolving · typical worst drawdown ~1.8%. Best move = the window's best point (maximum favourable excursion), not a captured return — exits are your own.
✓ Proof anchored to Bitcoin block 957,882
Simulated · historical replay — not live performance
3 years
tested
6,040
four-hour candles
288
simulated windows
957,882
Bitcoin block

Two records. Never blended.

The historical replay and the live public record answer different questions. They are published separately and are never combined into one performance figure.

Simulated

Historical replay

The production signal engine replayed across three years of historical Bitcoin data — 6,040 four-hour candles, 288 simulated windows. A simulation of our logic over history, labelled as such.

View historical methodology →
Live since launch

Live signal record

Every signal issued after launch belongs to a separate public record and is never mixed with the simulation. Each one is written to a hash-chained ledger and submitted for Bitcoin anchoring the moment it fires (confirmed on-chain within hours) — stamped to the exact engine version that produced it (engine v1 · block 957,863).

Compare the two for yourself — the live record is published in full.

View the live record →

How the proof becomes tamper-evident

If we ever improve the engine, the new version starts its own sealed record and the old one stays frozen and dated. Nothing can be revised or backdated.

01

Generate

The production engine creates the historical results and supporting files.

02

Fingerprint

Each published file receives a unique cryptographic fingerprint.

03

Anchor to Bitcoin

Those fingerprints are committed to a Bitcoin block. Change even one byte and the verification no longer matches.

Inspect the public proof

Review the published results, supporting files, and the fingerprints anchored to Bitcoin.

Historical results CLAIM.txt

The sealed statement of the three-year replay and its headline outcomes.

SHA-256 b04bb7e8f9a94ffa045f8bcc3af234b7d51ffa03e4c064b67dd8ab243a197c27
✓ VERIFIED · BLOCK 957,882
Inspect results Bitcoin seal (.ots)

Outcome dataset outcomes-summary.json

The window-by-window outcome distribution behind the headline numbers.

SHA-256 fa677a4a27e7de53a56881db4632d56d31ee52bdc06c513f78764c0f4d3c2bfa
✓ VERIFIED · BLOCK 957,882
Inspect data

Public proof manifest PUBLIC-MANIFEST.sha256

The tamper-evident fingerprints for every file included in the public proof.

SHA-256 6a6e547a72785e799759ec2d2d94386b5b2b6c16754a2932dbdaaead11d9b964
✓ VERIFIED · BLOCK 957,882
Inspect manifest Bitcoin seal (.ots)

Methodology & scope PROOF.md

Plain-English explanation of what the proof covers — and what it doesn't.

SHA-256 446adf8f61cc7c615f236d808ca456cd85c84de0d35ace57478f7ed10986d91a
✓ VERIFIED · BLOCK 957,882
Read methodology

Engine fingerprint engine-fingerprint-v1.txt

The production engine's cryptographic fingerprint, anchored to Bitcoin before the results seal (block 957,863 vs 957,882). Engine source stays private — full reproduction is open to a third-party auditor under NDA.

SHA-256 c28d665d65cab972dcf164caa8bc6d7e421041ee91bfdf18f4f643b9bd3c56fb
✓ VERIFIED · BLOCK 957,863
Inspect fingerprint Bitcoin seal (.ots)

Verify it yourself — no trust required

Three commands, free open-source tools, no account needed.

1
Install the free open-source checker.
pip3 install opentimestamps-client
2
Confirm the Bitcoin anchor.
ots upgrade CLAIM.txt.ots && ots verify CLAIM.txt.ots
3
Confirm nothing was altered since the seal.
shasum -a 256 -c PUBLIC-MANIFEST.sha256
→ expect CLAIM.txt: OK · PROOF.md: OK · outcomes-summary.json: OK
# the Bitcoin receipt inside CLAIM.txt.ots
File sha256: b04bb7e8f9a94ffa045f8bcc3af234b7d51ffa03e4c064b67dd8ab243a197c27
verify BitcoinBlockHeaderAttestation(957882)
# Bitcoin block merkle root 02688839321a53f14ee2663a63ca3cadf9e394a342d3c0f66b272c4c745a2ffa

No terminal? Drag CLAIM.txt and CLAIM.txt.ots onto the verifier at opentimestamps.org — it reads the same receipt in your browser and confirms the Bitcoin block.

The proof does not depend on trusting BUD Signal.

Download the files, recreate their fingerprints, and compare them with the values anchored to Bitcoin.

Verify the proof Return to BUD Signal

✓ What this proves

  • The results existed in this exact form on the seal date — unaltered since.
  • The engine fingerprint was sealed to Bitcoin before the results were published (block 957,863 vs 957,882).
  • The sealed files are the exact ones this page links — one changed byte breaks the check.

What it doesn't

  • It's not a prediction or a promise of profit — nothing can be. Trading carries real risk.
  • The 3-year figures are a simulation of our logic over history, labelled as such — separate from live.
  • Our engine's weighting & logic stay private; full line-by-line reproduction is open to a third-party auditor under NDA.
The three-year figures are a simulated historical replay of the production engine — not live performance. It's Bitcoin — expect some chop, and you set your own stop. Sealed 2026-07-13 via OpenTimestamps. Signals are informational and not financial advice.