Skip to main content
We hope to never need this page. We wrote it anyway, because the platforms that don’t have one are the ones you should be worried about.

​
Our commitments during an incident

  1. We tell you immediately. A status page at status.predictionarenas.app is updated within minutes of any detected anomaly. We post simultaneously on Twitter and Discord. We do not wait until we have a fix before acknowledging that something is wrong.
  2. We tell you what we know and what we don’t. Early-incident updates will explicitly say which facts are confirmed and which are still under investigation. We will not speculate, but we will not withhold confirmed facts to “protect the narrative” either.
  3. We tell you what user action is required, if any. Most incidents will require no action from players because of the non-custodial design — funds in active rounds remain locked safely in the contract regardless of what is happening to our application layer. If an incident does require user action, we will say so, prominently, in plain language.
  4. We publish a public post-mortem. Within seven days of incident resolution, we publish a detailed post-mortem explaining what happened, why, what we did, what we learned, and what we are changing to prevent recurrence.

​
Pause behavior

The contracts include a narrowly scoped pause capability that can halt the opening of new rounds in a critical incident. This capability:
  • Cannot move user funds. Pausing stops new rounds; it does not redirect, freeze, or seize anything that is already locked.
  • Cannot resolve in-flight rounds. Rounds that are already underway settle normally against the oracle — pause does not change their outcome.
  • Is logged and announced. Any use of pause is publicly announced with a reason and a timeline.
  • Has a documented unpause path. We never leave the platform in a paused state without a stated remediation plan and ETA.
The full pause policy — what triggers it, who can authorize it, how long it can last — is documented in our internal operations runbook and summarized publicly in our launch readiness report.

​
Contact