DocsHow Erocs scores a call
One post, priced and pinned.
What Erocs does
Erocs reads forecasts that public accounts post on X and scores each one against the prediction market price at the moment it was posted. Calling something the market already priced at 80% scores little. Calling something the market priced at 15% scores a lot, if it happens. Every hour the verdicts of that hour, including every post that was read and why it was or was not scored, are fixed on Solana as a Merkle root.
Erocs takes no bets and opens no markets. It is a reading and scoring tool. Market data comes from Kalshi.
From post to score
- Read. Original posts and quote posts from the last 90 days, text only, at most the latest 1,000 per scan. Replies, reposts, images and video are not read. In a quote post only the quoting account's own words count.
- Filter. A keyword filter keeps posts that look like a forecast on something Kalshi lists.
- Read with AI. A model decides call or not a call, under a strict rule: a call is the author's own committed forecast. Probability and rating words ("likely", "favored", race ratings), jokes, conditionals, questions and posts that relay someone else's forecast are not calls. The model id and prompt versions are stored with every verdict.
- Match. Search every Kalshi event that was open in the window, pick the market series that could hold the call, then match exactly one market and side: same subject, same date, same number. If no market fits exactly, the call is marked "no exact market" and is not scored.
- Price. The market probability at the call, from Kalshi's one-minute quotes (below).
- Settle. When Kalshi settles the market, the score is final. Void or cancelled markets are not scored.
Most posts are not scored. Every account page shows posts read, calls found, calls scored and calls not scored by reason. Call or not and the market match are server judgment: every receipt has a report button.
The market probability at the call
The call time is the time inside the post id. X post ids carry milliseconds, so anyone can recompute it from the id alone.
Each minute's value is the midpoint of Kalshi's yes bid and yes ask at the minute's close. A minute counts only when Kalshi sent data for that minute (it sends a minute when the book or a trade changed) and both a bid and an ask exist. Nothing is carried forward.
A= average over the counted minutes of the 60 minutes before the minute holding the call.B= average over the last 5 counted minutes before that minute.C= the highest value for the called side from the minute holding the call to 5 minutes after it. Our X data has no edit history, so every call uses the 60 minutes after it instead, the time X allows for edits.- All three are the called side's probability. The largest is used, because a larger probability always lowers the caller's score.
A post written in the same minute as the news meets the new price in C; news a few minutes earlier shows in B; pushing the price down just before a call moves B and C but not A. When a large account's post moves the market, the call is scored at the moved price.
Not scored: fewer than 10 counted minutes in the hour before the call, an average spread above 10 cents, volume in that hour below 1 contract or open interest at the call below 1,000 contracts. A call's price is final once its C window has ended.
Known limit: if nobody updates a stale quote after news, the old price stays. Use "called after the news" on the call to report it.
The score
Edge points = (100 if the called side happened, else 0) - market probability at the call
A 15% call that hits scores +85; if it misses, -15. An 80% call that hits scores +20; if it misses, -80. If the market priced things well, many calls average out near zero, so a total that stays positive means the account beat the market. Math is done in integers (basis points) and shown with two decimals.
Within one account and one Kalshi event there is one held call. Saying the same thing again is a "repeat" and is not scored. A later call that cannot be right together with the held one is a "flip": the held call is closed at the market price at the flip (score = close minus open, whatever the result) and the new call opens. YES at 15%, then NO when YES is at 40%: the YES call closes at +25 and the NO call opens at 60%. Calling both sides cannot lock in a score. Hit rate counts only calls held to settlement.
Fixed on Solana every hour
When each UTC hour ends, every verdict written or changed in that hour becomes a leaf, including calls that are still open. The Erocs program records the hour's Merkle root, the leaf count, the scored count and the hash of the rules in force. Hour numbers only go up, only finished hours are accepted, and a posted root cannot be overwritten. Hours with no leaves post a zero-leaf root. A root posted more than an hour after its hour ended shows as "late"; an hour with no root is a blank.
Leaf hash = SHA-256(0x00 || canonical JSON of the leaf). Node hash = SHA-256(0x01 || left || right). Leaves are sorted by leaf id; an odd node is carried up. An hour with no leaves has the root of 32 zero bytes. Leaf files are public at /data/leaves/<YYYY-MM-DD>/<HH>.json.
Every call found is published, even if the post is gone before the root. Once a posted root holds a call, the call and its score stay if the post disappears (deleted, account suspended or private), shown as "Post unavailable". Leaves hold a salted hash of the text; the text itself is kept encrypted in a separate store and opened only for report reviews, the author's own request, a legal request or a rule-version re-read, with every opening logged.
A post deleted before Erocs read it cannot be seen, so each leaf records how the call was found: "tracked" (within an hour of the post, while the account was being read), "late-found" (later, for example by the daily timeline check) or "backfilled" (when its last 90 days were first read). A tracked call whose market settled before any posted root held it is marked "settled before pin" and left out of totals.
Check it yourself
- /verify: your browser rebuilds any hour's root from the leaf file and compares it with the value on chain. For any call it recomputes the call time from the post id, and the probability and score from our mirror of the exact Kalshi response, whose SHA-256 is in the leaf (marked "mirrored data", because Kalshi does not answer browser requests from other sites).
- Without our server:
node verify-erocs.mjs call <post_id> <leaf file>fetches the same minute data straight from Kalshi (GET /series/{series}/markets/{ticker}/candlesticks?period_interval=1&include_latest_before_start=true, or/historical/markets/{ticker}/candlesticksfor older markets), checks it hashes to the leaf's mirror, and recomputes the score.node verify-erocs.mjs hour <leaf file> <rpc> <signature>rebuilds the root and reads it from the transaction on chain.
$ERCS
Scoring and every public page work without the token, and anyone signed in with a wallet watches 3 accounts free. The token raises limits: holders lock $ERCS in the Erocs program and the locked share of supply sets their tier. Each deposit counts after 24 hours; a withdrawal request stops counting at once and pays out after 3 days.
| Locked share of supply | Accounts you can watch | Lookups per day | Alerts |
|---|---|---|---|
| 0.01% | 10 | 10 | within 15 minutes |
| 0.05% | 50 | 30 | within 5 minutes |
| 0.2% | 200 | 100 | within 5 minutes, read-only API |
The same limits can be bought without the token in USDC, per month: Basic $3 (first tier), Watch $9 (second tier), Pro $49 (third tier). Buying the same plan again extends it from its current end; different plans run separately and the higher one applies.
Any address can be checked at /holders?address=: its lock deposits, tier and limits, recomputed in your browser from the chain. The token pays nothing out; locking only changes limits.
Supply and allocation are published here at launch.
Public API
GET /api/health: data sources, last hourly root, queue length, RPC latency.GET /api/board?area=all|economy|politics|sports|crypto&sort=total|avg&view=all|tracked: area views exist when 3 accounts qualify in the area.GET /api/accounts/{handle}: an account's record and every call.GET /api/calls/{post_id}: a call receipt with its leaves and Merkle proofs.GET /api/hours: hourly roots, when each was posted, and whether it was late or missed.GET /api/rules: the rules text and versions.
Read-only API key
The third lock tier and the Pro plan include a key that reads your own wallet's data. Make it in the app under Limits; it is shown once and Erocs keeps only its hash. Send it as Authorization: Bearer <key>, up to 60 requests a minute. A key cannot change anything. It pauses while the wallet has neither the tier nor the plan, and a new key replaces the old one.
GET /api/v1/me: the wallet, its limits and how many accounts it watches.GET /api/v1/watch: the accounts it watches, each with its record.GET /api/v1/inbox?after=<id>&limit=<1-200>: new calls from those accounts, oldest first after the given inbox id; passnext_afterback to read on.
What Erocs does not do
- No trade buttons, no exchange links with referral codes, no copy trading. Alerts are information.
- No accounts under 10,000 followers unless the owner adds them, and no private accounts.
- Not affiliated with any account or market shown. Not investment advice.