Market Readiness Checklist

Use this checklist before announcing a public futarchy market.

Proposal

• [ ] Proposal title is clear.
• [ ] YES and NO outcomes are mutually exclusive.
• [ ] Resolution source is public and durable.
• [ ] Resolution timing is specified.
• [ ] Proposal text avoids hidden side conditions.

Assets

• [ ] Project token address is verified.
• [ ] Currency token address is verified.
• [ ] Chain is specified.
• [ ] Conditional token wrappers are visible to users or indexers.
• [ ] Pool addresses are discoverable.

Market parameters

• [ ] Trading window is specified.
• [ ] TWAP window is specified.
• [ ] Threshold rule is specified.
• [ ] Liquidity amount and source are stated.
• [ ] Oracle and arbitration path are stated.

User protection

• [ ] Risk language explains conditional assets.
• [ ] UI explains that losing-side assets redeem for zero.
• [ ] Slippage settings are visible.
• [ ] Settlement path is documented.
• [ ] Users can verify contracts from public sources.

Operations

• [ ] Public status page or incident channel exists.
• [ ] Indexer/API health is checked.
• [ ] Market appears in the public UI.
• [ ] A dry-run of split, trade, merge, and redeem paths has been completed on the target chain or a fork.

This checklist is public by design. Internal signer procedures and private service credentials belong in private operational runbooks, not here.