Market Composition#

Seesaw's Solana program is intentionally binary. A market has one canonical YES order book, complementary YES/NO share mints, and a single terminal outcome byte. That shape is what keeps pair-mint solvency, complementary-only matching, and settlement proofs tractable.

Product Rule#

Do not retrofit native multi-outcome or range markets into the on-chain program for launch. Multi-outcome, threshold, and range experiences should be composed at the product layer from independent binary markets.

Examples:

• "Will SOL close above 200?" is one binary market.
• "Will SOL close above 220?" is a second binary market on the same feed and cadence.
• A range experience such as "SOL closes 200-220" can be displayed as a ladder of adjacent binary thresholds, with UI copy explaining that each leg is an independent market.

This works with the current PDA design because market identity already includes the feed id, duration, epoch id, and creator. Parallel binary markets on the same feed/cadence are native; no account layout or settlement rule changes are required.

Why Not Native Multi-Outcome#

Native multi-outcome markets would touch the core safety surface:

• pair-mint solvency would become N-outcome liability accounting;
• the single canonical YES book would become multiple books or a different matching model;
• complementary-only matching would no longer describe every fill;
• settlement and redemption would need new invariant families;
• the Kani, fuzz, and integration proof corpus would need a broad rewrite.

That is not a launch optimization. It is a separate protocol design.

Manual Resolution Boundary#

Custom/manual-resolution markets are not an oracle extension. They are a different trust model because some human, committee, or external resolver would decide the outcome instead of a pinned Pyth price rule. Treat manual resolution as a separate product and governance decision, not as part of the Pyth oracle roadmap.

Launch Signal#

Use binary ladders as the demand signal. If users consistently trade a family of threshold markets on the same feed/cadence, product can decide whether the UX needs a better grouped presentation. That evidence should come before any proposal to expand the on-chain outcome model.