Verify
Don't trust our track record. Check it.
Signal services can quietly delete losing calls or add winners after the fact. Vantum can't. Minutes after each batch of signals is created, its fingerprint is timestamped in the Bitcoin blockchain through OpenTimestamps, an open, free protocol we don't control. That proves each signal existed, unchanged, before its trade played out.
How it works
Each signal becomes one line in a ledger file: its id and the SHA-256 hash of its exact contents (ticker, rule, side, price, summary and time). The file's own SHA-256 is what gets timestamped. Change, add or remove a single signal and the hash no longer matches the timestamp.
Signal contents become public 24 hours after they fire, so you can recompute every line yourself once that delay has passed.
Verify a ledger entry
With Python and the official OpenTimestamps client:
pip install opentimestamps-client curl -o ledger.txt https://vantum.cc/api/ledger/<id> curl -o ledger.txt.ots https://vantum.cc/api/ledger/<id>/ots ots upgrade ledger.txt.ots # fetches the Bitcoin attestation (a few hours after stamping) ots verify ledger.txt.ots # prints the Bitcoin block time the file existed by
To check the lines inside the file, fetch /api/ledger/<id>/leaves: each leaf is a JSON string whose SHA-256 must equal the hash on that signal's line, and its contents must match the public signal.
AI agents and scripts can list everything at /api/ledger.
Latest entries
| Entry | Created | Signals | Root (SHA-256) | Proof |
|---|---|---|---|---|
| #24 | Nov 8, 2026 · 00:00 UTC | 2 | 1d0e61cef407c0a4… | .ots |
| #23 | Nov 7, 2026 · 00:00 UTC | 1 | 7bc1c0b05a5f321a… | .ots |
| #22 | Nov 6, 2026 · 00:00 UTC | 1 | 08cd356f5e667bb5… | .ots |
| #21 | Nov 5, 2026 · 00:00 UTC | 4 | 12484218a553979c… | .ots |
| #20 | Nov 4, 2026 · 00:00 UTC | 2 | 49a4b8b57780cf6d… | .ots |
| #19 | Nov 3, 2026 · 00:00 UTC | 1 | 2e6d161afb8d7711… | .ots |
| #18 | Nov 2, 2026 · 00:00 UTC | 1 | bd8908904b4b91e2… | .ots |
| #17 | Nov 1, 2026 · 00:00 UTC | 1 | 9f79d848214dbb2f… | .ots |
| #16 | Oct 31, 2026 · 01:30 UTC | 7 | c8ba6499492f22f7… | .ots |
| #15 | Oct 31, 2026 · 00:15 UTC | 1 | 3fbf7c8f0577da06… | .ots |
| #14 | Oct 31, 2026 · 00:00 UTC | 13 | 1f6faad40fd7a5bd… | .ots |
| #13 | Oct 30, 2026 · 01:45 UTC | 1 | b45ca926b0aff764… | .ots |
| #12 | Oct 29, 2026 · 01:45 UTC | 2 | c47bf6334b99f03d… | .ots |
| #11 | Oct 28, 2026 · 00:00 UTC | 1 | 8cc9651ff4747d03… | .ots |
| #10 | Oct 27, 2026 · 01:45 UTC | 1 | 155ebd41083b2c43… | .ots |
| #9 | Oct 27, 2026 · 00:00 UTC | 2 | 85b6fdc29f7a853d… | .ots |
| #8 | Oct 26, 2026 · 00:00 UTC | 2 | 77a4e7366c93e611… | .ots |
| #7 | Oct 25, 2026 · 00:00 UTC | 2 | c2f081092e5a2894… | .ots |
| #6 | Oct 24, 2026 · 01:30 UTC | 1 | 55f2d6b36153089b… | .ots |
| #5 | Oct 24, 2026 · 00:00 UTC | 1 | 2da080b6fb5f8828… | .ots |
| #4 | Oct 23, 2026 · 01:30 UTC | 1 | ef720efc51eca392… | .ots |
| #3 | Oct 20, 2026 · 01:45 UTC | 1 | 130be42ad83ff7a8… | .ots |
| #2 | Oct 19, 2026 · 00:00 UTC | 5 | b7a098015f876101… | .ots |
| #1 | Oct 18, 2026 · 00:00 UTC | 8 | 76e6ea5c01907192… | .ots |
The ledger proves when each signal was published and that it wasn't changed. It doesn't prove that a strategy will work; see the track record for results.