Explanation

How Statoblast Trading works

Statoblast Trading is a separate on-chain exchange around Statoblast outcome shares, one of possibly many that can be built on Statoblast. Statoblast core still owns market creation, collateral, migration, resolution, and redemption. The Trading pages call the market contract a “Zoltar SecurityPool” because it is the same contract the rest of this site calls the Statoblast core pool: Statoblast core is the market layer built on the Zoltar protocol, and a SecurityPool is its per-market contract.

From ETH to a directional position

Each ETH entry first creates a complete set: one Yes, one No, and one Invalid share. The pair contains only Yes and No reserves. The router sends the unwanted directional share into the pair, receives more of the selected directional share, and returns the matching Invalid share to the user. Invalid never enters the automated market maker (AMM).

For a binary market, a trader choosing Yes receives a Yes-heavy position plus the Invalid share created with the complete set. The Invalid share remains a separate claim if the market later resolves Invalid.

What the prices mean

Yes and No prices are conditional on valid resolution. They describe the relative price of the two directional outcomes; they are not estimates of invalidity. Interfaces should therefore label the Yes and No values directly and present Invalid separately.

Spot prices come from current reserves and can be manipulated. Protocol contracts never use them as truth or solvency oracles. Settlement uses the SecurityPool's resolved outcome, while solvency-sensitive REP/ETH operations use OpenOracle.

One pair per SecurityPool

Each SecurityPool maps to its own pair. Parent and child pools therefore have separate pairs, reserves, prices, and liquidity-provider tokens; liquidity, like everything else in a fork, is not copied between them.

Liquidity is removed directly from the pair; the router adds exact-amount permits for that path and handles exits and redemptions as share transfers, so the first-party UI never asks you for an allowance. The router reference lists every entrypoint.

Where to go next

Learn by doing: Your first Trading market and your first trade.
Get something done: Set up development, configure the UI, deploy the contracts, seed alternative odds, exit a position, remove liquidity, handle resolution, and handle a fork.
Understand the design: The two-way market, INVALID insurance, conditional pricing, the LP position, early-exit limits, forks and resolution, architecture decisions and limitations.
Look something up: Contracts, router, events, SDK, deployment configuration, invariants, units and rounding, and the security model.