Reference

Protocol glossary

Canonical, plain-language definitions for terms used throughout the documentation.

Universe: A Zoltar ledger and identity for universe-specific REP and application state. Universe 0 is the initialized root; later universes are descendants created through forks.
Child universe: A deterministic descendant that represents one valid answer to its parent's fork question. In a binary-market example, a Statoblast fork on its own question creates Invalid, Yes, and No children. If an unrelated fork interrupts that market, its children instead follow the unrelated categorical or scalar fork question's valid answers.
Question: A global Zoltar object that identifies a proposition, its end time, and its eligibility for a fork.
Outcome: One possible answer to a question. Statoblast binary markets use Invalid, Yes, and No.
Invalid: The legitimate third outcome for ambiguous, malformed, or otherwise unanswerable market wording.
REP: Universe-specific reputation tokens used as reporting, dispute, and security capital.
SecurityPool: The Statoblast contract for one question and universe. It holds settlement collateral and coordinates shares, vaults, resolution, migration, and repair.
Settlement collateral: ETH recorded by a SecurityPool to back outstanding outcome-share claims.
Open interest: The amount of settlement collateral backing complete sets that remain outstanding.
Complete set: One matching unit each of Invalid, Yes, and No shares, minted against ETH and redeemable together while the pool is operational.
Outcome share: An ERC-1155 token representing one outcome claim in one universe-specific SecurityPool.
Vault: A SecurityPool account that records a participant's REP backing, capacity ownership, obligations, and fees.
Backing units: Accounting units that represent a proportional claim on REP held for SecurityPool vaults.
Capacity ownership: A vault's proportional ownership of the pool's REP-denominated security capacity and fee eligibility.
Escalation Game: The local Statoblast dispute mechanism in which REP-backed balances accumulate behind Invalid, Yes, and No.
Binding capital: The median of the three outcome balances that determines the Escalation Game's scheduled deadline.
Non-decision threshold: The balance that two outcomes must each reach for the Escalation Game to enter local non-decision.
Reward-eligible cap: One and a half times binding capital. Only the portion of winning Escalation Game deposits up to this cap earns a bonus; deposits beyond it return principal only. See the EscalationGame reference.
Escalation haircut: Two fifths of binding capital, burned at Escalation Game settlement instead of being paid to winners as a bonus.
Fork threshold: The amount of parent-universe REP that a fork initiator supplies and burns to begin a fork, derived by getForkThresholdAttoRep from that universe's theoretical REP supply. See migration accounting.
Migration balance: A parent-universe credit created when REP is burned or committed for a fork. The same credited amount can be minted independently in each valid child, while per-child accounting prevents an account from consuming more than that amount in any one child.
Child REP: REP minted for one child universe. Its ledger and economic value are separate from parent and sibling REP.
Retention: The gradual transfer of outstanding complete-set collateral into a SecurityPool's fee reserve. Because it runs continuously, the ETH backing one complete set falls over time; see protocol fees.
Fork continuation: The state of a child pool whose inherited Escalation Game has not yet been fully resumed. While continuation is pending, the pool rejects new collateralized operations.
Truth Auction: A Statoblast auction that sells child REP to repair a child pool's ETH collateral shortfall. It does not select truth.
OpenOracle: An economically contestable price-reporting contract used by Statoblast for fresh REP/ETH prices, not market outcomes.
Price coordinator: The per-pool contract that requests OpenOracle prices, caches accepted reports, and queues solvency-sensitive SecurityPool operations.