Glossary
The Mentat vocabulary.
Every term you need to read the docs, the schema, and the rest of this site — defined plainly and accurately.
- zkTLS
- A zero-knowledge proof that a TLS session actually happened against a specific domain and returned specific bytes, at a specific time. In Mentat, a TLSNotary-style proof of a canonical source is verified on-chain to settle a market — the proof is the data, not a vote about the data.
- Resolution criteria
- The precise, checkable statement of how a market settles: which source, which value, which timestamp, and what counts as YES/NO. The Draft agent writes it and the Validator agent rejects criteria a source cannot attest to.
- Curator
- A human reviewer who approves, edits, or rejects AI-drafted markets in the Curator Console before anything deploys on-chain. Curators earn reputation and a Treasury-funded stipend.
- Curator Console
- The Vue 3 + FastAPI review surface with diff view, validation scores, bulk approve/reject, and version history. It treats AI output as a draft, never a verdict.
- MarketFactory
- The Solana Anchor program that deploys an approved market spec on-chain, storing a BLAKE2 hash of the AI rationale for auditability.
- MarketSettlement
- The Solana Anchor program that verifies a zkTLS proof and triggers payout when a market resolves.
- DSPy
- The framework the Scout/Draft/Validator agents are written in. Because they are DSPy programs, the underlying model is a config switch — OpenAI, Anthropic, or a local vLLM endpoint.
- Scout / Draft / Validator
- The three-stage AI pipeline. Scout gathers context and sources, Draft writes the formal spec, Validator re-checks it against a rubric and loops back until it passes.
- Source allowlist
- The explicit list of canonical endpoints a market may resolve against (e.g. api.coingecko.com, an official results API). A market can only settle from a source on its allowlist.
- Trigger condition
- The machine-checkable rule that flips a market to YES — for example, price >= 100000 at a named timestamp read from a named source.
- Invalidation clause
- The condition under which a market resolves INVALID (e.g. the source is unreachable for the full grace window), refunding traders rather than forcing a wrong answer.
- Proof submitter
- Anyone who produces a valid zkTLS proof of a resolved market. The fastest valid submission earns a bounty funded by the settlement fee, decaying with latency.
- Creator stake
- The escrow a market creator deposits (default 50 USDC). Refunded on clean resolution, slashed for ambiguous/invalid markets or policy violations.
- Dispute window
- The period after on-chain settlement in which a challenger can post a bond and submit a counter-proof or evidence the trigger was misread. The clean case resolves without ceremony.
- Rust indexer
- A Rust event indexer (rkyv + sled) that tails Solana program logs and serves fast reads to the discovery hub and trading UI over WebSocket.
- Canonical market schema
- The single standard every market conforms to — question, resolution criteria, source list, trigger, invalidation, economics, state machine — so indexers, UIs, and integrations all speak one format.
See these in context: how it works · tokenomics · FAQ