How Calls records, settles and proves market predictions
Calls is a public scoreboard for market calls. This page explains every rule that decides a result, and how anyone can check a record without trusting us. As of today the ledger holds 151 calls, 124 of them settled, sealed into 41 daily digests since 2026-09-25.
1. What a call is
- A ticker, a direction (up or down), a horizon from 1 hour to 90 days, and up to 280 characters of text.
- The live price at the moment of posting is recorded as the entry price. A post without a ticker and direction is plain text and is never scored.
- Calls are permanent. Neither the author nor the operator can edit, withdraw or backdate one.
2. How a call is timestamped
- Each call is hashed (SHA-256) over its handle, text, ticker, direction, entry price, deadline and creation time.
- At the end of each UTC day, every call from that day is folded into a Merkle tree. Its root, chained to the previous day's digest, is the daily digest.
- The digest is timestamped into the Bitcoin blockchain with OpenTimestamps. Once a Bitcoin block confirms it, nobody, including Calls, can change what was called or when without the proof failing.
3. How a call settles
- A call settles against the official closing price of the first completed trading day on or after its deadline, never an intraday print.
- Two independent price sources are cross-checked. If they disagree beyond a small tolerance, or one has not published, the call is held, not guessed.
- Up wins if the close is above the entry price, down wins if it is below. An unchanged close is void and does not count either way.
- Each settlement is appended to a hash-linked chain, so a result cannot be quietly rewritten later. The chain is public at /api/chain.
4. Why a hit rate needs a sample
A hit rate is shown only from 10 settled calls, and every profile says how often a fair coin would have done at least as well. The table shows how many wins it takes to beat a coin at the usual 5% significance level (one-sided binomial test).
| Settled calls | Wins needed | Hit rate needed |
|---|---|---|
| 10 | 9 | 90% |
| 20 | 15 | 75% |
| 30 | 20 | 67% |
| 50 | 32 | 64% |
| 100 | 59 | 59% |
| 200 | 113 | 56% |
A short record can look brilliant by chance. This is why Calls never ranks anyone below 10 settled calls, and why the benchmarks below exist.
5. The benchmarks
- @coinflip picks one of SPY, QQQ, AAPL, MSFT or NVDA and calls it up or down at random. It is the score a forecaster with no skill would get.
- @alwaysup calls SPY up every time. In a rising market it is hard to beat, which is the point.
- Both are labelled BOT everywhere, are listed where their record puts them, and are never ranked or counted as people.
6. How to verify a call yourself
- Open the call's receipt page (
/call/{id}) and its Merkle proof at/api/proof/{id}. - Recompute the post hash from the fields shown and check that it matches
leaf. - Fold the proof path into the leaf and check that the result equals
merkle_root. - Download the day's OpenTimestamps file from
/api/anchor/{date}/otsand runots verifyagainst the digest. It reports the Bitcoin block that proves the digest existed at that time.
The verification code is open in the repository (anchor.ts, verify.ts). 41 of 41 daily digests are confirmed in Bitcoin so far; the newest ones confirm within a few hours.
7. What Calls does not claim
- A record proves what someone called and how it turned out. It does not prove they traded it, and past accuracy does not predict future results.
- Hit rate ignores size of move. A caller who is right on small moves and wrong on big ones can score well and still lose money.
- Calls is not investment advice and is not a broker. Nothing here is a recommendation.
8. Citing Calls
Records, the ledger and the daily digests are open. Researchers and journalists can use the open dataset (CC BY 4.0). Suggested citation: Calls (calls.tech), Bitcoin-timestamped market call ledger, accessed 2026-11-22.