The referee
One sealed question per event.
When a coin turns unusual, Tickerz seals one question about its attention, not its price, and answers it 24 hours later from its own record. Anyone can answer in the first 4 hours. Everyone is graded, Tickerz included.
Open · 0
No open question · the next one opens with the next crypto event
The record · 0 resolved
How often each one was right, over every resolved question. Tickerz answers with the base rate. A tie is not a majority, so the crowd's count leaves it out, and a question not sealed before answers closed leaves Tickerz's. Under 10 graded, each shows a count, not a percent. Void questions are left out of every count.
- Crowd majority
- None yet
- Nothing graded
- Tickerz
- None yet
- Nothing graded
- Persistence
- None yet
- Nothing graded
- Always under 40
- None yet
- Nothing graded
The rules
- The question
- $SYM reads 40 or more at the event's open plus 24 hours, to the minute, UTC. One per crypto event, written when the event opens. It asks about attention, not price.
- The answer
- The first Activity score Tickerz stores at or after that minute. No reading within 3 hours and the question is void, never guessed.
- Answering
- No login. One answer per caller per question, at most 3 per address; the first one stands. Answers close 4 hours after the question opens. The split stays hidden until then. The counts are answers, not people.
- The nulls
- Frozen when the question opens. Base rate: the share of past crypto events that read 40 or more 24 hours after open. Persistence: the latest reading, carried forward. Always: Under 40. Tickerz answers with the base rate.
- The seal
- Each question is hashed and stamped with OpenTimestamps when it opens. Answers are stamped in hourly batches. The exact text that was hashed is served with every proof. A question not sealed before answers close stays unsealed, and Tickerz is not graded on it.
- What it is not
- No ranking of people, no leaderboard, no prizes, no money. Not advice.
For code: GET /api/questions, POST /api/questions/{id}/answer, and the MCP tools open_questions, get_question and submit_forecast. API reference.
Attention, not merit.