Start here
Contract architecture
Users call SecurityPools, the Statoblast contracts that expose each market's shares and reporting. Each question belongs to a portfolio, which holds cash in its central settlement engine. Pools rely on Zoltar for universes and REP, on a price coordinator for REP/ETH prices, and on the SecurityPoolForker after a fork.
Related reading: the generated transaction reference for exact caller and prerequisite rules, How Statoblast works for lifecycle context, and the invariant catalog for cross-contract safety properties.
Product layers
Zoltar — questions, universes, REP, forks
Statoblast core — pools, collateral, shares, resolution, migration
Trading — one implementation of swaps and liquidity around shares
OpenOracle — contestable REP/ETH prices
augurScan and bots — indexing, evidence, and permissionless operations
What each contract owns
ZoltarQuestionDatastores questions;Zoltarmanages universes, forks and universe-specific REP.SecurityPoolPortfolioregisters admitted questions and coordinates shared operations. A fixed single-question portfolio uses this same architecture.- The capital ledger records each owner's REP principal, commitment, health target and earned income. Its commitment index supports bounded health and retirement operations.
- The settlement engine and book track question demand, ETH, fee streams, minimum backing floors and recovery assets.
- A
SecurityPoolis a question adapter. ItsShareTokenrecords outcome balances across that question's universe lineage; itsEscalationGameresolves reports. Reporter REP has separate custody. - The shared OpenOracle feed accepts independently funded price candidates. Question price coordinators adapt that shared evidence.
- The portfolio fork coordinator records branch choices and prepares shared branch accounting. The uniform auction sells freshly unchosen provider REP for ETH when a branch needs repair.
Purchase and resolution
A trader purchases complete sets through the portfolio. Admission, fresh price, healthy capacity, fees and the question's backing floor are checked atomically. The question adapter mints distinct outcome shares. After final resolution, winning claims redeem against their question's settlement accounting. Returning complete sets earlier reduces demand and can free commitment for retirement.
Fork boundaries
Owners choose once per portfolio and universe. Shared roots and branch balances avoid a migration transaction per owner per question. A question adapter and reporter continuation are materialized only when used. Token holders still migrate their own claims through each intervening universe. Reporter checkpoint preparation is bounded per transaction and reusable by descendants.
See the fork lifecycle, uniform auctions, and the contract inventory for module interfaces and limits.