Docs · MoveReady

Event model

An event has an issuer, source and target networks, the official origins it may cite, and a list of facts. Each fact carries the URL and section it came from, a short paraphrase, when we fetched it, who reviewed it and a digest. A token is always network + address + provenance — never just a symbol.

Rules are fixed predicates over the holding types you declare: which types they apply to, what they ask, whether it is a condition, when it is due and how precise that due date is. No scripts, no model-written rules.

States

Facts move independently: announced, approved_by_source, snapshot_details_pending / published, claim_announced, claim_access_observed, paused, cancelled, conflicting. A team saying a vote passed is approved_by_source — not an on-chain verification. A reachable portal page is not a working claim.

Checklist items are not_reviewed, user_marked_reviewed, waiting_official_details, needs_attention, not_applicable_by_rule, source_conflict or review_needed_for_new_revision. There is no “eligible” state, and there never will be one from a declaration.

Dates & precision

Every date has a precision: day, minute, block height or unknown. A day without a time is shown as a calendar day with “exact time not announced” and gets no seconds countdown. A block-height deadline is never turned into a guaranteed hour; an estimated day is labelled as an estimate. Exact timestamps keep their original timezone next to UTC.

Revisions

Rule packs go draft → reviewed → published → superseded or withdrawn. The editor of a change cannot review it. Publishing needs the exact revision hash. When a rule changes, every personal item that depends on it becomes review_needed_for_new_revision; your old mark stays attached to the old revision. A new date never rewrites history or already-sent reminders.

Conflicting official sources are not resolved by whichever page is newer. Affected guidance stays pending or conflicting until a reviewer decides.

API

GET/v1/eventsTracked events and their current revision.GET/v1/events/{id}/revisions/{rev}A frozen revision: facts, rules, sources.GET/v1/sourcesRegistry with check status and digests.POST/v1/declarationsYour holding types (auth, CSRF, idempotency key).POST/v1/marksMark an item for a given rule revision.POST/v1/remindersUp to 3 per event; stable logical IDs.GET/v1/exports/{id}Your JSON or Markdown export, on request only.

There is no /claim, no /sign and no RPC relay — on purpose.

GET /v1/events/zeta-solana-2026/revisions/3 { "event": "zeta-solana-2026", "revision": 3, "hash": "r3·0b6f…d215", "planned": { "day": "2026-12-09", "precision": "day", "time": null }, "snapshot": { "block_height": 20755000, "estimate_day": "2026-12-09" }, "target": { "network": "solana", "mint": null, "program": null, "mint_status": "pending" }, "rules": [ { "id": "R-08", "rev": 3, "applies_to": ["pool"], "status": "confirmed_from_source", "due": { "block_height": 20755000, "precision": "block_height" }, "source": { "url": "https://www.zetachain.com/blog/zeta-moves-to-solana-dec-9", "fetched_at": "2026-11-08T06:00:04Z" } } ] }

Embed

Support desks drop the board into their help center and get a webhook on every published revision. The embed shows public facts and rules only — never anyone's checklist.

Privacy

Declarations and notes are yours and deleted on request. Public pages never show personal notes or addresses. Deleting your account cancels every future reminder. After an outage you get one summary with the current revision, not a burst of stale reminders.

$MOVEREADY

Holder checklists are free. Support-desk plans are $149 a month, or $112 when paid in $MOVEREADY; half of every token payment is burned. Holding $MOVEREADY never changes what a checklist says.

How the board works