Method

Version 24 Oct 2026 · changes are dated on the changelog

What gets on the record

• Only statements an educator published, publicly and dated, on their own channel. No paid or private posts, no third-party paraphrases, no inferred deadlines.
• Every call is stored with the exact quote, a link to the original post, an archived copy (web.archive.org or archive.ph), and the time it was published, with its timezone.
• Each call names one asset, one comparison (>, ≥, <, ≤) and one price in USD, and an explicit window.

Admitted before the window opens, then frozen

• A call is admitted only before its window opens. A call whose window had already opened is refused (“admitted after its window opened”) — past calls are never back-filled into the record.
• Once admitted, nothing about the call changes: not the quote, the source, the window or the rule. Its history is append-only.

Two kinds of call, kept apart

• Endpoint — “the price is above X at time T”. Resolved from CoinGecko’s USD price history: the sample nearest T, and only one within 60 minutes of it. Ties follow the stated comparison.
• Target-touch — “the price reaches X within the window”. Recorded, but unscored: sampled prices cannot prove every price in between, so a touch call is never rewritten into an endpoint to fit the data.
• A call is resolved only 6 hours after its window closes. If the source stops publishing before close, the question is void and unscored. Missing data is void, never a loss.

Numbers, never intent

• The record says what was published and what the price source showed. It does not characterise anyone.
• No rank, no score and no rate is shown for an educator with fewer than 10 resolved endpoint calls — the page says “not enough calls (n < 10)” instead.
• No payments from the people on the record, no prizes, no copy-trade and no affiliate links.

Right of reply and corrections

• Anyone on the record — or anyone who sees a mistake — can use the right of reply. Every message is answered within 7 days.
• A correction never rewrites history silently: it is added to the call’s history and dated on the changelog.