Terms of use

The terms under which you use this deployment of axmc: the sites at axmc.xyz, app.axmc.xyz and docs.axmc.xyz, the API at api.axmc.xyz, and the programs the app talks to on Solana. Plain language, because the protocol's rules are the interesting part and they are in the spec and the economics; these terms only say what the people running the sites promise and what they do not.

Last revised 12 October 2026. The operator of this deployment is named on the contact page. This is not legal advice, and a deployment serving real value should have these terms reviewed by counsel in its own jurisdiction before launch.

What this is

axmc is an optimistic oracle and escalation court: a set of programs on Solana that let a prediction market ask a question, let anyone answer it against a bond, let anyone challenge that answer against a bond, and settle disputes through sampled panels and an appeal, with a capped assembly to hear corrections. The app is a way to use those programs from a browser; the API is a way to read their history. Neither is the protocol. The protocol is the programs, and they are what settles what.

This deployment runs on devnet until the operator says otherwise on the front door. Devnet tokens have no value, devnet state may be reset, and nothing here is an offer of anything.

Who may use it

Anyone, subject to the law where you are. A market creator is approved by an operator before the app opens for them; a curator needs no one's approval. You are responsible for knowing whether prediction markets, staking and bonded dispute resolution are lawful for you, and for any tax that follows from what you earn.

You may not use the sites or the API to attack them or anyone else, to post evidence you have no right to post, or to register webhooks pointing at systems that are not yours.

Bonds, stakes and slashing are the product

Every position in the protocol puts something at risk, by design: a proposer's bond, a disputer's bond, a verifier's stake, an appellant's bond, a council member's bond, a petitioner's bond. The rules for when they are lost are in the programs and summarised in Participating. When a bond or a stake is slashed by the rules, it is gone, and no one running these sites can return it. The programs are what decides; the sites only show what they decided.

A juror's reveal secret lives in the browser that committed the ballot. Lose the browser before revealing and the ballot cannot be revealed, which the protocol treats as not revealing. The app says so where you commit.

What the operator does and does not do

The operator keeps the parameters, vets venues during the guarded launch, runs the crank and the services, and answers the contact form. They do not custody your funds, cannot reverse a transaction, cannot change an answer once the programs have settled it, and cannot move a venue's balance once the venue's own vault holds it.

The operator may approve or decline a venue's registration for any reason, withdraw access from one later, pause the programs, and change the parameters within the ranges the programs allow. Changes that matter are announced in the docs and, after the governance handover, decided by the multisig described in Governance.

No warranty

The sites, the API and the programs are provided as they are. The code has been reviewed internally, not yet by an outside auditor, and what it does not defend against is in Threat model; that is a statement of what was looked at, not a promise that nothing was missed. The services may be down, the chain may be congested, an RPC provider may rate-limit you, and the operator may be asleep. Nothing here is a guarantee of availability, accuracy or fitness for any purpose.

Limitation of liability

To the fullest extent the law allows, the people and entities operating this deployment are not liable to you for any loss arising from your use of it: not a slashed bond, not a missed deadline, not a wrong answer that the protocol upheld, not downtime, not a bug. Where the law does not allow that exclusion, liability is limited to the amount you paid the operator, which is nothing.

Your content

Evidence you post, messages you send and registrations you file are yours. By posting them you give the operator the right to store and show them for the purposes the protocol and these sites exist for. You confirm you have the right to post what you post.

Privacy

What is kept, and for how long, is in the privacy policy.

Changes and the rest

These terms are in the repository and every change is a commit; the date at the top is the last one. Using the sites after a change is accepting it. If any part of these terms cannot be enforced, the rest still stands. Questions go to the contact page.

Source: docs/TERMS.md in the axmc repo. Edit the file; the next deploy rebuilds this page.